Fixed generation of API documentation. Updated TDevelop API documentation toc file. This relates to bug 1859.

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

4 files changed, 8 insertions, 8 deletions

diff --git a/lib/interfaces/external/Mainpage.dox b/lib/interfaces/external/Mainpage.dox
index 4ed571dd..8c22ba73 100644
--- a/lib/interfaces/external/Mainpage.dox
+++ b/lib/interfaces/external/Mainpage.dox
@@ -26,7 +26,7 @@ KInterfaceDesigner::Designer interface):
     void editFunction(DesignerType type, const QString &formName, const QString &functionName)
     void editSource(DesignerType type, const QString &formName);
 @endcode
-are connected to corresponding Q_SLOTS of TDevelop designer integration engine which can be implemented in KDevelop language support plugin.
+are connected to corresponding Q_SLOTS of TDevelop designer integration engine which can be implemented in TDevelop language support plugin.
  
 Each language support which wants to use integrated designer, must reimplement 
 @code
@@ -39,8 +39,8 @@ developers. With the convenience library writing %Qt designer integration for th
 trivial task.
 
 
-\section kdevdesigner KDevelop Designer technical overview
-KDevelop version >= 3.1 comes with a customized version (fork ;)) of %Qt Designer. It is called KDevelop Designer (KDevDesigner, kdevdesigner from the command line). KDevDesigner has some important differences:
+\section kdevdesigner TDevelop Designer technical overview
+TDevelop version >= 3.1 comes with a customized version (fork ;)) of %Qt Designer. It is called TDevelop Designer (KDevDesigner, kdevdesigner from the command line). KDevDesigner has some important differences:
 - KDevDesigner provides a read/write KPart which can be embedded into any application which wants to edit .ui files. TDevelop IDE embeds KDevDesigner this way.
 - KDevDesigner uses %KDE icons and dialogs and thus provides better integration with a system.
 .
diff --git a/lib/util/Mainpage.dox b/lib/util/Mainpage.dox
index 7cd0974c..e28aa430 100644
--- a/lib/util/Mainpage.dox
+++ b/lib/util/Mainpage.dox
@@ -1,7 +1,7 @@
 /**
-@mainpage The KDevelop Utility Library
+@mainpage The TDevelop Utility Library
 
-This library contains utility classes for the KDevelop architecture.
+This library contains utility classes for the TDevelop architecture.
 
 <b>Link with</b>: -ltdevelop
 
diff --git a/lib/widgets/Mainpage.dox b/lib/widgets/Mainpage.dox
index 1208c02f..b3854054 100644
--- a/lib/widgets/Mainpage.dox
+++ b/lib/widgets/Mainpage.dox
@@ -1,5 +1,5 @@
 /**
-@mainpage The KDevelop Widgets Library
+@mainpage The TDevelop Widgets Library
 
 This library contains a collection of widgets.
 
diff --git a/lib/widgets/propeditor/Mainpage.dox b/lib/widgets/propeditor/Mainpage.dox
index 9a3a741a..d77010d0 100644
--- a/lib/widgets/propeditor/Mainpage.dox
+++ b/lib/widgets/propeditor/Mainpage.dox
@@ -1,5 +1,5 @@
 /**
-@mainpage The KDevelop Property Editing Library
+@mainpage The TDevelop Property Editing Library
 
 <b>Link with</b>: -ltdevelop
 
@@ -12,7 +12,7 @@
 properties of an object. For example, look at %Qt Designer. Each widget
 has a list of properties that can be edited in a nice table form.
 Same ideology is used to edit properties in Kugar Report Designer
-(from KOffice distribution). In KDevelop project manager can also display
+(from KOffice distribution). In TDevelop project manager can also display
 the properties of currently selected build item in property editor.
 
 \section over Library Overview