Paths/Developer/Tour of Qt and KDE frameworks

< Paths‎ | Developer
Revision as of 15:57, 30 December 2008 by Steveire (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

A knowledge of some of the Qt framework is necessary to understand the KDE framework and design.

Start by exploring the 'Core features' section in the documentation. and the associated Examples.

It is important to note that some of the features of Qt are not used in KDE applications.

  • The Qt resource system is not used.
  • CMake is used instead of QMake.
  • KDE uses the gettext system for translations instead of the Qt tr() system.
  • Many Qt classes have KDE subclasses or equivalents which should be used instead. (KFileDialog instead of QFileDialog, KTextEdit instead of QTextEdit). The KDE classes provide greater system integration.
  • The KIO system should be used instead of QHttp or QNetworkAccessManager (see also Policies/API_to_Avoid)


This page was last modified on 30 December 2008, at 15:57. Content is available under Creative Commons License SA 3.0 as well as the GNU Free Documentation License 1.2 unless otherwise noted.