On Fri, Feb 3, 2012 at 3:26 PM, <[email protected]> wrote: > > >> On Thursday 15 December 2011 18:40:45 Jesus Sanchez-Palencia wrote: > >>> Hi there, > >>> > >>> I would like to gather your opinion on whether we should move > >>> QUndoStack and QUndoCommand out of QtWidgets so they could be used > >>> without requiring this module as an extra dependency. > > > Yes I agree. These classes are useful for a significant class of > applications we will see people writing those types of apps in QML as well > as widgets in the future, so extracting them from the QtWidgets library > might be a good idea. > > 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. Br, Adriano
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
