diff options
Diffstat (limited to 'doc/kdevelop/setup.docbook')
| -rw-r--r-- | doc/kdevelop/setup.docbook | 184 |
1 files changed, 92 insertions, 92 deletions
diff --git a/doc/kdevelop/setup.docbook b/doc/kdevelop/setup.docbook index e5449a99..5dd15c06 100644 --- a/doc/kdevelop/setup.docbook +++ b/doc/kdevelop/setup.docbook @@ -7,10 +7,10 @@ </authorgroup> </chapterinfo> -<title>Configuring &kdevelop;</title> +<title>Configuring &tdevelop;</title> <para> -&kdevelop; is a very powerful and flexible IDE which offers many ways to tailor it to your needs. To start configuration select <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &kdevelop;...</guimenuitem></menuchoice>. This will cause the configuration dialog to pop up consisting of a selection window to the left and the configuration dialog on the right hand side whose contents will vary upon the configuration item you did select. +&tdevelop; is a very powerful and flexible IDE which offers many ways to tailor it to your needs. To start configuration select <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &tdevelop;...</guimenuitem></menuchoice>. This will cause the configuration dialog to pop up consisting of a selection window to the left and the configuration dialog on the right hand side whose contents will vary upon the configuration item you did select. </para> <screenshot> @@ -56,7 +56,7 @@ If you want directly look up a certain configuration item use one of the followi <title>General Configuration</title> <para> -General configuration concerns the more common tasks of tailoring &kdevelop; as there are: +General configuration concerns the more common tasks of tailoring &tdevelop; as there are: </para> <itemizedlist> <listitem><para> @@ -88,7 +88,7 @@ General configuration concerns the more common tasks of tailoring &kdevelop; as <title>General Setup</title> <para> -The <guilabel>General</guilabel> configuration dialog allows you to define some basic &kdevelop; behaviour which seldom will change in everyday work. This concerns: +The <guilabel>General</guilabel> configuration dialog allows you to define some basic &tdevelop; behaviour which seldom will change in everyday work. This concerns: </para> <variablelist> @@ -97,10 +97,10 @@ The <guilabel>General</guilabel> configuration dialog allows you to define some <listitem> <itemizedlist> <listitem><para> - defining a <link linkend="setup-main-projects">default parent directory</link> &kdevelop; shall use for new projects. + defining a <link linkend="setup-main-projects">default parent directory</link> &tdevelop; shall use for new projects. </para></listitem> <listitem><para> - deciding whether you want &kdevelop; to <link linkend="setup-main-preload">automatically load</link> the project you last worked on. + deciding whether you want &tdevelop; to <link linkend="setup-main-preload">automatically load</link> the project you last worked on. </para></listitem> </itemizedlist> </listitem> @@ -114,7 +114,7 @@ namely:</term> <itemizedlist> <listitem> <para>the <link linkend="setup-main-messages-font">Messages Output -View</link> &kdevelop; uses to communicate ⪚ compilation progresses, +View</link> &tdevelop; uses to communicate ⪚ compilation progresses, and</para> </listitem> <listitem> @@ -166,7 +166,7 @@ messages</link> issued by <command>make</command> will be shown.</para> startup</guilabel></term> <listitem> <para> -Mark this checkbox if you want to continue to work with the last project you worked on. This will cause &kdevelop; to automatically load this project on start-up. It will usually be shown in the state you left work so you can readily proceed. +Mark this checkbox if you want to continue to work with the last project you worked on. This will cause &tdevelop; to automatically load this project on start-up. It will usually be shown in the state you left work so you can readily proceed. </para> </listitem> </varlistentry> @@ -176,9 +176,9 @@ Mark this checkbox if you want to continue to work with the last project you wor <guilabel>Default projects directory:</guilabel></term> <listitem> <para> -By default, &kdevelop; uses a common parent directory for all new +By default, &tdevelop; uses a common parent directory for all new projects. Enter the absolute path of this common directory in the box or -select it from your directory structure. &kdevelop; will place the any new +select it from your directory structure. &tdevelop; will place the any new project here as a subdirectory.</para> <note><para> You may of course change the directory path of a new project at the time you set it up in the <link linkend="applicationwizard">&appwizard;</link>. @@ -190,13 +190,13 @@ You may of course change the directory path of a new project at the time you set <term id="setup-main-messages-font"><guilabel>Window font:</guilabel></term> <listitem> <para> -The <guilabel>Application Output View</guilabel> window is used to display error and state information from applications which are run from inside &kdevelop;. These are informations the applications usually sends to the console when run stand-alone. So you do not need to leave the IDE when testing the application you currently work on. +The <guilabel>Application Output View</guilabel> window is used to display error and state information from applications which are run from inside &tdevelop;. These are informations the applications usually sends to the console when run stand-alone. So you do not need to leave the IDE when testing the application you currently work on. </para> <para> To select a font suitable for the <guilabel>Messages Output View</guilabel> window click the <guilabel>Window Font</guilabel> button showing the currently selected font (it says <quote>Luxi Sans</quote> in the above illustration). The &kde; standard <guilabel>Select Font</guilabel> dialog will pop up from which you may select the font to be used. </para> <note><para> -On first start-up, &kdevelop; initializes this font setting to the standard font for which your &kde; user has been configured. <emphasis>This setting is fixed</emphasis>, so if you alter <menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Appearances & Themes</guimenuitem><guimenuitem>Fonts</guimenuitem></menuchoice> in the <guilabel>Control Center</guilabel>, this will not effect this &kdevelop; font selection. You will have to explicitely reselect the <guilabel>Messages Output View</guilabel> window font. +On first start-up, &tdevelop; initializes this font setting to the standard font for which your &kde; user has been configured. <emphasis>This setting is fixed</emphasis>, so if you alter <menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>Appearances & Themes</guimenuitem><guimenuitem>Fonts</guimenuitem></menuchoice> in the <guilabel>Control Center</guilabel>, this will not effect this &tdevelop; font selection. You will have to explicitely reselect the <guilabel>Messages Output View</guilabel> window font. </para></note> </listitem> </varlistentry> @@ -205,7 +205,7 @@ On first start-up, &kdevelop; initializes this font setting to the standard font <term id="setup-main-compile"><guilabel>Compiler Output</guilabel></term> <listitem> <para> -&kdevelop; preprocesses the messages the <guilabel>Messages Output View</guilabel> window receives during the build processes in order to filter superfluous information. You can control the level of detail &kdevelop; will display using the dropdown box in this field. +&tdevelop; preprocesses the messages the <guilabel>Messages Output View</guilabel> window receives during the build processes in order to filter superfluous information. You can control the level of detail &tdevelop; will display using the dropdown box in this field. </para> <variablelist> <varlistentry> @@ -238,7 +238,7 @@ There is an alternative way to switch the compiler output detail. Just right cli <term id="setup-main-wrap"><guilabel>Line wrapping</guilabel></term> <listitem> <para> -By default, &kdevelop; will wrap long lines around in the <guilabel>Messages Output View</guilabel> window so that valuable information will not be easily overlooked. In some cases this will clutter long message lists. Remove the checkbox mark if you do not want the lines wrap around. +By default, &tdevelop; will wrap long lines around in the <guilabel>Messages Output View</guilabel> window so that valuable information will not be easily overlooked. In some cases this will clutter long message lists. Remove the checkbox mark if you do not want the lines wrap around. </para> <tip><para> There is an alternative way to switch the line wrapping. Just &RMB; click in the <guilabel>Messages Output View</guilabel> window and mark/unmark the <guimenuitem>Line Wrapping</guimenuitem> entry in the menu which will pop up. @@ -251,7 +251,7 @@ There is an alternative way to switch the line wrapping. Just &RMB; click in the messages</guilabel></term> <listitem> <para> -The <command>make</command> tool usually will display messages like <quote>Entering directory</quote>, or <quote>Leaving directory</quote> when it switches the directories it currently works in. As this clutters the messages list in the <guilabel>Messages Output View</guilabel> window, &kdevelop; suppresses those messages by default. Mark the checkbox if you want to protocol which directories <command>make</command> worked in. +The <command>make</command> tool usually will display messages like <quote>Entering directory</quote>, or <quote>Leaving directory</quote> when it switches the directories it currently works in. As this clutters the messages list in the <guilabel>Messages Output View</guilabel> window, &tdevelop; suppresses those messages by default. Mark the checkbox if you want to protocol which directories <command>make</command> worked in. </para> <note><para> Changes in this setting effect the processing of new messages only. Old directory navigation messages will be kept visible when you switch this feature off. @@ -263,14 +263,14 @@ Changes in this setting effect the processing of new messages only. Old director <term id="ui-designer-integration"><guilabel>UI Designer Integration</guilabel></term> <listitem> <para> -This let you choose the way you want <filename>.ui</filename> files to be displayed in &kdevelop;. &kdevelop; comes with its own UI designer called KDeveDesigner that can either be embedded or be run as a separate program. Qt Designer can also be used to edit <filename>.ui</filename> files. +This let you choose the way you want <filename>.ui</filename> files to be displayed in &tdevelop;. &tdevelop; comes with its own UI designer called KDeveDesigner that can either be embedded or be run as a separate program. Qt Designer can also be used to edit <filename>.ui</filename> files. </para> <itemizedlist> <listitem><para> - Use &kdevelop;'s embedded designer - </para><para>This uses &kdevelop; own designer embedded within &kdevelop;</para></listitem> + Use &tdevelop;'s embedded designer + </para><para>This uses &tdevelop; own designer embedded within &tdevelop;</para></listitem> <listitem><para> - Run &kdevelop;'s designer as a separate application + Run &tdevelop;'s designer as a separate application </para><para>The KDevDesigner application will be run separately in its own window.</para> <screenshot> <mediaobject> @@ -285,7 +285,7 @@ This let you choose the way you want <filename>.ui</filename> files to be displa </listitem> <listitem><para> Run Qt Designer - </para><para>Qt Designer from your Qt installation will be started externally whenever you click on a <filename>.ui</filename> file in &kdevelop;.</para></listitem> + </para><para>Qt Designer from your Qt installation will be started externally whenever you click on a <filename>.ui</filename> file in &tdevelop;.</para></listitem> </itemizedlist> </listitem> </varlistentry> @@ -322,7 +322,7 @@ You choose here which terminal you want to be integrated within KDevelop. <primary>switch UI modes</primary></indexterm> <para> -As already said in the <link linkend="uimodes-survey">Available User Interface Modes</link> chapter there are five different ways the &kdevelop; work area may be set up, namely: +As already said in the <link linkend="uimodes-survey">Available User Interface Modes</link> chapter there are five different ways the &tdevelop; work area may be set up, namely: </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 &kdevelop;...</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> +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> @@ -368,7 +368,7 @@ Select the radio button of the user interface mode you want to switch to, then c </para> <note><para> -Do not forget to restart &kdevelop; in order to let any of these selections take effect. +Do not forget to restart &tdevelop; in order to let any of these selections take effect. </para></note> <para> @@ -384,26 +384,26 @@ In <guilabel>Simplified IDEAl window mode</guilabel> and in <guilabel>IDEAl wind <term id="setup-ui-tabs">Configuring the Documents Tab Bar Display</term> <listitem> <para> -In the IDEAl and tabbed pages modes there will be named tabs on top of the document windows by default, so you can easily select different documents with a &LMB; click. If you prefer to provide more space for the document windows in the &kdevelop; main work area, you may change to another behaviour in the <guilabel>Use Tabs</guilabel> configuration section. +In the IDEAl and tabbed pages modes there will be named tabs on top of the document windows by default, so you can easily select different documents with a &LMB; click. If you prefer to provide more space for the document windows in the &tdevelop; main work area, you may change to another behaviour in the <guilabel>Use Tabs</guilabel> configuration section. </para> <variablelist> <varlistentry> <term><guilabel>Always</guilabel></term> <listitem><para> - This is the default — show a tab comprising an icon and the document name on top of any document window in the &kdevelop; main area display. + This is the default — show a tab comprising an icon and the document name on top of any document window in the &tdevelop; main area display. </para></listitem> </varlistentry> <varlistentry> <term><guilabel>When more than one</guilabel></term> <listitem><para> - Do not show a tab when only one document is displayed. If there is more than one document, however, &kdevelop; will display an according tab bar as in the <guilabel>Always</guilabel> selection above. You may want to select this mode if you work on a single document most of the time as this provides more vertical space. + Do not show a tab when only one document is displayed. If there is more than one document, however, &tdevelop; will display an according tab bar as in the <guilabel>Always</guilabel> selection above. You may want to select this mode if you work on a single document most of the time as this provides more vertical space. </para></listitem> </varlistentry> <varlistentry> <term><guilabel>Never</guilabel></term> <listitem><para> - Never show any document selection tab. You may prefer this mode if you seldom use the mouse to switch between documents. It provides more vertical space for all document windows. To select another the document window or to close any, use the &kdevelop; <guimenu>Window</guimenu> menu. + Never show any document selection tab. You may prefer this mode if you seldom use the mouse to switch between documents. It provides more vertical space for all document windows. To select another the document window or to close any, use the &tdevelop; <guimenu>Window</guimenu> menu. </para></listitem> </varlistentry> </variablelist> @@ -415,7 +415,7 @@ In the IDEAl and tabbed pages modes there will be named tabs on top of the docum Tab</term> <listitem> <para> -When you configured &kdevelop; to display the documents tab bar, either always or when more than one document is displayed in the main work area, you may add more functionality to the tabs beyond their document selection capability. Use the <guilabel>Use Close On Hover</guilabel> coniguration section for this. +When you configured &tdevelop; to display the documents tab bar, either always or when more than one document is displayed in the main work area, you may add more functionality to the tabs beyond their document selection capability. Use the <guilabel>Use Close On Hover</guilabel> coniguration section for this. </para> <variablelist> @@ -428,13 +428,13 @@ When you configured &kdevelop; to display the documents tab bar, either always o <varlistentry> <term><guilabel>Yes</guilabel></term> <listitem><para> - When you selected this radio button, &kdevelop; will allow to close a document window by a &LMB; click. Use the mouse to point at the small icon on the on the left tab border. It will change to a close symbol. Now click with the &LMB; on this changed symbol and &kdevelop; will close the according document window. + When you selected this radio button, &tdevelop; will allow to close a document window by a &LMB; click. Use the mouse to point at the small icon on the on the left tab border. It will change to a close symbol. Now click with the &LMB; on this changed symbol and &tdevelop; will close the according document window. </para></listitem> </varlistentry> <varlistentry> <term><guilabel>Yes, Delayed</guilabel></term> <listitem><para> - After selecting this radio button, &kdevelop; will allow to close a document window as shown in the <guilabel>Yes</guilabel> case above. The icon will not change instantly, however, but there will be a short delay before the close icon shows up. + After selecting this radio button, &tdevelop; will allow to close a document window as shown in the <guilabel>Yes</guilabel> case above. The icon will not change instantly, however, but there will be a short delay before the close icon shows up. </para></listitem> </varlistentry> </variablelist> @@ -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>&kdevelop; 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>&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> @@ -560,7 +560,7 @@ To select a new editor, click on the arrow on the drop down list field. Dependin </variablelist> <para> -These editor interfaces are fully integrated in the &kdevelop; IDE concept. Particularly the possibility to jump to the offending source code line by just clicking on an error message in the <guilabel>Messages Output View</guilabel> window has been provided. +These editor interfaces are fully integrated in the &tdevelop; IDE concept. Particularly the possibility to jump to the offending source code line by just clicking on an error message in the <guilabel>Messages Output View</guilabel> window has been provided. </para> <note><para> @@ -655,15 +655,15 @@ KDevelop lets you use editor interfaces which have registered with &kde; and tha <title>Selecting a Source Format Style</title> <para> -&kdevelop; automatically formats a source text in a predefined style. This style is highly configurable. +&tdevelop; automatically formats a source text in a predefined style. This style is highly configurable. </para> <note><para> -The reformat source feature is currently available for C, C++, and &Java; only. Especially you cannot use it for scripting languages like ⪚ PHP. This is because &kdevelop; uses the <ulink url="http://astyle.sourceforge.net/">astyle</ulink> application to implement this feature. +The reformat source feature is currently available for C, C++, and &Java; only. Especially you cannot use it for scripting languages like ⪚ PHP. This is because &tdevelop; uses the <ulink url="http://astyle.sourceforge.net/">astyle</ulink> application to implement this feature. </para></note> <para> -To set up a specific format style, select <menuchoice> <guimenu>Settings</guimenu> <guimenuitem>Configure &kdevelop;..</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>. +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> @@ -930,7 +930,7 @@ namespace foospace <term>Controlling Extra Spaces</term> <listitem> <para> -By default &kdevelop; does minimize the use of spaces in source texts. +By default &tdevelop; does minimize the use of spaces in source texts. </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 &kdevelop; 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 &kdevelop;..</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. +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> @@ -1069,7 +1069,7 @@ variables' mechanism. You can set up it's behaviour in the <title>Configuring the File Selector</title> <para> -&kdevelop; provides a <guilabel>File Selector</guilabel> plugin which, when +&tdevelop; provides a <guilabel>File Selector</guilabel> plugin which, when loaded at start-up, allows to navigate to any file or directory in the system. </para> @@ -1088,7 +1088,7 @@ system. <para>The behaviour of the <guilabel>File Selector</guilabel> can be highly configured. Select <menuchoice> <guimenu>Settings</guimenu> -<guimenuitem>Configure &kdevelop;..</guimenuitem> </menuchoice> from the +<guimenuitem>Configure &tdevelop;..</guimenuitem> </menuchoice> from the 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> @@ -1240,11 +1240,11 @@ entries as follows.</para> <term>Controlling What Should be Remembered Between Sessions</term> <listitem> <para> -By default the <guilabel>File Selector</guilabel> is set up so that it shows the display of the most recent session again at the next &kdevelop; start-up. You may change this behaviour in the <guilabel>Session</guilabel> configuration group. +By default the <guilabel>File Selector</guilabel> is set up so that it shows the display of the most recent session again at the next &tdevelop; start-up. You may change this behaviour in the <guilabel>Session</guilabel> configuration group. </para> <note><para> -If &kdevelop; was automatically restarted by the &kde; session manager the changes in these settings will have no effect. In this case location and filter settings of the most recent &kde; session will always be restored. +If &tdevelop; was automatically restarted by the &kde; session manager the changes in these settings will have no effect. In this case location and filter settings of the most recent &kde; session will always be restored. </para></note> </listitem> </varlistentry> @@ -1310,7 +1310,7 @@ If &kdevelop; was automatically restarted by the &kde; session manager the chang <title>Configuring the Documentation</title> <para> -&kdevelop; contains a very powerful documentation facility which provides access to several kinds of extensive documentation. In ⪚ IDEAl mode you find a <guilabel>Documentation</guilabel> tab at the right border of the work area. +&tdevelop; contains a very powerful documentation facility which provides access to several kinds of extensive documentation. In ⪚ IDEAl mode you find a <guilabel>Documentation</guilabel> tab at the right border of the work area. </para> <screenshot> @@ -1318,19 +1318,19 @@ If &kdevelop; was automatically restarted by the &kde; session manager the chang <imageobject> <imagedata fileref="documents-contents.png" format="PNG"/> </imageobject> -<textobject><phrase>The &kdevelop; documentation window in IDEAl mode</phrase></textobject> +<textobject><phrase>The &tdevelop; documentation window in IDEAl mode</phrase></textobject> <caption><para> - The &kdevelop; documentation window (IDEAl mode) + The &tdevelop; documentation window (IDEAl mode) </para></caption> </mediaobject> </screenshot> <note><para> -&kdevelop; must have loaded the <guilabel>Documentation</guilabel> plugin in order to view the documentation tree. See the <link linkend="setup-plugins">Plugin Tools</link> section for more info. +&tdevelop; must have loaded the <guilabel>Documentation</guilabel> plugin in order to view the documentation tree. See the <link linkend="setup-plugins">Plugin Tools</link> section for more info. </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 &kdevelop;..</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. +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> @@ -1347,7 +1347,7 @@ The thus displayed <link linkend="configure-docu-general">configuration page</li <title>Setting Up Documentation Collections</title> <para> -The documentation configuration settings have been divided into a series of documentation collections, each providing access to documentation files of some unique format and content type. These setups control which documentation items will be listed on the <guilabel>Contents</guilabel> page of the &kdevelop; <guilabel>Documentation</guilabel> facility, and how the user may access documentation details by indexed and full text searches. +The documentation configuration settings have been divided into a series of documentation collections, each providing access to documentation files of some unique format and content type. These setups control which documentation items will be listed on the <guilabel>Contents</guilabel> page of the &tdevelop; <guilabel>Documentation</guilabel> facility, and how the user may access documentation details by indexed and full text searches. </para> <para> The <guilabel>Documentation</guilabel> tab provides a series of configuration pages which are ordered vertically like a stack of index cards. One page at a time will open after a click on its index card title: @@ -1356,7 +1356,7 @@ The <guilabel>Documentation</guilabel> tab provides a series of configuration pa <member><link linkend="setup-docu-general-qt">&Qt; Documentation Collection</link></member> <member><link linkend="setup-docu-general-chm">CHM Documentation Collection</link></member> <member><link linkend="setup-docu-general-dox">Doxygen Documentation Collection</link></member> - <member><link linkend="setup-docu-general-toc">&kdevelop; TOC Documentation Collection</link></member> + <member><link linkend="setup-docu-general-toc">&tdevelop; TOC Documentation Collection</link></member> <member><link linkend="setup-docu-general-devhelp">Devhelp Documentation Collection</link></member> <member><link linkend="setup-docu-general-custom">Custom Documentation Collection</link></member> </simplelist> @@ -1445,7 +1445,7 @@ Every documentation setup page shows the listed documentation items in a table w <term><guilabel>TOC</guilabel></term> <listitem> <para> - If this check box is marked, this documentation item will show up on the <guilabel>Contents</guilabel> page of the &kdevelop; <guilabel>Documentation</guilabel> facility. + If this check box is marked, this documentation item will show up on the <guilabel>Contents</guilabel> page of the &tdevelop; <guilabel>Documentation</guilabel> facility. </para> <note><para> Unchecking the <guilabel>TOC</guilabel> check box will in turn disable the <guilabel>Index</guilabel> and <guilabel>Search</guilabel> check boxes (see below). Thus you cannot have documentation collection items indexed but not shown in the contents. @@ -1456,7 +1456,7 @@ Every documentation setup page shows the listed documentation items in a table w <term><guilabel>Index</guilabel></term> <listitem> <para> - If this check box is marked, an internal index will be built of this documentation item. This provides fast access to the documentation by the use of the <guilabel>Index</guilabel> and (optionally) <guilabel>Finder</guilabel> pages of the &kdevelop; <guilabel>Documentation</guilabel> facility. + If this check box is marked, an internal index will be built of this documentation item. This provides fast access to the documentation by the use of the <guilabel>Index</guilabel> and (optionally) <guilabel>Finder</guilabel> pages of the &tdevelop; <guilabel>Documentation</guilabel> facility. </para> <note> <para> @@ -1472,14 +1472,14 @@ Every documentation setup page shows the listed documentation items in a table w <term><guilabel>Search</guilabel></term> <listitem> <para> - If this check box is marked, the contents of this documentation item will be included in the full text search path of the <guilabel>Search</guilabel> page of the &kdevelop; <guilabel>Documentation</guilabel> facility. + If this check box is marked, the contents of this documentation item will be included in the full text search path of the <guilabel>Search</guilabel> page of the &tdevelop; <guilabel>Documentation</guilabel> facility. </para> <note> <para> - &kdevelop; utilizes the htdig application collection to perform full text searches. This search is done over an internal index, the htdig machinery has to build before it can be used. + &tdevelop; utilizes the htdig application collection to perform full text searches. This search is done over an internal index, the htdig machinery has to build before it can be used. </para> <para> - Any change of the <guilabel>Search</guilabel> check box marks will thus effect the search runs only after you rebuilt the index on the <guilabel>Search</guilabel> page of the &kdevelop; <guilabel>Documentation</guilabel> facility. + Any change of the <guilabel>Search</guilabel> check box marks will thus effect the search runs only after you rebuilt the index on the <guilabel>Search</guilabel> page of the &tdevelop; <guilabel>Documentation</guilabel> facility. </para> </note> </listitem> @@ -1487,13 +1487,13 @@ Every documentation setup page shows the listed documentation items in a table w <varlistentry> <term><guilabel>Title</guilabel></term> <listitem><para> - This is the name of the Documentation item as it will be shown on the <guilabel>Contents</guilabel> page of the &kdevelop; <guilabel>Documentation</guilabel> facility. + This is the name of the Documentation item as it will be shown on the <guilabel>Contents</guilabel> page of the &tdevelop; <guilabel>Documentation</guilabel> facility. </para></listitem> </varlistentry> </variablelist> <note><para> -Former &kdevelop; versions allowed to select the documentation items to be displayed on a per-project basis. This is not available any more. +Former &tdevelop; versions allowed to select the documentation items to be displayed on a per-project basis. This is not available any more. </para></note> </listitem> </varlistentry> @@ -1521,7 +1521,7 @@ On this configuration page all &Qt; documentation is set up. </screenshot> <para> -Normally &kdevelop; will fill this in on its first start-up. It looks for standard <filename>*.xml</filename>, or <filename>*.dcf</filename> documentation files in the &Qt; installation directory. The table to the left lists the files &kdevelop; found by their standard titles. +Normally &tdevelop; will fill this in on its first start-up. It looks for standard <filename>*.xml</filename>, or <filename>*.dcf</filename> documentation files in the &Qt; installation directory. The table to the left lists the files &tdevelop; found by their standard titles. </para> <para> @@ -1529,11 +1529,11 @@ If you have a non-standard installation, either there will be no information lis </para> <note><para> -&kdevelop; will use the titles already provided by the installed &Qt; documentation. Hence the <guilabel>Title</guilabel> field in the <guilabel>Documentation Catalog Properties</guilabel> dialog is inaccessible. +&tdevelop; will use the titles already provided by the installed &Qt; documentation. Hence the <guilabel>Title</guilabel> field in the <guilabel>Documentation Catalog Properties</guilabel> dialog is inaccessible. </para></note> <para> -By default, not all &Qt; documentation will be shown on the <guilabel>Contents</guilabel> page of the &kdevelop; <guilabel>Documentation</guilabel> facility. Use the <guilabel>TOC</guilabel> check box in the <link linkend="setup-docu-columns">setup table</link> to select the documentation to be shown. +By default, not all &Qt; documentation will be shown on the <guilabel>Contents</guilabel> page of the &tdevelop; <guilabel>Documentation</guilabel> facility. Use the <guilabel>TOC</guilabel> check box in the <link linkend="setup-docu-columns">setup table</link> to select the documentation to be shown. </para> <para> @@ -1562,7 +1562,7 @@ On this configuration page you may collect documentation according to the &Micro </screenshot> <para> -By default, this configuration page will be empty (as shown above). You may add new entries using the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field. &kdevelop; will filter <filename>*.chm</filename> files in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. +By default, this configuration page will be empty (as shown above). You may add new entries using the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field. &tdevelop; will filter <filename>*.chm</filename> files in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. </para> <para> @@ -1594,13 +1594,13 @@ On this configuration page all &API; documentation generated by &doxygen; is set In short, such an &API; documents the interface to certain library functions. The &API; documentation on this page should be produced by the externally provided <ulink url="http://www.stack.nl/~dimitri/doxygen/">&doxygen;</ulink> tool. </para> <para> -&doxygen; generated &API; documentationconsists of a series of <filename>html</filename> files, starting with <filename>index.html</filename>. Additionally there may exist <filename>tag</filename> files which contain information to link to already existing &API; documentations. Thus &kdevelop; will look for <filename>index.html</filename> and <filename>*.tag</filename> files when seaching for &doxygen; generated &API; documentation. +&doxygen; generated &API; documentationconsists of a series of <filename>html</filename> files, starting with <filename>index.html</filename>. Additionally there may exist <filename>tag</filename> files which contain information to link to already existing &API; documentations. Thus &tdevelop; will look for <filename>index.html</filename> and <filename>*.tag</filename> files when seaching for &doxygen; generated &API; documentation. </para> <para> There are some structural constraints assumed when searching for &doxygen; generated &API; documentation. The directory in which the <filename>index.html</filename> file resides should contain subdirectories with separate documentation collections. Each of these subdirectories is assumed to contain a <filename>.tag</filename> file and a <filename class="directory">html/</filename> subdirectory. </para> <para> -You may have a look at <filename class="directory">$<envar>KDEDIR</envar>/share/doc/HTML/en/kdelibs-apidocs</filename> for an example of such a &doxygen; &API; documentation layout. +You may have a look at <filename class="directory">$<envar>KDEDIR</envar>/share/doc/HTML/en/tdelibs-apidocs</filename> for an example of such a &doxygen; &API; documentation layout. </para> <note><para> @@ -1608,25 +1608,25 @@ The older &kde; <ulink url="http://sirtaj.net/projects/kdoc/">KDoc</ulink> gener </para></note> <para> -&kdevelop; will have filled in a link to the current &kde; Libraries &API;, provided it found one. There are several ways for &kdevelop; to find out: +&tdevelop; will have filled in a link to the current &kde; Libraries &API;, provided it found one. There are several ways for &tdevelop; to find out: </para> <itemizedlist> <listitem><para> Either you provided the <command>configure</command> command with the - <option>--with-kdelibsdoxy-dir</option> option when you compiled - &kdevelop; (see the <link linkend="make-api">How to Obtain a &kdevelop; &API; Documentation</link> chapter). + <option>--with-tdelibsdoxy-dir</option> option when you compiled + &tdevelop; (see the <link linkend="make-api">How to Obtain a &tdevelop; &API; Documentation</link> chapter). </para></listitem> <listitem><para> Or the <command>configure</command> command did automatically find a &doxygen; generated &kde; Libraries &API; in one of several standard locations it knows of. </para></listitem> <listitem><para> - Or as a last resort the <filename class="directory">$<envar>KDEDIR</envar>/share/doc/HTML/en/kdelibs-apidocs/</filename> was found at the first &kdevelop; startup. + Or as a last resort the <filename class="directory">$<envar>KDEDIR</envar>/share/doc/HTML/en/tdelibs-apidocs/</filename> was found at the first &tdevelop; startup. </para></listitem> </itemizedlist> <para> -If &kdevelop; did not find a valid &doxygen; generated &kde; Libraries &API; at its first start-up the <guilabel>Doxygen Documentation Collection</guilabel> list will be empty. +If &tdevelop; did not find a valid &doxygen; generated &kde; Libraries &API; at its first start-up the <guilabel>Doxygen Documentation Collection</guilabel> list will be empty. </para> <para> @@ -1634,12 +1634,12 @@ You may add your own &API; documentation entries (⪚ from your current project </para> <note><para> -&kdevelop; uses the title information from the <filename>index.html</filename>. Hence the <guilabel>Title</guilabel> field in the <guilabel>Documentation Catalog Properties</guilabel> dialog is inaccessible. +&tdevelop; uses the title information from the <filename>index.html</filename>. Hence the <guilabel>Title</guilabel> field in the <guilabel>Documentation Catalog Properties</guilabel> dialog is inaccessible. </para></note> <tip> <para> - The &kde; system provides more &API; documentation than the &kde; Libraries &API; only. You will need additional interfaces information if you want to ⪚ include the &kate; part into you programs. For this &kate; part &API; for example you should compile and install the &kde; Base Libraries &API; from the <ulink url="http://developer.kde.org/source/index.html">sources</ulink> (using the <command>make apidox</command> and <command>make install</command> commands on the <filename class="directory">kdebase</filename> sources) and then add an entry to the <guilabel>Doxygen Documentation Collection</guilabel> list like this: + The &kde; system provides more &API; documentation than the &kde; Libraries &API; only. You will need additional interfaces information if you want to ⪚ include the &kate; part into you programs. For this &kate; part &API; for example you should compile and install the &kde; Base Libraries &API; from the <ulink url="http://developer.kde.org/source/index.html">sources</ulink> (using the <command>make apidox</command> and <command>make install</command> commands on the <filename class="directory">tdebase</filename> sources) and then add an entry to the <guilabel>Doxygen Documentation Collection</guilabel> list like this: </para> <screenshot><mediaobject> <imageobject> @@ -1656,7 +1656,7 @@ You may add your own &API; documentation entries (⪚ from your current project </tip> <note><para> -You must put the &API; of your current project into this <guilabel>Doxygen Documentation Collection</guilabel> as well. Former &kdevelop; versions did put it into the documentation tree on a per-project basis. This is not provided any more. +You must put the &API; of your current project into this <guilabel>Doxygen Documentation Collection</guilabel> as well. Former &tdevelop; versions did put it into the documentation tree on a per-project basis. This is not provided any more. </para></note> </sect3> <!-- setup-docu-general-dox --> @@ -1665,7 +1665,7 @@ You must put the &API; of your current project into this <guilabel>Doxygen Docum <title>Handling Structured Documentation (KDevelopTOC Files)</title> <para> -The main bulk of the &kdevelop; 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. +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> @@ -1680,31 +1680,31 @@ The main bulk of the &kdevelop; documentation facility provides immediate access </screenshot> <para> -&kdevelop; 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>. +&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> -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><index></computeroutput> tag. Thus the <guilabel>Index</guilabel> check box will be enabled ony when &kdevelop; finds an <computeroutput><index></computeroutput> tag in the <filename>.toc</filename> file. (For more detail see the description below in the <link linkend="setup-docu-general-toc-files">&kdevelop; 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><index></computeroutput> tag. Thus the <guilabel>Index</guilabel> check box will be enabled ony when &tdevelop; finds an <computeroutput><index></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. </para> <para> -You may add new entries using the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field. &kdevelop; will filter <filename>*.toc</filename> files in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. +You may add new entries using the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field. &tdevelop; will filter <filename>*.toc</filename> files in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. </para> <note><para> -Other than former &kdevelop; versions will the <guibutton>Remove</guibutton> button not change the <filename>*.toc</filename> files on disk, so the remove operation is safe now. +Other than former &tdevelop; versions will the <guibutton>Remove</guibutton> button not change the <filename>*.toc</filename> files on disk, so the remove operation is safe now. </para></note> </sect3> <!-- setup-docu-general-toc --> <sect3 id="setup-docu-general-toc-files"> -<title>&kdevelop; TOC Files</title> +<title>&tdevelop; TOC Files</title> <para> -There is a special feature associated with this. To illustrate, follow these steps: In the documentation tree find an entry shortly below the &Qt;/&kde; documentation (⪚ <quote>KDE2 Development Book (kde.org)</quote>). Click on the plus sign next to it. A tree will open where you can quickly navigate to subsequent chapters nested several levels deep, all offline. But if you finally select one of the chapters, &kdevelop; will in many cases try to access a <emphasis>remote</emphasis> documentation file. +There is a special feature associated with this. To illustrate, follow these steps: In the documentation tree find an entry shortly below the &Qt;/&kde; documentation (⪚ <quote>KDE2 Development Book (kde.org)</quote>). Click on the plus sign next to it. A tree will open where you can quickly navigate to subsequent chapters nested several levels deep, all offline. But if you finally select one of the chapters, &tdevelop; will in many cases try to access a <emphasis>remote</emphasis> documentation file. </para> <para> @@ -1712,15 +1712,15 @@ The rationale behind this is not only to locally navigate remote documentation w </para> <para> -Such structured access is made possible through the use of special <quote>table of content</quote> files, which are denoted by <filename>.toc</filename> filename extensions. Any such &kdevelop; TOC file contains an &XML; structured description of the document to be accessed. +Such structured access is made possible through the use of special <quote>table of content</quote> files, which are denoted by <filename>.toc</filename> filename extensions. Any such &tdevelop; TOC file contains an &XML; structured description of the document to be accessed. </para> <variablelist> <varlistentry> -<term>Standard Directory of &kdevelop; TOC Files</term> +<term>Standard Directory of &tdevelop; TOC Files</term> <listitem> <para> -When &kdevelop; was installed usually a series of predefined <filename>.toc</filename> files has been put into the <filename class="directory">$KDEDIR/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. +When &tdevelop; was installed usually a series of predefined <filename>.toc</filename> files has been put into the <filename class="directory">$KDEDIR/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> @@ -1730,16 +1730,16 @@ When &kdevelop; was installed usually a series of predefined <filename>.toc</fil <!-- this first revision is done. --> <variablelist id="toc-file-structure"> - <title>Basic Structure of &kdevelop; TOC Files</title> + <title>Basic Structure of &tdevelop; TOC Files</title> <varlistentry> <term>header</term> <listitem> <simplelist> <member> - <computeroutput><!DOCTYPE kdeveloptoc></computeroutput> + <computeroutput><!DOCTYPE tdeveloptoc></computeroutput> </member> <member> - <computeroutput><kdeveloptoc></computeroutput> + <computeroutput><tdeveloptoc></computeroutput> </member> <member> <emphasis>(title)</emphasis> @@ -1754,11 +1754,11 @@ When &kdevelop; was installed usually a series of predefined <filename>.toc</fil <emphasis>(index structure)</emphasis> </member> <member> - <computeroutput></kdeveloptoc></computeroutput> + <computeroutput></tdeveloptoc></computeroutput> </member> </simplelist> <para> - This &XML; structure will be parsed by the &kdevelop; <guilabel>Documentation</guilabel> plugin to set up the documentation tree contents and to guide the user in navigating the documentation. It contains all information necessary to display titles and access the documentation file contents. + This &XML; structure will be parsed by the &tdevelop; <guilabel>Documentation</guilabel> plugin to set up the documentation tree contents and to guide the user in navigating the documentation. It contains all information necessary to display titles and access the documentation file contents. </para> </listitem> </varlistentry> @@ -1773,7 +1773,7 @@ When &kdevelop; was installed usually a series of predefined <filename>.toc</fil </member> </simplelist> <para> - This is the title &kdevelop; will display at the basic levels in the documentation tree. + This is the title &tdevelop; will display at the basic levels in the documentation tree. </para> <note><para> This displayed title cannot be changed by the user. If you want another text be displayed, you must manually change the <computeroutput><title></computeroutput> entry in the <filename>.toc</filename> file. @@ -1826,7 +1826,7 @@ When &kdevelop; was installed usually a series of predefined <filename>.toc</fil Any <computeroutput><tocsecti></computeroutput> entry must have a <computeroutput>name="xxx"</computeroutput> attribute associated with it (the "xxx" denotes the actual title string). This name will be displayed as level title in the documentation tree. It should correspond to an actual documentation section. </para> <para> - There may be an <computeroutput>url=""</computeroutput> attribute associated with any <emphasis>i</emphasis> nesting level. When the user clicks on a section title in the documentation tree &kdevelop; will try to access the file at the location pointed to by the combined base and section &URL;. + There may be an <computeroutput>url=""</computeroutput> attribute associated with any <emphasis>i</emphasis> nesting level. When the user clicks on a section title in the documentation tree &tdevelop; will try to access the file at the location pointed to by the combined base and section &URL;. </para> <para> The <computeroutput><tocsectn/></computeroutput> entry must have an <computeroutput>url=""</computeroutput> attribute whatsoever. @@ -1869,7 +1869,7 @@ When &kdevelop; was installed usually a series of predefined <filename>.toc</fil <title>DevHelp Documentation</title> <para> -DevHelp documentation is another means of structured documentation access. It uses structured table of content files denoted by a <filename>.devhelp</filename> extension similar to <link linkend="setup-docu-general-toc-files">&kdevelop; TOC files</link> to access documentation for the GNOME 2 desktop. +DevHelp documentation is another means of structured documentation access. It uses structured table of content files denoted by a <filename>.devhelp</filename> extension similar to <link linkend="setup-docu-general-toc-files">&tdevelop; TOC files</link> to access documentation for the GNOME 2 desktop. </para> <para> You can control which DevHelp files should be accessible on the <guilabel>DevHelp Documentation Collection</guilabel> configuration page. @@ -1891,11 +1891,11 @@ DevHelp files originally were accessible on the <ulink url="http://lidn.sourcefo </para> <para> -When &kdevelop; is installed it will attempt to find all <filename>.devhelp</filename> files in some standard places in the system, ⪚ in the subdirectories of <filename class="directory">/opt/gnome/share/</filename>. Initially these files will not 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>. +When &tdevelop; is installed it will attempt to find all <filename>.devhelp</filename> files in some standard places in the system, ⪚ in the subdirectories of <filename class="directory">/opt/gnome/share/</filename>. Initially these files will not 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> -You may add new entries using the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field. &kdevelop; will filter <filename>*.toc</filename> files in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. +You may add new entries using the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field. &tdevelop; will filter <filename>*.toc</filename> files in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. </para> </sect3> <!-- setup-docu-general-devhelp --> @@ -1919,14 +1919,14 @@ This is for your own purpose. You may add almost any documentation files here, p </screenshot> <para> -Usually this collection will be empty at first &kdevelop; startup. We have filled in a deliberate item to show the entry structure. +Usually this collection will be empty at first &tdevelop; startup. We have filled in a deliberate item to show the entry structure. </para> <para> -Handling is straightforward here. Use the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field to add, edit or remove the document items. &kdevelop; will not filter anything in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. +Handling is straightforward here. Use the <link linkend="setup-docu-buttons">buttons</link> to the right of the list field to add, edit or remove the document items. &tdevelop; will not filter anything in the directory dialog associated to the <guibutton>Add</guibutton> and <guibutton>Edit</guibutton> buttons. </para> <para> -You will have to explicitely select the items for display in the &kdevelop; documentation facility. Mark the <guilabel>TOC</guilabel> check box of the entry in the <link linkend="setup-docu-columns">setup table</link>. +You will have to explicitely select the items for display in the &tdevelop; documentation facility. Mark the <guilabel>TOC</guilabel> check box of the entry in the <link linkend="setup-docu-columns">setup table</link>. </para> <note><para> |