Skip to content

Option to open windows in 'standalone' mode #3543

Open

Description

@rjwills28

Currently Phoebus supports opening new screens (BOB files) in new windows. These new windows are tied to the main window in that they adopt the same settings, i.e. display tabs, display toolbar.

At Diamond, a lot of our CS-Studio screens make use of the CS-Studio standalone mode where screens display in a separate windows with no other features other than a title bar with the minimize, maximize and close button, e.g.:
Image

It would be very useful if we could replicate this same sort of look in Phoebus.

I can see from the code that the 'standalone' target is still available on an ActionButton and that there are some deprecated method stubs that simply open the screen as a new window. For example see OpenDisplayAction and ToolkitRepresentaton. Presumably this is just there at the moment to support OPI->BOB conversions that reference 'standalone'.

I have had a quick play myself at leveraging these existing methods and implementing a way of opening standalone windows, which basically involves ensuring the toolbar and tabs do not show and that they also are not displayed when enabled from the main window options.

To minimize impact on other users we would suggest introducing some Phoebus preferences that enable the use of this standalone window mode and otherwise ignores it and maintains the current behaviour of just opening as a new window with a toolbar and tabs configured as standard.

We wanted to gauge whether the community would be open to having this additional feature if we were to spend some time properly developing the standalone window implementation?

Activity

  1. rjwills28 commented on Oct 29, 2025

    @rjwills28
    ContributorAuthor

    This was discussed in a CSS collaboration meeting and people seemed open to the idea of implementing support for standalone windows as long as it did not compromise the current Phoebus behavior.

    I have come up with an implementation for the standalone window model which:

    • Defines a standalone window as one that dos not display the toolbar or tabs. Toggling these on/off from the Phoebus main menu has no affect on a standalone window.
    • Allows you to open displays from an action as a standalone window, including this option in the editor interface.
    • Load standalone windows from mementos.
    • Open displays in the standalone window mode from the console.

    In addition, it does not make sense to have other applications open in the same active window as the standalone window as we have removed the tabs. To replicate CS-Studio behavior we suggest that when right-clicking and opening another app from a standalone window (e.g. the data browser, probe etc), this opens the app in the 'main' Phoebus window and not the last active one.
    This has been discussed in #3598. In our implementation, any app launched from a standalone window will open in the main Phoebus browser. We have also added a preference which would allow users to configure Phoebus to open any app launched from a 'regular' detached/tabbed display in the main window as well, with the default behavior left as is.

    This implementation is available in the branch: https://github.com/rjwills28/phoebus/tree/standalone_windows with the 'compare' here.

    We would very much appreciate any feedback on this implementation so that we can move it forward and get this feature merged.

  2. epicDirk commented on Mar 4, 2026

    @epicDirk

    We have the same problem at ESS Lund.

    Our operators use "New Window" (popup) to show detail views for equipment from the overview displays. The problem is that from inside a popup there is no possibility to navigate back to the main Phoebus window:

    Replace changes the content inside the popup (and does not resize the popup automatically)
    New Tab opens a new tab inside the popup
    New Window opens another popup window on top
    During shifts this creates many open windows and the operators lose the overview which window is which. Especially in stressful situations this is a real problem.

    What we would like to have: An option on the "Open Display" action (for example a checkbox "Open in main window") so that a button inside a popup can open a .bob file in the main Phoebus window instead of the popup. This way display designers can build popup detail views where the navigation goes back to the main window.

  3. emilioheredia-source commented on Nov 12, 2026

    @emilioheredia-source

    At CLS we're now looking into this for our operators. Many of them come from EDM and are used to many small, separate windows, and I think the main thing that holds them back from Phoebus is that it feels like one big application. We found that the standalone window mode from #3859 already covers a good part of what they need, so thank you very much for that. We'd like to contribute and propose a few additions. Before writing any code, could you please let us know which of them you'd accept, so that they fit with what you built?

    We tested it with real CLS EDM screens, converted with the Phoebus EDM converter and opened with ?target=standalone. The window is sized to the screen, with no toolbar or tabs, which I think is very close to EDM.

    1. A display opened in a new tab hides the current one (bug)

    In a standalone window, an action that opens a display in a new tab, or a Ctrl-click, adds the tab to the same standalone window. Its tab bar is always hidden, so the new display covers the old one and you can't switch back. The window also keeps its size. This happens on every related display of a converted EDM screen, because the converter turns them into new-tab actions.

    Before and after clicking "Details", with two small test displays (our converted screens behave the same way):

    before
    after

    I see two ways to fix it, and either is fine with us:

    • a. Open the display in the main window. That's what applications started from a standalone window already do, since a standalone window has no tabs.
    • b. Let standalone windows follow the existing "Always Show Tabs" off rule: no tab bar with one tab, and a tab bar with two or more.

    Which one would you prefer?

    2. EDM converter: related displays as standalone windows

    EDM opens a related display in a new window, or replaces the current one when "close display" is set. The converter currently maps the new-window case to a new tab. We'd add a converter preference that maps it to "New Window (undecorated)" instead. The default stays as it is, and only the converter changes, not the runtime.

    3. Back and Forward from the keyboard and the mouse

    When the toolbar is hidden, the context menu already offers Back and Forward, and Alt+Left / Alt+Right are already handled. But in a standalone window the keys often do nothing: they only work while a widget of the display has the keyboard focus, and there is no toolbar to hold it, so a display without buttons, or one that just replaced the previous display, doesn't react. We'd fix that, and add the mouse back/forward buttons, in all display windows, not just standalone ones.

    4. Switching a window between standalone and normal (opt-in)

    Operators sometimes want the full interface back on one screen, for example the toolbar to zoom or navigate. We'd add an action that turns a window between the two kinds that already exist, "New Window" and "New Window (undecorated)". It would be available from the context menu, from a keyboard shortcut, and next to "Always Show Tabs" / "Show Toolbar" in the main window. I understand you removed "Show toolbar" from standalone windows on purpose, so this would be off unless a preference enables it, and standalone windows at Diamond would stay as they are.

    Later, once JavaFX finalizes it

    JavaFX 25 has HeaderBar / StageStyle.EXTENDED (still a preview in 25 and 26). I think it would allow a thinner title bar with a Back button on standalone windows. We'd only look at that after the API becomes final.

    @rjwills28, could you please let us know whether 1 to 4 would work for you and Diamond? We'd implement whichever you agree with, as separate small PRs.

    Thanks for considering this. Cheers.

  4. rjwills28 commented on Nov 13, 2026

    @rjwills28
    ContributorAuthor

    Hi @emilioheredia-source - thanks for taking a look at this and testing out the standalone windows implementation. We weren't sure whether anyone else really used it so it's great that you are and have some feedback.

    Here are some thoughts on your points:

    1. I think (a) makes the most sense for this issue - so if a standalone window has an action button that opens a display in another tab then it would open that screen in the main window. That follows what happens when you open an application from a standalone window and leaves the standalone window untouched.
    2. Updating the converter sounds like a good idea so that a new window in EDM maps to a new (undecorated) window in Phoebus. The conversion from OPI->BOB already does this correctly for both 'normal' windows and 'standalone' windows.
    3. I think adding mouse backwards/forwards would be useful and would add extra functionality that others would benefit from. Most of our standalone windows have actions that open screens in the standalone mode so I'm not sure we see this case too often but it would add more flexibility to the standalone window implementation and allow you to use the 'replace' mode.
    4. An option to easily convert between a standalone and a ‘normal’ window I think is a nice idea and again adds functionality. I think at Diamond our intention would be to leave them as standalone windows so having this option as a preference would be nice for us. But with that said, I do like this idea.

    We have done a little more work on the resizing of standalone windows when opening them but haven't PR'd them yet.

  5. emilioheredia-source commented on Nov 15, 2026

    @emilioheredia-source

    Thank you, @rjwills28, that's very helpful. We'll go ahead with all four, as separate PRs:

    1. (a): a display opened in a new tab from a standalone window goes to the main window, which is brought to the front, and the standalone window stays as it was. A named pane is still honoured, and if the main window can't take the tab (for example its pane is locked), the display opens in a new window instead. The change is in DockItemRepresentation.openPanel, with a UI test.
    2. Converter preference: a new EDM converter preference for the target of related displays (tab stays the default; window or standalone). Good to know the OPI converter already does this; we'll mention it in the PR.
    3. Back/Forward: the fix for Alt+Left/Right in standalone windows, and the mouse back/forward buttons in all display windows. Thanks for pointing out that this mostly helps with the 'replace' mode.
    4. Standalone ⇄ normal: behind a preference, off by default, so Diamond's standalone windows stay as they are. We'll start on this one last.

    About your resizing work: so we don't step on it, could you let us know which parts it touches? Item 1 only changes openPanel and doesn't resize anything, but item 4 will have to resize the window when it switches between standalone and normal, so we'd like to build that on top of your changes rather than next to them. If your PR is coming soon, we're happy to wait for it before we start item 4.

    The fix for item 3 depends a little on #4017 (both touch DisplayRuntimeInstance), but they merge cleanly in either order.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions