Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
I would of course keep all the algorithms. I am just thinking of
dropping all classes and variable that have a Qt equivalent.
Why not. Remember that you need to have a menu with all the
uninterpreted things, and another one which is the raw menu. You can
probably make expandMenu generate directly a QMenu, but not much more.
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).
And this is at the price of moving to frontend/qt4/ some code that
does not belong there (belongs to frontends/ though).
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.
Abdel.
