>>>>> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes:
Marko> Toolbars are good for displaying states (layout & mode for
Marko> example) and for rarely used functions. However, since it is
Marko> possible to build up toolbars similar to menus by using
Marko> multiple toolbars and drop-down lists, it will be not wise to
Marko> limit users with one toolbar. Wouldn't that be logical to use
Marko> the same syntax in lib/ui/default.ui file for menus and
Marko> toolbars?
I am not sure whether menus and toolbars should be exactly the same
thing, but the two classes should at least be closer one to the other...
Feel free to investigate what kind of change should be done. Maybe the
backends could be merged into one (although there is no text
associated to an action in a toolbar, and no shortcut).
In general, ideas on the interface to menus/toolbars are welcome. Tey
still need further design work.
Marko> BTW, is it possible to have Layouts (xforms toolbar) in menu?
Since layout lists seems to be very long and xforms menu do not like
being taller than the screen, this would not make much sense... Unless
we change the layout files to allow classification of layouts in
categories, which would fit nicely in a menu with submenus.
JMarc
