summaryrefslogtreecommitdiffstats
path: root/doc/api/HowToAddPlugins.dox
diff options
context:
space:
mode:
Diffstat (limited to 'doc/api/HowToAddPlugins.dox')
-rw-r--r--doc/api/HowToAddPlugins.dox10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox
index fa7f74e2..012cb5d0 100644
--- a/doc/api/HowToAddPlugins.dox
+++ b/doc/api/HowToAddPlugins.dox
@@ -1,12 +1,12 @@
/** \file HowToAddPlugins.dox
- * \brief How to extend KDevelop via plugins
+ * \brief How to extend TDevelop via plugins
*/
-/** \page howToAddPlugins How to extend KDevelop via plugins
+/** \page howToAddPlugins How to extend TDevelop via plugins
\section createDesktop Step 1: Make your plugin loadable
-For a plugin <code>foo</code>, create a file <code>foo.desktop</code> which contains KDevelop/Part in its list of ServiceTypes.
+For a plugin <code>foo</code>, create a file <code>foo.desktop</code> which contains TDevelop/Part in its list of ServiceTypes.
- See <code>parts/doctreeview/kdevdoctreeview.desktop</code> for an example.
.
@@ -118,7 +118,7 @@ Take attention to the issue that the project file usually is shared in a team of
developers (e.g. via version control application CVS). So some user preferences might be
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
+That's why the TDevelop architecture makes a difference here and supports two files
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.
@@ -159,7 +159,7 @@ The base class of all TDevelop plugins is KDevPlugin. It provides two virtual me
restorePartialProjectSession(..) and savePartialProjectSession(..)
that you should reimplement in your special plugin to attach to session loading and saving.
-When KDevelop loads or closes a project, the program's project session manager
+When TDevelop loads or closes a project, the program's project session manager
(class ProjectSession) calls them for each plugin. That manager gives a QDOM node to the
plugin where it can read out or build up its partial DOM subtree with the session settings.
That subtree will be stored in the .kdevses file by that session manager.