diff options
Diffstat (limited to 'doc/tdevelop/app-files.docbook')
-rw-r--r-- | doc/tdevelop/app-files.docbook | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/doc/tdevelop/app-files.docbook b/doc/tdevelop/app-files.docbook index f79b81c1..547010ec 100644 --- a/doc/tdevelop/app-files.docbook +++ b/doc/tdevelop/app-files.docbook @@ -28,20 +28,20 @@ <title>&tdevelop; Default Configuration</title> <para> -On installation, &tdevelop; writes some default information files for setup and configuration purposes into subdirectories of the <filename class="directory">$<envar>KDEDIR</envar></filename> installation directory (usually something like <filename class="directory">/opt/kde</filename>, <filename class="directory">/usr/local/kde</filename>, or some other user-defined installation directory, see <link linkend="tdevelop-install">Installing &tdevelop;</link>). +On installation, &tdevelop; writes some default information files for setup and configuration purposes into subdirectories of the <filename class="directory">$<envar>TDEDIR</envar></filename> installation directory (usually something like <filename class="directory">/opt/kde</filename>, <filename class="directory">/usr/local/kde</filename>, or some other user-defined installation directory, see <link linkend="tdevelop-install">Installing &tdevelop;</link>). </para> <sect2 id="app-files-default-config"> <title>Default &tdevelop; Configuration</title> <para> -There is only one &tdevelop; specific default configuration file in the <filename class="directory">$<envar>KDEDIR</envar>/share/config/</filename> directory: +There is only one &tdevelop; specific default configuration file in the <filename class="directory">$<envar>TDEDIR</envar>/share/config/</filename> directory: </para> <variablelist> <varlistentry> <term><filename>tdeveloprc</filename></term> <listitem><para> - This file contains the basic settings &tdevelop; needs to start. It will be copied to the user's <filename class="directory">$<envar>KDEHOME</envar>/share/config</filename> directory when &tdevelop; does not find a <filename>tdeveloprc</filename> file there on startup. + This file contains the basic settings &tdevelop; needs to start. It will be copied to the user's <filename class="directory">$<envar>TDEHOME</envar>/share/config</filename> directory when &tdevelop; does not find a <filename>tdeveloprc</filename> file there on startup. </para></listitem> </varlistentry> </variablelist> @@ -52,11 +52,11 @@ There is only one &tdevelop; specific default configuration file in the <filenam <title>Application Specific Defaults</title> <para> -Most &tdevelop; features are provided by KParts. These are basically applications specially designed to run in the &tdevelop; framework (see the overview in the <link linkend="plugin-tools">Plugin Tools</link> appendix). Each KPart application has its own set of configuration files whose defaults will be stored in several subdirectories of the <filename class="directory">$<envar>KDEDIR</envar>/share/apps/</filename> installation directory. +Most &tdevelop; features are provided by KParts. These are basically applications specially designed to run in the &tdevelop; framework (see the overview in the <link linkend="plugin-tools">Plugin Tools</link> appendix). Each KPart application has its own set of configuration files whose defaults will be stored in several subdirectories of the <filename class="directory">$<envar>TDEDIR</envar>/share/apps/</filename> installation directory. </para> <para> -There are quite a lot of default configuration subdirectories in <filename class="directory">$<envar>KDEDIR</envar>/share/apps/</filename> whose names all start with a <filename>kdev</filename> sequence. Most of them are for &tdevelop; internal use only. They might be deliberately grouped for readability as: +There are quite a lot of default configuration subdirectories in <filename class="directory">$<envar>TDEDIR</envar>/share/apps/</filename> whose names all start with a <filename>kdev</filename> sequence. Most of them are for &tdevelop; internal use only. They might be deliberately grouped for readability as: <simplelist> <member><link linkend="app-files-default-apps-stdalone">Stand-alone Applications</link></member> <member><link linkend="app-files-default-apps-task">Task Specific Parts</link></member> @@ -201,10 +201,10 @@ There are quite a lot of default configuration subdirectories in <filename class <title>User Oriented Configuration</title> <para> -All information about user defined settings is kept in two subdirectories of <filename class="directory">$<envar>KDEHOME</envar></filename>, namely: +All information about user defined settings is kept in two subdirectories of <filename class="directory">$<envar>TDEHOME</envar></filename>, namely: <simplelist> - <member><link linkend="app-files-user-apps">Application Specific Configuration</link> in the <filename class="directory">$<envar>KDEHOME</envar>/share/apps/</filename> directory, and</member> - <member><link linkend="app-files-user-config">Resource Configuration File</link> in the <filename class="directory">$<envar>KDEHOME</envar>/share/config/</filename> directory.</member> + <member><link linkend="app-files-user-apps">Application Specific Configuration</link> in the <filename class="directory">$<envar>TDEHOME</envar>/share/apps/</filename> directory, and</member> + <member><link linkend="app-files-user-config">Resource Configuration File</link> in the <filename class="directory">$<envar>TDEHOME</envar>/share/config/</filename> directory.</member> </simplelist> </para> @@ -212,13 +212,13 @@ All information about user defined settings is kept in two subdirectories of <fi <title>Application Specific Configuration</title> <para> -Any user changes to the <link linkend="app-files-default">&tdevelop; Default Configuration</link> settings as well as user specific settings which are not kept in any of the <link linkend="app-files-user-config">Resource Configuration Files</link> are found in <filename>kdev...</filename> subdirectories of the <filename class="directory">$<envar>KDEHOME</envar>/share/apps/</filename> directory. +Any user changes to the <link linkend="app-files-default">&tdevelop; Default Configuration</link> settings as well as user specific settings which are not kept in any of the <link linkend="app-files-user-config">Resource Configuration Files</link> are found in <filename>kdev...</filename> subdirectories of the <filename class="directory">$<envar>TDEHOME</envar>/share/apps/</filename> directory. </para> <para> Most of these configuration files are however used by various &tdevelop; plugins in order to provide some specific menu and/or toolbar entries. Thus they are of interest only in case something went really wrong with the user interface. </para> <note><para> -In case the contents of these directories mirror those of the Default Configuration settings, &tdevelop; will have copied them from <filename class="directory">$<envar>KDEDIR</envar>/apps/</filename> into the <filename class="directory">$<envar>KDEHOME</envar>/apps/</filename> directory on its initial start. Any subsequent changes will be made to these copies only. The Default Configuration settings remain unchanged in any case. +In case the contents of these directories mirror those of the Default Configuration settings, &tdevelop; will have copied them from <filename class="directory">$<envar>TDEDIR</envar>/apps/</filename> into the <filename class="directory">$<envar>TDEHOME</envar>/apps/</filename> directory on its initial start. Any subsequent changes will be made to these copies only. The Default Configuration settings remain unchanged in any case. </para></note> <itemizedlist> @@ -270,7 +270,7 @@ In case the contents of these directories mirror those of the Default Configurat </listitem> <listitem> <para><filename class="directory">kdevdocumentation/</filename> — contains the actual files used by the <guilabel>Documentation</guilabel> plugin in addition to the <link linkend="app-files-default-kdevdoc"> default configuration files</link>. See there for more detail.</para> - <para>The directories in <filename class="directory">kdevdocumentation/</filename> mainly hold actual bookkeeping information. The actually set up documentation files are kept in <link linkend="app-files-user-config-doc"> <quote><filename>doc...pluginrc</filename></quote> files</link> in the <filename class="directory">$<envar>KDEHOME</envar>/share/config/</filename> directory.</para> + <para>The directories in <filename class="directory">kdevdocumentation/</filename> mainly hold actual bookkeeping information. The actually set up documentation files are kept in <link linkend="app-files-user-config-doc"> <quote><filename>doc...pluginrc</filename></quote> files</link> in the <filename class="directory">$<envar>TDEHOME</envar>/share/config/</filename> directory.</para> <itemizedlist> <listitem> <para><filename class="directory">bookmarks/</filename> — maintains the entries in the <guilabel>Bookmarks</guilabel> tab of the &tdevelop; <guilabel>Documentation</guilabel> plugin.</para> @@ -345,7 +345,7 @@ In case the contents of these directories mirror those of the Default Configurat <title>Resource Configuration Files</title> <para> -There are two groups of &tdevelop; configuration files in the <filename class="directory">$<envar>KDEHOME</envar>/share/config/</filename> directory, distiguished by their surrounding character sequences: +There are two groups of &tdevelop; configuration files in the <filename class="directory">$<envar>TDEHOME</envar>/share/config/</filename> directory, distiguished by their surrounding character sequences: <simplelist> <member><quote><filename>doc...pluginrc</filename></quote> denotes <link linkend="app-files-user-config-doc">files used by the documentation plugin.</link></member> <member><quote><filename>kdev...rc</filename></quote> denotes configuration <link linkend="app-files-user-config-kdev">files used by &tdevelop;</link> itself and its available plugins.</member> @@ -356,7 +356,7 @@ There are two groups of &tdevelop; configuration files in the <filename class="d <title>Configuration Files Used by &tdevelop;</title> <listitem> <para><filename>kdevabbrevrc</filename> — holds the current state of the <guilabel>Abbreviations</guilabel> configuration provided by the <guilabel>Abbreviation Expansion</guilabel> plugin.</para> - <note><para>This only records whether the abbreviations will be used or not. The actual definitions of new abbreviations will go into the <filename>$<envar>KDEHOME</envar>/share/apps/kdevabbrev/templates/templates</filename> file.</para></note> + <note><para>This only records whether the abbreviations will be used or not. The actual definitions of new abbreviations will go into the <filename>$<envar>TDEHOME</envar>/share/apps/kdevabbrev/templates/templates</filename> file.</para></note> </listitem> <listitem> <para><filename>kdevassistantrc</filename> — holds some configuration states specific of the stand-alone &tdevelop; Assistant documentation browser.</para> @@ -416,7 +416,7 @@ Both are &XML; coded files. They can be viewed and (cautiously) altered using an </para> <note><para> -There can be additional Persistant Code Store files be set up on the <guilabel>Code Completion</guilabel> tab of the <guilabel>C++ Specific</guilabel> project configuration page. Information about these additional <filename>.pcs</filename> is kept globally in the <filename class="directory">$<envar>KDEHOME</envar>/share/apps/kdevcppsupport/pcs/</filename> directory. +There can be additional Persistant Code Store files be set up on the <guilabel>Code Completion</guilabel> tab of the <guilabel>C++ Specific</guilabel> project configuration page. Information about these additional <filename>.pcs</filename> is kept globally in the <filename class="directory">$<envar>TDEHOME</envar>/share/apps/kdevcppsupport/pcs/</filename> directory. </para></note> </sect2> |