[Interest] QtArg

Nikos Chantziaras realnc at gmail.com
Tue Apr 10 21:07:49 CEST 2012


On 10/04/12 21:46, Thiago Macieira wrote:
> On terça-feira, 10 de abril de 2012 21.15.29, Nikos Chantziaras wrote:
>> On 10/04/12 17:32, Thiago Macieira wrote:
>>> On terça-feira, 10 de abril de 2012 17.17.09, Nikos Chantziaras wrote:
>>>> I'd recommend to support Igor Mironchik instead, since it's for Qt 4,
>>>> which we will be using for a long time (Qt 5 doesn't work in KDE.)
>>>
>>> KDE already has KCmdLineArgs, so KDE doesn't need a Qt 4 solution. It
>>> needs a Qt 5 solution.
>>
>> I don't understand.  With that logic, Qt 5 doesn't need a solution
>> either because KDE will support Qt 5 in the future, and you'll have
>> KCmdLineArgs too then.
>
> Except you're missing the fact that KDE wants to drop some of its old
> compatibility classes and move them upstream to Qt 5. Laszlo's work is exactly
> that: upstreaming of KCmdLineArgs functionality.
>
> The same thing happened to KStandardDirs (QStandardPaths) and the KDE MIME
> type classes (QMimeDatabase). Both are already in 5.0.
>
>> Furthermore, Qt application can't use KDE libraries, because then they
>> would be KDE applications, not Qt applications.  Qt 4 application run
>> very nice in KDE.  Qt 5 applications do not (they look very alien).
>
> Which is a pity. There's a lot of functionality in the KDE libs that you
> should use. You should consider transforming your Qt-only app into a KDE one.

That is really bad advise :-/  It would mean non-KDE users (about 90% of 
my userbase) will not use the app.  But I still care very much about the 
remaining 10%!  But if push came to shove, I'd rather drop KDE (10%) 
than the rest (90% - Gnome, Windows, OS X.)




More information about the Interest mailing list