Matthias Ettrich is proposing a new strategy for more strongly integrating Qt-only applications into KDE. It's an intriguing proposal and relevant to KDE, considering the growing number of cross-platform but Qt-only applications becoming available. The initial "not-perfect but simple" basic idea is that a small libQtKDE proxy library would invoke KDE functionality when available, or otherwise fall back to Qt functionality. This would not involve changing Qt or KDE, but would require the programmer to link against the libQtKDE wrapper. The benefits for the former Qt-only developer is that KDE functionality would be made available cheaply without giving up the Qt-only cross-platform approach. The benefits for the KDE user is that what would have otherwise been a pure Qt-only application could now potentially integrate much more strongly with KDE. Good thing or bad thing? Read on for the full details of the proposal.
Some time ago there was a rant somewhere about the emerging number of
Qt 3.0's style plugins will improve the situation somewhat, but not
One suggestion was to go cross-platform with parts of KDE and to
There's another solution, which I'd like to promote here.
KDE from the perspective of a cross-platform toolkit like Qt, is
The main reason why this isn't so easy, is the circular dependency: Qt
However, we don't need to start with a perfect solution. If would be a
Technically, the simplest approach does not even require changing Qt or
We write another small library libQtKDE, that wraps KDE
The library contains a dummy application-class (so that it's possible
In addition there are a bunch of static functions like
Later, the static functions in Qt itself (like
An application using libQtKDE is somewhere in the middle between a standard
Opinions? Do you think that would be useful at all?