Stewart wrote:
The User will see (nearly) no change to the GUI.On Wed, 5 Feb 2003 23:04:50 +0100 Thomas Reitelbach <[EMAIL PROTECTED]> wrote:I'm currently changing qt-gui to use QActions instead of manually managing menus. This is my first patch which converts the mnuStatus menu to use the QAction framework. The goal is to make usage of menus easier to developers. the user will (hopefully) see no much change.
Sorry for the naivette of my response, I'm barely a programmer anymore. :) What kind of tangible results will we see to the codebase? ie; will it reduce the codebase at all, will it make the menuing system more optimized, or effect any change in the uniformity of the QT and/or KDE GUI environments?
There will be some minor improvements, like the visibility of Menu Shortcuts in case of my last patch for example.
The Codebase may reduce a bit, but not much. The main improvement is, that managing menu's (and toolbars and pixmaps on them) will get easier. The code which manages menus will get more clear and easier to understand.
If we use a toolbar in licq then QActions make it very easy to keep menu entries and a related toolbar button in sync, simply by editing the connected QAction instead of first editing the menu, then editing the toolbutton.
So all in all it's an improvement for the gui developers.
Thomas
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Licq-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/licq-devel