summaryrefslogtreecommitdiffstats
path: root/doc/kdevelop/kdevelop-survey.docbook
diff options
context:
space:
mode:
Diffstat (limited to 'doc/kdevelop/kdevelop-survey.docbook')
-rw-r--r--doc/kdevelop/kdevelop-survey.docbook62
1 files changed, 31 insertions, 31 deletions
diff --git a/doc/kdevelop/kdevelop-survey.docbook b/doc/kdevelop/kdevelop-survey.docbook
index 9fe32d2d..0f117958 100644
--- a/doc/kdevelop/kdevelop-survey.docbook
+++ b/doc/kdevelop/kdevelop-survey.docbook
@@ -1,4 +1,4 @@
-<chapter id="kdevelop-survey">
+<chapter id="tdevelop-survey">
<chapterinfo>
<authorgroup>
@@ -7,18 +7,18 @@
</authorgroup>
</chapterinfo>
-<title>Overview of &kdevelop; Features</title>
+<title>Overview of &tdevelop; Features</title>
-<indexterm zone="kdevelop-survey">
- <primary>&kdevelop;</primary>
+<indexterm zone="tdevelop-survey">
+ <primary>&tdevelop;</primary>
<secondary>survey</secondary></indexterm>
-<indexterm zone="kdevelop-survey">
+<indexterm zone="tdevelop-survey">
<primary>overall view</primary></indexterm>
-<indexterm zone="kdevelop-survey">
+<indexterm zone="tdevelop-survey">
<primary>survey</primary></indexterm>
<para>
-&kdevelop; integrates a lot of tools, scripts, and templates in a common user interface. Basically it consists of
+&tdevelop; integrates a lot of tools, scripts, and templates in a common user interface. Basically it consists of
<itemizedlist>
<listitem><para>
@@ -40,7 +40,7 @@
various <link linkend="class-browsers">class browsers</link> to aid you in maintaining the classes and their relationships of your object-oriented programming project,
</para></listitem>
<listitem><para>
- a <link linkend="debugger">debugger interface</link> to find and remove program errors from within &kdevelop;, and
+ a <link linkend="debugger">debugger interface</link> to find and remove program errors from within &tdevelop;, and
</para></listitem>
<listitem><para>
several <link linkend="plugin-tools">plugin tools</link>, extensible modules which can be loaded at runtime and on demand. This allows you to only turn on those features you really need.
@@ -53,12 +53,12 @@
<note>
<para>
- In fact there are three &kdevelop;-based applications:
+ In fact there are three &tdevelop;-based applications:
</para>
<itemizedlist>
- <listitem><para>The &kdevelop; IDE &mdash; this is the place where you will usually work.</para></listitem>
- <listitem><para>The stand-alone &kdevelop; Assistant documentation browser &mdash; isolates all the powerful documentation facilities of the &kdevelop; IDE in a separate tool. This comes in handy when you want to look up some programming documentation but do not want to start the full IDE.</para></listitem>
- <listitem><para>The &kdevelop; Designer &mdash; enhances the &Qt; User Interface Designer by &kde; specific elements and integrates nicely in the &kdevelop; IDE.</para></listitem>
+ <listitem><para>The &tdevelop; IDE &mdash; this is the place where you will usually work.</para></listitem>
+ <listitem><para>The stand-alone &tdevelop; Assistant documentation browser &mdash; isolates all the powerful documentation facilities of the &tdevelop; IDE in a separate tool. This comes in handy when you want to look up some programming documentation but do not want to start the full IDE.</para></listitem>
+ <listitem><para>The &tdevelop; Designer &mdash; enhances the &Qt; User Interface Designer by &kde; specific elements and integrates nicely in the &tdevelop; IDE.</para></listitem>
</itemizedlist>
</note>
@@ -67,11 +67,11 @@
<title>Available User Interface Modes</title>
<indexterm zone="uimodes-survey">
- <primary>&kdevelop;</primary>
+ <primary>&tdevelop;</primary>
<secondary>user interface modes</secondary></indexterm>
<indexterm zone="uimodes-survey">
<primary>user interface</primary>
- <secondary>&kdevelop; modes</secondary></indexterm>
+ <secondary>&tdevelop; modes</secondary></indexterm>
<indexterm zone="uimodes-survey">
<primary>UI modes</primary></indexterm>
<indexterm zone="uimodes-survey">
@@ -84,7 +84,7 @@
<primary>IDEAl</primary></indexterm>
<para>
-&kdevelop; offers developers four separate user interface modes (click on the mode name to view an example):
+&tdevelop; offers developers four separate user interface modes (click on the mode name to view an example):
<itemizedlist>
<listitem><para><link linkend="ideal-desc">IDEAl</link></para>
<para>
@@ -160,7 +160,7 @@ To switch the user interface mode select <menuchoice> <guimenu>Settings</guimenu
</screenshot>
<para>
-(Older &kdevelop; versions provide the top mode selection section only.)
+(Older &tdevelop; versions provide the top mode selection section only.)
</para>
<para>
@@ -171,7 +171,7 @@ Dependent on the user interface mode you selected, other configuration sections
</para>
<note><para>
-Do not forget to restart &kdevelop; in order to let your selections take effect.
+Do not forget to restart &tdevelop; in order to let your selections take effect.
</para></note>
</sect2> <!-- uimodes-switch -->
@@ -180,10 +180,10 @@ Do not forget to restart &kdevelop; in order to let your selections take effect.
<title>How to Maximize the Work Space Area</title>
<indexterm zone="maximize-workspace">
- <primary>&kdevelop;</primary>
+ <primary>&tdevelop;</primary>
<secondary>work space</secondary></indexterm>
<indexterm zone="maximize-workspace">
- <primary>&kdevelop;</primary>
+ <primary>&tdevelop;</primary>
<secondary>maximize work space</secondary></indexterm>
<indexterm zone="maximize-workspace">
<primary>user interface</primary>
@@ -254,7 +254,7 @@ To <emphasis>hide</emphasis> the menubar select <menuchoice> <guimenu>Settings</
</sect2> <!-- ui-elements-workarea -->
<sect2 id="ui-elements-titlebar">
-<title>The &kdevelop; Titlebar</title>
+<title>The &tdevelop; Titlebar</title>
<para>
(... to be written ...)
@@ -262,7 +262,7 @@ To <emphasis>hide</emphasis> the menubar select <menuchoice> <guimenu>Settings</
</sect2> <!-- ui-elements-titlebar -->
<sect2 id="ui-elements-statusbar">
-<title>The &kdevelop; Statusbar</title>
+<title>The &tdevelop; Statusbar</title>
<para>
(... to be written ...)
@@ -312,7 +312,7 @@ To <emphasis>hide</emphasis> the menubar select <menuchoice> <guimenu>Settings</
<primary>project management</primary></indexterm>
<para>
-Globally, a project will rely on some form of project management system. &kdevelop; offers four <emphasis>project management systems</emphasis> the programmer can select from when creating a new project.
+Globally, a project will rely on some form of project management system. &tdevelop; offers four <emphasis>project management systems</emphasis> the programmer can select from when creating a new project.
<itemizedlist>
<listitem><para>
@@ -341,7 +341,7 @@ Globally, a project will rely on some form of project management system. &kdeve
<secondary>projects</secondary></indexterm>
<para>
-Projects created with &kdevelop;'s &automanag; make it very easy for developers to use the &GNU; standard development tools. They provide
+Projects created with &tdevelop;'s &automanag; make it very easy for developers to use the &GNU; standard development tools. They provide
<itemizedlist>
<listitem><para>
a better way of <filename>Makefile</filename> generation and
@@ -364,7 +364,7 @@ Projects created with &kdevelop;'s &automanag; make it very easy for developers
<secondary>projects</secondary></indexterm>
<para>
-For developers who enjoy the flexibility and feel of &Qt;'s qmake system, &kdevelop; offers the ability to handle qmake based projects (.pro files) within the &GUI;.
+For developers who enjoy the flexibility and feel of &Qt;'s qmake system, &tdevelop; offers the ability to handle qmake based projects (.pro files) within the &GUI;.
</para>
<para>
For more information on the QMake project manager see the <quote>qmake User Guide</quote> which should be included in your distribution or have a look at the <ulink url="http://doc.trolltech.com/">TROLLTECH Documentation</ulink> home page where you may find the QMake documentation of your <quote>Qt C++ GUI Application Development Toolkit</quote> version.
@@ -382,12 +382,12 @@ For more information on the QMake project manager see the <quote>qmake User Guid
<secondary>projects</secondary></indexterm>
<para>
-CMake will be the &kde; build system for &kde; 4 and &kdevelop; already
+CMake will be the &kde; build system for &kde; 4 and &tdevelop; already
provides you some CMake based templates in C and C++. You only need the cmake
program in your $<envar>PATH</envar> to build them.
</para>
<para>
-To set up a new C or C++ project in &kdevelop; select
+To set up a new C or C++ project in &tdevelop; select
<menuchoice><guimenu>Project</guimenu>
<guimenuitem>New Project...</guimenuitem>
<guimenuitem>C or C++</guimenuitem>
@@ -417,7 +417,7 @@ To set up a new C or C++ project in &kdevelop; select
<secondary>Java</secondary></indexterm>
<para>
-&Java; developers may want to use the Apache ANT project manager for their projects. To set up a new Ant project in &kdevelop; select <menuchoice><guimenu>Project</guimenu>
+&Java; developers may want to use the Apache ANT project manager for their projects. To set up a new Ant project in &tdevelop; select <menuchoice><guimenu>Project</guimenu>
<guimenuitem>New Project...</guimenuitem>
<guimenuitem>Java</guimenuitem>
<guimenuitem>Ant Project</guimenuitem>
@@ -441,7 +441,7 @@ For more information see <ulink url="http://ant.apache.org/">The Apache Ant Proj
<secondary>custom projects</secondary></indexterm>
<para>
-If you prefer to maintain your own <filename>Makefiles</filename> for your project you may use the custom project option of &kdevelop;. This may be feasible in unusually structured projects or if you want to retain full control over the <command>make</command> process.
+If you prefer to maintain your own <filename>Makefiles</filename> for your project you may use the custom project option of &tdevelop;. This may be feasible in unusually structured projects or if you want to retain full control over the <command>make</command> process.
</para>
<para>
Yet, if you do not <emphasis>really need</emphasis> the extra flexibility and control of the custom project manager you should consider &automanag; or one of the other project managers, because they considerably ease the program building and distribution processes.
@@ -470,10 +470,10 @@ The distribution of your applications does not require the end-user to have anyt
<para>
which at least for C++ applications is most often the case. But you can as well distribute <emphasis>binary packages</emphasis> of your application.
<!-- ### more detail on binary construction needed somewhere -->
-In either way, the end-user of your product does not need &kdevelop; installed.
+In either way, the end-user of your product does not need &tdevelop; installed.
</para>
<para>
-For giving away your sources, we advise to include the <emphasis>project file</emphasis> of &kdevelop; as well. This makes it very easy for other developers&mdash;if they use &kdevelop;&mdash;to work with your sources.
+For giving away your sources, we advise to include the <emphasis>project file</emphasis> of &tdevelop; as well. This makes it very easy for other developers&mdash;if they use &tdevelop;&mdash;to work with your sources.
</para>
<para>
For projects where <emphasis>several developers</emphasis>, maybe working on different places, are involved, this should be the case anyway. So you can ensure consistency of the <filename>Makefiles</filename> to not run into trouble.
@@ -486,4 +486,4 @@ Especially on multi language applications, <emphasis>translators</emphasis> won'
</sect1> <!-- makesystems -->
-</chapter> <!-- kdevelop-survey -->
+</chapter> <!-- tdevelop-survey -->