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.
Permalink for comment 459023
To read all comments associated with this story, please click here.
RE[5]: De kogel is door de kerk
by lemur2 on Wed 19th Jan 2011 09:14 UTC in reply to "RE[4]: De kogel is door de kerk"
lemur2
Member since:
2007-02-17

Yep, they must. All Qt programmers that do not use dconf will be arrested and executed.

Oh wait, the only downside to not implementing dconf is that you won't see your application installed by default on the Ubuntu live CD. So no, nobody must do anything.

All Canonical is doing is creating a new piece of software that allows Qt application to integrate better into GNOME and Ubuntu. Yes, not just Ubuntu, this will also benefit other distros that combine GNOME with Qt applications. And everybody is free to use or ignore it.

I don't get all these comments saying "I have wanted Qt apps in Ubuntu for years, and now they are doing it. Those bastards!"


I'm sorry you missed the sarcasm tag, I actually did put one right there in that post for you.

Anyway, my point is this ... why should authors of Qt applications be falling over themselves to re-write their apps just for the "honour" of being included on Mr Shuttleworth's Ubuntu default install CD?

Why would it be so hard for Mr Shuttleworth to arrange to do the work of integration, if he wants to include these best-of-class Qt applications on his default CD?

There are two methods which come to mind, neither of which would require Qt authors to leap to Mr Shuttleworth's bidding (for Mr Shuttleworth's benefit):

1. Ubuntu writes a replacement qtconfig
http://doc.qt.nokia.com/latest/qtconfig.html
The qtconfig tool allows users to customize the default settings for Qt applications on a per-user basis, enabling features such as the widget style to be changed without requiring applications to be recompiled.
and a replacement for QsettingsClass in the QtCore module, both of which integrate with dconf, all other parts of Qt remain untouched,

http://doc.qt.nokia.com/4.6.2/qsettings.html
Detailed Description

The QSettings class provides persistent platform-independent application settings.

Users normally expect an application to remember its settings (window sizes and positions, options, etc.) across sessions. This information is often stored in the system registry on Windows, and in XML preferences files on Mac OS X. On Unix systems, in the absence of a standard, many applications (including the KDE applications) use INI text files.

QSettings is an abstraction around these technologies, enabling you to save and restore application settings in a portable manner. It also supports custom storage formats.

QSettings's API is based on QVariant, allowing you to save most value-based types, such as QString, QRect, and QImage, with the minimum of effort.


or

2. Ubuntu writes an expanded dconf module which edits both the dconf database and the qtconfig and QsettingsClass storage.

Either way, it seems to me, suddenly Qt applications running on Ubuntu will see the same settings changes as dconf does, without any requirement for said Qt applications to be re-written or even re-compiled.

Surely this is an infinitely better solution for everybody, even for Mr Shuttleworth?

Edited 2011-01-19 09:24 UTC

Reply Parent Score: 3