From b4e545384b42deff2db00ff815c4cacbeb5d1860 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sun, 6 Nov 2011 02:32:07 -0600 Subject: Additional kde to tde renaming --- doc/kde_app_devel/index.docbook | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'doc/kde_app_devel') diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook index 2ec1f0e4..0ebf7e71 100644 --- a/doc/kde_app_devel/index.docbook +++ b/doc/kde_app_devel/index.docbook @@ -525,10 +525,10 @@ and the Qt online reference. The main KDE libraries you'll be using for creating your own KDE applications are: -the kdecore library, containing all classes that are non-visible elements to provide application functionality +the tdecore library, containing all classes that are non-visible elements to provide application functionality -the kdeui library, containing user interface elements like menubars, toolbars, etc. +the tdeui library, containing user interface elements like menubars, toolbars, etc. the kfile library, containing the file selection dialogs @@ -539,7 +539,7 @@ the kfile library, containing the file selection dialogs Additionally, for specific solutions KDE offers the following libraries: -the kdefx library, containing pixmaps, image effects the KStyle extension to QStyle +the tdefx library, containing pixmaps, image effects the KStyle extension to QStyle the khtml library, containing KDE's html component @@ -590,7 +590,7 @@ You see that first we have changed from QApplication to < . Further, we had to change the previously used setMainWidget() method to setTopWidget, which KApplication uses to set the main widget. That's it! Your first KDE application is ready - you only have to tell the compiler the KDE -include path and the linker to link in the kdecore library with -lkdecore. +include path and the linker to link in the tdecore library with -ltdecore. As you now know what at least the main() function provides generally and how an @@ -601,7 +601,7 @@ mentioned before and see the effects. What you should have looked into additionally until now is the reference documentation for Qt, especially the QApplication, QWidget and QObject - class and the kdecore library documentation for the KApplication class. + class and the tdecore library documentation for the KApplication class. The KDE Library Reference handbook also covers a complete description about the invocation of the QApplication and KApplication constructors including command-line argument processing. @@ -803,7 +803,7 @@ the compilation phase. -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -O2 -fno-exceptions -fno-check-new -o kscribble_client -R /usr/local/trinity/lib -R /usr/lib/qt/lib -R /usr/X11R6/lib -L/usr/X11R6/lib -L/usr/lib/qt/lib - -L/usr/local/trinity/lib kscribble_client.o -lkdecore + -L/usr/local/trinity/lib kscribble_client.o -ltdecore 59 gmake[2]: Leaving directory `/home/caleb/kscribble/src' 60 gmake[2]: Entering directory `/home/caleb/kscribble' 61 gmake[2]: Nothing to be done for `all-am'. @@ -1120,7 +1120,7 @@ know how to handle them and only have to concentrate on the displayed data. KDE Views The KDE libraries were invented to make designing applications for the K Desktop Environment easier -and capable of more functionality than what Qt alone is offering. The kdeui library offers: +and capable of more functionality than what Qt alone is offering. The tdeui library offers: KListView: a more powerful version of QListView @@ -1274,7 +1274,7 @@ either displaying the button, button with text on the right, button with text be This possibility should be made configurable by the user, but isn't a must-be. The text is shown as a tool-tip anyway and a toolbar usually consists of buttons and other widgets like lineedits and combo boxes. For a complete reference, see the KToolBar class reference located -in the kdeui library. +in the tdeui library. As an example, we have a look at the "New File" button in a generic application: -- cgit v1.2.1