[Qt-interest] QT and KDE code

[Stephen Kelly]

Anatoly Burakov wrote:

> Hi all
> 
> I was reading some mailing lists and articles about coding for KDE vs
> coding for QT. In that swarm of information the main idea i got was that
> KDE classes are basically QT classes with added functionality and names
> starting with K instead of Q. Does that mean that basically if i replace
> all Q's in class names in header files with K (when the corresponding
> class is available) the code will compile without any further
> modifications (provided i have included all the needed KDE headers of
> course)?

That's not quite the point.

The KDE development platform is written with Qt and consists of a lot of 
libraries and classes extending existing Qt functionality and adding new 
APIs not provided by Qt. These include APIs for writing games, educational 
software, personal information management (the bit that I do), as well as 
platform integration such as common dialogs, uniform configuration 
management, standard application data directory structures and more.

The API docs for the KDE development platform are

* http://api.kde.org/4.4-api/kdelibs-apidocs/
* http://api.kde.org/4.4-api/kdepimlibs-apidocs/

and there are tutorials here:

http://techbase.kde.org/Development/Tutorials/

Many KDE classes do inherit Qt classes and add functionality but that's the 
case with all software that uses Qt. Just using KTextEdit instead of 
QTextEdit won't make your application better unless you know why your using 
it. In the case of KTextEdit, the widget will automatically respect the 
system settings for mouse hiding for example, so it doesn't need to be 
configured per application. 

http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKTextEdit.html

Best regards,

Steve.

> 
> Best regards,
> Anatoly