From 99ee6fd7e9737b5441af4a6cfdd69ff4b7eff5d3 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Wed, 7 Dec 2011 19:14:11 -0600 Subject: Rename KDEHOME and KDEDIR --- doc/kommander/extending.docbook | 8 ++++---- doc/kommander/translating.docbook | 4 ++-- doc/kommander/tutorials.docbook | 2 +- doc/quanta/config-quanta.docbook | 2 +- doc/quanta/extending-quanta.docbook | 8 ++++---- doc/quanta/quanta-menus.docbook | 2 +- doc/quanta/working-with-quanta.docbook | 2 +- 7 files changed, 14 insertions(+), 14 deletions(-) (limited to 'doc') diff --git a/doc/kommander/extending.docbook b/doc/kommander/extending.docbook index 1adfdc25..473b8ec5 100644 --- a/doc/kommander/extending.docbook +++ b/doc/kommander/extending.docbook @@ -346,12 +346,12 @@ mykomplugin.cpp, compiling and installing your plugin would involve something similar to the following commands: -libtool --mode=compile g++ -$KDEDIR/include -IQTDIR/include \ +libtool --mode=compile g++ -$TDEDIR/include -IQTDIR/include \ -I. -fPIC -c komlineedit.cpp -libtool --mode=compile g++ -$KDEDIR/include -IQTDIR/include \ +libtool --mode=compile g++ -$TDEDIR/include -IQTDIR/include \ -I. -fPIC -c mykomplugin.cpp -libtool --mode=link g++ -shared -L$KDEDIR/lib -ltdeui -lkommanderwidget \ +libtool --mode=link g++ -shared -L$TDEDIR/lib -ltdeui -lkommanderwidget \ -lkommanderplugin komlineedit.cppkomlineedit.o mykomplugin.o -o libmykomplugin.so @@ -359,7 +359,7 @@ libtool --mode=link g++ -shared -L$KDEDIR/lib -ltdeui -lkommanderwidget \ If you want to install new plugin system-wide, root, use: -su -c "cp libmykomplugin.so $KDEDIR/lib" +su -c "cp libmykomplugin.so $TDEDIR/lib" If you use the KDevelop project generator, you will not need to do the above, but instead adapt the Makefile.am to link against extra libraries. By default, it will link to &Qt; and &kde; libraries and generate all the needed object files. Just run make to build, and su -c make install to install. diff --git a/doc/kommander/translating.docbook b/doc/kommander/translating.docbook index 15d7def2..629b22ea 100644 --- a/doc/kommander/translating.docbook +++ b/doc/kommander/translating.docbook @@ -34,7 +34,7 @@ Here is a short description about the needed steps to make a dialog translatable How to extract the messages and create the .po file? - Use the kmdr2po script to extract the strings. The script is inside the working directory of the source release tarball and should be installed to $KDEDIR/share/apps/kommander/translating as well. + Use the kmdr2po script to extract the strings. The script is inside the working directory of the source release tarball and should be installed to $TDEDIR/share/apps/kommander/translating as well. Just run: @@ -52,7 +52,7 @@ An appropriate <your-kommander-dialog.po> file will be created. How to install the translation? Put the compiled *.mo file either to -$KDEDIR/share/locale/<your language>/LC_MESSAGES/ (will be available globally for all users) +$TDEDIR/share/locale/<your language>/LC_MESSAGES/ (will be available globally for all users) or to $HOME/.kde/share/locale/<your language>/LC_MESSAGES/ (will be available only for the current user) directory. diff --git a/doc/kommander/tutorials.docbook b/doc/kommander/tutorials.docbook index 0f6fd954..00f44d87 100644 --- a/doc/kommander/tutorials.docbook +++ b/doc/kommander/tutorials.docbook @@ -316,7 +316,7 @@ Shows how to use Table widget These examples reflect the most recent development state of &kommander;. In its current state &kommander; has few limitations for developing small to medium applications. It certainly is not suitable for building a KWord clone, but for a simple editor, database frontend, GUI for commandline programs or any application in the spirit of Unix/Linux small applications it is a good choice. The examples presented here are intended to show the potential as well as how to work around limitations. There are some useful tricks included in these if you want to do a more capable small application with &kommander;. Remember &kommander; is not intended to do everything, but to do most things. For this concession you should be able to build something in &kommander; faster than other alternatives ad add GUI to scripting languages not otherwise supported in KDE. -The examples are installed to $KDEDIR/share/apps/kmdr-editor/editor. In case you do not have them there, get from our home page, by downloading the latest release. +The examples are installed to $TDEDIR/share/apps/kmdr-editor/editor. In case you do not have them there, get from our home page, by downloading the latest release. diff --git a/doc/quanta/config-quanta.docbook b/doc/quanta/config-quanta.docbook index 0b332330..3ba20ea0 100644 --- a/doc/quanta/config-quanta.docbook +++ b/doc/quanta/config-quanta.docbook @@ -113,7 +113,7 @@ The place to define abbreviations (some kind of templates), that can be expanded Name: the user visible name Output window: plugins can appear in a tab of the editor area or in a separate toolview at the bottom - Location: the path to the plugin, if it is not located in the standard locations, like $KDEDIR/lib . + Location: the path to the plugin, if it is not located in the standard locations, like $TDEDIR/lib . File name: the relative path and the filename to the plugin's libtool file, like trinity/libcervisiapart.la Input: the plugin will get this information on startup, so it can open the Current File, the folder of the current file (Current File Path) or the Project Folder. Read only part: check if the plugin refuses to load. Read-only KParts usually refuse to load without this option checked. diff --git a/doc/quanta/extending-quanta.docbook b/doc/quanta/extending-quanta.docbook index 6dd0629e..df92f408 100644 --- a/doc/quanta/extending-quanta.docbook +++ b/doc/quanta/extending-quanta.docbook @@ -1195,8 +1195,8 @@ First you have to enter the name of your script with the interpreter as well. Ex Although you can use full paths, the recommended way is to use the %scriptdir variable in the command line, like sh %scriptdir/myScript.sh. This way &quantaplus; will try to locate your script in the following places: -global script folder: $KDEDIR/share/apps/quanta/scripts -local script folder: $KDEHOME/share/apps/quanta/scripts +global script folder: $TDEDIR/share/apps/quanta/scripts +local script folder: $TDEHOME/share/apps/quanta/scripts your path: $PATH There are other special variables that you can use in the command line: @@ -1700,7 +1700,7 @@ addslashes=function.addslashes.html Now you can just save your docrc file, save it in $HOME/.kde/share/apps/quanta/doc or $KDEDIR/share/apps/quanta/doc +class="directory">$TDEDIR/share/apps/quanta/doc for local or global use respectively. Then create a folder (the one specified in your docrc file) in the same folder as your docrc file and copy your &HTML; pages in @@ -1771,7 +1771,7 @@ After a resource was downloaded, but before it is installed, &quantaplus; verifi The entries are: - Target directory name:the newly created &DTEP; will go under this name to the $KDEHOME/share/apps/quanta/dtep folder. + Target directory name:the newly created &DTEP; will go under this name to the $TDEHOME/share/apps/quanta/dtep folder. Name:the name (definition string) of the DTD diff --git a/doc/quanta/quanta-menus.docbook b/doc/quanta/quanta-menus.docbook index 751f4591..66449f78 100644 --- a/doc/quanta/quanta-menus.docbook +++ b/doc/quanta/quanta-menus.docbook @@ -1397,7 +1397,7 @@ details. Loads a globally defined toolbar. These are kept in $KDEDIR/share/apps/quanta/toolbars +class="directory">$TDEDIR/share/apps/quanta/toolbars by default. diff --git a/doc/quanta/working-with-quanta.docbook b/doc/quanta/working-with-quanta.docbook index 4a0ca0b1..54471778 100644 --- a/doc/quanta/working-with-quanta.docbook +++ b/doc/quanta/working-with-quanta.docbook @@ -330,7 +330,7 @@ track this so you will need to change links. Template structure on the template tab is based on the files found in -$KDEDIR/share/apps/quanta/templates and +$TDEDIR/share/apps/quanta/templates and $HOME/.kde/share/apps/quanta/templates. Each of these folders is specified as one of four types of container as explained above. -- cgit v1.2.3