Abdelrazak Younes <[EMAIL PROTECTED]> writes: > I thought a bit more about that. Instead of QMenu, I'd generate a list > of Actions instead. A QMenu can be automatically constructed with > that. The idea is that this would get us closer to my idea of "Action > unification" (menu and toobar actions if you remember).
A list of actions would not be bad (provided you have an action for Separator). > The ui file parsing code can (and probably should) stay in frontends/, > for the rest each frontend (if more than one :-)) should decide what > to do with those list of actions. Some of the algorithms (Navigation) are really painful and recreating them every time is not funny. JMarc
