Hi Peter. 2018-06-02 19:17 GMT+03:00 Peter Uhnák <[email protected]>:
> > I believe we should move to Commander with first class commands. > > How would that work when menu entries can be generated dynamically? > Commands are responsible to build menu items for themselves. By default they build single item. But you can override method and generate multiple items. Look for example at ClySwitchQueryScopeCommand>>#fillContextMenu:using: > > Peter > > On Sat, Jun 2, 2018 at 1:32 PM, H. Hirzel <[email protected]> wrote: > >> On 6/1/18, Torsten Bergmann <[email protected]> wrote: >> > >> >>Guille & Cyril wrote> >> >> > Since some decades now the default way to display a menu in >> >> > applications >> >> > is to have a bar at the top of the windows. >> > >> > >> > Alistair wrote >> >>> Instead of a menu bar at the top, which takes quite a bit of space, >> >>> and as mentioned may not fit on a small screen how about a "Start" >> >>button in the task-bar that pops up the menu a-la Windows >> > >> > >> > So this basically reduces to the two UI options: >> > >> > 1. Should Pharo look like an application (and have the menu at the top) >> > >> > 2. Should Pharo look like an OS itself (with a primary "Start" menu in >> the >> > taskbar as on Windows) >> > >> > Maybe we should support both styles using a setting. >> > >> > Bye >> > T. >> +1 >> > >> >> >
