diff options
Diffstat (limited to 'doc/kdevelop/getting-started.docbook')
| -rw-r--r-- | doc/kdevelop/getting-started.docbook | 324 |
1 files changed, 162 insertions, 162 deletions
diff --git a/doc/kdevelop/getting-started.docbook b/doc/kdevelop/getting-started.docbook index 11a08253..33bfee94 100644 --- a/doc/kdevelop/getting-started.docbook +++ b/doc/kdevelop/getting-started.docbook @@ -14,9 +14,9 @@ Keep lines at 80 characters length maximum. </authorgroup> </chapterinfo> -<title>Getting Started with &kdevelop; — a Guided Tour</title> +<title>Getting Started with &tdevelop; — a Guided Tour</title> -<para>Now that you have got your new &kdevelop; &IDE;, how are you going to make +<para>Now that you have got your new &tdevelop; &IDE;, how are you going to make good use of it? As this is a complex application, the learning curve may be somewhat steep, especially if you are not already used to this type of an Integrated Development Environment.</para> @@ -27,7 +27,7 @@ at:</para> <simplelist> <member><link linkend="gettingstarted-overview">A first look — the user -interface elements of the &kdevelop; &IDE;.</link></member> +interface elements of the &tdevelop; &IDE;.</link></member> <member><link linkend="gettingstarted-configure">Doing some initial configuration.</link></member> <member><link linkend="gettingstarted-new">How to create a new project.</link> @@ -50,20 +50,20 @@ shortcuts</link></member> <formalpara> <title>What to expect?</title> -<para>As said, &kdevelop; is an <emphasis>Integrated Development -Environment</emphasis>. That means in essence that &kdevelop; is no development +<para>As said, &tdevelop; is an <emphasis>Integrated Development +Environment</emphasis>. That means in essence that &tdevelop; is no development tool by itself but rather a graphical front end to easily access a wide range of development tools, many of which actually would require complex keyboard commands run from a text console.</para> </formalpara> -<para>While &kdevelop; eases many of those programming tasks, much of the +<para>While &tdevelop; eases many of those programming tasks, much of the complexity from this bundle of tools still remains which means that in order to -fully understand the &kdevelop; &IDE; you will still need to comprehend these +fully understand the &tdevelop; &IDE; you will still need to comprehend these tools actually running beneath the surface.</para> <para>Hence, we cannot teach you how to build software, but rather introduce you -to some of the ways &kdevelop; was designed to ease such a software building +to some of the ways &tdevelop; was designed to ease such a software building process. If you want to learn more about what an Integrated Development Environment is meant for, you might want to have a look at the <link linkend="unixdev">Development on &UNIX;</link> historical overview and there @@ -71,20 +71,20 @@ especially at the <link linkend="unixdev-ide">Integrating Concepts and Tools</link> chapter.</para> <note> -<para>The following discussions apply to the default case, where &kdevelop; +<para>The following discussions apply to the default case, where &tdevelop; starts up in the <guilabel>Simplified IDEAl Window Mode</guilabel>. If you already did switch to another user interface mode some items may not be there as described or will behave slightly different. If in doubt which user interface -mode your &kdevelop; currently uses, check with the +mode your &tdevelop; currently uses, check with the <menuchoice><guimenu>Settings</guimenu> <guimenuitem>Configure KDevelop...</guimenuitem> <guimenuitem>User Interface</guimenuitem></menuchoice> dialog.</para> </note> <sect1 id="gettingstarted-overview"> -<title>A Very First Look at &kdevelop;</title> +<title>A Very First Look at &tdevelop;</title> -<para>This is all about what you will see when you first started &kdevelop;. +<para>This is all about what you will see when you first started &tdevelop;. You will find preliminary information about:</para> <simplelist> @@ -101,7 +101,7 @@ for?</link></member> <sect2 id="gettingstarted-overview-basic"> <title>On the Surface</title> -<para>When you start &kdevelop; for the first time you will get a display +<para>When you start &tdevelop; for the first time you will get a display similar to this one:</para> <screenshot> @@ -110,8 +110,8 @@ similar to this one:</para> <imagedata fileref="empty-ide.png" format="PNG"/> </imageobject> <caption> -<para>The &kdevelop; initial layout</para> -<para>(Actually the initial &kdevelop; window will be larger, but the elements +<para>The &tdevelop; initial layout</para> +<para>(Actually the initial &tdevelop; window will be larger, but the elements you see are the same.)</para> </caption> </mediaobject> @@ -119,7 +119,7 @@ you see are the same.)</para> <formalpara> <title>Workspace Area and Tool View Tabs</title> -<para>In this initial case &kdevelop; uses the so-called <link +<para>In this initial case &tdevelop; uses the so-called <link linkend="uimodes-survey">IDEAl user interface mode</link>. A workspace area of maximum possible size is surrounded left, bottom, and right by a series of buttons which act similar to tabs on a tabbed display. If you click on one of @@ -196,7 +196,7 @@ the <link linkend="commands">Command Reference</link>.</para> <formalpara> <title>Usual Actions</title> <para>This is pretty standard. It allows to create, open, save, print, and close -document files as well as quitting the &kdevelop; application as usual.</para> +document files as well as quitting the &tdevelop; application as usual.</para> </formalpara> <formalpara> @@ -282,7 +282,7 @@ text.</para> <varlistentry> <term><guimenu>Project</guimenu></term> <listitem> -<para>All work of &kdevelop; is based on <emphasis>projects</emphasis> which +<para>All work of &tdevelop; is based on <emphasis>projects</emphasis> which basically collect source files, build management files, and other information in one project directory. In this menu you control which project to use, which properties it has, and some other managing actions. @@ -365,7 +365,7 @@ application in the debugger and step through it in various ways.</para> <formalpara> <title>Breakpoints</title> -<para>&kdevelop; provides several means to set breakpoints in your application +<para>&tdevelop; provides several means to set breakpoints in your application sources. One is through the use of the <guimenuitem>Toggle Breakpoint</guimenuitem> menu entry.</para> </formalpara> @@ -406,7 +406,7 @@ editor window horizontally as well as vertically.</para> <varlistentry> <term><guimenu>Tools</guimenu></term> <listitem> -<para>&kdevelop; is highly customizable. +<para>&tdevelop; is highly customizable. You may select a favorite editor for your documents as well as provide external and plugged-in tools to extend the basic &IDE; capabilities. The <guimenu>Tools</guimenu> menu reflects most of this setup.</para> @@ -445,7 +445,7 @@ purposes.</para> <listitem> <para>This menu allows you to show and hide menubar, toolbars and statusbar. Also, you can configure shortcuts, toolbars, notifications, the editor and -&kdevelop;'s general behavior.</para> +&tdevelop;'s general behavior.</para> </listitem> </varlistentry> @@ -496,7 +496,7 @@ different main purpose.</para> <para>The number of tool view tabs shown will change once a project is open for actual work. More tools to work on that project will be available then. The actual number of tool views depends on the <link linkend="plugin-tools">Plugin -Tools</link> being currently available to &kdevelop;. You will find more on this +Tools</link> being currently available to &tdevelop;. You will find more on this topic in the <link linkend="setup">Configuring KDevelop</link> chapter.</para> <para>Currently, with no project open and the default number of plugin tools @@ -534,7 +534,7 @@ menu.</para> <formalpara> <title>Application</title> <para>Displays the output from an application started from within -&kdevelop;.</para> +&tdevelop;.</para> </formalpara> <formalpara> @@ -548,7 +548,7 @@ Viewer...</guimenuitem></menuchoice> menu.</para> <formalpara> <title>Messages</title> <para>Displays messages produced by the build tools called from within -&kdevelop;, usually from the <guimenu>Build</guimenu> menu.</para> +&tdevelop;, usually from the <guimenu>Build</guimenu> menu.</para> </formalpara> <formalpara> @@ -570,7 +570,7 @@ or not.</para> </formalpara> <note> <para>This global search-and-replace facility is actually available only after a -project has been loaded into &kdevelop;. Otherwise the global replace tool in +project has been loaded into &tdevelop;. Otherwise the global replace tool in the <menuchoice><guimenu>Edit</guimenu> <guimenuitem>Find-Select-Replace...</guimenuitem> </menuchoice> menu will in fact be be disabled.</para> @@ -590,7 +590,7 @@ interface.</para> <listitem> <formalpara> <title>Documentation</title> -<para>&kdevelop; provides access to a whole bunch of documentation through this +<para>&tdevelop; provides access to a whole bunch of documentation through this tool. You may here access document files, usually online from remote locations, in a structured way. And there are several ways available to directly access valuable information from &kde; or &Qt; manuals.</para> @@ -621,19 +621,19 @@ chapters.</para> <title>A Bit of Configuration</title> <para>Before we actually start a first example project, we should tailor the -&kdevelop; behavior to our needs. Although most of the default settings will be +&tdevelop; behavior to our needs. Although most of the default settings will be appropriate for now, there are a few places which better should be adjusted.</para> <note> -<para>If you want to know more about &kdevelop; configuration, have a look at +<para>If you want to know more about &tdevelop; configuration, have a look at the <link linkend="setup">Configuring KDevelop</link> chapter.</para> </note> <sect2 id="gettingstarted-configure-general"> <title>Some General Settings</title> -<para>To configure &kdevelop;, click the +<para>To configure &tdevelop;, click the <menuchoice><guimenu>Settings</guimenu></menuchoice> menu and select <menuchoice><guimenuitem>Configure KDevelop...</guimenuitem></menuchoice>. The <guilabel>Configure KDevelop</guilabel> dialog will pop up, showing the @@ -645,7 +645,7 @@ following <guilabel>General</guilabel> settings page to the right.</para> <imagedata fileref="configure-general.png" format="PNG"/> </imageobject> <caption> -<para>The &kdevelop; general configuration dialog</para> +<para>The &tdevelop; general configuration dialog</para> </caption> </mediaobject> </screenshot> @@ -655,7 +655,7 @@ But you will probably want to change two of those settings.</para> <formalpara> <title>Default projects directory</title> -<para>At first start of &kdevelop; this will most likely be preset to your home +<para>At first start of &tdevelop; this will most likely be preset to your home directory. Most people however prefer a dedicated projects directory for software development. Change the text box to your preferred parent development directory. You may select it from the directory tree if you press the @@ -671,7 +671,7 @@ parent directory for actual development. Again, replace <filename class="directory">projects</filename> with your development directory name. </para> -<para>&kdevelop; will by default set up an own subdirectory below this parent +<para>&tdevelop; will by default set up an own subdirectory below this parent for every new project you create. So will ⪚ all files of a project named <quote>Hello</quote> in our case be located in the <filename class="directory">/home/devel/projects/hello</filename> directory.</para> @@ -682,15 +682,15 @@ for more info on this.</para> <formalpara> <title>Compiler output</title> -<para>Whenever &kdevelop; compiles some source, it will display the messages of +<para>Whenever &tdevelop; compiles some source, it will display the messages of the <application>make</application>, etc. build tools in the <guilabel>Messages</guilabel> window in the lower part of the workspace area. Usually these messages will be overwhelmingly wordy. To keep a better overview -of what happens, &kdevelop; has some means of shortening those messages built +of what happens, &tdevelop; has some means of shortening those messages built in.</para> </formalpara> -<para>Depending on the &kdevelop; version you use, the <guilabel>Compiler +<para>Depending on the &tdevelop; version you use, the <guilabel>Compiler output</guilabel> selection may be preset to <quote>Long</quote>, which will cause all message contents be fully shown. You may probably want to change this to the far more convenient <quote>Very Short</quote> setting. Just select this @@ -711,13 +711,13 @@ Output</quote> from the popup menu.</para> <para>There is another, not so obvious, item which preferably should be initialized before you start actual development work. This is because you will -want to perform documentation search regularly during development. &kdevelop; +want to perform documentation search regularly during development. &tdevelop; requires some search indexes be created before such search operations can be performed. So let's initialize them before we attempt our first steps -toward actual &kdevelop; work.</para> +toward actual &tdevelop; work.</para> <para>Open the <guilabel>Documentation</guilabel> tool view at the right side of -the &kdevelop; main window. There open the <guilabel>Search</guilabel> dialog +the &tdevelop; main window. There open the <guilabel>Search</guilabel> dialog page.</para> <screenshot> @@ -734,7 +734,7 @@ basic search tools are properly set up. A dialog should pop up, telling <quote>Configuration file updated</quote>. Click <guibutton>OK</guibutton> to make it disappear.</para> -<para>This done, &kdevelop; will be ready to parse the documentation it knows of +<para>This done, &tdevelop; will be ready to parse the documentation it knows of and build some useful search indexes from it. Press the <guibutton>Update Index</guibutton> button to the right. Now the <guilabel>Generating Search Index</guilabel> dialog will pop up showing the progress of the index build @@ -745,7 +745,7 @@ operations.</para> <imageobject> <imagedata fileref="configure-docu-indexgen.png" format="PNG"/> </imageobject> -<caption><para>&kdevelop; is generating documentation search +<caption><para>&tdevelop; is generating documentation search indexes.</para></caption> </mediaobject> </screenshot> @@ -758,7 +758,7 @@ place to <guibutton>OK</guibutton>. Just press this button to proceed.</para> <itemizedlist> <listitem> <para>This usually should work out of the box. In some cases the -<application>htdig</application> application &kdevelop; uses to perform its full +<application>htdig</application> application &tdevelop; uses to perform its full text searches might not be properly set up. Refer to the <link linkend="setup-docu-textsearch">Setting Up Text Search Indexes</link> chapter for more help in this case.</para> @@ -766,10 +766,10 @@ for more help in this case.</para> <listitem> <para>To be able to look up &kde; and &Qt; specific API documentation, it is mandatory that the <emphasis>KDELibs Apidocs</emphasis> were present when -&kdevelop; was installed. If you experience problems building the indexes or +&tdevelop; was installed. If you experience problems building the indexes or perform the <link linkend="gettingstarted-edit-defs">identifier lookup examples</link> later in this chapter, make sure that this documentation exists -and is accessible to &kdevelop;. See <link linkend="kdevelop-install">Installing +and is accessible to &tdevelop;. See <link linkend="tdevelop-install">Installing KDevelop</link> fore more detail.</para> </listitem> </itemizedlist> @@ -783,17 +783,17 @@ KDevelop</link> fore more detail.</para> <para>Almost any application will consist of dozens, hundreds, even thousands of files which need kept structured and maintainable. To accomplish this, -&kdevelop; organizes software development tasks in +&tdevelop; organizes software development tasks in <emphasis>projects</emphasis>. Thus the first practical step to develop software -in &kdevelop; usually is to create a new project.</para> +in &tdevelop; usually is to create a new project.</para> -<para>Fortunately this is fairly easily accomplished. &kdevelop; provides the +<para>Fortunately this is fairly easily accomplished. &tdevelop; provides the so-called &appwizard; tool for this. (See the <link linkend="applicationwizard">Getting Started — the &appwizard;</link> chapter for more.)</para> <para>We will now start a simple &kde; application project to illustrate how -easily this is accomplished and which files and tools &kdevelop; will have +easily this is accomplished and which files and tools &tdevelop; will have provided. Thereby we will have a short look at:</para> <simplelist> @@ -927,7 +927,7 @@ The &appwizard; will take over and construct a series of initial files in the <guilabel>Final location</guilabel> directory you provided in step 2c above.</para> -<para>Once this file creation phase is finished, &kdevelop; will open an editor +<para>Once this file creation phase is finished, &tdevelop; will open an editor window for the <emphasis>application main window</emphasis> implementation file (which is <filename>hello.cpp</filename> in our example), so you can readily proceed.</para> @@ -990,8 +990,8 @@ created.</para> </programlisting> <para>You will find exactly the same text headers in every source file you will -create inside &kdevelop; (provided you use the proper built in tools for file -creation). &kdevelop; remembers these settings in some template files you may +create inside &tdevelop; (provided you use the proper built in tools for file +creation). &tdevelop; remembers these settings in some template files you may find in the <filename class="directory">templates</filename> directory.</para> <formalpara> @@ -1040,13 +1040,13 @@ application, namely</para> <itemizedlist> <listitem> <para><filename>hello.desktop</filename> contains some meta data used by -&kdevelop; to maintain and start the application.</para> +&tdevelop; to maintain and start the application.</para> </listitem> <listitem> <para><filename>hi16-app-hello.png</filename>, and <filename>hi32-app-hello.png</filename> contain some initial default icons, -&kdevelop; will use for application display.</para> +&tdevelop; will use for application display.</para> </listitem> <listitem> @@ -1103,7 +1103,7 @@ application.</para> </formalpara> <para>Those <filename>Makefile.am</filename> files need to be maintained -throughout the development process. Luckily, &kdevelop; relieves you of most of +throughout the development process. Luckily, &tdevelop; relieves you of most of this burden by the &automanag; tool, which basically is a graphical front end to maintain <filename>Makefile.am</filename> contents.</para> @@ -1118,20 +1118,20 @@ binaries.</para> <listitem> <formalpara> -<title>&kdevelop; Control Files</title> -<para>&kdevelop; needs some control and administration data on its own. These +<title>&tdevelop; Control Files</title> +<para>&tdevelop; needs some control and administration data on its own. These are located in the project root directory, in our example -<filename>hello.kdevelop</filename>, <filename>hello.kdevelop.pcs</filename>, +<filename>hello.tdevelop</filename>, <filename>hello.tdevelop.pcs</filename>, and <filename>hello.kdevses</filename>.</para> </formalpara> <para>Of particular importance in each project is the -<filename>xxx.kdevelop</filename> (where <quote>xxx</quote> denotes the project +<filename>xxx.tdevelop</filename> (where <quote>xxx</quote> denotes the project name) file. It is the main <emphasis>KDevelop 3 Project File</emphasis> and needed if you later want load this project into the &IDE;.</para> <warning> -<para>Never do manually modify, rename, or even delete any of these &kdevelop; +<para>Never do manually modify, rename, or even delete any of these &tdevelop; control files! The &IDE; will most likely not function properly on your project afterwards.</para> </warning> @@ -1203,7 +1203,7 @@ functionality.</para> <note> <para>The tool views actually visible depend on the plugins currently loaded -into &kdevelop;. There are ways to control this. See the <link +into &tdevelop;. There are ways to control this. See the <link linkend="setup-plugins">Plugin Tools</link> chapter for instructions.</para> </note> @@ -1215,7 +1215,7 @@ linkend="setup-plugins">Plugin Tools</link> chapter for instructions.</para> <formalpara> <title>Bookmarks</title> <para>You can mark any text file line in order to quickly return to this -position from everywhere. &kdevelop; will remember all those +position from everywhere. &tdevelop; will remember all those <emphasis>bookmarks</emphasis>, even if you close the editor window afterwards. The <guilabel>Bookmarks</guilabel> tool view lists all those bookmarks by file name and line number. You need only click such an entry to open the editor @@ -1268,7 +1268,7 @@ memory leaks.</para> <formalpara> <title>Security Problems</title> <para>There is a <guilabel>Security Checker</guilabel> plugin tool for -&kdevelop;. It analyzes the currently edited source file for several common +&tdevelop;. It analyzes the currently edited source file for several common security problems which may occur in the application and notifies the user in this tool view window.</para> </formalpara> @@ -1297,7 +1297,7 @@ position the cursor on the appropriate identifier there.</para> <listitem> <formalpara> <title>Problems</title> -<para>&kdevelop; keeps track of common programming problems in the currently +<para>&tdevelop; keeps track of common programming problems in the currently edited source file and notifies the user in this tool view window.</para> </formalpara> </listitem> @@ -1345,7 +1345,7 @@ a more extensive description.</para> <filename>hello.cpp</filename> file open in an editor window, so you can immediately start working. Now, we may well assume your are knowledgeable about using an editor, so we do not need talk much about this here. But there are some -handy &kdevelop; specifics about dealing with such tabbed editor windows and the +handy &tdevelop; specifics about dealing with such tabbed editor windows and the documents you are working on. We will have a short look at some of them, namely:</para> @@ -1363,7 +1363,7 @@ common problems.</link></member> <sect2 id="gettingstarted-edit-headers"> <title>Switching Between Header and Implementation Files</title> -<para>&kdevelop; provides a quick and easy way to switch from a given +<para>&tdevelop; provides a quick and easy way to switch from a given implementation (<filename>.cpp</filename>) file to the corresponding header (<filename>.h</filename>) file and vice versa. Just right click into the editor window you want to switch. A menu similar to the following will pop up.</para> @@ -1379,20 +1379,20 @@ files.</para></caption> </screenshot> <para>Find the <guimenuitem>Switch header/implementation</guimenuitem> entry and -select it. &kdevelop; will look up the corresponding header or implementation +select it. &tdevelop; will look up the corresponding header or implementation file and open it in another editor window. In our example, if you did right click into the <filename>hello.cpp</filename> source, the <filename>hello.h</filename> file will be displayed and the cursor positioned there.</para> <para>There is even more. If you do right click inside the text of a class -implementation, &kdevelop; will position the cursor on the corresponding +implementation, &tdevelop; will position the cursor on the corresponding declaration line in the header file. And vice versa, right clicking on a declaration line will bring you to the corresponding class implementation.</para> <para>If the editor window with the file to be switched to already exists, -&kdevelop; will of course activate this one and reposition the cursor there if +&tdevelop; will of course activate this one and reposition the cursor there if necessary.</para> </sect2> @@ -1417,8 +1417,8 @@ internal text items</link>.</member> <para>In a most common case you want to look up an identifier which was defined externally to your project. In &kde; projects such identifiers are most likely -documented in various &kde; or &Qt; libraries. If &kde; and &kdevelop; were -properly installed, &kdevelop; will be able to access such so-called API +documented in various &kde; or &Qt; libraries. If &kde; and &tdevelop; were +properly installed, &tdevelop; will be able to access such so-called API documentation and be able to search it for identifiers of this kind.</para> <para>Let us look at an example. In the <filename>hello.cpp</filename> editor @@ -1475,7 +1475,7 @@ then come back here and try again.</para> <para>Such search facilities in external documentation have their limitations, however. Of course one cannot look up an identifier externally if it is only -defined and used inside the current project. But there is help. &kdevelop; can +defined and used inside the current project. But there is help. &tdevelop; can use indexes built by the <application>CTags</application> application to search the sources in your project.</para> @@ -1518,14 +1518,14 @@ possibilities.</para> <title>Use the CTags tool view</title> <para>This is easy. Just start typing the identifier name you are interested in into the -<guilabel>Lookup</guilabel> input field in the bottom left. &kdevelop; will try +<guilabel>Lookup</guilabel> input field in the bottom left. &tdevelop; will try to complete the word you have typed so far and show all occurrences of those identifiers which start with this character sequence.</para> </formalpara> <para>If for example you want to know wherever the <quote>Hello</quote> identifier was used in our example project, type an "H" into the -<guilabel>Lookup</guilabel> input field. &kdevelop; will immediately start +<guilabel>Lookup</guilabel> input field. &tdevelop; will immediately start working and present you a result like this:</para> <screenshot> @@ -1538,7 +1538,7 @@ tool view.</para></caption> </mediaobject> </screenshot> -<para>If you click one of the listed entries, &kdevelop; will open an editor +<para>If you click one of the listed entries, &tdevelop; will open an editor window with this file and position the cursor on the appropriate place.</para> </listitem> @@ -1568,7 +1568,7 @@ internal identifier.</para></caption> </screenshot> <para>Click what you are interested in, say <guilabel>CTags - Go to Definition: -Hello</guilabel>, and &kdevelop; will immediately open the +Hello</guilabel>, and &tdevelop; will immediately open the <filename>hello.cpp</filename> editor window and position the cursor right in front of this class definition:</para> <programlisting> @@ -1583,7 +1583,7 @@ Hello::Hello() <title>Do a global search</title> <para>This is especially useful if you want to look up arbitrary text in your project source. There are two possibilities to start a global search from within -&kdevelop;.</para> +&tdevelop;.</para> </formalpara> <itemizedlist> <listitem> @@ -1602,7 +1602,7 @@ The outcome of the menu call will essentially be the same. Let us assume you are studying the <filename>hello.cpp</filename> source file and have the cursor positioned on the first Hello occurrence there. Now you wonder, where this one word <quote>Hello</quote> was used in the project source and how many -occurrences there are. This is a typical case where to use &kdevelop;'s +occurrences there are. This is a typical case where to use &tdevelop;'s global search facilities.</para> <para>Now, still keeping the cursor somewhere on this <quote>Hello</quote> in @@ -1645,13 +1645,13 @@ the <guibutton>Search</guibutton> button at the bottom right.</para> <para>Now the <guilabel>Find in Files</guilabel> tool view will open at the bottom, showing you file names and lines of all literal occurrences of <quote>Hello</quote> in our example project. As usual, if you click an entry, -&kdevelop; will get you to exactly that position in an editor window in the +&tdevelop; will get you to exactly that position in an editor window in the workspace area.</para> <para>There are two lines of special interest in the tool view window.</para> <itemizedlist> <listitem> -<para>Right on top you will find the command sequences &kdevelop; did actually +<para>Right on top you will find the command sequences &tdevelop; did actually use to perform the search. This will be useful to more precisely control the search outcome.</para> </listitem> @@ -1663,7 +1663,7 @@ listed. In our example this should read <quote>*** 11 matches found </listitem> </itemizedlist> -<para>&kdevelop; will remember these search results throughout the currently +<para>&tdevelop; will remember these search results throughout the currently running session. If you initiate another global search, its results will display in another tabbed window in the <guilabel>Find in Files</guilabel> tool view window.</para> @@ -1678,7 +1678,7 @@ window.</para> <para>When your work with large complex projects you will often end up with quite a lot of tabbed editor windows residing on the tab bar. This makes specific facilities to clean up, order, and group all those editor tabs -necessary. &kdevelop; provides several means for this. We will have a short look +necessary. &tdevelop; provides several means for this. We will have a short look at some of them.</para> <simplelist> <member><link linkend="gettingstarted-edit-arrange-clean">How to remove unneeded @@ -1699,7 +1699,7 @@ files into development sessions.</link></member> <para>If the vast amount of editor window tabs becomes badly arranged at all, you usually may want to close all those tabs you really do not need any more. -&kdevelop; provides several facilities to do so, the usual way of bulk closing +&tdevelop; provides several facilities to do so, the usual way of bulk closing open editor windows and a more specific approach where you can expressly command which ones to close and which to keep open.</para> @@ -1727,7 +1727,7 @@ may find in other &kde; applications as well. You can use the <para>The step-by-step approach of closing individual editor window tabs can become awkward if there are a great number of tabs from which you want to still keep several open. Instead of searching and closing one editor window tab after -another &kdevelop; provides a means to select the candidates from a list and +another &tdevelop; provides a means to select the candidates from a list and close those, and only those, with one single mouse click.</para> </formalpara> @@ -1766,7 +1766,7 @@ step.</para></caption> </mediaobject> </screenshot> <para>That was all. -&kdevelop; will have closed all editor windows at your wish, and you are ready +&tdevelop; will have closed all editor windows at your wish, and you are ready to proceed with a clean tab bar again.</para> </sect3> @@ -1774,7 +1774,7 @@ to proceed with a clean tab bar again.</para> <title>How to Rearrange Edit Window Tabs</title> <para>Even if you have only the really necessary editor windows open you may -still want to have their tabs arranged in some logical way. &kdevelop; provides +still want to have their tabs arranged in some logical way. &tdevelop; provides some common means to do so, in short:</para> <formalpara> @@ -1784,7 +1784,7 @@ some common means to do so, in short:</para> the right of the editor window tab currently in use. This can be changed so that the new tab will open to the far right on the tab bar.</para> </formalpara> -<para>You must change a basic user interface setting in &kdevelop; to enable +<para>You must change a basic user interface setting in &tdevelop; to enable this behavior.</para> <procedure> <step> @@ -1802,7 +1802,7 @@ Browsing</guilabel>. Remove the check mark on the <guilabel>Open new tab after current tab</guilabel> line.</para> </step> <step> -<para>Close &kdevelop; and restart it again. Now the new editor window tabs will +<para>Close &tdevelop; and restart it again. Now the new editor window tabs will open at the far right end of the current tabs row.</para> </step> </procedure> @@ -1810,13 +1810,13 @@ open at the far right end of the current tabs row.</para> <para>Unfortunately, this setting cannot be changed on the fly during a development session. You must make up your mind which behavior you prefer in the long run and then stick to it, at least until the next start of -&kdevelop;.</para> +&tdevelop;.</para> <formalpara> <title>How to Rearrange the Tabs</title> <para>As development tasks do vary over time, the need to rearrange the tabbed editor windows will more or less often arise. This is easily accomplished in -&kdevelop;.</para> +&tdevelop;.</para> </formalpara> <para> Just click the tab you want to move with the middle mouse button and move the @@ -1832,7 +1832,7 @@ into the place where you want it to be.</para> work on a source file. Although you may fast switch the tabbed windows, there are times where you want have several files open at once, ⪚ for reference purposes or to keep complex tasks under better control. To accomplish this, -&kdevelop; provides a way to split the workspace area into different, +&tdevelop; provides a way to split the workspace area into different, simultaneously visible sections which each can hold their own series of tabbed windows.</para> @@ -1905,11 +1905,11 @@ It closes automatically, once the last tabbed window in it was closed.</para> <title>Edit C++ Source and Header Files Simultaneously</title> <para>There is a neat application of the above mentioned workspace split -feature built into &kdevelop;. It allows to automatically keep a +feature built into &tdevelop;. It allows to automatically keep a <filename>.cpp</filename> source and its accompanying <filename>.h</filename> header file side by side open in the workspace area. And, optionally, it allows to work on both files synchronously, such that if -you select a declaration in the header file &kdevelop; will navigate to the +you select a declaration in the header file &tdevelop; will navigate to the respective definition in the source file and vice versa.</para> <para>This feature is however deactivated by default. If you want to use it in @@ -1942,7 +1942,7 @@ both the <filename>hello.cpp</filename> and <filename>hello.h</filename> editor windows, if necessary. Then select <filename>hello.cpp</filename> again from the <filename class="directory">src</filename> subdirectory of the project. The editor window will open as usual. But if you now open the -<filename>hello.h</filename> belonging to it, &kdevelop; will automatically +<filename>hello.h</filename> belonging to it, &tdevelop; will automatically split the workspace and open this header file editor window just beneath the <filename>hello.cpp</filename> window.</para> @@ -1953,7 +1953,7 @@ line:</para> Hello::Hello() </programlisting> <para>and put the cursor there. Then look at the <filename>hello.h</filename> -window below and note how &kdevelop; did navigate to the corresponding default +window below and note how &tdevelop; did navigate to the corresponding default constructor declaration line.</para> <screenshot> @@ -1961,13 +1961,13 @@ constructor declaration line.</para> <imageobject> <imagedata fileref="split-source-header-navigate.png" format="PNG"/> </imageobject> -<caption><para>&kdevelop; automatically navigated to the constructor +<caption><para>&tdevelop; automatically navigated to the constructor declaration.</para></caption> </mediaobject> </screenshot> <para>This works vice versa as well. Whenever you put the cursor somewhere into -a construct in one editor window, &kdevelop; will navigate to the corresponding +a construct in one editor window, &tdevelop; will navigate to the corresponding construct in the other.</para> </sect3> @@ -1977,7 +1977,7 @@ construct in the other.</para> <para>When your project grows larger, and the development tasks become more and more complex and force you to often switch between different, even distinct sets of files, it is about time to organize your development work into distinct -sessions. The <guilabel>File List</guilabel> tool view of &kdevelop; allows you +sessions. The <guilabel>File List</guilabel> tool view of &tdevelop; allows you do to just this.</para> <para>On top of the <guilabel>File List</guilabel> tool view window there is a @@ -2034,7 +2034,7 @@ planned.</para> </step> <step> <para>Once your file list is complete, click the <guiicon>Save Session</guiicon> -icon in the toolbar. Do not skip this step, &kdevelop; will forget the file list +icon in the toolbar. Do not skip this step, &tdevelop; will forget the file list otherwise.</para> </step> </substeps> @@ -2042,7 +2042,7 @@ otherwise.</para> </procedure> <para>That was it. Whenever you select the <guilabel>sources</guilabel> session -from the <guilabel>Open Session</guilabel> drop down box, &kdevelop; will close +from the <guilabel>Open Session</guilabel> drop down box, &tdevelop; will close all currently open editor windows and open the remembered ones (<filename>hello.cpp</filename>, <filename>hello.h</filename>, and <filename>main.cpp</filename> in our example) instead.</para> @@ -2053,7 +2053,7 @@ remembered file list with a <guiicon>Save Session</guiicon> click. And if you want get rid of a session, select it in the drop down box, then click the <guiicon>Delete Session</guiicon> icon in the toolbar right.</para> -<para>There is even more. You can force &kdevelop; to open a given session by +<para>There is even more. You can force &tdevelop; to open a given session by default when it loads the project. Just select the session in the drop down box on the <menuchoice><guimenu>Projects</guimenu> <guimenuitem>Project Options</guimenuitem> <guimenuitem>File List</guimenuitem></menuchoice> project @@ -2064,7 +2064,7 @@ options configuration page.</para> <imageobject> <imagedata fileref="file-list-session-default.png" format="PNG"/> </imageobject> -<caption><para>Let &kdevelop; open a specific session when the project is +<caption><para>Let &tdevelop; open a specific session when the project is loaded.</para></caption> </mediaobject> </screenshot> @@ -2074,7 +2074,7 @@ loaded.</para></caption> <sect2 id="gettingstarted-edit-problems"> <title>Keeping an Eye on Common Problems</title> -<para>When you open an editor window containing a source file, &kdevelop; will +<para>When you open an editor window containing a source file, &tdevelop; will parse its contents. This allows the built in <emphasis>problem reporter</emphasis> to scan the source text for some common errors it knows of. And it can alert the user of different places which have been marked for special @@ -2107,7 +2107,7 @@ row. If all went right, it will currently report this todo:</para> <imageobject> <imagedata fileref="problem-report-todo.png"/> </imageobject> -<caption><para>&kdevelop; is alerting a source code line containing a todo +<caption><para>&tdevelop; is alerting a source code line containing a todo mark.</para></caption> </mediaobject> </screenshot> @@ -2153,7 +2153,7 @@ currently edited file.</para></caption> <para>Note the other tabs in the <guilabel>Problem</guilabel> reporter tool view window, especially <guilabel>Fixme</guilabel>, and <guilabel>Todo</guilabel>. If you open them, you will find all <computeroutput>FIXME</computeroutput> and -<computeroutput>TODO</computeroutput> marked lines, &kdevelop; has found so far +<computeroutput>TODO</computeroutput> marked lines, &tdevelop; has found so far in this session. For example the <computeroutput>TODO</computeroutput> alerts will currently look thus:</para> @@ -2173,7 +2173,7 @@ you will find here alerts of some common programming mistakes which would likely go unnoticed otherwise and probably be catched with difficulties during complex debugging session.</para> -<para>You will find the &kdevelop; problem reporter facility a very valuable +<para>You will find the &tdevelop; problem reporter facility a very valuable tool, so check the <guilabel>Problems</guilabel> tool view regularly in the development process.</para> </sect2> @@ -2182,7 +2182,7 @@ development process.</para> <sect1 id="gettingstarted-compile"> <title>How to Compile a Project</title> -<para>Compiling a project in &kdevelop; requires several setup steps and then +<para>Compiling a project in &tdevelop; requires several setup steps and then building the application. All these are available through the <guimenu>Build</guimenu> menu.</para> @@ -2203,7 +2203,7 @@ needed. Other entries are there to compile selected project portions or a single file only, to perform several initialization sequences, or to install the completed application binaries.</para> -<para>For now we will concentrate on several facilities which &kdevelop; +<para>For now we will concentrate on several facilities which &tdevelop; provides for project setup, initializing, building, and running an application. In general, this includes:</para> @@ -2229,12 +2229,12 @@ initial configuration.</link></member> <member><link linkend="gettingstarted-compile-basic-build">How to build the project.</link></member> <member><link linkend="gettingstarted-compile-basic-run">How to run the -application from within &kdevelop;.</link></member> +application from within &tdevelop;.</link></member> </simplelist> <note> <para>This discussion implies that your project is based on the &GNU; autotools, -which enabled the &automanag; tool in &kdevelop; as our example Hello project +which enabled the &automanag; tool in &tdevelop; as our example Hello project does. If you created another type project, ⪚ for the &Qt; based <application>QMake</application> project manager, there will be other facilities available in the menus or perhaps even none of them. You will have to consult @@ -2263,7 +2263,7 @@ function key, you will get the following warning.</para> </screenshot> <para>You may press the <guibutton>Run Them</guibutton> button in which case -&kdevelop; will try to automatically run all required setup steps prior to +&tdevelop; will try to automatically run all required setup steps prior to compiling and linking the application. But we will look at those initial steps in sequence, so cancel the dialog by pressing <guibutton>Do Not run</guibutton>. </para> @@ -2282,12 +2282,12 @@ through the <guimenu>Build</guimenu> menu. Call it up and select </screenshot> <para> -&kdevelop; will now open the <guilabel>Messages</guilabel> tool view window at +&tdevelop; will now open the <guilabel>Messages</guilabel> tool view window at the bottom and list a series of messages produced by several make tools. If everything went right, the final line will read <quote><computeroutput>*** Success ***</computeroutput></quote>.</para> -<para>If you scroll back to the top, you will find the command line, &kdevelop; +<para>If you scroll back to the top, you will find the command line, &tdevelop; issued to call up the tools beneath the surface:</para> <programlisting> @@ -2295,7 +2295,7 @@ cd '/home/devel/projects/hello' && \ WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" gmake -f Makefile.cvs </programlisting> -<para>This basically tells that &kdevelop; first switched to the root directory +<para>This basically tells that &tdevelop; first switched to the root directory of our example project. Then it set up a dedicated environment, advising the make system of the <application>autoconf</application> and <application>automake</application> tool revisions used for this initialization. @@ -2323,16 +2323,16 @@ available. This done, select the <menuchoice><guimenu>Build</guimenu> <guimenuitem>Run Configure</guimenuitem></menuchoice> menu entry to initiate a configuration sequence.</para> -<para>&kdevelop; opened the <guilabel>Messages</guilabel> tool view +<para>&tdevelop; opened the <guilabel>Messages</guilabel> tool view window again if necessary and listed the messages of the configure run therein. If all went right, the final messages will be <quote><computeroutput>Good - your configure finished. Start make now</computeroutput></quote> (which was issued by -configure) followed by the &kdevelop; <quote><computeroutput>*** Success +configure) followed by the &tdevelop; <quote><computeroutput>*** Success ***</computeroutput></quote> message.</para> <para id="gettingstarted-compile-basic-config-cmd">On top of the <guilabel>Messages</guilabel> window you will again find -the command line, &kdevelop; used to initiate this configuration run:</para> +the command line, &tdevelop; used to initiate this configuration run:</para> <programlisting> mkdir '/home/devel/projects/hello/debug' && \ @@ -2354,7 +2354,7 @@ CXXFLAGS="-O0 -g3" "/home/devel/projects/hello/configure" --enable-debug=full <entry> <itemizedlist> <listitem> -<para>First, &kdevelop; uses a dedicated subdirectory in the project directory +<para>First, &tdevelop; uses a dedicated subdirectory in the project directory tree for the build process. This <filename class="directory">debug</filename> build directory (shown to the left) mirrors the basic project structure and contains some set of build related files, such as several @@ -2365,8 +2365,8 @@ contains some set of build related files, such as several <para>In the <link linkend="gettingstarted-compile-setup">Configuring the Project</link> section shortly below we will have a brief look at the motivations why -&kdevelop; uses separate build directories in cases like this one. For the -moment it is enough to know that &kdevelop; created this <filename +&tdevelop; uses separate build directories in cases like this one. For the +moment it is enough to know that &tdevelop; created this <filename class="directory">debug</filename> directory — if necessary — prior to the configure call and that the <filename>configure</filename> script did build the sub structure and all the <filename>Makefiles</filename> in @@ -2374,7 +2374,7 @@ there.</para> </listitem> <listitem> <para>Next, from within the <filename class="directory">debug</filename> build -directory, &kdevelop; called the <filename>configure</filename> script in the +directory, &tdevelop; called the <filename>configure</filename> script in the root directory of our project using a dedicated environment, where the <computeroutput>CXXFLAGS="-O0 -g3"</computeroutput> flags will later signal the &gcc; compiler that it should not optimize the resulting binaries and include @@ -2409,7 +2409,7 @@ there are three such compile options from which to select.</para> <imageobject> <imagedata fileref="build-commands.png" format="PNG"/> </imageobject> -<caption><para>&kdevelop; commands to build binaries.</para></caption> +<caption><para>&tdevelop; commands to build binaries.</para></caption> </mediaobject> </screenshot> @@ -2446,14 +2446,14 @@ class="directory">Debug</filename> subtree.</para> <para id="gettingstarted-compile-basic-build-cmd">There are not many source files in our Hello example project, so the <guilabel>Messages</guilabel> window will contain only a few lines. On top of them again find the command line -&kdevelop; issued to the underlying shell.</para> +&tdevelop; issued to the underlying shell.</para> <programlisting> cd '/home/devel/projects/hello/debug' && \ WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" gmake -k </programlisting> -<para>Not very surprisingly, &kdevelop; switched to the <filename +<para>Not very surprisingly, &tdevelop; switched to the <filename class="directory">Debug</filename> subtree root in order to run the <filename>Makefile</filename> located there. A dedicated sub-environment was set up again as before in the <link @@ -2462,10 +2462,10 @@ then the <application>gmake</application> tool was called.</para> <para>Note the <computeroutput>-k</computeroutput> option in the <application>gmake</application> call. It forces the build process to continue -up to its very end, even if errors will occur. This makes sense as &kdevelop; +up to its very end, even if errors will occur. This makes sense as &tdevelop; will list all error messages in the <guilabel>Messages</guilabel> window. If there are any, use the virtues of an &IDE;: Just click on the error message in -the <guilabel>Messages</guilabel> window and &kdevelop; will take you to +the <guilabel>Messages</guilabel> window and &tdevelop; will take you to exactly the position where the error occurred in the source file.</para> <para>And what did happen inside the <filename @@ -2500,9 +2500,9 @@ Toolbar</guilabel>.</para> </mediaobject> </screenshot> -<para>That was all. &kdevelop; will now start the new application in +<para>That was all. &tdevelop; will now start the new application in the dedicated console window which opens as <guilabel>Application</guilabel> -tool view on the bottom. There the command &kdevelop; issued to execute the +tool view on the bottom. There the command &tdevelop; issued to execute the program will be shown in the top line:</para> <programlisting> @@ -2530,7 +2530,7 @@ our <application>Hello</application> form running.</para> </screenshot> <para>Close the <application>Hello</application> application window as -usual. If no errors occurred, &kdevelop; will report this as +usual. If no errors occurred, &tdevelop; will report this as <quote><computeroutput>*** Exited normally ***</computeroutput></quote> in the <guilabel>Application</guilabel> tool view window.</para> </sect3> @@ -2539,7 +2539,7 @@ in the <guilabel>Application</guilabel> tool view window.</para> <sect2 id="gettingstarted-compile-setup"> <title>Configuring the Project</title> -<para>In &kdevelop; there are numerous ways how you can manage your project. +<para>In &tdevelop; there are numerous ways how you can manage your project. This behavior is configurable on a per-project basis and mostly of interest to the advanced developer. Yet there are a few project specific settings you should know of right from the beginning. @@ -2564,12 +2564,12 @@ executable be and how should it be called?</link></member> <para>When we did a first run of the <filename>configure</filename> script in the <link linkend="gettingstarted-compile-basic-config">Initial Hello -Configuration</link> section above, we noted that &kdevelop; had set up a +Configuration</link> section above, we noted that &tdevelop; had set up a dedicated <filename class="directory">debug</filename> subdirectory for this purpose. In this section we will briefly consider some consequences of this feature.</para> -<para>First of all, &kdevelop; does not necessarily use dedicated build +<para>First of all, &tdevelop; does not necessarily use dedicated build directories apart from the source. The preparations to automatically use dedicated build configurations is done through templates the &appwizard; uses when creating a new project.</para> @@ -2670,7 +2670,7 @@ the resulting application. So in many cases, when the logical structure of some routine appears to be correct, you may want to test whether it still behaves correctly under more practical conditions.</para> -<para>This is where the build configurations of &kdevelop; step in. Because +<para>This is where the build configurations of &tdevelop; step in. Because the built object and executable files in each dedicated build directory and the build commands are kept separately from each other only source changes need to be handled when you switch between these build configurations.</para> @@ -2699,7 +2699,7 @@ environment prior to running <filename>configure</filename> as ⪚ the <computeroutput>CXXFLAGS</computeroutput> in our previous discussions.</para> <para>You may set most of the configuring options for a given project from -within &kdevelop; &GUI;. Select +within &tdevelop; &GUI;. Select <menuchoice><guimenu>Project</guimenu> <guimenuitem>Project Options</guimenuitem></menuchoice> and then from the icon bar on the left of the dialog the <guiicon>Configure Options</guiicon> @@ -2762,7 +2762,7 @@ configuration options can be defined:</para> <listitem> <formalpara> <title>Configure arguments</title> -<para>These are the options &kdevelop; assigns to the +<para>These are the options &tdevelop; assigns to the <filename>configure</filename> script call in the build process. See the <link linkend="gettingstarted-compile-basic-config-cmd">example</link> in the <quote>Initial Hello Configuration</quote> section above.</para> @@ -2772,7 +2772,7 @@ the <quote>Initial Hello Configuration</quote> section above.</para> <listitem> <formalpara> <title>Build directory</title> -<para>This is the subdirectory in the current project root, where &kdevelop; +<para>This is the subdirectory in the current project root, where &tdevelop; will put all files created in the build process. Ideally, this should correspond to the name of the build configuration in use, but you are free to use any name you like, provided it is different from any other @@ -2792,7 +2792,7 @@ in another place.</para> <listitem> <formalpara> <title>C/C++ preprocessor flags (CPPFLAGS)</title> -<para>Put specific instructions for the preprocessor here. &kdevelop; will +<para>Put specific instructions for the preprocessor here. &tdevelop; will use this to set up a temporary environment before it calls the actual build tool. Again, see the <link linkend="gettingstarted-compile-basic-config-cmd">example</link> in @@ -2814,7 +2814,7 @@ temporary build environment as well.</para> <formalpara> <title>Environment Variables</title> <para>Here you may define additional variables to be set up in the -temporal build environment, &kdevelop; will set up before calling the +temporal build environment, &tdevelop; will set up before calling the respective build tool. Again, you must define these environment variables for every build configuration where they are to be used.</para> </formalpara> @@ -2834,7 +2834,7 @@ so it suffices to have a brief look at the <guilabel>C++</guilabel> page.</para> <imageobject> <imagedata fileref="configure-project-cpp.png" format="PNG"/> </imageobject> -<caption><para>Select the compiler and its working environment &kdevelop; shall +<caption><para>Select the compiler and its working environment &tdevelop; shall use here.</para></caption> </mediaobject> </screenshot> @@ -2845,8 +2845,8 @@ use here.</para></caption> <listitem> <formalpara> <title>C++ compiler</title> -<para>Select the C++ compiler &kdevelop; should regularly use from this -combo box. It however lists only those compilers &kdevelop; really knows +<para>Select the C++ compiler &tdevelop; should regularly use from this +combo box. It however lists only those compilers &tdevelop; really knows of.</para> </formalpara> </listitem> @@ -2862,7 +2862,7 @@ Put the name by which it is called here.</para> <listitem> <formalpara> <title>Compiler flags (CXXFLAGS)</title> -<para>Here you can enter any extra option &kdevelop; shall pass (via the +<para>Here you can enter any extra option &tdevelop; shall pass (via the <filename>Makefile</filename>) to the compiler. Some option values will be preset according to the build configuration selected in the <guilabel>Configuration</guilabel> combo box.</para> @@ -2900,7 +2900,7 @@ configuration would have to be altered manually if ever needed.</para> <sect3 id="gettingstarted-compile-setup-make"> <title>How Make Should Build the Program</title> -<para>You can as well configure the way &kdevelop; will call the +<para>You can as well configure the way &tdevelop; will call the <application>make</application> tool in the project build. Select <menuchoice><guimenu>Project</guimenu> <guimenuitem>Project Options</guimenuitem></menuchoice> and then the @@ -2913,7 +2913,7 @@ the right.</para> <imageobject> <imagedata fileref="configure-project-make.png" format="PNG"/> </imageobject> -<caption><para>Define how &kdevelop; will call the +<caption><para>Define how &tdevelop; will call the <application>make</application> tool.</para></caption> </mediaobject> </screenshot> @@ -2926,7 +2926,7 @@ You will find it deactivated in most projects. This corresponds to the linkend="gettingstarted-compile-basic-build-cmd">initial build</link> of our example Hello project.</para> -<para>This makes sense in an &IDE; like &kdevelop; which will protocol any +<para>This makes sense in an &IDE; like &tdevelop; which will protocol any error message during the build. After the build process you may easily navigate to any error message in the <guilabel>Messages</guilabel> tool window. Use <menuchoice><guimenu>View</guimenu> @@ -2934,12 +2934,12 @@ window. Use <menuchoice><guimenu>View</guimenu> <menuchoice><guimenu>View</guimenu> <guimenuitem>Previous Error</guimenuitem></menuchoice> or respectively the <keycap>F4</keycap> and <keycombo><keycap>Shift</keycap> <keycap>F4</keycap></keycombo> keys for this. -&kdevelop; will automatically activate the editor window of the source file in +&tdevelop; will automatically activate the editor window of the source file in question and put the cursor on the error line.</para> <para>If on the other hand you rather want the build be stopped on whenever an error occurs, check the <guilabel>Abort on first error</guilabel> option -in this dialog. &kdevelop; will then call <application>gmake</application> +in this dialog. &tdevelop; will then call <application>gmake</application> without the <computeroutput>-k</computeroutput> option.</para> </sect3> @@ -2947,11 +2947,11 @@ without the <computeroutput>-k</computeroutput> option.</para> <title>How to Run the Executable</title> <para>Once the build is complete, you can easily run the application from within -&kdevelop;. Use either <menuchoice><guimenu>Build</guimenu> +&tdevelop;. Use either <menuchoice><guimenu>Build</guimenu> <guimenuitem>Execute Program</guimenuitem></menuchoice>, the <keycombo><keycap>Shift</keycap> <keycap>F9</keycap></keycombo> keys, or the <guibutton>Execute program</guibutton> button in the <guilabel>Build -Toolbar</guilabel> of &kdevelop;.</para> +Toolbar</guilabel> of &tdevelop;.</para> <screenshot> <mediaobject> @@ -2963,12 +2963,12 @@ Toolbar</guilabel> of &kdevelop;.</para> </screenshot> <para>But where is the executable located which should be run? How does -one have &kdevelop; append options to the call? Or, how can I have the +one have &tdevelop; append options to the call? Or, how can I have the application executed in a terminal by its own to test its console interactive behavior?</para> <para>All this can be solved by configuring some project oriented run options in -&kdevelop;. Select <menuchoice><guimenu>Project</guimenu> +&tdevelop;. Select <menuchoice><guimenu>Project</guimenu> <guimenuitem>Project Options</guimenuitem></menuchoice> and then the <guiicon>Run Options</guiicon> icon from the icon bar on the left dialog window side. The <guilabel>Run Options</guilabel> dialog page will display to the @@ -2990,13 +2990,13 @@ Basically there are four groups of configuration items.</para> <listitem> <formalpara> <title>Directory</title> -<para>This tells &kdevelop; where it basically shall assume the +<para>This tells &tdevelop; where it basically shall assume the executable to be called. There are three possibilities you can select from.</para> </formalpara> <para>Note however that only root directories are defined here. -&kdevelop; usually looks for the executable in some subdirectory +&tdevelop; usually looks for the executable in some subdirectory given in the next configuration group.</para> <itemizedlist> @@ -3012,7 +3012,7 @@ The name of this directory was set up on the <link linkend="gettingstarted-compile-setup-config-general">General Configuration</link> dialog page.</para> -<para>This is the root where &kdevelop; will find the executable. It +<para>This is the root where &tdevelop; will find the executable. It changes automatically with the selection you made in <menuchoice><guimenu>Project</guimenu> <guisubmenu>Build Configurations</guisubmenu></menuchoice> menu. Try it.</para> @@ -3037,17 +3037,17 @@ the version located in the project directories.</para> <listitem> <formalpara> <title>Program</title> -<para>This tells &kdevelop; the relative position and name of the +<para>This tells &tdevelop; the relative position and name of the program it shall actually call. This is relative to the root directory defined in the configuration group above. Furthermore you can define any -argument &kdevelop; will pass to the program when it is actually called.</para> +argument &tdevelop; will pass to the program when it is actually called.</para> </formalpara> <note> <para>If leave the <guilabel>Main program</guilabel> text box empty, the <emphasis>active target</emphasis> settings of the &automanag; will be used. Although this is an expert setting, inadvertently leaving this input -field blank is a common cause of problems. Check this setting if &kdevelop; +field blank is a common cause of problems. Check this setting if &tdevelop; appears not to call the executable you wanted.</para> </note> </listitem> @@ -3055,7 +3055,7 @@ appears not to call the executable you wanted.</para> <listitem> <formalpara> <title>Environment Variables</title> -<para>&kdevelop; will set up a dedicated shell environment to run the +<para>&tdevelop; will set up a dedicated shell environment to run the program in. Define any extra environment variable in this configuration group.</para> </formalpara> @@ -3070,7 +3070,7 @@ group.</para> <itemizedlist> <listitem> <para><guilabel>Automatically compile before execution</guilabel> comes -in handy most of time. &kdevelop; will check the project for changes and +in handy most of time. &tdevelop; will check the project for changes and perform necessary configure and build steps for you any time you command it to run the program.</para> @@ -3081,7 +3081,7 @@ last change.</para> <listitem> <para><guilabel>Start in external terminal</guilabel> is interesting if you want to test the input/output behavior of non-&GUI; programs in a console -terminal. This is unchecked by default, so &kdevelop; does start the program in +terminal. This is unchecked by default, so &tdevelop; does start the program in a window of its own without console terminal I/O capabilities.</para> </listitem> </itemizedlist> @@ -3160,17 +3160,17 @@ After building your project, the user manual is displayed in &kde; are the main features and how to configure it. It should also explain the advanced features if any. </para> -<para>All &kde; based templates in &kdevelop; have a doc subdir which contains +<para>All &kde; based templates in &tdevelop; have a doc subdir which contains a <filename>index.docbook</filename> template in the en folder to get you started in writing the user manual. You should edit this -<filename>index.docbook</filename> in &kdevelop; and start changing personal +<filename>index.docbook</filename> in &tdevelop; and start changing personal details such as name, email, &etc;. Look at the comments in this file and try following these indications to start your application documentation. Rebuild your project to see the changes in &khelpcenter;.</para> <note><para>You need to install your project using <menuchoice><guimenu>Build</guimenu> <guimenuitem>Install</guimenuitem></menuchoice > or <guimenuitem>Install (as -root user)</guimenuitem> in &kdevelop; to see the user manual in +root user)</guimenuitem> in &tdevelop; to see the user manual in &khelpcenter;.</para></note> <para>You can find more about the docbook syntax on <ulink url="http://l10n.kde.org/docs/markup/index.html">the &kde; documentation @@ -3205,7 +3205,7 @@ website</ulink>.</para> <para>(- to be written -)</para> <sect3 id="gettingstarted-whereto-projects-open"> -<title>Using Existing &kdevelop; Projects</title> +<title>Using Existing &tdevelop; Projects</title> <para>(- to be written -)</para> </sect3> |