Linked by Thom Holwerda on Tue 18th Jan 2011 22:18 UTC, submitted by alinandrei
Ubuntu, Kubuntu, Xubuntu De kogel is door de kerk. After years of focussing entirely on Gtk+ and GNOME, Ubuntu will finally start evaluating Qt applications for inclusion in the defaukt Ubuntu installation. Mark Shuttleworth announced the policy change on his blog today.
Thread beginning with comment 459031
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Talk about arrogance
by mart on Wed 19th Jan 2011 09:50 UTC in reply to "RE[5]: Talk about arrogance"
Member since:

Why is that not a valid approach? What does KDE have to lose if Qt devs implement dconf suport?

The admirable target of this move is to add more unification and consistence...

...what it would do in reality is adding more fragmentation, having just another API for a configuration system doesn't really add value but confusion.
Also, expecting developers to "write applications for Ubuntu" is not quite realistic. Most Qt-only applications are targeted to the most wide target platform (especially Windows and Mac in primis) so expecting them to target a specific Linux distribution (with the hope some other distributions will adopt it, but i wouldn't hold my breath) instead seems not realistic to me.

Now, writing it as a QSettings/KConfig backend is another story and makes more sense for sure, this is what i fully support (where the best case scenario is having a backend for both, with the KConfig one as the fully functional one, see below).

Now, probably QSettings itself is a bit too limited and I'm not sure it's possible to have a full support to dconf with its API.
Different discourse for KConfig, (that btw has good reasons to exist and to be sed in place of QSettings, we didn't write it just because we were bored) it adds things like better groups nesting support, system/user config fallback, type safety, change notifications..
all things that are necessary to represent 100% of dconf

Reply Parent Score: 4