From 2ecab1a194b0dc551b478820e1aaa3b8713354cc Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Wed, 16 Nov 2011 13:53:18 -0600 Subject: Additional renaming of kde to tde --- doc/Makefile.am | 2 +- doc/api/FutureTasks.dox | 2 +- doc/api/HighPriTasks.dox | 10 +- doc/api/HowToAddApplicationTemplates.dox | 26 +-- doc/api/HowToAddPlugins.dox | 6 +- doc/api/HowToAddProgrammingLanguages.dox | 4 +- doc/api/HowToDocument.dox | 2 +- doc/api/Mainpage.dox | 8 +- doc/extras/opengl.toc | 6 +- doc/extras/sdl.toc | 6 +- doc/extras/w3c/w3c-dom-level2-html.toc | 6 +- doc/extras/w3c/w3c-svg.toc | 6 +- doc/extras/w3c/w3c-uaag10.toc | 6 +- doc/kde_app_devel/index.docbook | 52 ++--- doc/kdearch/index.docbook | 16 +- doc/kdevelop/adv-build-management.docbook | 6 +- doc/kdevelop/app-files.docbook | 84 ++++---- doc/kdevelop/app-uimodes-examples.docbook | 22 +- doc/kdevelop/applicationwizard.docbook | 38 ++-- doc/kdevelop/class-browsers.docbook | 2 +- doc/kdevelop/credits.docbook | 2 +- doc/kdevelop/cvs.docbook | 6 +- doc/kdevelop/debugger.docbook | 12 +- doc/kdevelop/documentation.docbook | 2 +- doc/kdevelop/file-browsers.docbook | 8 +- doc/kdevelop/getting-started.docbook | 324 +++++++++++++++--------------- doc/kdevelop/index.docbook | 26 +-- doc/kdevelop/kdevelop-install.docbook | 190 +++++++++--------- doc/kdevelop/kdevelop-scripting.docbook | 8 +- doc/kdevelop/kdevelop-survey.docbook | 62 +++--- doc/kdevelop/listplugins.sh | 2 +- doc/kdevelop/nutshell.docbook | 20 +- doc/kdevelop/plugin-tools.docbook | 6 +- doc/kdevelop/project-advanced.docbook | 4 +- doc/kdevelop/project-management.docbook | 18 +- doc/kdevelop/setup.docbook | 184 ++++++++--------- doc/kdevelop/survey-manual.docbook | 42 ++-- doc/kdevelop/unixdev.docbook | 16 +- doc/platform/Mainpage.dox | 12 +- doc/std/kdev3api.toc | 8 +- 40 files changed, 631 insertions(+), 631 deletions(-) (limited to 'doc') diff --git a/doc/Makefile.am b/doc/Makefile.am index 2c7c6128..06f6c7cb 100644 --- a/doc/Makefile.am +++ b/doc/Makefile.am @@ -1,2 +1,2 @@ -SUBDIRS = kdevelop std extras kde_app_devel +SUBDIRS = tdevelop std extras kde_app_devel diff --git a/doc/api/FutureTasks.dox b/doc/api/FutureTasks.dox index fbed119a..5e2b8268 100644 --- a/doc/api/FutureTasks.dox +++ b/doc/api/FutureTasks.dox @@ -99,7 +99,7 @@ - cd's when selecting a file, but doesn't when selecting a dir, desired: a menu option to "cd" to that directory - QEditor - - Replace editors/qeditor/koReplace.* and editors/qeditor/koFind.* with kdelibs/kutils/kreplace.* and kdelibs/kutils/kfind.* + - Replace editors/qeditor/koReplace.* and editors/qeditor/koFind.* with tdelibs/kutils/kreplace.* and tdelibs/kutils/kfind.* \section extensiontodo Extensions / New Functionality: diff --git a/doc/api/HighPriTasks.dox b/doc/api/HighPriTasks.dox index 21116342..062b3b06 100644 --- a/doc/api/HighPriTasks.dox +++ b/doc/api/HighPriTasks.dox @@ -5,16 +5,16 @@ \section fixMajBugs Fixing major/annoying bugs - - Fix the mess of .kdevelop and .kdevses file. - - All project wide setings should go into .kdevelop and + - Fix the mess of .tdevelop and .kdevses file. + - All project wide setings should go into .tdevelop and - all session (and personal) options should go into .kdevses file . - This way the .kdevelop file can be shared in teams of developers. + This way the .tdevelop file can be shared in teams of developers. \section KDevelop2compat KDevelop 2 compatibility (These are things that must be accomplished before we can say that KDevelop 3 ->= kdevelop 2.x UI-wise and functionality-wise!) +>= tdevelop 2.x UI-wise and functionality-wise!) - general UI issues: - toplevel UI mode broken concerning to the accels @@ -29,7 +29,7 @@ - implement "Make User Manual" - use kdoc to update Qt/KDE docs . - - Solve the regression bugs. These are the ones + - Solve the regression bugs. These are the ones marked with priority "HI" in the bug database diff --git a/doc/api/HowToAddApplicationTemplates.dox b/doc/api/HowToAddApplicationTemplates.dox index 7eec80c7..b948c934 100644 --- a/doc/api/HowToAddApplicationTemplates.dox +++ b/doc/api/HowToAddApplicationTemplates.dox @@ -6,7 +6,7 @@ Project templates provide the developer with a basic application framework. This is necessary for rapid application development (RAD) and makes it even possible for an inexperienced 3rd party developer to create standard conforming -applications like kedit as well as plugins for example for kdevelop or noatun.\n\n +applications like kedit as well as plugins for example for tdevelop or noatun.\n\n \ref templates_1\n - \ref templates_1_1 - \ref templates_1_2 @@ -36,7 +36,7 @@ Create a directory template-khello with the files - template-khello/app.cpp - template-khello/app.h - template-khello/app.desktop - - template-khello/app.kdevelop + - template-khello/app.tdevelop - template-khello/appui.rc - template-khello/khello - template-khello/main.cpp @@ -64,7 +64,7 @@ wizard will replace: - \%{YEAR} ........ by the year . -All this can be found in $KDEDIR/share/apps/kdevappwizard/template-common/kdevelop.pm. +All this can be found in $KDEDIR/share/apps/kdevappwizard/template-common/tdevelop.pm. \subsubsection templates_1_2a I.2.1. The Source Files The files template-khello/app.cpp, template-khello/app.h and @@ -117,7 +117,7 @@ This file will be copied to the $PROJECTDIR/src/. The following script is used to install the template and replaces all variables by the corresponding value. The result is a hopefully working -kdevelop project! +tdevelop project! \verbinclude khello/script
\note There are several application templates which use some identical @@ -155,7 +155,7 @@ if [ ! -e "${newdir}/template-common" ]; then ln -s "${kde_prefix}/share/apps/kd # install now cp -R --target-directory "$newdir" template-khello # the file template-khello/khello must go to the "templates" directory that -# kdevelop knows that it exists +# tdevelop knows that it exists mv "$newdir/template-khello/khello" "$newdir/templates/" echo "done" \endcode @@ -164,9 +164,9 @@ echo "done" \section templates_3 III. How To Add The Template To KDevelop CVS HEAD -This section is for kdevelop developers only. Most probably you don't have to read this!.\n -Move the directory "template-khello" to kdevelop/languages/cpp/app_templates/ -and then add the following files in kdevelop/languages/cpp/app_templates/template-khello/ +This section is for tdevelop developers only. Most probably you don't have to read this!.\n +Move the directory "template-khello" to tdevelop/languages/cpp/app_templates/ +and then add the following files in tdevelop/languages/cpp/app_templates/template-khello/ (in this example the language is c++ if you use other language replace cpp with the language name): - ".kdev_ignore" is an empty file. It prevents KDevelop's C++-parser from parsing the C++ template files. This is necessary because the template files are just code templates and not real code (yet). @@ -179,9 +179,9 @@ script.local - "Makefile.am" looks like this: \verbinclude khello/Makefile.am . -Finally add "template-khello" to "SUBDIRS = " in kdevelop/languages/cpp/app_templates/Makefile.am.\n +Finally add "template-khello" to "SUBDIRS = " in tdevelop/languages/cpp/app_templates/Makefile.am.\n \attention Please test your template whether it installs and behaves correctly! -Test, test and test again! It works? Well - now talk to the kdevelop guys so +Test, test and test again! It works? Well - now talk to the tdevelop guys so that they know what's going on and probably you may commit. ;) \section templates_4 IV. Changes to the template system (VERY IMPORTANT) @@ -192,14 +192,14 @@ information from the script file will need to be moved into the ini file. The example is as follows: \code install( -"${src}/template-chello/app.kdevelop","${dest}/${APPNAMELC}.kdevelop" ); +"${src}/template-chello/app.tdevelop","${dest}/${APPNAMELC}.tdevelop" ); \endcode becomes \code [PROJECT] Type=install -Source=%{src}/template-chello/app.kdevelop -Dest=%{dest}/%{APPNAMELC}.kdevelop +Source=%{src}/template-chello/app.tdevelop +Dest=%{dest}/%{APPNAMELC}.tdevelop \endcode Things like installIncAdmin(); and installGNU(); now involve unpacking diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox index 6171d9aa..3ab31af9 100644 --- a/doc/api/HowToAddPlugins.dox +++ b/doc/api/HowToAddPlugins.dox @@ -119,11 +119,11 @@ developers (e.g. via version control application CVS). So some user preferences very individual, and some may be valid for all of the team - project-wide so to speak. That's why the KDevelop architecture makes a difference here and supports two files -which will be stored in the project root directory. They are the project file (*.kdevelop) +which will be stored in the project root directory. They are the project file (*.tdevelop) and the session (*.kdevses) file. The later is for individual settings, not to be thought to be shared. -\subsection domProject Project file (*.kdevelop) +\subsection domProject Project file (*.tdevelop) For your convenience, you don't have to use the quite complex DOM API. Strings can very easily be read from and written to this document using the @@ -195,7 +195,7 @@ void GDBBreakpointWidget::savePartialProjectSession(QDomElement* el) Note that the .kdevses is related to a project. User settings equal for all projects don't -belong to here. You save them to ~/.kde/share/config/kdeveloprc via class KConfig of the +belong to here. You save them to ~/.kde/share/config/tdeveloprc via class KConfig of the tdecore library. Document your part in the way described at \ref howToDocument (doc/api/HowToDocument.dox file). diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox index 5cfa3643..504a397e 100644 --- a/doc/api/HowToAddProgrammingLanguages.dox +++ b/doc/api/HowToAddProgrammingLanguages.dox @@ -42,7 +42,7 @@ Take a look at \ref LangSupportStatus (doc/api/LangSupportStatus.dox file) to se \section sectionLanguageSupport Language Support -Any language support should be written as a kdevelop part and implement +Any language support should be written as a tdevelop part and implement KDevLanguageSupport interface (lib/interfaces/kdevlanguagesupport.h). Implementing methods: @@ -137,7 +137,7 @@ and look at languages/ruby/app_templates/rubyhello, languages \subsubsection sectionApplicationImportTemplates Application import templates KDevelop has the ability to create a new project from existing projects or source code. -It scans for project files ('*.kdevelop, *.kdevprj, *.studio, *.pro) and if +It scans for project files ('*.tdevelop, *.kdevprj, *.studio, *.pro) and if - it finds a project it extracts the necessary information - it does not find project files it scans for source files (*.cpp, *.java, *.pl, *.py, ...) . diff --git a/doc/api/HowToDocument.dox b/doc/api/HowToDocument.dox index d606a8bf..f767fc5b 100644 --- a/doc/api/HowToDocument.dox +++ b/doc/api/HowToDocument.dox @@ -8,7 +8,7 @@ You should add a README and a README.dox file to your part (KDevPlugin). On the README file put this text: \verbatim Please read the on-line, automaticaly updated KDevelop API documentation at: -http://www.kdevelop.org +http://www.tdevelop.org or read the README.dox file. \endverbatim diff --git a/doc/api/Mainpage.dox b/doc/api/Mainpage.dox index 9d4b6d4c..48640827 100644 --- a/doc/api/Mainpage.dox +++ b/doc/api/Mainpage.dox @@ -13,14 +13,14 @@ This document is targeted at all those that want to add or improve KDevelop's so If you are instead looking for a user manual, just go to the help menu of your KDevelop and select KDevelop handbook. This documentation contains the KDevelop online class reference for the current development version of KDevelop. Additionally, you -can subscribe or read the mailing list for any additions and/or +can subscribe or read the mailing list for any additions and/or modifications to the %API. -An on-line, updated every 24H, html version of this documentation can be found at: http://www.kdevelop.org/HEAD/doc/api/html/index.html +An on-line, updated every 24H, html version of this documentation can be found at: http://www.tdevelop.org/HEAD/doc/api/html/index.html More information about the KDevelop architecture in form of tutorials, HOWTOs, and FAQs can be found at -the KDevelop website. +the KDevelop website. \section status Current Status @@ -45,7 +45,7 @@ Additionally you may also want to find out \ref howToDocument (doc/api/HowToDocu Here is a priority ordered list: -# \ref HighPriTasks (doc/api/HighPriTasks.dox file) -# fix the dispersed \ref fixme - -# reported bugs in bugzilla database + -# reported bugs in bugzilla database -# fix the bugs in the \ref bug -# fix the dispersed \ref todo all over the code. . diff --git a/doc/extras/opengl.toc b/doc/extras/opengl.toc index efe104ff..cc420a7d 100644 --- a/doc/extras/opengl.toc +++ b/doc/extras/opengl.toc @@ -1,5 +1,5 @@ - - + + OpenGL @@ -264,4 +264,4 @@ - + diff --git a/doc/extras/sdl.toc b/doc/extras/sdl.toc index 947dd09a..01b7e7d7 100644 --- a/doc/extras/sdl.toc +++ b/doc/extras/sdl.toc @@ -1,5 +1,5 @@ - - + + SDL @@ -216,4 +216,4 @@ - + diff --git a/doc/extras/w3c/w3c-dom-level2-html.toc b/doc/extras/w3c/w3c-dom-level2-html.toc index f3540ff1..e41c5172 100644 --- a/doc/extras/w3c/w3c-dom-level2-html.toc +++ b/doc/extras/w3c/w3c-dom-level2-html.toc @@ -1,5 +1,5 @@ - - + + Document Object Model (DOM) Level 2 HTML Specification @@ -66,5 +66,5 @@ - + diff --git a/doc/extras/w3c/w3c-svg.toc b/doc/extras/w3c/w3c-svg.toc index a53e34fc..c7ef3f3d 100644 --- a/doc/extras/w3c/w3c-svg.toc +++ b/doc/extras/w3c/w3c-svg.toc @@ -1,5 +1,5 @@ - - + + Scalable Vector Graphics (SVG) 1.1 Specification @@ -1442,5 +1442,5 @@ - + diff --git a/doc/extras/w3c/w3c-uaag10.toc b/doc/extras/w3c/w3c-uaag10.toc index 08f90cc9..b0b581f7 100644 --- a/doc/extras/w3c/w3c-uaag10.toc +++ b/doc/extras/w3c/w3c-uaag10.toc @@ -1,5 +1,5 @@ - - + + User Agent Accessibility Guidelines 1.0 @@ -66,4 +66,4 @@ - + diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook index 0ebf7e71..3cc34883 100644 --- a/doc/kde_app_devel/index.docbook +++ b/doc/kde_app_devel/index.docbook @@ -1,7 +1,7 @@ KDevelop"> - + KDevelop"> + ]> @@ -9,7 +9,7 @@ -The &kdevelop; Programming Handbook +The &tdevelop; Programming Handbook 2002-12-05 2.0 @@ -42,7 +42,7 @@ The User Guide to C++ Application Design for the K Desktop Environment (KDE) with -the &kdevelop; IDE +the &tdevelop; IDE @@ -76,7 +76,7 @@ C++ is available through various sources either in printed form at your local bo found on the Internet. Knowledge about the design of Graphical User Interfaces is not required, as this handbook tries to cover the application design for KDE programs, which also includes an introduction into the Qt toolkit as well as the KDE libraries and the design of User Interfaces. Also, you should have made -yourself comfortable with &kdevelop; by reading The User Manual to &kdevelop;, which contains a descriptive +yourself comfortable with &tdevelop; by reading The User Manual to &tdevelop;, which contains a descriptive review of the functionality provided by the IDE. @@ -106,8 +106,8 @@ online-manuals. We'll take a look at the Qt and KDE libraries, showing basic concepts and why things are the way they are. Also, we will discuss how to create the tutorial applications provided with the Qt toolkit by using -kdevelop;, so beginners can already see first results with a few steps, and thereby will learn how to make -use of some of &kdevelop;'s best features. +tdevelop;, so beginners can already see first results with a few steps, and thereby will learn how to make +use of some of &tdevelop;'s best features. @@ -135,7 +135,7 @@ You will learn how to: Additional information about Qt/KDE programming is available by various sources: Programming with Qt by Matthias Kalle Dalheimer -The User Manual to KDevelop, provided with the KDevelop IDE +The User Manual to KDevelop, provided with the KDevelop IDE The Online Reference to the Qt library The KDE Developer web site @@ -147,7 +147,7 @@ Unix Systems as well as about the C and C++ programming language. For obtaining help about the KDevelop IDE, you should send requests to our mailinglist at -kdevelop@kdevelop.org. Mind that the KDevelop team is dedicated to provide the means to enable you to +tdevelop@tdevelop.org. Mind that the KDevelop team is dedicated to provide the means to enable you to program applications and therefore is not intended as a technical support team in cases where the applications you're developing don't work due to implementation errors or misconfigurations of your operating system. By this, we ask all users to take advantage of the mailinglist in any case you're running @@ -259,7 +259,7 @@ an integer value to the overlaying Operating System signaling that the applicati The Reference Documentation for Qt Now, let's have a quick look at the reference documentation of the Qt library. To do this, start -&kdevelop; and select "Qt" from the tree in the Documentation tab. The documentation browser opens +&tdevelop; and select "Qt" from the tree in the Documentation tab. The documentation browser opens and shows you the start page of the Qt reference. This will be your first place to get information about Qt, it's classes and the available functions they provide. Also, the above program is the first that is included in the tutorials section. To get to the classes we want to have a look at, @@ -595,7 +595,7 @@ include path and the linker to link in the tdecore library with -ltdecore. As you now know what at least the main() function provides generally and how an application gets visible and allows user and object interaction, we'll go on with the next chapter, -where our first application is made with &kdevelop;. There you can also test everything which was +where our first application is made with &tdevelop;. There you can also test everything which was mentioned before and see the effects. @@ -617,7 +617,7 @@ also covers a complete description about the invocation of the QAppli The Application Wizard -&kdevelop;'s Application Wizard is intended to let you start working on new project with &kdevelop;. Therefore +&tdevelop;'s Application Wizard is intended to let you start working on new project with &tdevelop;. Therefore all of your projects are first created by the wizard, and then you can start building them and extend what is already provided by the source skeleton. You can choose from several project types according to your project goals: @@ -648,7 +648,7 @@ may not have as many options available. Starting the Application Wizard and the First Page -To start with your KDE application, open &kdevelop;. From the Project menu, selection New Project. The +To start with your KDE application, open &tdevelop;. From the Project menu, selection New Project. The Application Wizard starts, and you'll see the selection tree on the first page containing available project types that can be created. Choose the C++ subtree, then KDE, then Application Framework. @@ -673,7 +673,7 @@ and select Next. Header and Source Templates The next two pages show example headers that will go at the top of each of the header and source files that -you create using &kdevelop;. For now, just leave these as the default, and select Next, then Finish. If the +you create using &tdevelop;. For now, just leave these as the default, and select Next, then Finish. If the Finish button is not activated, you haven't set all of the options correct. Use the Back button to return to earlier menus and correct any mistakes. @@ -682,7 +682,7 @@ to earlier menus and correct any mistakes. Finishing Up Upon completion, the Application Wizard should close and the messages window should popup displaying -information about the tasks that &kdevelop; is currently doing. At the end of all of the tasks, you +information about the tasks that &tdevelop; is currently doing. At the end of all of the tasks, you should see **** Success *****. This means the application framework was successfully loaded. @@ -696,7 +696,7 @@ of how the application framework looks. This won't only help us get started, bu what in later steps. -This chapter makes the assumption that you understand the basic navigation of &kdevelop;. Consult the +This chapter makes the assumption that you understand the basic navigation of &tdevelop;. Consult the KDevelop User Manual for information if you need it. @@ -707,7 +707,7 @@ The Automake manager shows the project files as follows: -Before diving into the sources, we'll let &kdevelop; build an run our new application. To do this, select +Before diving into the sources, we'll let &tdevelop; build an run our new application. To do this, select Build Project from the Build menu, or press F8. The output window opens and displays output messages during the compilation phase. @@ -822,7 +822,7 @@ returns to the directory it was started, processes it, then finishes. Our first line of interest is 24. Notice on this line that g++, which is our C++ compiler, gets called by make to compile the first source code file in our project - in this case main.cpp. Many extra command line options are also being used with the g++ compiler; some of which are defaults and some of which can be configured -via &kdevelop;. +via &tdevelop;. Before the next file (kscribble.cpp, line 29) is compiled, the moc (meta object compiler) is first @@ -1023,7 +1023,7 @@ inherits QWidget already. This chapter therefore describes how to use library widgets for creating views of KDE or -Qt applications that are generated with &kdevelop;, then we look at the libraries and what kind of +Qt applications that are generated with &tdevelop;, then we look at the libraries and what kind of views are already offered. @@ -1046,7 +1046,7 @@ Change the inheritance of the provided view class to the class of the library wi In either way, it is important to know that if the application framework is currently not linked against the library that contains the widget, the linker will fail. After you decided to use a -certain widget, look for the library to link to; then open "Project"->"Options" from the &kdevelop; +certain widget, look for the library to link to; then open "Project"->"Options" from the &tdevelop; menubar. Switch to the "Linker Options" page and look for the checkmarks indicating the libraries that are currently used. If the library of your view widget is already checked, you can leave the project options untouched and start doing the necessary changes due to your choice. If not, and the @@ -1206,7 +1206,7 @@ KAction, which provides the keyboard accelerator keys and access to standard keyboard accelerators. -By default, frame applications generated by &kdevelop; only use standard keyboard accelerators +By default, frame applications generated by &tdevelop; only use standard keyboard accelerators such as F1 for accessing online-help, Ctrl+N for New File etc. @@ -1252,7 +1252,7 @@ using the standard help key F1. This context based help system is provided auto KMainWindow class, though as the author you must provide the content. -As &kdevelop; also offers all types of help as well as the KDE framework generated by the +As &tdevelop; also offers all types of help as well as the KDE framework generated by the application wizard already contains support for this, this chapter will help you find out where and how to add your help functionality. @@ -1306,7 +1306,7 @@ that the user wants to get help about a certain widget within the working view o It is placed in the toolbar and gets activated once the user hits the button. The cursor changes to an arrow cursor with a question mark like the button itself looks like. The the user can press on a visible widget item and gets a help window. As an exercise, you could try this behavior with the -What's this...? button within &kdevelop;. +What's this...? button within &tdevelop;. To add the What's This...? help to one of your widgets, use the static method @@ -1321,7 +1321,7 @@ To add the What's This...? help to one of your widgets, use the static method Introduction Due to the fact that projects often lack a complete set of user documentation, -all &kdevelop; projects contain a pre-build handbook that can be easily adapted; +all &tdevelop; projects contain a pre-build handbook that can be easily adapted; therefore fulfiling another goal of KDE: providing enough online-help to support users that are not familiar with an application. This chapter therefore introduces you on how to extend the provided documentation template and what you have to do to make it available to the user. @@ -1341,10 +1341,10 @@ The format for editing this file is explained on Another important part of the documentation is including a descriptive help for your class interfaces. This will allow you and other programmers to use your classes by reading the HTML class documentation -that can be created with KDoc. &kdevelop; supports the use of KDoc completely by creating the +that can be created with KDoc. &tdevelop; supports the use of KDoc completely by creating the KDE-library documentation, also your application frameworks are already documented. To work yourself into the provided code, it would be a good start to read the included documentation online. -The following describes what to do to get the API documentation, where &kdevelop; helps you add it +The following describes what to do to get the API documentation, where &tdevelop; helps you add it and what kind of special tags KDoc provides. diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook index a17aaa87..fff7cd57 100644 --- a/doc/kdearch/index.docbook +++ b/doc/kdearch/index.docbook @@ -16,7 +16,7 @@ Bernd Gehrmann -
bernd@kdevelop.org
 +
bernd@tdevelop.org
 @@ -1451,7 +1451,7 @@ in this screenshot: The XML file begins with a document type declaration. The DTD for kpartgui can -be found in the kdelibs sources in tdeui/kpartgui.dtd. The +be found in the tdelibs sources in tdeui/kpartgui.dtd. The outermost element of the file contains the instance name of the application as attribute. It can also contain a version number in the form "version=2". This is useful when you release new versions of an application with a changed menu @@ -1480,7 +1480,7 @@ declared as follows: In KDE's automake framework, such titles are automatically extracted and put -into the application's .po +into the application's .po file , so it is considered by translators. Note that you have to write the accelerator marker "&" in the form XML compliant form "&". @@ -1503,7 +1503,7 @@ actions are created by the class When you create such actions in your application (such as in the C++ example above), they will automatically be inserted in a prescribed position, and possibly with an icon and a shortcut key. You can look up these locations in -the file tdeui/ui_standards.rc in the kdelibs sources. +the file tdeui/ui_standards.rc in the tdelibs sources. @@ -1913,12 +1913,12 @@ snippet: -kde_servicetypesdir_DATA = kdeveloppart.desktop +kde_servicetypesdir_DATA = tdeveloppart.desktop EXTRA_DIST = $(kde_servicetypesdir_DATA) -The definition kdeveloppart.desktop of a +The definition tdeveloppart.desktop of a KDevelop part looks as follows: @@ -2920,7 +2920,7 @@ cache, you can use: void FooClass::reloadPage() { - KURL url("http://www.kdevelop.org/index.html"); + KURL url("http://www.tdevelop.org/index.html"); KIO::TransferJob *job = KIO::get(url, true, false); job->addMetaData("cache", "reload"); ... @@ -3119,7 +3119,7 @@ extern "C" { int kdemain(int argc, char **argv); } int kdemain(int argc, char **argv) { - KLocale::setMainCatalogue("kdelibs"); + KLocale::setMainCatalogue("tdelibs"); KInstance instance("kio_ftp"); (void) KGlobal::locale(); diff --git a/doc/kdevelop/adv-build-management.docbook b/doc/kdevelop/adv-build-management.docbook index e589a007..02dd987e 100644 --- a/doc/kdevelop/adv-build-management.docbook +++ b/doc/kdevelop/adv-build-management.docbook @@ -23,7 +23,7 @@ When you have suitable cross compilers available, you can cross compile your programs for processors and operating systems different from the system where -&kdevelop; and the compiler is running. The &GNU; compiler collection &gcc; can +&tdevelop; and the compiler is running. The &GNU; compiler collection &gcc; can be configured and compiled as a cross compiler if you compile it yourself. Consult the GCC info pages for more information. Some &Linux; distributions also provide binary packages. @@ -36,7 +36,7 @@ configure script and setting the CC and CXX environment variables to the respective cross compiler binaries. Often you want to switch between a the cross-compiled version of your application and one compiled for your development system. For this, it is advantageous to -use &kdevelop; capability of creating multiple build configurations, as +use &tdevelop; capability of creating multiple build configurations, as explained in . Once you have created a new build configuration for cross-compiling in the ProjectProject @@ -79,7 +79,7 @@ the one of the X11 version. -Developing an application for &qte; with &kdevelop; is not very different +Developing an application for &qte; with &tdevelop; is not very different from developing a program for the X11 version of &Qt;. In fact, you can use the same codebase for both versions. If you use the autoproject project management, you switch to the embedded version by passing the argument diff --git a/doc/kdevelop/app-files.docbook b/doc/kdevelop/app-files.docbook index 210e1469..f79b81c1 100644 --- a/doc/kdevelop/app-files.docbook +++ b/doc/kdevelop/app-files.docbook @@ -10,38 +10,38 @@ -Configuration Files Used by &kdevelop; +Configuration Files Used by &tdevelop; -&kdevelop; uses a series of configuration files which are distributed amongst several directories. There are two main groups of configuration files to distinguish: +&tdevelop; uses a series of configuration files which are distributed amongst several directories. There are two main groups of configuration files to distinguish: - &kdevelop; Default Configuration — files set up when &kdevelop; was installed. + &tdevelop; Default Configuration — files set up when &tdevelop; was installed. - User Oriented Configuration — files which contain user modifications of the defaults as well as settings made by the &kdevelop; application itself and its plugins. + User Oriented Configuration — files which contain user modifications of the defaults as well as settings made by the &tdevelop; application itself and its plugins. -&kdevelop; Default Configuration +&tdevelop; Default Configuration -On installation, &kdevelop; writes some default information files for setup and configuration purposes into subdirectories of the $KDEDIR installation directory (usually something like /opt/kde, /usr/local/kde, or some other user-defined installation directory, see Installing &kdevelop;). +On installation, &tdevelop; writes some default information files for setup and configuration purposes into subdirectories of the $KDEDIR installation directory (usually something like /opt/kde, /usr/local/kde, or some other user-defined installation directory, see Installing &tdevelop;). -Default &kdevelop; Configuration +Default &tdevelop; Configuration -There is only one &kdevelop; specific default configuration file in the $KDEDIR/share/config/ directory: +There is only one &tdevelop; specific default configuration file in the $KDEDIR/share/config/ directory: - kdeveloprc + tdeveloprc - This file contains the basic settings &kdevelop; needs to start. It will be copied to the user's $KDEHOME/share/config directory when &kdevelop; does not find a kdeveloprc file there on startup. + This file contains the basic settings &tdevelop; needs to start. It will be copied to the user's $KDEHOME/share/config directory when &tdevelop; does not find a tdeveloprc file there on startup. @@ -52,11 +52,11 @@ There is only one &kdevelop; specific default configuration file in the Application Specific Defaults -Most &kdevelop; features are provided by KParts. These are basically applications specially designed to run in the &kdevelop; framework (see the overview in the Plugin Tools appendix). Each KPart application has its own set of configuration files whose defaults will be stored in several subdirectories of the $KDEDIR/share/apps/ installation directory. +Most &tdevelop; features are provided by KParts. These are basically applications specially designed to run in the &tdevelop; framework (see the overview in the Plugin Tools appendix). Each KPart application has its own set of configuration files whose defaults will be stored in several subdirectories of the $KDEDIR/share/apps/ installation directory. -There are quite a lot of default configuration subdirectories in $KDEDIR/share/apps/ whose names all start with a kdev sequence. Most of them are for &kdevelop; internal use only. They might be deliberately grouped for readability as: +There are quite a lot of default configuration subdirectories in $KDEDIR/share/apps/ whose names all start with a kdev sequence. Most of them are for &tdevelop; internal use only. They might be deliberately grouped for readability as: Stand-alone Applications Task Specific Parts @@ -69,18 +69,18 @@ There are quite a lot of default configuration subdirectories in Stand-alone Applications - kdevelop/ — contains files to configure the &kdevelop; &IDE;: + tdevelop/ — contains files to configure the &tdevelop; &IDE;: licenses/ — contains various licenses texts. - pics/ — contains the picture files used for the &kdevelop;, &kdevelop; Assistant, and &kdevelop; Designer splash screens. - profiles/ — contains default plugin profile settings. (Currently there is only a tiny profile provided which defines a minimum set of active &kdevelop; plugins.) + pics/ — contains the picture files used for the &tdevelop;, &tdevelop; Assistant, and &tdevelop; Designer splash screens. + profiles/ — contains default plugin profile settings. (Currently there is only a tiny profile provided which defines a minimum set of active &tdevelop; plugins.) eventsrc — holds a lot of Process successful localization strings. - kdevelopui.rc — provides the basic menu and tool bar entries &kdevelop; uses. + tdevelopui.rc — provides the basic menu and tool bar entries &tdevelop; uses. kdevhtml_partui.rc — provides a Print... entry in the File menu, a Copy entry in the Edit menu, and Back and Forward arrows in the Browser Toolbar in case a &HTML; file is browsed from the Documentation plugin. - kdevassistant/ — provides the menu and tool bars of the stand-alone &kdevelop; Assistant documentation browser. - kdevdesigner/ and kdevdesignerpart/ — provide menu bar and tool bars of the stand-alone &kdevelop; user interface designer. + kdevassistant/ — provides the menu and tool bars of the stand-alone &tdevelop; Assistant documentation browser. + kdevdesigner/ and kdevdesignerpart/ — provide menu bar and tool bars of the stand-alone &tdevelop; user interface designer. @@ -96,7 +96,7 @@ There are quite a lot of default configuration subdirectories in kdevappwizard/ — contains files used by the &appwizard; part: - importfiles/ — contains .kdevelop project files which control the initialization of a new project. + importfiles/ — contains .tdevelop project files which control the initialization of a new project. imports/ — contains templates to set up project specific .desktop files. template-common/ — contains various files commonly included in the project source directories. templates/ — contains configuration files which describe the information to be included in a given project source directory. @@ -105,7 +105,7 @@ There are quite a lot of default configuration subdirectories in kdevastyle/ — provides the Reformat Source entry in the Edit menu. - kdevautoproject/ — provides most of the entries in the Build menu and the Build Toolbar (&kdevelop;) toolbar. + kdevautoproject/ — provides most of the entries in the Build menu and the Build Toolbar (&tdevelop;) toolbar. kdevclassview/ — contains files used by the Class View project plugin: @@ -123,7 +123,7 @@ There are quite a lot of default configuration subdirectories in kdevdocumentation/ — contains files used by the Documentation plugin: en/ and pics/ — contain files used by the htdig search tool. - tocs/ — contain the default &kdevelop; documentation content description files (see the description in Basic Structure of &kdevelop; TOC Files). + tocs/ — contain the default &tdevelop; documentation content description files (see the description in Basic Structure of &tdevelop; TOC Files). kdevpart_documentation.rc — provides the search related entries in the Help menu. @@ -212,20 +212,20 @@ All information about user defined settings is kept in two subdirectories of Application Specific Configuration -Any user changes to the &kdevelop; Default Configuration settings as well as user specific settings which are not kept in any of the Resource Configuration Files are found in kdev... subdirectories of the $KDEHOME/share/apps/ directory. +Any user changes to the &tdevelop; Default Configuration settings as well as user specific settings which are not kept in any of the Resource Configuration Files are found in kdev... subdirectories of the $KDEHOME/share/apps/ directory. -Most of these configuration files are however used by various &kdevelop; plugins in order to provide some specific menu and/or toolbar entries. Thus they are of interest only in case something went really wrong with the user interface. +Most of these configuration files are however used by various &tdevelop; plugins in order to provide some specific menu and/or toolbar entries. Thus they are of interest only in case something went really wrong with the user interface. -In case the contents of these directories mirror those of the Default Configuration settings, &kdevelop; will have copied them from $KDEDIR/apps/ into the $KDEHOME/apps/ directory on its initial start. Any subsequent changes will be made to these copies only. The Default Configuration settings remain unchanged in any case. +In case the contents of these directories mirror those of the Default Configuration settings, &tdevelop; will have copied them from $KDEDIR/apps/ into the $KDEHOME/apps/ directory on its initial start. Any subsequent changes will be made to these copies only. The Default Configuration settings remain unchanged in any case. kdevabbrev/ — contains files used by the Abbreviation Expansion plugin: - sources/ — currently empty; &kdevelop; uses the default keyword definition files for Expand Text commands. + sources/ — currently empty; &tdevelop; uses the default keyword definition files for Expand Text commands. templates/ — contains the user modified template definition files used by the Expand Abbreviation command. kdevabbrev.rc — provides the Expand Text and Expand Abbreviation entries in the Edit menu. @@ -252,7 +252,7 @@ In case the contents of these directories mirror those of the Default Configurat newclass/ — contains the actual header and source templates from which the &appwizard; builds the according source files. - pcs/ — contains database files &kdevelop; uses build the actual Persistent Code Store (.pcs) file of a &kde; C++ project. + pcs/ — contains database files &tdevelop; uses build the actual Persistent Code Store (.pcs) file of a &kde; C++ project. kdevcppsupport.rc — provides the Complete Text and Make Member entries fo the Edit menu, the Switch Header/Implementation entry for the View menu, and the New Class entry for the Project menu as well as a New Class icon for the Browser Toolbar. @@ -273,10 +273,10 @@ In case the contents of these directories mirror those of the Default Configurat The directories in kdevdocumentation/ mainly hold actual bookkeeping information. The actually set up documentation files are kept in doc...pluginrc files in the $KDEHOME/share/config/ directory. - bookmarks/ — maintains the entries in the Bookmarks tab of the &kdevelop; Documentation plugin. + bookmarks/ — maintains the entries in the Bookmarks tab of the &tdevelop; Documentation plugin. - index/ — holds various cache files &kdevelop; uses to speed up indexed documentation searches in the Index tab of the Documentation plugin. + index/ — holds various cache files &tdevelop; uses to speed up indexed documentation searches in the Index tab of the Documentation plugin. search/ — contains files used by the htdig search tool which serves search calls from the Search tab of the Documentation plugin. @@ -290,10 +290,10 @@ In case the contents of these directories mirror those of the Default Configurat kdevdoxygen/ — provides the menu entries for the Doxygen Support project plugin. - kdevelop/ — contains some actual settings &kdevelop; uses for its basic setup: + tdevelop/ — contains some actual settings &tdevelop; uses for its basic setup: - profiles/ — provides actual plugin profile setting. (Initially there is only a FullIDE profile which defines a full set of initially active &kdevelop; plugins.) - kdevelopui.rc — provides the basic menu and tool bar entries &kdevelop; uses. + profiles/ — provides actual plugin profile setting. (Initially there is only a FullIDE profile which defines a full set of initially active &tdevelop; plugins.) + tdevelopui.rc — provides the basic menu and tool bar entries &tdevelop; uses. @@ -345,32 +345,32 @@ In case the contents of these directories mirror those of the Default Configurat Resource Configuration Files -There are two groups of &kdevelop; configuration files in the $KDEHOME/share/config/ directory, distiguished by their surrounding character sequences: +There are two groups of &tdevelop; configuration files in the $KDEHOME/share/config/ directory, distiguished by their surrounding character sequences: doc...pluginrc denotes files used by the documentation plugin. - kdev...rc denotes configuration files used by &kdevelop; itself and its available plugins. + kdev...rc denotes configuration files used by &tdevelop; itself and its available plugins. -Configuration Files Used by &kdevelop; +Configuration Files Used by &tdevelop; kdevabbrevrc — holds the current state of the Abbreviations configuration provided by the Abbreviation Expansion plugin. This only records whether the abbreviations will be used or not. The actual definitions of new abbreviations will go into the $KDEHOME/share/apps/kdevabbrev/templates/templates file. - kdevassistantrc — holds some configuration states specific of the stand-alone &kdevelop; Assistant documentation browser. - Most common configuration settings are shared with the &kdevelop; IDE kdeveloprc file. + kdevassistantrc — holds some configuration states specific of the stand-alone &tdevelop; Assistant documentation browser. + Most common configuration settings are shared with the &tdevelop; IDE tdeveloprc file. - kdevassistantuimode4rc — holds the current MDI configuration states (dock positions &etc;) of the stand-alone &kdevelop; Assistant documentation browser. + kdevassistantuimode4rc — holds the current MDI configuration states (dock positions &etc;) of the stand-alone &tdevelop; Assistant documentation browser. kdevclassviewrc — holds the View Mode setting of the Classes class browser tab provided by the Class View project plugin. This is a global setting, although the Class View plugin may be disabled on a per project basis. Any change in this setting will be globally updated whenever the current project is closed and thus affect all subsequently loaded projects. kdevcppsupportrc — holds some settings used to set up CPP source files. In particular you will find the settings made on the C++ Class Generator configuration dialog in here. kdevdocumentationrc — holds actual settings the Documentation plugin uses. - kdeveloprc — holds the global settings the &kdevelop; IDE and the &kdevelop; Assistant stand-alone documentation browser will use. - kdevelopuimode4rc — holds the current MDI configuration states (dock positions &etc;) of the &kdevelop; IDE. + tdeveloprc — holds the global settings the &tdevelop; IDE and the &tdevelop; Assistant stand-alone documentation browser will use. + tdevelopuimode4rc — holds the current MDI configuration states (dock positions &etc;) of the &tdevelop; IDE. kdevfileselectorrc — holds actual settings the File Selector plugin uses. kdevfileviewrc — holds the actual filename color settings the CVS Integration (Cervisia) project plugin uses for display. kdevfilterrc — holds actual settings the Shell Filtering and Insertion plugin uses. @@ -399,10 +399,10 @@ There are two groups of &kdevelop; configuration files in the -&kdevelop; User Interface Mode Examples +&tdevelop; User Interface Mode Examples IDEAl Mode @@ -11,10 +11,10 @@ Click here to return to the modes overview - + Screenshot - &kdevelop; IDEAl mode + &tdevelop; IDEAl mode @@ -25,10 +25,10 @@ Click here to return to the modes overview - + Screenshot - &kdevelop; IDEAl mode, closed tabs + &tdevelop; IDEAl mode, closed tabs @@ -57,10 +57,10 @@ Click here to return to the modes overview - + Screenshot - &kdevelop; child frame windows mode + &tdevelop; child frame windows mode @@ -82,10 +82,10 @@ Click here to return to the modes overview - + Screenshot - &kdevelop; tabbed pages mode + &tdevelop; tabbed pages mode @@ -107,10 +107,10 @@ Click here to return to the modes overview - + Screenshot - &kdevelop; toplevel windows mode + &tdevelop; toplevel windows mode diff --git a/doc/kdevelop/applicationwizard.docbook b/doc/kdevelop/applicationwizard.docbook index 6370cb12..601cc801 100644 --- a/doc/kdevelop/applicationwizard.docbook +++ b/doc/kdevelop/applicationwizard.docbook @@ -16,10 +16,10 @@ &appwizard; -In &kdevelop; software development work is organized in projects. Such a project keeps everything together which belongs to a complete programming task: source files, additional data files, any actually needed management facilities as the make system as well as access to all components and any additional tools needed to get the application up and running. +In &tdevelop; software development work is organized in projects. Such a project keeps everything together which belongs to a complete programming task: source files, additional data files, any actually needed management facilities as the make system as well as access to all components and any additional tools needed to get the application up and running. -Organizing all development work in projects allows you to easily switch between the global tasks at hand. This is quite handy if you ⪚ work on several applications at the same time as is often the case. Tell &kdevelop; to open the project you want to work at and you may proceed in the environment just where you left. +Organizing all development work in projects allows you to easily switch between the global tasks at hand. This is quite handy if you ⪚ work on several applications at the same time as is often the case. Tell &tdevelop; to open the project you want to work at and you may proceed in the environment just where you left. @@ -36,7 +36,7 @@ Organizing all development work in projects allows you to easily switch between Whenever you want to initiate a new programming project quite a lot of formal setup procedures need to be done. An initial directory structure has to be set up, initial header and source files must be provided, the make system has to be initialized, &etc; -&kdevelop; provides an easy way to initiate a new programming project—the &appwizard;. You will find the &appwizard; at menu entry Project New Project. +&tdevelop; provides an easy way to initiate a new programming project—the &appwizard;. You will find the &appwizard; at menu entry Project New Project. Only a short series of steps is necessary to start a new programming project, using the &appwizard;: @@ -83,7 +83,7 @@ Let's look at all this in more detail now ... project -To create a new project in &kdevelop;, select New Project from the Project menu. The Create New Project dialog will pop up showing an initial General page: +To create a new project in &tdevelop;, select New Project from the Project menu. The Create New Project dialog will pop up showing an initial General page: @@ -318,7 +318,7 @@ There are two ways to select another path for your new application. One is to se This is done in the second row input field of the Properties, named Location. What you enter here is the starting path of the new application development directory. The &appwizard; appends the application name to this path when it initializes the new project. The result is shown in the Final location line to give you better control on what is going on. -&appwizard; will copy an initial value to the Location field on start-up. This is taken from what you have chosen in the Default projects directory field during the general configuration steps. In our case we have &kdevelop; set up to use /home/devel/projects/ as initial path for new projects. +&appwizard; will copy an initial value to the Location field on start-up. This is taken from what you have chosen in the Default projects directory field during the general configuration steps. In our case we have &tdevelop; set up to use /home/devel/projects/ as initial path for new projects. Alter the Location field contents so that the application development directory shown in the Final location line will be unique. @@ -439,7 +439,7 @@ Otherwise you must reselect the version control system you want to use from the -A version control system such as &CVS; (which means Concurrent Versions System) stores copies of selected project files in some sort of a database. If you use &CVS; you can amongst others upload (commit) those files or load them back into your project directory (checkout, or update). The special thing about this is that the files in the versioning database are stored in a structured way which allows you to always revert to an earlier development state if you need so. And &CVS; allows multiple designers to fairly easily collaborate on a big project (such as &kdevelop;) without disturbing each others work. +A version control system such as &CVS; (which means Concurrent Versions System) stores copies of selected project files in some sort of a database. If you use &CVS; you can amongst others upload (commit) those files or load them back into your project directory (checkout, or update). The special thing about this is that the files in the versioning database are stored in a structured way which allows you to always revert to an earlier development state if you need so. And &CVS; allows multiple designers to fairly easily collaborate on a big project (such as &tdevelop;) without disturbing each others work. @@ -465,7 +465,7 @@ A version control system such as &CVS; (which means Concurrent Versions S &CVS; Root -&CVS; needs to manage the versioning database it keeps from your project files. To accomplish this it keeps some special database information in an own directory, called the &CVS; root. The first step on setting up &CVS; for your new project thus is to tell &kdevelop; where this root is located. +&CVS; needs to manage the versioning database it keeps from your project files. To accomplish this it keeps some special database information in an own directory, called the &CVS; root. The first step on setting up &CVS; for your new project thus is to tell &tdevelop; where this root is located. @@ -483,10 +483,10 @@ In fact, this is a short form. Exactly, the local &CVS; root should be addressed Enter the name of the &CVS; root directory your system has been set up for in the CVS root field. In principle you can select any name, even use multiple &CVS; databases, but it is advisable that you stick to the &CVS; root once set up. -Initialize a new &CVS; root. If there does not exist a &CVS; root yet, &kdevelop; can command the &CVS; system to create one for you in the given directory. Just check the Init root checkbox below the CVS root field. +Initialize a new &CVS; root. If there does not exist a &CVS; root yet, &tdevelop; can command the &CVS; system to create one for you in the given directory. Just check the Init root checkbox below the CVS root field. -As said, &kdevelop; only commands the &CVS; system to initialize a new &CVS; root. It does nothing by itself to this directory. Fortunately &CVS; is clever enough to check whether the &CVS; root directory already exists. Hence it does no harm if you should have inadvertently checked Init root on an already existing &CVS; root directory. +As said, &tdevelop; only commands the &CVS; system to initialize a new &CVS; root. It does nothing by itself to this directory. Fortunately &CVS; is clever enough to check whether the &CVS; root directory already exists. Hence it does no harm if you should have inadvertently checked Init root on an already existing &CVS; root directory. @@ -540,11 +540,11 @@ for an rsh or ssh encrypted server type. For example accesses the &CVS; root of the widely used Cervisia &CVS; management tool on the SourceForge server. -If you want to use an rsh or ssh encrypted server for &CVS; access you must tell &kdevelop; the encryption protocol to be used. Just enter rsh or ssh in the CVS_RSH field of the Create New Project Version Control System page. +If you want to use an rsh or ssh encrypted server for &CVS; access you must tell &tdevelop; the encryption protocol to be used. Just enter rsh or ssh in the CVS_RSH field of the Create New Project Version Control System page. -There is a caveat if you use an encrypted server for &CVS; from within &kdevelop;. See the Using &CVS; chapter for details. +There is a caveat if you use an encrypted server for &CVS; from within &tdevelop;. See the Using &CVS; chapter for details. @@ -557,7 +557,7 @@ There is a caveat if you use an encrypted server for &CVS; from within &kdevelop The &CVS; Repository -So far you have told &kdevelop; where the &CVS; root resides which manages the versioning database and how to access it. Now you need to tell &kdevelop; under which name you want &CVS; save your project files in that database. Such a place your project files will be held in &CVS; is called a repository. +So far you have told &tdevelop; where the &CVS; root resides which manages the versioning database and how to access it. Now you need to tell &tdevelop; under which name you want &CVS; save your project files in that database. Such a place your project files will be held in &CVS; is called a repository. @@ -592,7 +592,7 @@ The &appwizard; has put a default start tag in here which is a wo -When any information of all these is wrong &kdevelop; usually will not know about until project construction time. It is the &CVS; system which will figure out those errors when it tries to build the repository. Hence you must keep an eye to the Messages window of &kdevelop; when the project is created in the final setup step. If anything was in error with &CVS; you will in most cases see an error message like this: +When any information of all these is wrong &tdevelop; usually will not know about until project construction time. It is the &CVS; system which will figure out those errors when it tries to build the repository. Hence you must keep an eye to the Messages window of &tdevelop; when the project is created in the final setup step. If anything was in error with &CVS; you will in most cases see an error message like this: @@ -606,7 +606,7 @@ When any information of all these is wrong &kdevelop; usually will not know abou -If this happens you will have to either manually set up &CVS; (&kdevelop; should have successfully initialized your project files at this time) or delete the project directory and start over again with New Project from the Project menu. +If this happens you will have to either manually set up &CVS; (&tdevelop; should have successfully initialized your project files at this time) or delete the project directory and start over again with New Project from the Project menu. @@ -675,10 +675,10 @@ As you might have noticed, the applications manager did readily fill in some inf edit -The templates you set up in the Create New Project dialog will later be processed whenever you command &kdevelop; to set up a new source and/or header file. The information you provided here will be included at top as a documentation header, before the code parts begin. +The templates you set up in the Create New Project dialog will later be processed whenever you command &tdevelop; to set up a new source and/or header file. The information you provided here will be included at top as a documentation header, before the code parts begin. -You are not restricted to plain text however. &kdevelop; knows of several variables which allow you to include actual information in the file. The &appwizard; did in fact use some such variables to insert the Author, Email, and License informations into the initial template text. +You are not restricted to plain text however. &tdevelop; knows of several variables which allow you to include actual information in the file. The &appwizard; did in fact use some such variables to insert the Author, Email, and License informations into the initial template text. @@ -695,7 +695,7 @@ If, for example, you want the &doxygen;-built &API; documentation to display som **/ -Whenever you create a new source file, &kdevelop; will replace the $MODULE$ variable by the name body of the newly created file. For example, if you created a new C++ class named ASimpleTest you will see the following lines in the asimpletest.cpp file: +Whenever you create a new source file, &tdevelop; will replace the $MODULE$ variable by the name body of the newly created file. For example, if you created a new C++ class named ASimpleTest you will see the following lines in the asimpletest.cpp file: /** @@ -735,7 +735,7 @@ for the GPL license, or if you decided to put your application under the BSD license. -Thee are of course more variables &kdevelop; knows of. See the Editing the templates section in the Editing tools chapter for what is possible. +Thee are of course more variables &tdevelop; knows of. See the Editing the templates section in the Editing tools chapter for what is possible. @@ -773,7 +773,7 @@ If you want to use a versioning system (&CVS;) there will be two runs actually. -In many cases when your new project has been set up this way, &kdevelop; will automatically load the source file(s) of one or more basically important modules so you can readily start work. (Which source modules will be displayed—if any at all—however depends on the template initially selected in the &appwizard;.) +In many cases when your new project has been set up this way, &tdevelop; will automatically load the source file(s) of one or more basically important modules so you can readily start work. (Which source modules will be displayed—if any at all—however depends on the template initially selected in the &appwizard;.) diff --git a/doc/kdevelop/class-browsers.docbook b/doc/kdevelop/class-browsers.docbook index 7c251ee1..a0358761 100644 --- a/doc/kdevelop/class-browsers.docbook +++ b/doc/kdevelop/class-browsers.docbook @@ -6,7 +6,7 @@ When working on a project in an object-oriented language, your emphasis when working on a project is not on the source files and their names, but on the classes and their relationships. In order to help you navigating in the space -of defined classes and symbols, &kdevelop; includes various class browsers +of defined classes and symbols, &tdevelop; includes various class browsers that visualize the class structure in different ways. diff --git a/doc/kdevelop/credits.docbook b/doc/kdevelop/credits.docbook index 77712cc4..d47af015 100644 --- a/doc/kdevelop/credits.docbook +++ b/doc/kdevelop/credits.docbook @@ -7,7 +7,7 @@ - The initial contents of this manual were witten by Bernd Gehrmann bernd@kdevelop.org and Caleb Tennis caleb@aei-tech.com. + The initial contents of this manual were witten by Bernd Gehrmann bernd@tdevelop.org and Caleb Tennis caleb@aei-tech.com. The Summary of &automanag; and Automake Manager Operation chapters were written by Ian Wadham, ianw@netspace.net.au). diff --git a/doc/kdevelop/cvs.docbook b/doc/kdevelop/cvs.docbook index ccdce4e6..116e24f6 100644 --- a/doc/kdevelop/cvs.docbook +++ b/doc/kdevelop/cvs.docbook @@ -39,7 +39,7 @@ differences between revisions, the revision history of files &etc; with the repository goes through the command line program &cvs;. A higher level user interface is available through frontends like &cervisia; () or TkCVS (). In &kdevelop;, only a small part of the &cvs; +url="http://tkcvs.sf.net"/>). In &tdevelop;, only a small part of the &cvs; functionality which is important for your daily work can be used directly. @@ -56,7 +56,7 @@ distributed (except for the non-technical chapters). See -&CVS; Commands in &kdevelop; +&CVS; Commands in &tdevelop; In the file views, the following context menu items are available: @@ -109,7 +109,7 @@ Otherwise, when another user has committed his own changes before, -All these commands are invoked as subprocesses by &kdevelop; without any +All these commands are invoked as subprocesses by &tdevelop; without any further command line options or environment variables. This may be a problem when the connection with the &CVS; server goes through a &ssh; connection and requires that you enter your password each time diff --git a/doc/kdevelop/debugger.docbook b/doc/kdevelop/debugger.docbook index a06f2c83..247d26ff 100644 --- a/doc/kdevelop/debugger.docbook +++ b/doc/kdevelop/debugger.docbook @@ -3,7 +3,7 @@ debugger -For C and C++, &kdevelop; contains an internal debugger that is directly +For C and C++, &tdevelop; contains an internal debugger that is directly integrated with the editor. Technically, it is implemented as a frontend that uses the portable &GNU; debugger gdb through a pipe. The debugger can be started in several ways: @@ -100,13 +100,13 @@ via the context menu. breakpoints This window allows you to see and manipulate the breakpoints. Remember that -&kdevelop; uses GDB, so to fully understand the -&kdevelop; debugging features, you should know a little bit about the GDB, so to fully understand the +&tdevelop; debugging features, you should know a little bit about the GDB. If you want to look at the source code, breakpoints are defined in -kdevelop/languages/cpp/debugger/breakpoint.h. +tdevelop/languages/cpp/debugger/breakpoint.h. At the left edge, the window has buttons to: @@ -215,10 +215,10 @@ The debugger backend gdb does not allow to set breakpoints within code that is not currently loaded. In a highly modular application, where often code is only loaded on demand as a plugin (using the libc function dlopen(3)), this can be inconvenient. -Therefore, &kdevelop; rolls its own support for breakpoints in shared +Therefore, &tdevelop; rolls its own support for breakpoints in shared libraries. If you set this option, it allows you to set breakpoints in libraries which are not loaded. Then, whenever gdb -notifies that a library is loaded, &kdevelop; tries to set the pending +notifies that a library is loaded, &tdevelop; tries to set the pending breakpoints. diff --git a/doc/kdevelop/documentation.docbook b/doc/kdevelop/documentation.docbook index eed065b0..2214fed3 100644 --- a/doc/kdevelop/documentation.docbook +++ b/doc/kdevelop/documentation.docbook @@ -36,7 +36,7 @@ Documentation has multiple facets. There is -All this documentation should be easily maintainable and ready at hand whenever you need it. &kdevelop; has provisions for just this. +All this documentation should be easily maintainable and ready at hand whenever you need it. &tdevelop; has provisions for just this. diff --git a/doc/kdevelop/file-browsers.docbook b/doc/kdevelop/file-browsers.docbook index f8b37735..93a096e5 100644 --- a/doc/kdevelop/file-browsers.docbook +++ b/doc/kdevelop/file-browsers.docbook @@ -2,7 +2,7 @@ The File Browsers -On the left side of the main window, &kdevelop; can display various kinds of +On the left side of the main window, &tdevelop; can display various kinds of lists and trees for the selection of files: @@ -13,14 +13,14 @@ lists and trees for the selection of files: This shows a tree view of the file hierarchy below the project directory. If you click on a file, it is loaded into the editor. For files which do not -contain text, &kdevelop; starts an application that can handle the respective +contain text, &tdevelop; starts an application that can handle the respective MIME type. The file tree is regularly updated whenever something changes in the file system. For example, if you create new files or directories (even outside -&kdevelop;), this is immediately reflected in the file list. On &Linux;, +&tdevelop;), this is immediately reflected in the file list. On &Linux;, this feature makes use of the FAM library. On other operating systems or over NFS, the directories shown are polled in small intervals. @@ -62,7 +62,7 @@ The groups shown in this view can be configured under File views in the Project options dialog. In order to customize the view to your needs, it is helpful to understand how files are distributed on -the groups. For each file, &kdevelop; goes through all groups from top to +the groups. For each file, &tdevelop; goes through all groups from top to bottom. In each group, it looks whether the file name matches one of the patterns. If there is a match, the file is shown in this group and the iteration is aborted. This makes it clear that more general patterns should 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. -Getting Started with &kdevelop; — a Guided Tour +Getting Started with &tdevelop; — a Guided Tour -Now that you have got your new &kdevelop; &IDE;, how are you going to make +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. @@ -27,7 +27,7 @@ at: A first look — the user -interface elements of the &kdevelop; &IDE;. +interface elements of the &tdevelop; &IDE;. Doing some initial configuration. How to create a new project. @@ -50,20 +50,20 @@ shortcuts What to expect? -As said, &kdevelop; is an Integrated Development -Environment. That means in essence that &kdevelop; is no development +As said, &tdevelop; is an Integrated Development +Environment. 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. -While &kdevelop; eases many of those programming tasks, much of the +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. 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 Development on &UNIX; historical overview and there @@ -71,20 +71,20 @@ especially at the Integrating Concepts and Tools chapter. -The following discussions apply to the default case, where &kdevelop; +The following discussions apply to the default case, where &tdevelop; starts up in the Simplified IDEAl Window Mode. 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 Settings Configure KDevelop... User Interface dialog. -A Very First Look at &kdevelop; +A Very First Look at &tdevelop; -This is all about what you will see when you first started &kdevelop;. +This is all about what you will see when you first started &tdevelop;. You will find preliminary information about: @@ -101,7 +101,7 @@ for? On the Surface -When you start &kdevelop; for the first time you will get a display +When you start &tdevelop; for the first time you will get a display similar to this one: @@ -110,8 +110,8 @@ similar to this one: -The &kdevelop; initial layout -(Actually the initial &kdevelop; window will be larger, but the elements +The &tdevelop; initial layout +(Actually the initial &tdevelop; window will be larger, but the elements you see are the same.) @@ -119,7 +119,7 @@ you see are the same.) Workspace Area and Tool View Tabs -In this initial case &kdevelop; uses the so-called In this initial case &tdevelop; uses the so-called IDEAl user interface mode. 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 Command Reference. Usual Actions This is pretty standard. It allows to create, open, save, print, and close -document files as well as quitting the &kdevelop; application as usual. +document files as well as quitting the &tdevelop; application as usual. @@ -282,7 +282,7 @@ text. Project -All work of &kdevelop; is based on projects which +All work of &tdevelop; is based on projects 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. Breakpoints -&kdevelop; provides several means to set breakpoints in your application +&tdevelop; provides several means to set breakpoints in your application sources. One is through the use of the Toggle Breakpoint menu entry. @@ -406,7 +406,7 @@ editor window horizontally as well as vertically. Tools -&kdevelop; is highly customizable. +&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 Tools menu reflects most of this setup. @@ -445,7 +445,7 @@ purposes. 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. +&tdevelop;'s general behavior. @@ -496,7 +496,7 @@ different main purpose. 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 Plugin -Tools being currently available to &kdevelop;. You will find more on this +Tools being currently available to &tdevelop;. You will find more on this topic in the Configuring KDevelop chapter. Currently, with no project open and the default number of plugin tools @@ -534,7 +534,7 @@ menu. Application Displays the output from an application started from within -&kdevelop;. +&tdevelop;. @@ -548,7 +548,7 @@ Viewer... menu. Messages Displays messages produced by the build tools called from within -&kdevelop;, usually from the Build menu. +&tdevelop;, usually from the Build menu. @@ -570,7 +570,7 @@ or not. 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 Edit Find-Select-Replace... menu will in fact be be disabled. @@ -590,7 +590,7 @@ interface. Documentation -&kdevelop; provides access to a whole bunch of documentation through this +&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. @@ -621,19 +621,19 @@ chapters. A Bit of Configuration 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. -If you want to know more about &kdevelop; configuration, have a look at +If you want to know more about &tdevelop; configuration, have a look at the Configuring KDevelop chapter. Some General Settings -To configure &kdevelop;, click the +To configure &tdevelop;, click the Settings menu and select Configure KDevelop.... The Configure KDevelop dialog will pop up, showing the @@ -645,7 +645,7 @@ following General settings page to the right. -The &kdevelop; general configuration dialog +The &tdevelop; general configuration dialog @@ -655,7 +655,7 @@ But you will probably want to change two of those settings. Default projects directory -At first start of &kdevelop; this will most likely be preset to your home +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 projects with your development directory name. -&kdevelop; will by default set up an own subdirectory below this parent +&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 Hello in our case be located in the /home/devel/projects/hello directory. @@ -682,15 +682,15 @@ for more info on this. Compiler output -Whenever &kdevelop; compiles some source, it will display the messages of +Whenever &tdevelop; compiles some source, it will display the messages of the make, etc. build tools in the Messages 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. -Depending on the &kdevelop; version you use, the Compiler +Depending on the &tdevelop; version you use, the Compiler output selection may be preset to Long, which will cause all message contents be fully shown. You may probably want to change this to the far more convenient Very Short setting. Just select this @@ -711,13 +711,13 @@ Output from the popup menu. 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. +toward actual &tdevelop; work. Open the Documentation tool view at the right side of -the &kdevelop; main window. There open the Search dialog +the &tdevelop; main window. There open the Search dialog page. @@ -734,7 +734,7 @@ basic search tools are properly set up. A dialog should pop up, telling Configuration file updated. Click OK to make it disappear. -This done, &kdevelop; will be ready to parse the documentation it knows of +This done, &tdevelop; will be ready to parse the documentation it knows of and build some useful search indexes from it. Press the Update Index button to the right. Now the Generating Search Index dialog will pop up showing the progress of the index build @@ -745,7 +745,7 @@ operations. -&kdevelop; is generating documentation search +&tdevelop; is generating documentation search indexes. @@ -758,7 +758,7 @@ place to OK. Just press this button to proceed. This usually should work out of the box. In some cases the -htdig application &kdevelop; uses to perform its full +htdig application &tdevelop; uses to perform its full text searches might not be properly set up. Refer to the Setting Up Text Search Indexes chapter for more help in this case. @@ -766,10 +766,10 @@ for more help in this case. To be able to look up &kde; and &Qt; specific API documentation, it is mandatory that the KDELibs Apidocs 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 identifier lookup examples later in this chapter, make sure that this documentation exists -and is accessible to &kdevelop;. See Installing +and is accessible to &tdevelop;. See Installing KDevelop fore more detail. @@ -783,17 +783,17 @@ KDevelop fore more detail. 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 projects. Thus the first practical step to develop software -in &kdevelop; usually is to create a new project. +in &tdevelop; usually is to create a new project. -Fortunately this is fairly easily accomplished. &kdevelop; provides the +Fortunately this is fairly easily accomplished. &tdevelop; provides the so-called &appwizard; tool for this. (See the Getting Started — the &appwizard; chapter for more.) 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: @@ -927,7 +927,7 @@ The &appwizard; will take over and construct a series of initial files in the Final location directory you provided in step 2c above. -Once this file creation phase is finished, &kdevelop; will open an editor +Once this file creation phase is finished, &tdevelop; will open an editor window for the application main window implementation file (which is hello.cpp in our example), so you can readily proceed. @@ -990,8 +990,8 @@ created. 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 templates directory. @@ -1040,13 +1040,13 @@ application, namely hello.desktop contains some meta data used by -&kdevelop; to maintain and start the application. +&tdevelop; to maintain and start the application. hi16-app-hello.png, and hi32-app-hello.png contain some initial default icons, -&kdevelop; will use for application display. +&tdevelop; will use for application display. @@ -1103,7 +1103,7 @@ application. Those Makefile.am 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 Makefile.am contents. @@ -1118,20 +1118,20 @@ binaries. -&kdevelop; Control Files -&kdevelop; needs some control and administration data on its own. These +&tdevelop; Control Files +&tdevelop; needs some control and administration data on its own. These are located in the project root directory, in our example -hello.kdevelop, hello.kdevelop.pcs, +hello.tdevelop, hello.tdevelop.pcs, and hello.kdevses. Of particular importance in each project is the -xxx.kdevelop (where xxx denotes the project +xxx.tdevelop (where xxx denotes the project name) file. It is the main KDevelop 3 Project File and needed if you later want load this project into the &IDE;. -Never do manually modify, rename, or even delete any of these &kdevelop; +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. @@ -1203,7 +1203,7 @@ functionality. The tool views actually visible depend on the plugins currently loaded -into &kdevelop;. There are ways to control this. See the Plugin Tools chapter for instructions. @@ -1215,7 +1215,7 @@ linkend="setup-plugins">Plugin Tools chapter for instructions. Bookmarks 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 bookmarks, even if you close the editor window afterwards. The Bookmarks 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. Security Problems There is a Security Checker 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. @@ -1297,7 +1297,7 @@ position the cursor on the appropriate identifier there. Problems -&kdevelop; keeps track of common programming problems in the currently +&tdevelop; keeps track of common programming problems in the currently edited source file and notifies the user in this tool view window. @@ -1345,7 +1345,7 @@ a more extensive description. hello.cpp 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: @@ -1363,7 +1363,7 @@ common problems. Switching Between Header and Implementation Files -&kdevelop; provides a quick and easy way to switch from a given +&tdevelop; provides a quick and easy way to switch from a given implementation (.cpp) file to the corresponding header (.h) file and vice versa. Just right click into the editor window you want to switch. A menu similar to the following will pop up. @@ -1379,20 +1379,20 @@ files. Find the Switch header/implementation 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 hello.cpp source, the hello.h file will be displayed and the cursor positioned there. 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. 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. @@ -1417,8 +1417,8 @@ internal text items. 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. Let us look at an example. In the hello.cpp editor @@ -1475,7 +1475,7 @@ then come back here and try again. 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 CTags application to search the sources in your project. @@ -1518,14 +1518,14 @@ possibilities. Use the CTags tool view This is easy. Just start typing the identifier name you are interested in into the -Lookup input field in the bottom left. &kdevelop; will try +Lookup 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. If for example you want to know wherever the Hello identifier was used in our example project, type an "H" into the -Lookup input field. &kdevelop; will immediately start +Lookup input field. &tdevelop; will immediately start working and present you a result like this: @@ -1538,7 +1538,7 @@ tool view. -If you click one of the listed entries, &kdevelop; will open an editor +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. @@ -1568,7 +1568,7 @@ internal identifier. Click what you are interested in, say CTags - Go to Definition: -Hello, and &kdevelop; will immediately open the +Hello, and &tdevelop; will immediately open the hello.cpp editor window and position the cursor right in front of this class definition: @@ -1583,7 +1583,7 @@ Hello::Hello() Do a global search 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;. +&tdevelop;. @@ -1602,7 +1602,7 @@ The outcome of the menu call will essentially be the same. Let us assume you are studying the hello.cpp source file and have the cursor positioned on the first Hello occurrence there. Now you wonder, where this one word Hello 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. Now, still keeping the cursor somewhere on this Hello in @@ -1645,13 +1645,13 @@ the Search button at the bottom right. Now the Find in Files tool view will open at the bottom, showing you file names and lines of all literal occurrences of Hello 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. There are two lines of special interest in the tool view window. -Right on top you will find the command sequences &kdevelop; did actually +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. @@ -1663,7 +1663,7 @@ listed. In our example this should read *** 11 matches found -&kdevelop; will remember these search results throughout the currently +&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 Find in Files tool view window. @@ -1678,7 +1678,7 @@ window. 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. How to remove unneeded @@ -1699,7 +1699,7 @@ files into development sessions. 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. @@ -1727,7 +1727,7 @@ may find in other &kde; applications as well. You can use the 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. @@ -1766,7 +1766,7 @@ step. 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. @@ -1774,7 +1774,7 @@ to proceed with a clean tab bar again. How to Rearrange Edit Window Tabs 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: @@ -1784,7 +1784,7 @@ some common means to do so, in short: 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. -You must change a basic user interface setting in &kdevelop; to enable +You must change a basic user interface setting in &tdevelop; to enable this behavior. @@ -1802,7 +1802,7 @@ Browsing. Remove the check mark on the Open new tab after current tab line. -Close &kdevelop; and restart it again. Now the new editor window tabs will +Close &tdevelop; and restart it again. Now the new editor window tabs will open at the far right end of the current tabs row. @@ -1810,13 +1810,13 @@ open at the far right end of the current tabs row. 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;. +&tdevelop;. How to Rearrange the Tabs 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;. +&tdevelop;. 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. 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. @@ -1905,11 +1905,11 @@ It closes automatically, once the last tabbed window in it was closed. Edit C++ Source and Header Files Simultaneously 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 .cpp source and its accompanying .h 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. This feature is however deactivated by default. If you want to use it in @@ -1942,7 +1942,7 @@ both the hello.cpp and hello.h editor windows, if necessary. Then select hello.cpp again from the src subdirectory of the project. The editor window will open as usual. But if you now open the -hello.h belonging to it, &kdevelop; will automatically +hello.h belonging to it, &tdevelop; will automatically split the workspace and open this header file editor window just beneath the hello.cpp window. @@ -1953,7 +1953,7 @@ line: Hello::Hello() and put the cursor there. Then look at the hello.h -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. @@ -1961,13 +1961,13 @@ constructor declaration line. -&kdevelop; automatically navigated to the constructor +&tdevelop; automatically navigated to the constructor declaration. 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. @@ -1977,7 +1977,7 @@ construct in the other. 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 File List tool view of &kdevelop; allows you +sessions. The File List tool view of &tdevelop; allows you do to just this. On top of the File List tool view window there is a @@ -2034,7 +2034,7 @@ planned. Once your file list is complete, click the Save Session -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. @@ -2042,7 +2042,7 @@ otherwise. That was it. Whenever you select the sources session -from the Open Session drop down box, &kdevelop; will close +from the Open Session drop down box, &tdevelop; will close all currently open editor windows and open the remembered ones (hello.cpp, hello.h, and main.cpp in our example) instead. @@ -2053,7 +2053,7 @@ remembered file list with a Save Session click. And if you want get rid of a session, select it in the drop down box, then click the Delete Session icon in the toolbar right. -There is even more. You can force &kdevelop; to open a given session by +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 Projects Project Options File List project @@ -2064,7 +2064,7 @@ options configuration page. -Let &kdevelop; open a specific session when the project is +Let &tdevelop; open a specific session when the project is loaded. @@ -2074,7 +2074,7 @@ loaded. Keeping an Eye on Common Problems -When you open an editor window containing a source file, &kdevelop; will +When you open an editor window containing a source file, &tdevelop; will parse its contents. This allows the built in problem reporter 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: -&kdevelop; is alerting a source code line containing a todo +&tdevelop; is alerting a source code line containing a todo mark. @@ -2153,7 +2153,7 @@ currently edited file. Note the other tabs in the Problem reporter tool view window, especially Fixme, and Todo. If you open them, you will find all FIXME and -TODO marked lines, &kdevelop; has found so far +TODO marked lines, &tdevelop; has found so far in this session. For example the TODO alerts will currently look thus: @@ -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. -You will find the &kdevelop; problem reporter facility a very valuable +You will find the &tdevelop; problem reporter facility a very valuable tool, so check the Problems tool view regularly in the development process. @@ -2182,7 +2182,7 @@ development process. How to Compile a Project -Compiling a project in &kdevelop; requires several setup steps and then +Compiling a project in &tdevelop; requires several setup steps and then building the application. All these are available through the Build menu. @@ -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. -For now we will concentrate on several facilities which &kdevelop; +For now we will concentrate on several facilities which &tdevelop; provides for project setup, initializing, building, and running an application. In general, this includes: @@ -2229,12 +2229,12 @@ initial configuration. How to build the project. How to run the -application from within &kdevelop;. +application from within &tdevelop;. 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 QMake 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. You may press the Run Them 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 Do Not run. @@ -2282,12 +2282,12 @@ through the Build menu. Call it up and select -&kdevelop; will now open the Messages tool view window at +&tdevelop; will now open the Messages 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 *** Success ***. -If you scroll back to the top, you will find the command line, &kdevelop; +If you scroll back to the top, you will find the command line, &tdevelop; issued to call up the tools beneath the surface: @@ -2295,7 +2295,7 @@ cd '/home/devel/projects/hello' && \ WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" gmake -f Makefile.cvs -This basically tells that &kdevelop; first switched to the root directory +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 autoconf and automake tool revisions used for this initialization. @@ -2323,16 +2323,16 @@ available. This done, select the Build Run Configure menu entry to initiate a configuration sequence. -&kdevelop; opened the Messages tool view +&tdevelop; opened the Messages tool view window again if necessary and listed the messages of the configure run therein. If all went right, the final messages will be Good - your configure finished. Start make now (which was issued by -configure) followed by the &kdevelop; *** Success +configure) followed by the &tdevelop; *** Success *** message. On top of the Messages window you will again find -the command line, &kdevelop; used to initiate this configuration run: +the command line, &tdevelop; used to initiate this configuration run: mkdir '/home/devel/projects/hello/debug' && \ @@ -2354,7 +2354,7 @@ CXXFLAGS="-O0 -g3" "/home/devel/projects/hello/configure" --enable-debug=full -First, &kdevelop; uses a dedicated subdirectory in the project directory +First, &tdevelop; uses a dedicated subdirectory in the project directory tree for the build process. This debug 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 In the Configuring the Project 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 debug directory — if necessary — prior to the configure call and that the configure script did build the sub structure and all the Makefiles in @@ -2374,7 +2374,7 @@ there. Next, from within the debug build -directory, &kdevelop; called the configure script in the +directory, &tdevelop; called the configure script in the root directory of our project using a dedicated environment, where the CXXFLAGS="-O0 -g3" 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. -&kdevelop; commands to build binaries. +&tdevelop; commands to build binaries. @@ -2446,14 +2446,14 @@ class="directory">Debug subtree. There are not many source files in our Hello example project, so the Messages window will contain only a few lines. On top of them again find the command line -&kdevelop; issued to the underlying shell. +&tdevelop; issued to the underlying shell. cd '/home/devel/projects/hello/debug' && \ WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_6="1" gmake -k -Not very surprisingly, &kdevelop; switched to the Not very surprisingly, &tdevelop; switched to the Debug subtree root in order to run the Makefile located there. A dedicated sub-environment was set up again as before in the gmake tool was called. Note the -k option in the gmake 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 Messages window. If there are any, use the virtues of an &IDE;: Just click on the error message in -the Messages window and &kdevelop; will take you to +the Messages window and &tdevelop; will take you to exactly the position where the error occurred in the source file. And what did happen inside the . -That was all. &kdevelop; will now start the new application in +That was all. &tdevelop; will now start the new application in the dedicated console window which opens as Application -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: @@ -2530,7 +2530,7 @@ our Hello form running. Close the Hello application window as -usual. If no errors occurred, &kdevelop; will report this as +usual. If no errors occurred, &tdevelop; will report this as *** Exited normally *** in the Application tool view window. @@ -2539,7 +2539,7 @@ in the Application tool view window. Configuring the Project -In &kdevelop; there are numerous ways how you can manage your project. +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? When we did a first run of the configure script in the Initial Hello -Configuration section above, we noted that &kdevelop; had set up a +Configuration section above, we noted that &tdevelop; had set up a dedicated debug subdirectory for this purpose. In this section we will briefly consider some consequences of this feature. -First of all, &kdevelop; does not necessarily use dedicated build +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. @@ -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. -This is where the build configurations of &kdevelop; step in. Because +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. @@ -2699,7 +2699,7 @@ environment prior to running configure as ⪚ the CXXFLAGS in our previous discussions. You may set most of the configuring options for a given project from -within &kdevelop; &GUI;. Select +within &tdevelop; &GUI;. Select Project Project Options and then from the icon bar on the left of the dialog the Configure Options @@ -2762,7 +2762,7 @@ configuration options can be defined: Configure arguments -These are the options &kdevelop; assigns to the +These are the options &tdevelop; assigns to the configure script call in the build process. See the example in the Initial Hello Configuration section above. @@ -2772,7 +2772,7 @@ the Initial Hello Configuration section above. Build directory -This is the subdirectory in the current project root, where &kdevelop; +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. C/C++ preprocessor flags (CPPFLAGS) -Put specific instructions for the preprocessor here. &kdevelop; will +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 example in @@ -2814,7 +2814,7 @@ temporary build environment as well. Environment Variables 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. @@ -2834,7 +2834,7 @@ so it suffices to have a brief look at the C++ page. -Select the compiler and its working environment &kdevelop; shall +Select the compiler and its working environment &tdevelop; shall use here. @@ -2845,8 +2845,8 @@ use here. C++ compiler -Select the C++ compiler &kdevelop; should regularly use from this -combo box. It however lists only those compilers &kdevelop; really knows +Select the C++ compiler &tdevelop; should regularly use from this +combo box. It however lists only those compilers &tdevelop; really knows of. @@ -2862,7 +2862,7 @@ Put the name by which it is called here. Compiler flags (CXXFLAGS) -Here you can enter any extra option &kdevelop; shall pass (via the +Here you can enter any extra option &tdevelop; shall pass (via the Makefile) to the compiler. Some option values will be preset according to the build configuration selected in the Configuration combo box. @@ -2900,7 +2900,7 @@ configuration would have to be altered manually if ever needed. How Make Should Build the Program -You can as well configure the way &kdevelop; will call the +You can as well configure the way &tdevelop; will call the make tool in the project build. Select Project Project Options and then the @@ -2913,7 +2913,7 @@ the right. -Define how &kdevelop; will call the +Define how &tdevelop; will call the make tool. @@ -2926,7 +2926,7 @@ You will find it deactivated in most projects. This corresponds to the linkend="gettingstarted-compile-basic-build-cmd">initial build of our example Hello project. -This makes sense in an &IDE; like &kdevelop; which will protocol any +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 Messages tool window. Use View @@ -2934,12 +2934,12 @@ window. Use View View Previous Error or respectively the F4 and Shift F4 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. If on the other hand you rather want the build be stopped on whenever an error occurs, check the Abort on first error option -in this dialog. &kdevelop; will then call gmake +in this dialog. &tdevelop; will then call gmake without the -k option. @@ -2947,11 +2947,11 @@ without the -k option. How to Run the Executable Once the build is complete, you can easily run the application from within -&kdevelop;. Use either Build +&tdevelop;. Use either Build Execute Program, the Shift F9 keys, or the Execute program button in the Build -Toolbar of &kdevelop;. +Toolbar of &tdevelop;. @@ -2963,12 +2963,12 @@ Toolbar of &kdevelop;. 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? All this can be solved by configuring some project oriented run options in -&kdevelop;. Select Project +&tdevelop;. Select Project Project Options and then the Run Options icon from the icon bar on the left dialog window side. The Run Options dialog page will display to the @@ -2990,13 +2990,13 @@ Basically there are four groups of configuration items. Directory -This tells &kdevelop; where it basically shall assume the +This tells &tdevelop; where it basically shall assume the executable to be called. There are three possibilities you can select from. 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. @@ -3012,7 +3012,7 @@ The name of this directory was set up on the General Configuration dialog page. -This is the root where &kdevelop; will find the executable. It +This is the root where &tdevelop; will find the executable. It changes automatically with the selection you made in Project Build Configurations menu. Try it. @@ -3037,17 +3037,17 @@ the version located in the project directories. Program -This tells &kdevelop; the relative position and name of the +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. +argument &tdevelop; will pass to the program when it is actually called. If leave the Main program text box empty, the active target 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. @@ -3055,7 +3055,7 @@ appears not to call the executable you wanted. Environment Variables -&kdevelop; will set up a dedicated shell environment to run the +&tdevelop; will set up a dedicated shell environment to run the program in. Define any extra environment variable in this configuration group. @@ -3070,7 +3070,7 @@ group. Automatically compile before execution 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. @@ -3081,7 +3081,7 @@ last change. Start in external terminal 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. @@ -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. -All &kde; based templates in &kdevelop; have a doc subdir which contains +All &kde; based templates in &tdevelop; have a doc subdir which contains a index.docbook template in the en folder to get you started in writing the user manual. You should edit this -index.docbook in &kdevelop; and start changing personal +index.docbook 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;. You need to install your project using Build Install or Install (as -root user) in &kdevelop; to see the user manual in +root user) in &tdevelop; to see the user manual in &khelpcenter;. You can find more about the docbook syntax on the &kde; documentation @@ -3205,7 +3205,7 @@ website. (- to be written -) -Using Existing &kdevelop; Projects +Using Existing &tdevelop; Projects (- to be written -) diff --git a/doc/kdevelop/index.docbook b/doc/kdevelop/index.docbook index 993400c0..e3d800ec 100644 --- a/doc/kdevelop/index.docbook +++ b/doc/kdevelop/index.docbook @@ -1,7 +1,7 @@ KDevelop"> --> - + + @@ -32,7 +32,7 @@ - + @@ -46,10 +46,10 @@ - + - + @@ -63,7 +63,7 @@ - + ]> @@ -76,7 +76,7 @@ Entries which require special treatment are marked with comments starting with ' - &kdevelop; User Manual + &tdevelop; User Manual 2006-06-19 &kdevrelease; @@ -86,7 +86,7 @@ Entries which require special treatment are marked with comments starting with ' Bernd Gehrmann -
bernd@kdevelop.org
+
bernd@tdevelop.org
 @@ -137,7 +137,7 @@ Entries which require special treatment are marked with comments starting with ' &FDLNotice; - &kdevelop; is an Integrated Development Environment to be used for a wide variety of programming tasks. + &tdevelop; is an Integrated Development Environment to be used for a wide variety of programming tasks. @@ -154,8 +154,8 @@ Entries which require special treatment are marked with comments starting with ' &survey-manual; &getting-started; -&kdevelop-survey; -&setup; +&tdevelop-survey; +&setup; &applicationwizard; &editing; &file-browsers; @@ -165,13 +165,13 @@ Entries which require special treatment are marked with comments starting with ' &adv-build-management; &debugger; &cvs-chapter; - + &credits; -&kdevelop-install; +&tdevelop-install; &nutshell; &unixdev; SuSE, RedHat and others. These binaries are packed in some convenient format, mostly RPM, for easy installation. To install, follow the standard instructions given in your distribution. +&tdevelop; is available in binary form from many different &Linux; distributions such as SuSE, RedHat and others. These binaries are packed in some convenient format, mostly RPM, for easy installation. To install, follow the standard instructions given in your distribution. -You may as well obtain the &kdevelop; sources, compile and install them by yourself. These sources can be found via the project home page at http://www.kdevelop.org or via the &kde; ftp site. +You may as well obtain the &tdevelop; sources, compile and install them by yourself. These sources can be found via the project home page at http://www.tdevelop.org or via the &kde; ftp site. -Get Daily &kdevelop; Snapshots from svn +Get Daily &tdevelop; Snapshots from svn svn If you want to be in front of current development, anonymous svn repository snapshots are available. -The module name is kdevelop at svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdevelop. +The module name is tdevelop at svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/tdevelop. @@ -64,16 +64,16 @@ You may as well obtain the &kdevelop; sources, compile and install them by yours checkout - &kdevelop; + &tdevelop; svn checkout -To obtain an initial version of &kdevelop; you must download it from anonymous svn. For this so-called checkout operation follow these steps. +To obtain an initial version of &tdevelop; you must download it from anonymous svn. For this so-called checkout operation follow these steps. -We assume you want to put your &kdevelop; copy into the trinitysrc subdirectory of your home directory (~). +We assume you want to put your &tdevelop; copy into the trinitysrc subdirectory of your home directory (~). @@ -90,24 +90,24 @@ We assume you want to put your &kdevelop; copy into the &kdevelop; Compilation and Installation section. +Now you may compile your &tdevelop; version as shown in the &tdevelop; Compilation and Installation section. @@ -118,12 +118,12 @@ Now you may compile your &kdevelop; version as shown in the update - &kdevelop; + &tdevelop; svn update -After you checked out (and successfully compiled) &kdevelop; from svn as shown above, you'll want to keep it up to date in order to get all the patches. Follow these steps. (We again assume you have put your &kdevelop; copy into the trinitysrc directory.) +After you checked out (and successfully compiled) &tdevelop; from svn as shown above, you'll want to keep it up to date in order to get all the patches. Follow these steps. (We again assume you have put your &tdevelop; copy into the trinitysrc directory.) Note the up (= update) command instead of the co (which stands for checkout). @@ -136,7 +136,7 @@ Note the up (= update) command instead o ~/trinitysrc> - cd kdevelop + cd tdevelop ~/trinitysrc> @@ -149,7 +149,7 @@ Keep an eye on the messages svn produces during the update sequence. The exact s -Now you can compile a new &kdevelop; version as shown in the Special svn compilation considerations chapter. +Now you can compile a new &tdevelop; version as shown in the Special svn compilation considerations chapter. @@ -160,19 +160,19 @@ Now you can compile a new &kdevelop; version as shown in the -&kdevelop; Requirements +&tdevelop; Requirements requirements - &kdevelop; + &tdevelop; requirements GNU requirements -In order to successfully compile and use &kdevelop;, you need the following programs and libraries. They are available on most platforms as distribution packages and thereby can be installed easily. +In order to successfully compile and use &tdevelop;, you need the following programs and libraries. They are available on most platforms as distribution packages and thereby can be installed easily. @@ -306,7 +306,7 @@ In order to successfully compile and use &kdevelop;, you need the following prog - You can, to a certain extent, circumvent the need for &autoconf; ≥ 2.52 and &automake; ≥ 1.6. Just remove the admin directory in your &kdevelop; installation directory and type + You can, to a certain extent, circumvent the need for &autoconf; ≥ 2.52 and &automake; ≥ 1.6. Just remove the admin directory in your &tdevelop; installation directory and type autoconf circumvent version need @@ -318,16 +318,16 @@ In order to successfully compile and use &kdevelop;, you need the following prog circumvent for autoconf/automake - (your-kdevelop-directory)> - ln -s $KDEDIR/share/apps/kdelibs/admin admin + (your-tdevelop-directory)> + ln -s $KDEDIR/share/apps/tdelibs/admin admin - at the console. This causes &kdevelop; to use the standard settings in the &kde; admin directory instead. + at the console. This causes &tdevelop; to use the standard settings in the &kde; admin directory instead. - Be careful not to mix &Qt; versions. Always link &kdevelop; to the same &Qt; version your &kde; library was compiled. Otherwise you will most likely experience very strange behaviours. + Be careful not to mix &Qt; versions. Always link &tdevelop; to the same &Qt; version your &kde; library was compiled. Otherwise you will most likely experience very strange behaviours. @@ -338,27 +338,27 @@ In order to successfully compile and use &kdevelop;, you need the following prog -&kdevelop; Compilation and Installation +&tdevelop; Compilation and Installation - &kdevelop; + &tdevelop; compilation - &kdevelop; + &tdevelop; installation -Once all requirements are met, you are ready to compile and install &kdevelop;. This appendix will discuss the necessary steps to do so. +Once all requirements are met, you are ready to compile and install &tdevelop;. This appendix will discuss the necessary steps to do so. Preliminary Steps tells you about setting up a proper environment. - Compile &kdevelop; deals with obtaining the &kdevelop; sources from svn, how to prepare them for the installation process, and finally shows the steps necessary to compile and install &kdevelop;. + Compile &tdevelop; deals with obtaining the &tdevelop; sources from svn, how to prepare them for the installation process, and finally shows the steps necessary to compile and install &tdevelop;. - Some Notes on configure Options tells you how to run &kdevelop; if it has been installed in a location other than the &kde; directory. + Some Notes on configure Options tells you how to run &tdevelop; if it has been installed in a location other than the &kde; directory. @@ -367,7 +367,7 @@ Once all requirements are met, you are ready to compile and install &kdevelop;. preliminaries - &kdevelop; installation + &tdevelop; installation KDEDIR @@ -426,24 +426,24 @@ If you use the tcsh shell add the following lines: -Compile &kdevelop; +Compile &tdevelop; make - &kdevelop; installation + &tdevelop; installation compiling - &kdevelop; + &tdevelop; -In the following discussion we assume that you have put your &kdevelop; sources in the ~/trinitysrc/kdevelop directory. +In the following discussion we assume that you have put your &tdevelop; sources in the ~/trinitysrc/tdevelop directory. Special svn Compilation Considerations -In case you use a &kdevelop; snapshot from svn the initial compilation steps depend on whether you just did a complete checkout or only updated the source. +In case you use a &tdevelop; snapshot from svn the initial compilation steps depend on whether you just did a complete checkout or only updated the source. @@ -455,7 +455,7 @@ You must initialize the make system after a fresh checkout. - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> make -f admin/Makefile.common svn-clean @@ -484,7 +484,7 @@ U /some_directory_path/Makefile.am or if you just did a full checkout, you must enter: - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> make -f Makefile.svn @@ -499,11 +499,11 @@ before you proceed with all of the following steps. Basic <command>make</command> Command Sequence -Once the basic make system is set up you must decide which type of the &kdevelop; system you want to use. This is done in the following configure step which builds the actual Makefiles the make command will use. +Once the basic make system is set up you must decide which type of the &tdevelop; system you want to use. This is done in the following configure step which builds the actual Makefiles the make command will use. -You may drop the option in the following configure command lines if you want &kdevelop; be installed in the default &kde; directory. See the Some notes on configure options chapter for this. +You may drop the option in the following configure command lines if you want &tdevelop; be installed in the default &kde; directory. See the Some notes on configure options chapter for this. @@ -511,11 +511,11 @@ You may drop the option in the following conf A Debug-Compiled Version -If you want to keep track of what your &kdevelop; application does at run-time you may build a debug-compiled version. Just command configure to do so: +If you want to keep track of what your &tdevelop; application does at run-time you may build a debug-compiled version. Just command configure to do so: - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> ./configure --enable-debug=full --prefix=(where-your-trinity-is) @@ -524,64 +524,64 @@ If you want to keep track of what your &kdevelop; application does at run-time y A Release-Compiled Version -If you only want to use &kdevelop; as-is a (smaller and faster +If you only want to use &tdevelop; as-is a (smaller and faster running) release version suffices. configure defaults to this. - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> ./configure --prefix=(where-your-trinity-is) -If you want to build your own API documentation for &kdevelop; you must include yet another option in the configure command: +If you want to build your own API documentation for &tdevelop; you must include yet another option in the configure command: - ~/trinitysrc/kdevelop> - ./configure --(options-as-above) \ --with-kdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/kdelibs-apidocs + ~/trinitysrc/tdevelop> + ./configure --(options-as-above) \ --with-tdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/tdelibs-apidocs -Make and Install &kdevelop; +Make and Install &tdevelop; configure will check the system and build some Makefiles according to what it found. The make command will use the main Makefile by default. Thus - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> make suffices. If necessary, now gain root user rights using the command - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> su and entering the root password. Then install the application: - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> make install -That's all. If you installed &kdevelop; in the default &kde; directory you may now run the IDE. Otherwise some additional steps will be necessary as shown in the Non-default installation directory section below. +That's all. If you installed &tdevelop; in the default &kde; directory you may now run the IDE. Otherwise some additional steps will be necessary as shown in the Non-default installation directory section below. - In fact there usually will have been three &kdevelop;-based applications installed: + In fact there usually will have been three &tdevelop;-based applications installed: - The &kdevelop; IDE — this is the place where you will usually work. - The stand-alone &kdevelop; Assistant documentation browser — 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. - The &kdevelop; Designer — enhances the &Qt; User Interface Designer by &kde; specific elements and integrates nicely in the &kdevelop; IDE. + The &tdevelop; IDE — this is the place where you will usually work. + The stand-alone &tdevelop; Assistant documentation browser — 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. + The &tdevelop; Designer — enhances the &Qt; User Interface Designer by &kde; specific elements and integrates nicely in the &tdevelop; IDE. @@ -600,7 +600,7 @@ That's all. If you installed &kdevelop; in the default &kde; directory you may n Non-default Installation Directory - &kdevelop; + &tdevelop; installation non-default directory @@ -611,17 +611,17 @@ That's all. If you installed &kdevelop; in the default &kde; directory you may n kbuildsycoca -By default configure prepares the IDE to be installed in the default &kde; directory. This is necessary because &kdevelop; assumes direct access to some tools and parts which reside there. If want to use your own installation directory, you must tell configure this by the option: +By default configure prepares the IDE to be installed in the default &kde; directory. This is necessary because &tdevelop; assumes direct access to some tools and parts which reside there. If want to use your own installation directory, you must tell configure this by the option: - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> ./configure --prefix=(where-your-trinity-is) -There is a caveat if you do so. You must provide a means for &kdevelop; to access the needed tools and parts in the &kde; directory when running. (You can still use the IDE without doing so, but with very restrained capabilities.) +There is a caveat if you do so. You must provide a means for &tdevelop; to access the needed tools and parts in the &kde; directory when running. (You can still use the IDE without doing so, but with very restrained capabilities.) -Call up a shell and have the following commands executed before you start &kdevelop; at the shell prompt. +Call up a shell and have the following commands executed before you start &tdevelop; at the shell prompt. @@ -638,11 +638,11 @@ Call up a shell and have the following commands executed before you start &kdeve kbuildsycoca - (Now start &kdevelop;:) + (Now start &tdevelop;:) ~> - kdevelop + tdevelop @@ -661,7 +661,7 @@ In a tcsh shell you must set the environment variables using: setenv KDEDIRS /usr/local/kde:/opt/trinity -The kbuildsycoca command (build system control cache) looks around for libraries and caches their location and version, so that &kdevelop; can find them. The caveat is that it takes noticeable time—and it has to be run any time you call up the shell to start &kdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort. +The kbuildsycoca command (build system control cache) looks around for libraries and caches their location and version, so that &tdevelop; can find them. The caveat is that it takes noticeable time—and it has to be run any time you call up the shell to start &tdevelop; from a non-default directory. You may want to put the above commands into a shell script to reduce the typing effort. (You could as well put the lines in your .bashrc or .cshrc file, but this is not advisable as kbuildsycoca will then be run any time you call up the shell.) @@ -679,56 +679,56 @@ The kbuildsycoca command does not run from within the root. Y -How to Obtain a &kdevelop; API Documentation +How to Obtain a &tdevelop; API Documentation API - &kdevelop; + &tdevelop; - &kdevelop; + &tdevelop; API compiling - &kdevelop; + &tdevelop; API configure - &kdevelop; API + &tdevelop; API API is the short form of Application Program Interface. Actually such an API cotains a series of descriptions (&ie; calling conventions) by which an application program can access the operating system and other services. In our context, however, a broader definition was adopted. The API of a &kde; or &Qt; application is an abstract of the classes and methods interfaces, a synopsis to be used like a dictionary to navigate the sources. -There is a version of the most current API available at the KDevelop-Home website. It will be automatically updated every 24 hours so you can keep up. +There is a version of the most current API available at the KDevelop-Home website. It will be automatically updated every 24 hours so you can keep up. -Alas, this version is best used read-only over the internet. If you do not always have internet access you may as well build your own API documentation from the &kdevelop; sources. To do so, you must tell the automake system where to find the KDELIBS API in your system. This is accomplished by the special option in the configure command when you prepare to compile the &kdevelop; sources: +Alas, this version is best used read-only over the internet. If you do not always have internet access you may as well build your own API documentation from the &tdevelop; sources. To do so, you must tell the automake system where to find the KDELIBS API in your system. This is accomplished by the special option in the configure command when you prepare to compile the &tdevelop; sources: - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> ./configure --(options-as-usual) \ - --with-kdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/kdelibs-apidocs + --with-tdelibsdoxy-dir=$KDEDIR/share/doc/HTML/en/tdelibs-apidocs -(make will replace the global $KDEDIR variable with the actual &kde; directory setting recorded therein.) Then issue a make command as usual. After the &kdevelop; IDE has been built you have the option to build the API as well. For this you must issue +(make will replace the global $KDEDIR variable with the actual &kde; directory setting recorded therein.) Then issue a make command as usual. After the &tdevelop; IDE has been built you have the option to build the API as well. For this you must issue - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> make apidocs -This will build a Doxyfile in your &kdevelop; base directory which in turn will be processed by the Doxygen application to build quite a lot of .html API files. When this rather lengthy API building process (may last more than an hour on a slow system) finally comes to an end, you must install the API just like you have to install the &kdevelop; IDE itself. If necessary obtain superuser rights by +This will build a Doxyfile in your &tdevelop; base directory which in turn will be processed by the Doxygen application to build quite a lot of .html API files. When this rather lengthy API building process (may last more than an hour on a slow system) finally comes to an end, you must install the API just like you have to install the &tdevelop; IDE itself. If necessary obtain superuser rights by - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> su @@ -737,18 +737,18 @@ and entering the root password. Then install the API files: - ~/trinitysrc/kdevelop> + ~/trinitysrc/tdevelop> make install-apidox -Once this is done, make will inform you about the directory where you can finally look at the API documentation's contents. Note this address, you can use it from &konqueror; as well as from inside &kdevelop;, in case you have set up the &kdevelop; sources themselves as a project to work on. +Once this is done, make will inform you about the directory where you can finally look at the API documentation's contents. Note this address, you can use it from &konqueror; as well as from inside &tdevelop;, in case you have set up the &tdevelop; sources themselves as a project to work on. -You will most probably see a lot of warning and/or error messages during the API build run by Doxygen. It is best to ignore them, they are of interest to the &kdevelop; developers only. If the API generation ever comes to a successful end, the .html API files will be usable. +You will most probably see a lot of warning and/or error messages during the API build run by Doxygen. It is best to ignore them, they are of interest to the &tdevelop; developers only. If the API generation ever comes to a successful end, the .html API files will be usable. - + diff --git a/doc/kdevelop/kdevelop-scripting.docbook b/doc/kdevelop/kdevelop-scripting.docbook index d9e59bb5..177a0b65 100644 --- a/doc/kdevelop/kdevelop-scripting.docbook +++ b/doc/kdevelop/kdevelop-scripting.docbook @@ -1,4 +1,4 @@ - + @@ -12,7 +12,7 @@ Running Scripts - To access a script that is available to &kdevelop; use the ToolsScripts menu. If there there is no such menu item then there are no installed scripts available to KDevelop. + To access a script that is available to &tdevelop; use the ToolsScripts menu. If there there is no such menu item then there are no installed scripts available to KDevelop. @@ -30,7 +30,7 @@ The next step is to create the actual script. For the above example the Type of One of the most useful tools in developing scripts for applications is the KDCOP application.
- KDCOP Browsing DCOP Interfaces in &kdevelop; + KDCOP Browsing DCOP Interfaces in &tdevelop; @@ -41,7 +41,7 @@ The next step is to create the actual script. For the above example the Type of Once the script is complete it is ready to be installed. Application developers should document the location that will be scanned for scripts. In the case of the above example for Kate the scripts are located in "$KDEDIRS/share/apps/kate/scripts".
- &kdevelop; Scripts on the Filesystem + &tdevelop; Scripts on the Filesystem 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 @@ - + @@ -7,18 +7,18 @@ -Overview of &kdevelop; Features +Overview of &tdevelop; Features - - &kdevelop; + + &tdevelop; survey - + overall view - + survey -&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 @@ -40,7 +40,7 @@ various class browsers to aid you in maintaining the classes and their relationships of your object-oriented programming project, - a debugger interface to find and remove program errors from within &kdevelop;, and + a debugger interface to find and remove program errors from within &tdevelop;, and several plugin tools, 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 @@ - In fact there are three &kdevelop;-based applications: + In fact there are three &tdevelop;-based applications: - The &kdevelop; IDE — this is the place where you will usually work. - The stand-alone &kdevelop; Assistant documentation browser — 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. - The &kdevelop; Designer — enhances the &Qt; User Interface Designer by &kde; specific elements and integrates nicely in the &kdevelop; IDE. + The &tdevelop; IDE — this is the place where you will usually work. + The stand-alone &tdevelop; Assistant documentation browser — 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. + The &tdevelop; Designer — enhances the &Qt; User Interface Designer by &kde; specific elements and integrates nicely in the &tdevelop; IDE. @@ -67,11 +67,11 @@ Available User Interface Modes - &kdevelop; + &tdevelop; user interface modes user interface - &kdevelop; modes + &tdevelop; modes UI modes @@ -84,7 +84,7 @@ IDEAl -&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): IDEAl @@ -160,7 +160,7 @@ To switch the user interface mode select Settings -(Older &kdevelop; versions provide the top mode selection section only.) +(Older &tdevelop; versions provide the top mode selection section only.) @@ -171,7 +171,7 @@ Dependent on the user interface mode you selected, other configuration sections -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. @@ -180,10 +180,10 @@ Do not forget to restart &kdevelop; in order to let your selections take effect. How to Maximize the Work Space Area - &kdevelop; + &tdevelop; work space - &kdevelop; + &tdevelop; maximize work space user interface @@ -254,7 +254,7 @@ To hide the menubar select Settings -The &kdevelop; Titlebar +The &tdevelop; Titlebar (... to be written ...) @@ -262,7 +262,7 @@ To hide the menubar select Settings -The &kdevelop; Statusbar +The &tdevelop; Statusbar (... to be written ...) @@ -312,7 +312,7 @@ To hide the menubar select Settingsproject management -Globally, a project will rely on some form of project management system. &kdevelop; offers four project management systems 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 project management systems the programmer can select from when creating a new project. @@ -341,7 +341,7 @@ Globally, a project will rely on some form of project management system. &kdeve projects -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 a better way of Makefile generation and @@ -364,7 +364,7 @@ Projects created with &kdevelop;'s &automanag; make it very easy for developers projects -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;. For more information on the QMake project manager see the qmake User Guide which should be included in your distribution or have a look at the TROLLTECH Documentation home page where you may find the QMake documentation of your Qt C++ GUI Application Development Toolkit version. @@ -382,12 +382,12 @@ For more information on the QMake project manager see the qmake User Guid projects -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 $PATH to build them. -To set up a new C or C++ project in &kdevelop; select +To set up a new C or C++ project in &tdevelop; select Project New Project... C or C++ @@ -417,7 +417,7 @@ To set up a new C or C++ project in &kdevelop; select Java -&Java; developers may want to use the Apache ANT project manager for their projects. To set up a new Ant project in &kdevelop; select Project +&Java; developers may want to use the Apache ANT project manager for their projects. To set up a new Ant project in &tdevelop; select Project New Project... Java Ant Project @@ -441,7 +441,7 @@ For more information see The Apache Ant Proj custom projects -If you prefer to maintain your own Makefiles 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 make process. +If you prefer to maintain your own Makefiles 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 make process. Yet, if you do not really need 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 which at least for C++ applications is most often the case. But you can as well distribute binary packages of your application. -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. -For giving away your sources, we advise to include the project file of &kdevelop; as well. This makes it very easy for other developers—if they use &kdevelop;—to work with your sources. +For giving away your sources, we advise to include the project file of &tdevelop; as well. This makes it very easy for other developers—if they use &tdevelop;—to work with your sources. For projects where several developers, maybe working on different places, are involved, this should be the case anyway. So you can ensure consistency of the Makefiles to not run into trouble. @@ -486,4 +486,4 @@ Especially on multi language applications, translators won' - + diff --git a/doc/kdevelop/listplugins.sh b/doc/kdevelop/listplugins.sh index e21b3a15..f916b7fe 100755 --- a/doc/kdevelop/listplugins.sh +++ b/doc/kdevelop/listplugins.sh @@ -1,6 +1,6 @@ # kdevdir must be set to the KDevelop project directory. -kdevdir=/home/volker/data/prj/kdevelop/kdevelop/ +kdevdir=/home/volker/data/prj/tdevelop/tdevelop/ # The plugins are in the parts/ subdirectory. pushd $kdevdir/parts >/dev/null diff --git a/doc/kdevelop/nutshell.docbook b/doc/kdevelop/nutshell.docbook index 1c5395dd..59ee283b 100644 --- a/doc/kdevelop/nutshell.docbook +++ b/doc/kdevelop/nutshell.docbook @@ -10,7 +10,7 @@ This chapter is meant to provide short hints and tips together with (mandatory) There should be an additional FAQ section near the end nevertheless which contains more general stuff not directly related to navigating the manual. --> -The information in this chapter is meant as a quick reference for a head start or if you (momentarily) forgot about some basic concept. There are also short hints on how to solve some common problems when working with &kdevelop;. +The information in this chapter is meant as a quick reference for a head start or if you (momentarily) forgot about some basic concept. There are also short hints on how to solve some common problems when working with &tdevelop;. If you want more information on a topic, just follow the link in the title starting that advice. @@ -34,16 +34,16 @@ Information on these topics is availabe: Force smaller tool view tabs in IDEAl Mode -By default &kdevelop; starts with large text-based tool tip tabs +By default &tdevelop; starts with large text-based tool tip tabs around the work area. You may change this look to ⪚ save space in the -&kdevelop; configuration dialog (Settings +&tdevelop; configuration dialog (Settings Configure KDevelop... User Interface). -If you use an older &kdevelop; 3 version, this configuration dialog +If you use an older &tdevelop; 3 version, this configuration dialog may not be available. To change the toolview tabs display manually, place a entry under the tag in your -$KDEHOME/share/config/kdeveloprc configuration file as +$KDEHOME/share/config/tdeveloprc configuration file as follows: @@ -60,20 +60,20 @@ follows: style If you notice random colored letters everywhere (&ie; on tabs, on tool -bars, etc.) and the &kdevelop; window seemingly uses a wrong display style, +bars, etc.) and the &tdevelop; window seemingly uses a wrong display style, this may help: In your -$KDEHOME/share/config/kdeveloprc +$KDEHOME/share/config/tdeveloprc configuration file find the line containing Style=Checked and remove -it. Then restart &kdevelop;. +it. Then restart &tdevelop;. (This behaviour does sometimes occur after you left clicked a .ui file -in one of the file navigators and &kdevelop; did load +in one of the file navigators and &tdevelop; did load KUIViewer to show the &GUI; which was produced from this file.) @@ -231,7 +231,7 @@ try to update the information in the &GNU; Build System files. See Other Topics Configuration -Files used by &kdevelop; +Files used by &tdevelop; Usually you should not need to care, but this is very useful to know in case something went wrong with your setup. diff --git a/doc/kdevelop/plugin-tools.docbook b/doc/kdevelop/plugin-tools.docbook index 1c07cb7a..35e2c206 100644 --- a/doc/kdevelop/plugin-tools.docbook +++ b/doc/kdevelop/plugin-tools.docbook @@ -5,7 +5,7 @@ plugins -&kdevelop; contains a large number of little tools that help you to perform +&tdevelop; contains a large number of little tools that help you to perform certain task. Most of them are realized as plugins. That means, if you do not need a plugin, you can disable it. That also means, if you are looking for a functionality that should be there @@ -179,7 +179,7 @@ it is because the plugin authors made them this way. -Project Management Plugins in &kdevelop; +Project Management Plugins in &tdevelop; antproject @@ -205,7 +205,7 @@ in the future.
-Language Support Plugins in &kdevelop; +Language Support Plugins in &tdevelop; cppsupportSupport for C/C++ diff --git a/doc/kdevelop/project-advanced.docbook b/doc/kdevelop/project-advanced.docbook index d597e65e..a87b1658 100644 --- a/doc/kdevelop/project-advanced.docbook +++ b/doc/kdevelop/project-advanced.docbook @@ -45,7 +45,7 @@ Converting Old KDevelop Project Files -&kdevelop; allows you to open old KDevelop 2.x project files and convert them to &kdevelop; files. To do so go to Open Project... and select KDevelop 2 project files in the Filter:. Then select project file you want to open. The project gets converted to &kdevelop; and saved as a &kdevelop; project file. +&tdevelop; allows you to open old KDevelop 2.x project files and convert them to &tdevelop; files. To do so go to Open Project... and select KDevelop 2 project files in the Filter:. Then select project file you want to open. The project gets converted to &tdevelop; and saved as a &tdevelop; project file. @@ -54,7 +54,7 @@ Importing an Existing Project -To import an existing directory in &kdevelop; select Import Existing Directory +To import an existing directory in &tdevelop; select Import Existing Directory from the Project menu. You should see the Import Directory Wizard, as seen below: diff --git a/doc/kdevelop/project-management.docbook b/doc/kdevelop/project-management.docbook index 75674203..69ca9474 100644 --- a/doc/kdevelop/project-management.docbook +++ b/doc/kdevelop/project-management.docbook @@ -34,7 +34,7 @@ You will find here information on: In the Build systems chapter we have given a rough overview of the build systems commonly in use on &UNIX; systems. In the following sections we will look at this in more detail. -There is some confusion about how to name such things. &GNU; calls them build systems when it describes Automake, Autoconf and Libtool. QMake calls itself a tool to write Makefiles for different compilers and platforms. In &kde; often the term project management systems is used. We will use this term in a broader sense to describe the built-in environments in &kdevelop; which are used to organize and build your projects. In the context of this section, however, we will mostly talk about automated build systems. +There is some confusion about how to name such things. &GNU; calls them build systems when it describes Automake, Autoconf and Libtool. QMake calls itself a tool to write Makefiles for different compilers and platforms. In &kde; often the term project management systems is used. We will use this term in a broader sense to describe the built-in environments in &tdevelop; which are used to organize and build your projects. In the context of this section, however, we will mostly talk about automated build systems. @@ -95,7 +95,7 @@ A build system will iron out these differences for you. -In brief, a build system offers safe and secure methods for your application to be compiled and installed correctly on any receiving machine. As we have shown before in the Project Management Systems survey, &kdevelop; offers three automated build systems and the option of creating your own Makefile, in short (click on the project names to get more information): +In brief, a build system offers safe and secure methods for your application to be compiled and installed correctly on any receiving machine. As we have shown before in the Project Management Systems survey, &tdevelop; offers three automated build systems and the option of creating your own Makefile, in short (click on the project names to get more information): @@ -126,7 +126,7 @@ One of these four alternatives must be chosen when you create a project and Autoconf, Automake and Libtool) of which the &automanag; makes use. - A short autoconf tutorial written by Christopher W. Curtis available on the &kdevelop; home page. It concentrates on some basic steps to modify a Makefile. + A short autoconf tutorial written by Christopher W. Curtis available on the &tdevelop; home page. It concentrates on some basic steps to modify a Makefile. A more detailed tutorial can be found in a greater set of tutorials on Developing software with GNU. @@ -181,14 +181,14 @@ How does this work? Well configure is a script that The Makefile.in are input files—templates which provide basic information for the Makefiles to be produced from them by filling in some system dependent information. They are generated by the Automake utility from the Makefile.am files. -The process of going from Makefile.am (.am denotes Automake template files) to Makefile files is handled automatically by the &kdevelop; &promanag;, using the Autoconf utility, M4 macros and other arcana we need not go into here. +The process of going from Makefile.am (.am denotes Automake template files) to Makefile files is handled automatically by the &tdevelop; &promanag;, using the Autoconf utility, M4 macros and other arcana we need not go into here. So when make runs, it automatically picks up the correct pieces from the current environment, such as compilers and libraries. Similarly, make install puts your application components, such as executables, documentation and data files in the correct places for that environment. -If you distribute your application as a tarball (a single compressed file that &kdevelop; can create for you), it will include the Makefile.in files and the configure script file, so the recipient can compile, build and install your application without having Automake, Autoconf or &kdevelop; on their machine. The Makefile.am files are also included, just in case the receiver needs to do any source-code modifications. +If you distribute your application as a tarball (a single compressed file that &tdevelop; can create for you), it will include the Makefile.in files and the configure script file, so the recipient can compile, build and install your application without having Automake, Autoconf or &tdevelop; on their machine. The Makefile.am files are also included, just in case the receiver needs to do any source-code modifications. The rules are rather different if you distribute via a web-based source-code repository such as &kde; &cvs;. @@ -290,7 +290,7 @@ As you can see, many of the items on the right hand side are symbols of the form -Also, sometime after you have started with &kdevelop;, it is a good idea to run the command ./configure --help, which will show you the range of things you can change at build and installation time, such as for a test environment. In particular, the command: +Also, sometime after you have started with &tdevelop;, it is a good idea to run the command ./configure --help, which will show you the range of things you can change at build and installation time, such as for a test environment. In particular, the command: ./configure --prefix=/where/you/wish @@ -346,7 +346,7 @@ In this chapter you will find a basic description of the &automanag; elements an On top of each view there is a toolbar, the buttons in which will become activated when an element in this view is selected. This provides one way you can access the actions provided for that view element. The other are context menus which pop up on right mouse button click as will be discussed below. - In IDEAl mode there are two additional small buttons in the &automanag; window titlebar left hand side – a triangular shaped right arrow, and a dot button. The arrow button is used to close the window. The dot button on the other hand will keep the window open even if another &kdevelop; window has been selected. (Otherwise the &automanag; window will automatically close whenever another window gets the input focus.) + In IDEAl mode there are two additional small buttons in the &automanag; window titlebar left hand side – a triangular shaped right arrow, and a dot button. The arrow button is used to close the window. The dot button on the other hand will keep the window open even if another &tdevelop; window has been selected. (Otherwise the &automanag; window will automatically close whenever another window gets the input focus.) @@ -429,7 +429,7 @@ In both the overall and the detail view you can left-click on the +Opening a file for Edit If you &LMB; click on a file name in the detail -view, the corresponding file opens up in &kdevelop;'s editing window. +view, the corresponding file opens up in &tdevelop;'s editing window. @@ -677,7 +677,7 @@ CXX = g++ -&kdevelop;'s &automanag; +&tdevelop;'s &automanag;
A screenshot of the automake manager 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 @@ -Configuring &kdevelop; +Configuring &tdevelop; -&kdevelop; is a very powerful and flexible IDE which offers many ways to tailor it to your needs. To start configuration select SettingsConfigure &kdevelop;.... 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 SettingsConfigure &tdevelop;.... 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. @@ -56,7 +56,7 @@ If you want directly look up a certain configuration item use one of the followi General Configuration -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: @@ -88,7 +88,7 @@ General configuration concerns the more common tasks of tailoring &kdevelop; as General Setup -The General configuration dialog allows you to define some basic &kdevelop; behaviour which seldom will change in everyday work. This concerns: +The General configuration dialog allows you to define some basic &tdevelop; behaviour which seldom will change in everyday work. This concerns: @@ -97,10 +97,10 @@ The General configuration dialog allows you to define some - defining a default parent directory &kdevelop; shall use for new projects. + defining a default parent directory &tdevelop; shall use for new projects. - deciding whether you want &kdevelop; to automatically load the project you last worked on. + deciding whether you want &tdevelop; to automatically load the project you last worked on. @@ -114,7 +114,7 @@ namely: the Messages Output -View &kdevelop; uses to communicate ⪚ compilation progresses, +View &tdevelop; uses to communicate ⪚ compilation progresses, and @@ -166,7 +166,7 @@ messages issued by make will be shown. startup -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. @@ -176,9 +176,9 @@ Mark this checkbox if you want to continue to work with the last project you wor Default projects directory: -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. You may of course change the directory path of a new project at the time you set it up in the &appwizard;. @@ -190,13 +190,13 @@ You may of course change the directory path of a new project at the time you set Window font: -The Application Output View 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 Application Output View 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. To select a font suitable for the Messages Output View window click the Window Font button showing the currently selected font (it says Luxi Sans in the above illustration). The &kde; standard Select Font dialog will pop up from which you may select the font to be used. -On first start-up, &kdevelop; initializes this font setting to the standard font for which your &kde; user has been configured. This setting is fixed, so if you alter PreferencesAppearances & ThemesFonts in the Control Center, this will not effect this &kdevelop; font selection. You will have to explicitely reselect the Messages Output View window font. +On first start-up, &tdevelop; initializes this font setting to the standard font for which your &kde; user has been configured. This setting is fixed, so if you alter PreferencesAppearances & ThemesFonts in the Control Center, this will not effect this &tdevelop; font selection. You will have to explicitely reselect the Messages Output View window font. @@ -205,7 +205,7 @@ On first start-up, &kdevelop; initializes this font setting to the standard font Compiler Output -&kdevelop; preprocesses the messages the Messages Output View 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 Messages Output View 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. @@ -238,7 +238,7 @@ There is an alternative way to switch the compiler output detail. Just right cli Line wrapping -By default, &kdevelop; will wrap long lines around in the Messages Output View 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 Messages Output View 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. There is an alternative way to switch the line wrapping. Just &RMB; click in the Messages Output View window and mark/unmark the Line Wrapping 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 -The make tool usually will display messages like Entering directory, or Leaving directory when it switches the directories it currently works in. As this clutters the messages list in the Messages Output View window, &kdevelop; suppresses those messages by default. Mark the checkbox if you want to protocol which directories make worked in. +The make tool usually will display messages like Entering directory, or Leaving directory when it switches the directories it currently works in. As this clutters the messages list in the Messages Output View window, &tdevelop; suppresses those messages by default. Mark the checkbox if you want to protocol which directories make worked in. 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 UI Designer Integration -This let you choose the way you want .ui 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 .ui files. +This let you choose the way you want .ui 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 .ui files. - Use &kdevelop;'s embedded designer - This uses &kdevelop; own designer embedded within &kdevelop; + Use &tdevelop;'s embedded designer + This uses &tdevelop; own designer embedded within &tdevelop; - Run &kdevelop;'s designer as a separate application + Run &tdevelop;'s designer as a separate application The KDevDesigner application will be run separately in its own window. @@ -285,7 +285,7 @@ This let you choose the way you want .ui files to be displa Run Qt Designer - Qt Designer from your Qt installation will be started externally whenever you click on a .ui file in &kdevelop;. + Qt Designer from your Qt installation will be started externally whenever you click on a .ui file in &tdevelop;. @@ -322,7 +322,7 @@ You choose here which terminal you want to be integrated within KDevelop. switch UI modes -As already said in the Available User Interface Modes chapter there are five different ways the &kdevelop; work area may be set up, namely: +As already said in the Available User Interface Modes chapter there are five different ways the &tdevelop; work area may be set up, namely: @@ -349,7 +349,7 @@ A typical example of this user interface mode is Borland Delphi 6.0. -To switch the user interface mode select Settings Configure &kdevelop;... from the menus. The Customize KDevelop dialog will pop up, where you have to select User Interface in the left hand tree. This will display the following settings dialog to the right. +To switch the user interface mode select Settings Configure &tdevelop;... from the menus. The Customize KDevelop dialog will pop up, where you have to select User Interface in the left hand tree. This will display the following settings dialog to the right. @@ -368,7 +368,7 @@ Select the radio button of the user interface mode you want to switch to, then c -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. @@ -384,26 +384,26 @@ In Simplified IDEAl window mode and in IDEAl wind Configuring the Documents Tab Bar Display -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 Use Tabs 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 Use Tabs configuration section. Always - 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. When more than one - 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 Always 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 Always 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. Never - 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; Window 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; Window menu. @@ -415,7 +415,7 @@ In the IDEAl and tabbed pages modes there will be named tabs on top of the docum Tab -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 Use Close On Hover 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 Use Close On Hover coniguration section for this. @@ -428,13 +428,13 @@ When you configured &kdevelop; to display the documents tab bar, either always o Yes - 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. Yes, Delayed - After selecting this radio button, &kdevelop; will allow to close a document window as shown in the Yes 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 Yes case above. The icon will not change instantly, however, but there will be a short delay before the close icon shows up. @@ -524,7 +524,7 @@ The active toolview window must be shown fixed (non-overlap mode), sharing the w Selecting an Editor -&kdevelop; allows you to select your favorite text editor tool. Mark the Editor entry in the left hand side selections tree of the Configure KDevelop window. The following dialog will be displayed to the right. +&tdevelop; allows you to select your favorite text editor tool. Mark the Editor entry in the left hand side selections tree of the Configure KDevelop window. The following dialog will be displayed to the right. @@ -560,7 +560,7 @@ To select a new editor, click on the arrow on the drop down list field. Dependin -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 Messages Output View 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 Messages Output View window has been provided. @@ -655,15 +655,15 @@ KDevelop lets you use editor interfaces which have registered with &kde; and tha Selecting a Source Format Style -&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. -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 astyle 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 astyle application to implement this feature. -To set up a specific format style, select Settings Configure &kdevelop;.. from the menubar. The Customize KDevelop dialog will pop up, where you have to select Source Formatter in the left hand tree. This will display a series of three settings dialog tabs to the right, namely a General Formatting Setup, a Indentation Style Setup, and a Other Formatting Setup. +To set up a specific format style, select Settings Configure &tdevelop;.. from the menubar. The Customize KDevelop dialog will pop up, where you have to select Source Formatter in the left hand tree. This will display a series of three settings dialog tabs to the right, namely a General Formatting Setup, a Indentation Style Setup, and a Other Formatting Setup. @@ -930,7 +930,7 @@ namespace foospace Controlling Extra Spaces -By default &kdevelop; does minimize the use of spaces in source texts. +By default &tdevelop; does minimize the use of spaces in source texts. @@ -997,7 +997,7 @@ split a long line apart. For C/C++ code this can be controlled here. Setting Up the Code Snippets Tool -When editing in &kdevelop; you can store often used parts of code as Code Snippets. To configure the capabilities of the code snippets part select Settings Configure &kdevelop;.. from the menubar. The Customize KDevelop dialog will pop up, where you have to select Code Snippets 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 Code Snippets. To configure the capabilities of the code snippets part select Settings Configure &tdevelop;.. from the menubar. The Customize KDevelop dialog will pop up, where you have to select Code Snippets in the left hand tree. This will show the following dialog in the right hand side. @@ -1069,7 +1069,7 @@ variables' mechanism. You can set up it's behaviour in the Configuring the File Selector -&kdevelop; provides a File Selector plugin which, when +&tdevelop; provides a File Selector plugin which, when loaded at start-up, allows to navigate to any file or directory in the system. @@ -1088,7 +1088,7 @@ system. The behaviour of the File Selector can be highly configured. Select Settings -Configure &kdevelop;.. from the +Configure &tdevelop;.. from the menubar. The Customize KDevelop dialog will pop up, where you have to select File Selector in the left hand tree. This will show the following dialog in the right hand side. @@ -1240,11 +1240,11 @@ entries as follows. Controlling What Should be Remembered Between Sessions -By default the File Selector 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 Session configuration group. +By default the File Selector 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 Session configuration group. -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. @@ -1310,7 +1310,7 @@ If &kdevelop; was automatically restarted by the &kde; session manager the chang Configuring the Documentation -&kdevelop; contains a very powerful documentation facility which provides access to several kinds of extensive documentation. In ⪚ IDEAl mode you find a Documentation 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 Documentation tab at the right border of the work area. @@ -1318,19 +1318,19 @@ If &kdevelop; was automatically restarted by the &kde; session manager the chang -The &kdevelop; documentation window in IDEAl mode +The &tdevelop; documentation window in IDEAl mode
-&kdevelop; must have loaded the Documentation plugin in order to view the documentation tree. See the Plugin Tools section for more info. +&tdevelop; must have loaded the Documentation plugin in order to view the documentation tree. See the Plugin Tools section for more info. -You may set up contents and behaviour of the various parts of this documentation window if you select Settings Configure &kdevelop;.. from the menubar. The Customize KDevelop dialog will pop up, where you have to select Documentation in the left hand window. +You may set up contents and behaviour of the various parts of this documentation window if you select Settings Configure &tdevelop;.. from the menubar. The Customize KDevelop dialog will pop up, where you have to select Documentation in the left hand window. @@ -1347,7 +1347,7 @@ The thus displayed configuration pageSetting Up Documentation Collections -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 Contents page of the &kdevelop; Documentation 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 Contents page of the &tdevelop; Documentation facility, and how the user may access documentation details by indexed and full text searches. The Documentation 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 Documentation tab provides a series of configuration pa &Qt; Documentation Collection CHM Documentation Collection Doxygen Documentation Collection - &kdevelop; TOC Documentation Collection + &tdevelop; TOC Documentation Collection Devhelp Documentation Collection Custom Documentation Collection @@ -1445,7 +1445,7 @@ Every documentation setup page shows the listed documentation items in a table w TOC - If this check box is marked, this documentation item will show up on the Contents page of the &kdevelop; Documentation facility. + If this check box is marked, this documentation item will show up on the Contents page of the &tdevelop; Documentation facility. Unchecking the TOC check box will in turn disable the Index and Search 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 Index - 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 Index and (optionally) Finder pages of the &kdevelop; Documentation 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 Index and (optionally) Finder pages of the &tdevelop; Documentation facility. @@ -1472,14 +1472,14 @@ Every documentation setup page shows the listed documentation items in a table w Search - If this check box is marked, the contents of this documentation item will be included in the full text search path of the Search page of the &kdevelop; Documentation facility. + If this check box is marked, the contents of this documentation item will be included in the full text search path of the Search page of the &tdevelop; Documentation facility. - &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. - Any change of the Search check box marks will thus effect the search runs only after you rebuilt the index on the Search page of the &kdevelop; Documentation facility. + Any change of the Search check box marks will thus effect the search runs only after you rebuilt the index on the Search page of the &tdevelop; Documentation facility. @@ -1487,13 +1487,13 @@ Every documentation setup page shows the listed documentation items in a table w Title - This is the name of the Documentation item as it will be shown on the Contents page of the &kdevelop; Documentation facility. + This is the name of the Documentation item as it will be shown on the Contents page of the &tdevelop; Documentation facility. -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. @@ -1521,7 +1521,7 @@ On this configuration page all &Qt; documentation is set up. -Normally &kdevelop; will fill this in on its first start-up. It looks for standard *.xml, or *.dcf 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 *.xml, or *.dcf documentation files in the &Qt; installation directory. The table to the left lists the files &tdevelop; found by their standard titles. @@ -1529,11 +1529,11 @@ If you have a non-standard installation, either there will be no information lis -&kdevelop; will use the titles already provided by the installed &Qt; documentation. Hence the Title field in the Documentation Catalog Properties dialog is inaccessible. +&tdevelop; will use the titles already provided by the installed &Qt; documentation. Hence the Title field in the Documentation Catalog Properties dialog is inaccessible. -By default, not all &Qt; documentation will be shown on the Contents page of the &kdevelop; Documentation facility. Use the TOC check box in the setup table to select the documentation to be shown. +By default, not all &Qt; documentation will be shown on the Contents page of the &tdevelop; Documentation facility. Use the TOC check box in the setup table to select the documentation to be shown. @@ -1562,7 +1562,7 @@ On this configuration page you may collect documentation according to the &Micro -By default, this configuration page will be empty (as shown above). You may add new entries using the buttons to the right of the list field. &kdevelop; will filter *.chm files in the directory dialog associated to the Add and Edit buttons. +By default, this configuration page will be empty (as shown above). You may add new entries using the buttons to the right of the list field. &tdevelop; will filter *.chm files in the directory dialog associated to the Add and Edit buttons. @@ -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 &doxygen; tool. -&doxygen; generated &API; documentationconsists of a series of html files, starting with index.html. Additionally there may exist tag files which contain information to link to already existing &API; documentations. Thus &kdevelop; will look for index.html and *.tag files when seaching for &doxygen; generated &API; documentation. +&doxygen; generated &API; documentationconsists of a series of html files, starting with index.html. Additionally there may exist tag files which contain information to link to already existing &API; documentations. Thus &tdevelop; will look for index.html and *.tag files when seaching for &doxygen; generated &API; documentation. There are some structural constraints assumed when searching for &doxygen; generated &API; documentation. The directory in which the index.html file resides should contain subdirectories with separate documentation collections. Each of these subdirectories is assumed to contain a .tag file and a html/ subdirectory. -You may have a look at $KDEDIR/share/doc/HTML/en/kdelibs-apidocs for an example of such a &doxygen; &API; documentation layout. +You may have a look at $KDEDIR/share/doc/HTML/en/tdelibs-apidocs for an example of such a &doxygen; &API; documentation layout. @@ -1608,25 +1608,25 @@ The older &kde; KDoc gener -&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: Either you provided the configure command with the - option when you compiled - &kdevelop; (see the How to Obtain a &kdevelop; &API; Documentation chapter). + option when you compiled + &tdevelop; (see the How to Obtain a &tdevelop; &API; Documentation chapter). Or the configure command did automatically find a &doxygen; generated &kde; Libraries &API; in one of several standard locations it knows of. - Or as a last resort the $KDEDIR/share/doc/HTML/en/kdelibs-apidocs/ was found at the first &kdevelop; startup. + Or as a last resort the $KDEDIR/share/doc/HTML/en/tdelibs-apidocs/ was found at the first &tdevelop; startup. -If &kdevelop; did not find a valid &doxygen; generated &kde; Libraries &API; at its first start-up the Doxygen Documentation Collection list will be empty. +If &tdevelop; did not find a valid &doxygen; generated &kde; Libraries &API; at its first start-up the Doxygen Documentation Collection list will be empty. @@ -1634,12 +1634,12 @@ You may add your own &API; documentation entries (⪚ from your current project -&kdevelop; uses the title information from the index.html. Hence the Title field in the Documentation Catalog Properties dialog is inaccessible. +&tdevelop; uses the title information from the index.html. Hence the Title field in the Documentation Catalog Properties dialog is inaccessible. - 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 sources (using the make apidox and make install commands on the kdebase sources) and then add an entry to the Doxygen Documentation Collection 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 sources (using the make apidox and make install commands on the tdebase sources) and then add an entry to the Doxygen Documentation Collection list like this: @@ -1656,7 +1656,7 @@ You may add your own &API; documentation entries (⪚ from your current project -You must put the &API; of your current project into this Doxygen Documentation Collection 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 Doxygen Documentation Collection as well. Former &tdevelop; versions did put it into the documentation tree on a per-project basis. This is not provided any more. @@ -1665,7 +1665,7 @@ You must put the &API; of your current project into this Doxygen Docum Handling Structured Documentation (KDevelopTOC Files) -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 KDevelopTOC Documentation Collection 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 KDevelopTOC Documentation Collection page. @@ -1680,31 +1680,31 @@ The main bulk of the &kdevelop; documentation facility provides immediate access -&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 TOC check box in the setup table. +&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 TOC check box in the setup table. -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 .toc file can have an index manually defined, using the <index> tag. Thus the Index check box will be enabled ony when &kdevelop; finds an <index> tag in the .toc file. (For more detail see the description below in the &kdevelop; TOC Files 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 .toc file can have an index manually defined, using the <index> tag. Thus the Index check box will be enabled ony when &tdevelop; finds an <index> tag in the .toc file. (For more detail see the description below in the &tdevelop; TOC Files section.) The Search check box in the setup table will alway be disabled. -You may add new entries using the buttons to the right of the list field. &kdevelop; will filter *.toc files in the directory dialog associated to the Add and Edit buttons. +You may add new entries using the buttons to the right of the list field. &tdevelop; will filter *.toc files in the directory dialog associated to the Add and Edit buttons. -Other than former &kdevelop; versions will the Remove button not change the *.toc files on disk, so the remove operation is safe now. +Other than former &tdevelop; versions will the Remove button not change the *.toc files on disk, so the remove operation is safe now. -&kdevelop; TOC Files +&tdevelop; TOC Files -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 (⪚ KDE2 Development Book (kde.org)). 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 remote 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 (⪚ KDE2 Development Book (kde.org)). 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 remote documentation file. @@ -1712,15 +1712,15 @@ The rationale behind this is not only to locally navigate remote documentation w -Such structured access is made possible through the use of special table of content files, which are denoted by .toc 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 table of content files, which are denoted by .toc filename extensions. Any such &tdevelop; TOC file contains an &XML; structured description of the document to be accessed. -Standard Directory of &kdevelop; TOC Files +Standard Directory of &tdevelop; TOC Files -When &kdevelop; was installed usually a series of predefined .toc files has been put into the $KDEDIR/share/apps/kdevdocumentation/tocs 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 .toc files has been put into the $KDEDIR/share/apps/kdevdocumentation/tocs directory. These are fairly simple, structured text files. You may look at them using a text editor or other text display facility. @@ -1730,16 +1730,16 @@ When &kdevelop; was installed usually a series of predefined .toc - Basic Structure of &kdevelop; TOC Files + Basic Structure of &tdevelop; TOC Files header - <!DOCTYPE kdeveloptoc> + <!DOCTYPE tdeveloptoc> - <kdeveloptoc> + <tdeveloptoc> (title) @@ -1754,11 +1754,11 @@ When &kdevelop; was installed usually a series of predefined .toc(index structure) - </kdeveloptoc> + </tdeveloptoc> - This &XML; structure will be parsed by the &kdevelop; Documentation 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; Documentation 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. @@ -1773,7 +1773,7 @@ When &kdevelop; was installed usually a series of predefined .toc - 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. This displayed title cannot be changed by the user. If you want another text be displayed, you must manually change the <title> entry in the .toc file. @@ -1826,7 +1826,7 @@ When &kdevelop; was installed usually a series of predefined .toc<tocsecti> entry must have a name="xxx" 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. - There may be an url="" attribute associated with any i 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 url="" attribute associated with any i 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;. The <tocsectn/> entry must have an url="" attribute whatsoever. @@ -1869,7 +1869,7 @@ When &kdevelop; was installed usually a series of predefined .tocDevHelp Documentation -DevHelp documentation is another means of structured documentation access. It uses structured table of content files denoted by a .devhelp extension similar to &kdevelop; TOC files 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 .devhelp extension similar to &tdevelop; TOC files to access documentation for the GNOME 2 desktop. You can control which DevHelp files should be accessible on the DevHelp Documentation Collection configuration page. @@ -1891,11 +1891,11 @@ DevHelp files originally were accessible on the /opt/gnome/share/. Initially these files will not be marked for display. If you want to see another documentation, mark the TOC check box in the setup table. +When &tdevelop; is installed it will attempt to find all .devhelp files in some standard places in the system, ⪚ in the subdirectories of /opt/gnome/share/. Initially these files will not be marked for display. If you want to see another documentation, mark the TOC check box in the setup table. -You may add new entries using the buttons to the right of the list field. &kdevelop; will filter *.toc files in the directory dialog associated to the Add and Edit buttons. +You may add new entries using the buttons to the right of the list field. &tdevelop; will filter *.toc files in the directory dialog associated to the Add and Edit buttons. @@ -1919,14 +1919,14 @@ This is for your own purpose. You may add almost any documentation files here, p -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. -Handling is straightforward here. Use the buttons 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 Add and Edit buttons. +Handling is straightforward here. Use the buttons 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 Add and Edit buttons. -You will have to explicitely select the items for display in the &kdevelop; documentation facility. Mark the TOC check box of the entry in the setup table. +You will have to explicitely select the items for display in the &tdevelop; documentation facility. Mark the TOC check box of the entry in the setup table. diff --git a/doc/kdevelop/survey-manual.docbook b/doc/kdevelop/survey-manual.docbook index d9611a03..0bd59c8d 100644 --- a/doc/kdevelop/survey-manual.docbook +++ b/doc/kdevelop/survey-manual.docbook @@ -2,30 +2,30 @@ What This Manual Contains -This user manual is intended to describe the contents and use of the &kdevelop; &kdevrelease; Integrated Development Environment (IDE) from a user's point of view. It is not a programming manual, nor does it describe the development process in detail. Its only aim is to guide you in the handling of the IDE. +This user manual is intended to describe the contents and use of the &tdevelop; &kdevrelease; Integrated Development Environment (IDE) from a user's point of view. It is not a programming manual, nor does it describe the development process in detail. Its only aim is to guide you in the handling of the IDE. Here you will find information on the following topics: -Getting Started with &kdevelop; — a Guided Tour +Getting Started with &tdevelop; — a Guided Tour Gives you a quick start on the use of this &IDE;, introducing the basic steps of how to work on a project. -Overview of the Features of - &kdevelop; +Overview of the Features of + &tdevelop; Extends the guided tour in the previous chapter, giving an overall -view of what is built-in within &kdevelop; and gets you acquainted with the +view of what is built-in within &tdevelop; and gets you acquainted with the look and feel of this &IDE;. -Configuring &kdevelop; +Configuring &tdevelop; Shows how you can tailor the &IDE; to suit your needs. @@ -35,7 +35,7 @@ look and feel of this &IDE;. Getting started: the &appwizard; -Describes the basics of how to set up a new project in &kdevelop; +Describes the basics of how to set up a new project in &tdevelop; using the built-in &appwizard;. @@ -60,7 +60,7 @@ and how to access the files you want to work with. The Class Browsers -Describes one of the most powerful tools of &kdevelop; which lets you +Describes one of the most powerful tools of &tdevelop; which lets you navigate through class dependencies and allows you to easily create and access the classes and methods you need. @@ -70,7 +70,7 @@ access the classes and methods you need. Documentation -Shows how to access the rich built-in documentation &kdevelop; +Shows how to access the rich built-in documentation &tdevelop; provides and tells you how to create documentation of your project, concise and powerful &API; documentation providing you an overall view of all your project sources as well as docbook-based user documentation. @@ -103,16 +103,16 @@ for diverse platforms, or to make an embedded system using the Describes how to use the integrated gdb debugger interface so you can hunt down bugs without leaving -&kdevelop;. +&tdevelop;. @@ -127,7 +127,7 @@ project. Configuration Files Used by - &kdevelop; -Lists the files &kdevelop; uses to save its internal + &tdevelop; +Lists the files &tdevelop; uses to save its internal information. This is particularly useful in case something went wrong with your setup. @@ -189,12 +189,12 @@ necessary and why you need an &IDE;. Plugin Tools Lists the pluggable tools you can use to taylor the capabilities of -&kdevelop; to your needs. +&tdevelop; to your needs. diff --git a/doc/kdevelop/unixdev.docbook b/doc/kdevelop/unixdev.docbook index d7881afb..8151f30b 100644 --- a/doc/kdevelop/unixdev.docbook +++ b/doc/kdevelop/unixdev.docbook @@ -241,7 +241,7 @@ Basically the make command will read the rules one after anot There are several additional possibilities to control such a make process, and a Makefile can thus grow very complex. We cannot go into the details here. However, we recommend that you make yourself accustomed to the syntax of make. Even if you do not normally use it directly, an understanding of the fundamentals of the build system can be useful. See the GNU Make Manual for more information. -For more &kdevelop; specific detail see the Building and Project Management chapter of this manual. +For more &tdevelop; specific detail see the Building and Project Management chapter of this manual. There are several tutorials available, see the references in the Building and project management chapter. @@ -307,16 +307,16 @@ For example—would it not be convenient if a debugger were able to open the To more easily accomplish such a scheme, Integrated Development Environments (&IDE;s) were devised. Such an &IDE; integrates all templates, tools, and scripts which are commonly needed in the development process into one single environment. -For the &kde; platform &kdevelop; is such an &IDE;. It provides a wide range of tools which ease program development and maintenance, even for different programming languages and across platforms. +For the &kde; platform &tdevelop; is such an &IDE;. It provides a wide range of tools which ease program development and maintenance, even for different programming languages and across platforms. - -Basic Features of &kdevelop; &kdevrelease; + +Basic Features of &tdevelop; &kdevrelease; - - &kdevelop; + + &tdevelop; features - + features @@ -378,7 +378,7 @@ For the &kde; platform &kdevelop; is such an &IDE;. It provides a wide range of - + diff --git a/doc/platform/Mainpage.dox b/doc/platform/Mainpage.dox index dd69ba92..b5d008c6 100644 --- a/doc/platform/Mainpage.dox +++ b/doc/platform/Mainpage.dox @@ -22,18 +22,18 @@ This document is targeted at all those that want to build their own IDE or impro If you are instead looking for a user manual, just go to the help menu of your KDevelop and select KDevelop handbook. This documentation contains the KDevelop Platform online class reference for the current development version of KDevelop. Additionally, you -can subscribe or read the mailing list for any additions and/or +can subscribe or read the mailing list for any additions and/or modifications to the Platform %API. -An on-line, updated every 24H, html version of this documentation can be found at: http://www.kdevelop.org/HEAD/doc/platform/html/index.html +An on-line, updated every 24H, html version of this documentation can be found at: http://www.tdevelop.org/HEAD/doc/platform/html/index.html -You can also download a local browseable copy form http://www.kdevelop.org/HEAD/doc/platform/kdevplatformdoc.tar.bz2 . It gets updated every single day too. +You can also download a local browseable copy form http://www.tdevelop.org/HEAD/doc/platform/kdevplatformdoc.tar.bz2 . It gets updated every single day too. More information about the KDevelop Platform architecture in form of tutorials, Wikis, HOWTOs, and FAQs can be found at -the KDevelop website. +the KDevelop website. -Quick overviews of the architecture can also be found in the issues of +Quick overviews of the architecture can also be found in the issues of KDevelop Technotes. \section platformapi Platform Libraries API @@ -122,7 +122,7 @@ KDevelop Technotes. Here is a priority ordered list: -# fix the dispersed fixme - -# reported bugs in bugzilla database + -# reported bugs in bugzilla database -# fix the dispersed todo all over the code. . diff --git a/doc/std/kdev3api.toc b/doc/std/kdev3api.toc index 28d9cf3a..be3c7f0c 100644 --- a/doc/std/kdev3api.toc +++ b/doc/std/kdev3api.toc @@ -1,7 +1,7 @@ - - + + KDevelop API Documentation - + @@ -42,4 +42,4 @@ - + -- cgit v1.2.3
- The &kdevelop; documentation window (IDEAl mode) + The &tdevelop; documentation window (IDEAl mode)