diff options
Diffstat (limited to 'doc/api/HowToAddPlugins.dox')
| -rw-r--r-- | doc/api/HowToAddPlugins.dox | 6 |
1 files changed, 3 insertions, 3 deletions
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) </pre></code> 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). |