Hi,
@Cyril
I don't know if it should be in the SettingBrowser since Pharo currently
comes with only one menu (if someone know how to implement a new one it
will be easy for him to find the option to change the pragma of the
MenuBarMorph), but the pragma should be parametrizable in any case.
Adding a new pragma is not a problem, you can use whatever name you want (see e.g. worldMenuExample pragma), but there is no way to tell Pharo to use this instead of the default one.
I don't know if it should be in the SettingBrowser since Pharo currently��comes with only one menu
Oh, never mind. I just found out that this is already in place, in WorldState class>>desktopMenuPragmaKeyword:. I don't know how I managed to miss this in the past.
So if the new menu bar just uses this (WorldState class>>discoveredMenuPragmaKeyword), or uses a similar mechanism (so the menus can differ, which would be also nice), then all is well.
I'll rephrase, we have ideas to manage all those problems but how do we
implement it? Currently there is no widget to do that and sadly we don't
have enough time to create them :(
I don't know about menu morph, but the bottom menu can handle overflow, can that be used for the time-being?
��
@Sean:
Were these projects where you were the only user?��
No.
For experienced users, I struggle to see how "Navigate over to Xyz��which takes up screen real estate" is better than "click wherever the cursor��happens to be"
Pharo adds 25px margin on all sides of a full-screen window. This is enough to add menu to each side. So in fact Pharo already wastes 4x as much space to do what you want.
Secondly, my menu doesn't match the world menu, it provides the most important/common options that user needs; so yes, it is faster, because it is one or two clicks instead of going through items that are not relevant to the user.
Finally, even if I didn't consider full screen, very often I find myself having to move windows, just so I can expose a piece of desktop to click on.
Please don't forget that some Pharo applications are meant for (non-programmer) end users, and not for (Pharo) developers.
But don't see a problem with adding a checkbox to settings "Menu bar [x]". There is already such a setting for the bottom task bar ("Taskbar...").
Peter