Linked by Thom Holwerda on Tue 26th Oct 2010 15:20 UTC, submitted by diegocg
Qt Recently a project called 'Qt Modularization' was initiated. This is a project that aims to modularize Qt at every level. As you may know already, Qt is currently modularized on the DLL level; each module has its own DLL. However, the project as a whole is still monolithic; all the code is hosted in a single repository, you cannot build a leaf module without building the modules on which it depends. This project aims to change that, so that the modules are hosted in different repositories, with separate maintainers, and modules may have different release schedules.
Thread beginning with comment 447388
To read all comments associated with this story, please click here.
Just like the GTK+ folks, Good
by Mystilleef on Thu 28th Oct 2010 04:10 UTC
Mystilleef
Member since:
2005-06-29

This is one thing the GTK+ (glib, gobject, cairo, pango, gio, gvfs, etc) folks got right and I'm glad Qt is following suit.

Reply Score: 2

Delgarde Member since:
2008-08-19

This is one thing the GTK+ (glib, gobject, cairo, pango, gio, gvfs, etc) folks got right and I'm glad Qt is following suit.


Not entirely right - the GTK family are coming away from the opposite extreme of having too many pieces to the puzzle, by merging some of them into the core - e.g libunique and the dbus-glib bindings merging into glib, libsexy and some of the libgnomeui widgets going into gtk+, etc.

It's a balancing act, really. Monolithic and modular both have advantages, both have disadvantages. The gtk+ folk seem to be finding a happy balance these days, and I guess the same will be true of the next few Qt releases...

Reply Parent Score: 3