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 447289
To read all comments associated with this story, please click here.
Please don't overdo it
by ndrw on Wed 27th Oct 2010 06:22 UTC
Member since:

One of the best Qt features is that it is a monolithic toolkit, shipped and tested as a single unit.

It make sense to separate out development tools, documentation, less popular bindings but putting parts of the toolkit (like Qt WebKit) in separate packages is a slippery slope. It make deployment of applications unnecessarily difficult (unless they're bundled with all the needed libraries). Just look what happened to Gtk applications that often copy-paste library code just to avoid excessive dependencies.

Also, please don't partition namespaces too much, especially horizontally. There are already problems caused by the split between QtCore and QtGui (data containers are in QtCore, things to put in them are in QtGui) - with few boundaries like that this is just an annoyance that leads to uglier code, with many - applications may easily become unmanageable.

Reply Score: 2