Be able to re-use windows/splits by plugins

Abierto
#370 4 comentarios 0 reacciones 1 asignado Ver en GitHub

@EduardMe ya está trabajando en esto.

Desde el 2/12/2022.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

API E-2 enhancement P-7

We can ask for new windows or split-view panels to be shown from API calls.
But as we use these more, we need some other controls as well. Particularly, to reuse existing splits/windows if open when opening a new split or window. This will stop many windows piling up when calling the same commands in quick succession.

I can think of various potential solutions, but as I don't know the relative complexity of these, I'll restrict myself to giving some more detailed use cases.

SearchExtensions' /quickSearch and /searchOver* commands

These commands open a new split window as a convenience when they run. When you run the command again (or via the psuedo-button at the top of the note), another split window is created, even when there's an existing split showing the same note.
I want a way to say "show note in new split, unless that note is already open in a window, in which case just give it focus".

Reviews' /project lists command

This opens an HTML window. If it's run again, it re-uses the same window -- this is what I want in the first use case above.
But it's easier here, as there's a limit of just 1 HTML window at a time.
When that limit is removed, this also needs a way to say 'reuse'.

NoteHelpers' /open current note new split

To make things slightly harder, this command shows the need to be able to deliberately open a second split view of the same note as is already open in the Editor.

Lenguaje dominante
JavaScript
Estrellas
204
Forks
82
Merge medio
22 h 27 min
PR fusionados (30 d)
3

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NotePlan/plugins

Todos los issues de NotePlan/plugins

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.