Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More flexible Phoebus Layout memento file selection proposal. #3133

Open
wbadgett opened this issue Sep 5, 2024 · 1 comment
Open

More flexible Phoebus Layout memento file selection proposal. #3133

wbadgett opened this issue Sep 5, 2024 · 1 comment

Comments

@wbadgett
Copy link

wbadgett commented Sep 5, 2024

When one has many memento Phoebus Layout files, the Phoebus layout selector popup pane becomes very large. May I propose using a more flexible approach, at least recognizing subdirectories in the ${HOME}/.phoebus area? Or bring up a general purpose file browser? What would be the best approach?

@kasemir
Copy link
Collaborator

kasemir commented Sep 6, 2024

Previous EPICS display managers (edd/dm, medm, dm2k, edm, ...) didn't have any idea of a layout. You open some top-level "start" display, and on there you'd typically have some top-level view of the machine with buttons to drill down via related displays.
The result is a well-known startup scenario from which you can reach what you need within a few clicks.
With layouts we offer a few different starting points. On a Beamline/instrument, you thus may have a "User" and "Expert" option. But if the layout menu turns into a multi-page phone book, the "shortcut" idea is somewhat lost.

So I think it's a bad idea.

Technically, however, I suggest you add AppResourceDescriptor support for *memento files to the UI framework.
That way, you could start CSS with a -resource /path/to/xx.mememto command line option, or click on a *memento file in the file browser. That App would then load the memento.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants