summaryrefslogtreecommitdiffstats
path: root/doc/tdevelop/setup.docbook
diff options
context:
space:
mode:
Diffstat (limited to 'doc/tdevelop/setup.docbook')
-rw-r--r--doc/tdevelop/setup.docbook34
1 files changed, 17 insertions, 17 deletions
diff --git a/doc/tdevelop/setup.docbook b/doc/tdevelop/setup.docbook
index 2c448945..0c078a3b 100644
--- a/doc/tdevelop/setup.docbook
+++ b/doc/tdevelop/setup.docbook
@@ -271,14 +271,14 @@ This let you choose the way you want <filename>.ui</filename> files to be displa
</para><para>This uses &tdevelop; own designer embedded within &tdevelop;</para></listitem>
<listitem><para>
Run &tdevelop;'s designer as a separate application
- </para><para>The TDevDesigner application will be run separately in its own window.</para>
+ </para><para>The KDevDesigner application will be run separately in its own window.</para>
<screenshot>
<mediaobject>
<imageobject>
- <imagedata fileref="tdevdesigner.png" format="PNG"/>
+ <imagedata fileref="kdevdesigner.png" format="PNG"/>
</imageobject>
<caption><para>
- TDevDesigner in its own window
+ KDevDesigner in its own window
</para></caption>
</mediaobject>
</screenshot>
@@ -294,7 +294,7 @@ Run Qt Designer
<term id="terminal-emulation"><guilabel>Terminal Emulation</guilabel></term>
<listitem>
<para>
-You choose here which terminal you want to be integrated within TDevelop.
+You choose here which terminal you want to be integrated within KDevelop.
</para>
<itemizedlist>
<listitem><para>
@@ -349,7 +349,7 @@ A typical example of this user interface mode is Borland Delphi 6.0.</para></lis
</itemizedlist>
<para>
-To switch the user interface mode select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;...</guimenuitem> </menuchoice> from the menus. The <guilabel>Customize TDevelop</guilabel> dialog will pop up, where you have to select <guilabel>User Interface</guilabel> in the left hand tree. This will display the following settings dialog to the right.</para>
+To switch the user interface mode select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;...</guimenuitem> </menuchoice> from the menus. The <guilabel>Customize KDevelop</guilabel> dialog will pop up, where you have to select <guilabel>User Interface</guilabel> in the left hand tree. This will display the following settings dialog to the right.</para>
<screenshot>
<mediaobject>
@@ -524,7 +524,7 @@ The active toolview window must be shown fixed (non-overlap mode), sharing the w
<sect2 id="setup-editor">
<title>Selecting an Editor</title>
-<para>&tdevelop; allows you to select your favorite text editor tool. Mark the <guilabel>Editor</guilabel> entry in the left hand side selections tree of the <guilabel>Configure TDevelop</guilabel> window. The following dialog will be displayed to the right.
+<para>&tdevelop; allows you to select your favorite text editor tool. Mark the <guilabel>Editor</guilabel> entry in the left hand side selections tree of the <guilabel>Configure KDevelop</guilabel> window. The following dialog will be displayed to the right.
</para>
<screenshot>
@@ -568,7 +568,7 @@ Changing the editor will not effect already open files. There are two possibilit
</para></note>
<important id="setup-editor-tdeparts"><para>
-TDevelop lets you use editor interfaces which have registered with &kde; and that provide a KatePart interface. If you miss one one of the selections shown above check your &kde; installation if the corresponding KPart was correctly installed.
+KDevelop lets you use editor interfaces which have registered with &kde; and that provide a KatePart interface. If you miss one one of the selections shown above check your &kde; installation if the corresponding KPart was correctly installed.
</para></important>
<para>What to do if the file has been changed externally:</para>
@@ -663,7 +663,7 @@ The reformat source feature is currently available for C, C++, and &Java; only.
</para></note>
<para>
-To set up a specific format style, select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the menubar. The <guilabel>Customize TDevelop</guilabel> dialog will pop up, where you have to select <guilabel>Source Formatter</guilabel> in the left hand tree. This will display a series of three settings dialog tabs to the right, namely a <link linkend="setup-format-general">General Formatting Setup</link>, a <link linkend="setup-format-indent">Indentation Style Setup</link>, and a <link linkend="setup-format-other">Other Formatting Setup</link>.
+To set up a specific format style, select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the menubar. The <guilabel>Customize KDevelop</guilabel> dialog will pop up, where you have to select <guilabel>Source Formatter</guilabel> in the left hand tree. This will display a series of three settings dialog tabs to the right, namely a <link linkend="setup-format-general">General Formatting Setup</link>, a <link linkend="setup-format-indent">Indentation Style Setup</link>, and a <link linkend="setup-format-other">Other Formatting Setup</link>.
</para>
<tip><para>
@@ -997,7 +997,7 @@ split a long line apart. For C/C++ code this can be controlled here.</para>
<title>Setting Up the Code Snippets Tool</title>
<para>
-When editing in &tdevelop; you can store often used parts of code as <link linkend="editing-snippets">Code Snippets</link>. To configure the capabilities of the code snippets part select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the menubar. The <guilabel>Customize TDevelop</guilabel> dialog will pop up, where you have to select <guilabel>Code Snippets</guilabel> in the left hand tree. This will show the following dialog in the right hand side.
+When editing in &tdevelop; you can store often used parts of code as <link linkend="editing-snippets">Code Snippets</link>. To configure the capabilities of the code snippets part select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the menubar. The <guilabel>Customize KDevelop</guilabel> dialog will pop up, where you have to select <guilabel>Code Snippets</guilabel> in the left hand tree. This will show the following dialog in the right hand side.
</para>
<screenshot>
@@ -1089,7 +1089,7 @@ system.
<para>The behaviour of the <guilabel>File Selector</guilabel> can be highly
configured. Select <menuchoice> <guimenu>Settings</guimenu>
<guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the
-menubar. The <guilabel>Customize TDevelop</guilabel> dialog will pop up,
+menubar. The <guilabel>Customize KDevelop</guilabel> dialog will pop up,
where you have to select <guilabel>File Selector</guilabel> in the left hand
tree. This will show the following dialog in the right hand side.</para>
@@ -1330,7 +1330,7 @@ If &tdevelop; was automatically restarted by the &kde; session manager the chang
</para></note>
<para>
-You may set up contents and behaviour of the various parts of this documentation window if you select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the menubar. The <guilabel>Customize TDevelop</guilabel> dialog will pop up, where you have to select <guilabel>Documentation</guilabel> in the left hand window.
+You may set up contents and behaviour of the various parts of this documentation window if you select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the menubar. The <guilabel>Customize KDevelop</guilabel> dialog will pop up, where you have to select <guilabel>Documentation</guilabel> in the left hand window.
</para>
<para>
@@ -1662,10 +1662,10 @@ You must put the &API; of your current project into this <guilabel>Doxygen Docum
</sect3> <!-- setup-docu-general-dox -->
<sect3 id="setup-docu-general-toc">
-<title>Handling Structured Documentation (TDevelopTOC Files)</title>
+<title>Handling Structured Documentation (KDevelopTOC Files)</title>
<para>
-The main bulk of the &tdevelop; documentation facility provides immediate access to structured documentation, local as well as remote ones. You can configure this on the <guilabel>TDevelopTOC Documentation Collection</guilabel> page.
+The main bulk of the &tdevelop; documentation facility provides immediate access to structured documentation, local as well as remote ones. You can configure this on the <guilabel>KDevelopTOC Documentation Collection</guilabel> page.
</para>
<screenshot>
@@ -1674,17 +1674,17 @@ The main bulk of the &tdevelop; documentation facility provides immediate access
<imagedata fileref="configure-docu-toc.png" format="PNG"/>
</imageobject>
<caption><para>
- Providing TDevelopTOC structured documentation access
+ Providing KDevelopTOC structured documentation access
</para></caption>
</mediaobject>
</screenshot>
<para>
-&tdevelop; comes with a bunch of predefined TDevelopTOC files which are automatically entered in the table at installation time. To keep the display manageable only the most often used will initially be marked for display. If you want to see another documentation, mark the <guilabel>TOC</guilabel> check box in the <link linkend="setup-docu-columns">setup table</link>.
+&tdevelop; comes with a bunch of predefined KDevelopTOC files which are automatically entered in the table at installation time. To keep the display manageable only the most often used will initially be marked for display. If you want to see another documentation, mark the <guilabel>TOC</guilabel> check box in the <link linkend="setup-docu-columns">setup table</link>.
</para>
<para>
-TDevelopTOC files cannot be indexed to perform a full text search because they usually point to a remote location. On the other hand, such a <filename>.toc</filename> file can have an index manually defined, using the <computeroutput>&lt;index&gt;</computeroutput> tag. Thus the <guilabel>Index</guilabel> check box will be enabled ony when &tdevelop; finds an <computeroutput>&lt;index&gt;</computeroutput> tag in the <filename>.toc</filename> file. (For more detail see the description below in the <link linkend="setup-docu-general-toc-files">&tdevelop; TOC Files</link> section.)
+KDevelopTOC files cannot be indexed to perform a full text search because they usually point to a remote location. On the other hand, such a <filename>.toc</filename> file can have an index manually defined, using the <computeroutput>&lt;index&gt;</computeroutput> tag. Thus the <guilabel>Index</guilabel> check box will be enabled ony when &tdevelop; finds an <computeroutput>&lt;index&gt;</computeroutput> tag in the <filename>.toc</filename> file. (For more detail see the description below in the <link linkend="setup-docu-general-toc-files">&tdevelop; TOC Files</link> section.)
</para>
<para>
The <guilabel>Search</guilabel> check box in the <link linkend="setup-docu-columns">setup table</link> will alway be disabled.
@@ -1720,7 +1720,7 @@ Such structured access is made possible through the use of special <quote>table
<term>Standard Directory of &tdevelop; TOC Files</term>
<listitem>
<para>
-When &tdevelop; was installed usually a series of predefined <filename>.toc</filename> files has been put into the <filename class="directory">$TDEDIR/share/apps/tdevdocumentation/tocs</filename> directory. These are fairly simple, structured text files. You may look at them using a text editor or other text display facility.
+When &tdevelop; was installed usually a series of predefined <filename>.toc</filename> files has been put into the <filename class="directory">$TDEDIR/share/apps/kdevdocumentation/tocs</filename> directory. These are fairly simple, structured text files. You may look at them using a text editor or other text display facility.
</para>
</listitem>
</varlistentry></variablelist>