Feature request: allow plugin panels to be detached into their own window

Problem / motivation

Notes can be opened in a separate window by double-clicking them, which is great for multitasking. Plugin panels (the views created via joplin.views.panels) don't have this option β€” they're locked into the sidebar/docked area of the main window.

For panel-heavy plugins (dashboards, task boards, kanban views, custom editors, etc.) this is limiting. The panel competes for space with the note list and editor, and it can't be moved to a second monitor or kept visible while working in a different note.

Proposed solution

Add a "Detach into its own window" option for plugin panels, mirroring the existing detached-note-window behaviour:

  • A way for the user to pop a panel out into a standalone OS window (e.g. a context-menu item on the panel, or a window control), and dock it back.
  • Optionally, an API flag/method so plugins can declare a panel as detachable and/or request detaching programmatically, e.g. joplin.views.panels.setDetachable(handle, true) or a detach() call.
  • The detached window should keep the panel's webview state and continue receiving the normal message/update lifecycle.

Alternatives considered

  • Rendering the panel in the sidebar only β€” works, but can't be moved to a second monitor or kept open independently of the main layout.
  • Opening a plugin dialog as a stand-in for a window β€” dialogs are modal/transient and not a substitute for a persistent, resizable, independent window.

Additional context

Desktop already supports detached note windows, so much of the windowing infrastructure presumably exists; this request is to extend that capability to plugin panel views.

3 Likes