On 02/03/2012 03:15 PM, Adriano Rezende wrote: > On Fri, Feb 3, 2012 at 3:26 PM, <[email protected] > <mailto:[email protected]>> wrote: > Where to put them is another question. To me, these classes fall into the > same category as QIcon, QAction, QFileSystemModel and a > probably a few others. They are enablers for certain UI's, but are at the > same time not useful for a different class of apps. For > instance mobile apps. For this reason, I do not think QtGui is the right > place for them. As I mentioned in the previous thread on > QFileSystemModel, I think a new module of non-widgetbased desktopui > enabling would be a better location. > > > It seems to be just a matter of defining a module name for these kind of > classes. Maybe "QtUtils" could be used until a better name or > module fragmentation is defined.
There is a patch in gerrit[1] moving QUndoCommand, QUndoStack and QUndoGroup to QtGui. I have another version of this patch, moving QUndo* classes to the new "QtUtils" module. [1] http://codereview.qt-project.org/#change,15857 Cheers, Anselmo -- Anselmo L. S. Melo openBossa / INdT http://www.indt.org
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
