faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: what's it gonna be called?
by Matze on Sunday 21/Dec/2003, @13:36
|
What's the real difference between a KDE application and a qt application? Do all 3rd party KDE programs require QT? Why do shlashdotties alsways say that gpled qt was less free than lgpl of gtk? I don't understand this.
One example:
Hbasic (http://hbasic.sf.net), is it a KDE program? |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: what's it gonna be called?
by Aaron J. Seigo on Sunday 21/Dec/2003, @16:30
|
KDE applications use the added KDE technologies which include things such as KIO (network/device-transparent file access), XMLUI (which gives the ability to easily customize menus, shortcuts and toolbars), the KDE file dialog, the KDE printing system, the various standard KDE dialogs (e.g. edit toolbars, config windows), KConfig, DCOP (for IPC and scripting), icon (and other) themes... etc, etc.. basically a whole bunch of stuff that improves on or adds to what Qt provides.
HBasic isn't a KDE app, it's a Qt app... but it does work well and blend in quite nicely with a KDE desktop. KBasic, on the other hand, is a KDE app (http://kbasic.org)
|
[
Reply To This | View ]
|
Re: what's it gonna be called?
by manyoso on Sunday 21/Dec/2003, @19:03
|
<i>"Why do shlashdotties alsways say that gpled qt was less free than lgpl of gtk? I don't understand this."</i>
They do this because some fairly prominent developers have chosen to pass around this FUD to slur KDE/Qt... despite knowing better. It is an embarrasment and deeply ironic.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|