summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/api/HowToAddPlugins.dox10
-rw-r--r--doc/api/HowToAddProgrammingLanguages.dox2
-rw-r--r--doc/api/HowToDocument.dox2
-rw-r--r--doc/api/Mainpage.dox6
-rw-r--r--doc/kde_app_devel/index.docbook4
-rw-r--r--doc/kdearch/index.docbook2
-rw-r--r--doc/platform/Mainpage.dox20
-rw-r--r--doc/std/kdev3api.toc2
-rwxr-xr-xdoc/tdevelop/listplugins.sh2
-rw-r--r--doc/tdevelop/plugin-tools.docbook4
-rw-r--r--doc/tdevelop/project-management.docbook2
-rw-r--r--doc/tdevelop/tdevelop-install.docbook4
12 files changed, 30 insertions, 30 deletions
diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox
index 3ab31af9..70176630 100644
--- a/doc/api/HowToAddPlugins.dox
+++ b/doc/api/HowToAddPlugins.dox
@@ -17,14 +17,14 @@ If you install this file into <code>\$(kde_servicesdir)</code>, your plugin will
You can change the default loading by changing some settings in your <code>foo.desktop</code> file:
- - Set <code>X-KDevelop-Scope=</code> to <code>Global</code> or
+ - Set <code>X-TDevelop-Scope=</code> to <code>Global</code> or
<code>Project</code>
- <b>Note:</b> This property is <i>not</i> optional
.
- You can add a list of programming languages which are supported by your
plugin
- If your plugin works with all languages leave the
- <code>X-KDevelop-ProgrammingLanguages=</code> field empty
+ <code>X-TDevelop-ProgrammingLanguages=</code> field empty
<i>(optional)</i>
.
- You can add a list of keywords.
@@ -37,8 +37,8 @@ An example from the Java Debugger Plugin:
<code><pre>
#######################
- X-KDevelop-Scope=Project
- X-KDevelop-ProgrammingLanguages=Java
+ X-TDevelop-Scope=Project
+ X-TDevelop-ProgrammingLanguages=Java
Keywords=
##########################
</pre></code>
@@ -155,7 +155,7 @@ to write it back.
\subsection sessionAccess Project session file (*.kdevses)
-The base class of all KDevelop plugins is KDevPlugin. It provides two virtual methods
+The base class of all TDevelop plugins is KDevPlugin. It provides two virtual methods
restorePartialProjectSession(..) and savePartialProjectSession(..)
that you should reimplement in your special plugin to attach to session loading and saving.
diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox
index 504a397e..a5840885 100644
--- a/doc/api/HowToAddProgrammingLanguages.dox
+++ b/doc/api/HowToAddProgrammingLanguages.dox
@@ -184,7 +184,7 @@ Compiler plugins must implement KDevCompilerOptions interface.
In the end you should add the language you implemented to the doc/api/LangSupportStatus.dox file and
document your language support part in the way described at \ref howToDocument (doc/api/HowToDocument.dox file).
-See also \ref howToAddPlugins (doc/api/HowToAddPlugins.dox file) for an information on how to create a generic KDevelop plugin and how to manage project and global configuration information.
+See also \ref howToAddPlugins (doc/api/HowToAddPlugins.dox file) for an information on how to create a generic TDevelop plugin and how to manage project and global configuration information.
diff --git a/doc/api/HowToDocument.dox b/doc/api/HowToDocument.dox
index f767fc5b..d606a8bf 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.tdevelop.org
+http://www.kdevelop.org
or read the README.dox file.
\endverbatim
diff --git a/doc/api/Mainpage.dox b/doc/api/Mainpage.dox
index 44fa64db..262cd2ed 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 <a href="http://www.tdevelop.org/index.html?filename=mailinglist.html">mailing list</a> for any additions and/or
+can subscribe or read the <a href="http://www.kdevelop.org/index.html?filename=mailinglist.html">mailing list</a> 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.tdevelop.org/HEAD/doc/api/html/index.html
+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
More information about the KDevelop architecture in form of tutorials, HOWTOs,
and FAQs can be found at
-the <a href="http://www.tdevelop.org">KDevelop website</a>.
+the <a href="http://www.kdevelop.org">KDevelop website</a>.
\section status Current Status
diff --git a/doc/kde_app_devel/index.docbook b/doc/kde_app_devel/index.docbook
index ac8e05b6..188297f9 100644
--- a/doc/kde_app_devel/index.docbook
+++ b/doc/kde_app_devel/index.docbook
@@ -135,7 +135,7 @@ You will learn how to:
Additional information about Qt/KDE programming is available by various sources:
<itemizedlist>
<listitem><para>Programming with Qt by Matthias Kalle Dalheimer</para></listitem>
-<listitem><para><ulink url="www.tdevelop.org">The User Manual to KDevelop, provided with the KDevelop IDE</ulink></para></listitem>
+<listitem><para><ulink url="www.kdevelop.org">The User Manual to KDevelop, provided with the TDevelop IDE</ulink></para></listitem>
<listitem><para><ulink url="doc.trolltech.com">The Online Reference to the Qt library</ulink></para></listitem>
<listitem><para><ulink url="developer.kde.org">The KDE Developer web site</ulink></para></listitem>
</itemizedlist>
@@ -146,7 +146,7 @@ are available on the mentioned web sites, and on the Usenet newsgroups dedicated
Unix Systems as well as about the C and C++ programming language.
</para>
<para>
-For obtaining help about the KDevelop IDE, you should send requests to our mailinglist at
+For obtaining help about the TDevelop IDE, you should send requests to our mailinglist at
<email>tdevelop@tdevelop.org</email>. 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
diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook
index c016affd..000cf9c3 100644
--- a/doc/kdearch/index.docbook
+++ b/doc/kdearch/index.docbook
@@ -2920,7 +2920,7 @@ cache, you can use:
<programlisting>
void FooClass::reloadPage()
{
- KURL url("http://www.tdevelop.org/index.html");
+ KURL url("http://www.kdevelop.org/index.html");
KIO::TransferJob *job = KIO::get(url, true, false);
job->addMetaData("cache", "reload");
...
diff --git a/doc/platform/Mainpage.dox b/doc/platform/Mainpage.dox
index b5d008c6..29f6deb0 100644
--- a/doc/platform/Mainpage.dox
+++ b/doc/platform/Mainpage.dox
@@ -22,34 +22,34 @@ 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 <a href="http://www.tdevelop.org/index.html?filename=mailinglist.html">mailing list</a> for any additions and/or
+can subscribe or read the <a href="http://www.kdevelop.org/index.html?filename=mailinglist.html">mailing list</a> 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.tdevelop.org/HEAD/doc/platform/html/index.html
+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
-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.
+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.
More information about the KDevelop Platform architecture in form of tutorials, Wikis, HOWTOs,
and FAQs can be found at
-the <a href="http://www.tdevelop.org">KDevelop website</a>.
+the <a href="http://www.kdevelop.org">KDevelop website</a>.
-Quick overviews of the architecture can also be found in the issues of <a href="http://www.tdevelop.org/doc/tehcnotes">
+Quick overviews of the architecture can also be found in the issues of <a href="http://www.kdevelop.org/doc/tehcnotes">
KDevelop Technotes</a>.
\section platformapi Platform Libraries API
- <a href="kdevinterfaces/html/index.html"><b>Interfaces Library</b></a>
(<a href="kdevinterfaces/html/classes.html">classes</a>)\n
- <i>Interfaces and classes that form KDevelop plugin architecture.</i>
+ <i>Interfaces and classes that form TDevelop plugin architecture.</i>
- <a href="kdevextensions/html/index.html"><b>Extension Interfaces Library</b></a>
(<a href="kdevextensions/html/classes.html">classes</a>)\n
- <i>Extension interfaces used by KDevelop plugin architecture.</i>
+ <i>Extension interfaces used by TDevelop plugin architecture.</i>
- <a href="kdevutil/html/index.html"><b>Utility Library</b></a>
(<a href="kdevutil/html/classes.html">classes</a>)\n
<i>Utility classes for the KDevelop architecture.</i>
- <a href="kdevextras/html/index.html"><b>Extra Interfaces Library</b></a>
(<a href="kdevextras/html/classes.html">classes</a>)\n
- <i>Extra interfaces that are not the part of KDevelop plugin architecture
+ <i>Extra interfaces that are not the part of TDevelop plugin architecture
but that can be implemented by extra plugins or "plugins for plugins".</i>
- <a href="kdevwidgets/html/index.html"><b>Widgets Library</b></a>
(<a href="kdevwidgets/html/classes.html">classes</a>)\n
@@ -112,10 +112,10 @@ KDevelop Technotes</a>.
- <a href="kdevshellsrc/html/index.html"><b>Generic Shell</b></a>
(<a href="kdevshellsrc/html/classes.html">classes</a>)\n
- <i>The Shell - a profile-based implementation of KDevelop plugin architecture.</i>
+ <i>The Shell - a profile-based implementation of TDevelop plugin architecture.</i>
- <a href="kdevprofileslib/html/index.html"><b>Shell Profiles Library</b></a>
(<a href="kdevprofileslib/html/classes.html">classes</a>)\n
- <i>Plugin profiles implementation for KDevelop shell.</i>
+ <i>Plugin profiles implementation for TDevelop shell.</i>
.
\section PlannedTasks Planned tasks
diff --git a/doc/std/kdev3api.toc b/doc/std/kdev3api.toc
index be3c7f0c..ef1c82dc 100644
--- a/doc/std/kdev3api.toc
+++ b/doc/std/kdev3api.toc
@@ -1,7 +1,7 @@
<!DOCTYPE tdeveloptoc>
<tdeveloptoc>
<title>KDevelop API Documentation</title>
-<base href="http://www.tdevelop.org/HEAD/doc/api/html"/>
+<base href="http://www.kdevelop.org/HEAD/doc/api/html"/>
<tocsect1 name="Overview" url="index.html">
<tocsect2 name="KDevelop 3 Architecture" url="KDev3Arch.html"/>
<tocsect2 name="Programming Languages Status" url="LangSupportStatus.html"/>
diff --git a/doc/tdevelop/listplugins.sh b/doc/tdevelop/listplugins.sh
index f916b7fe..22251293 100755
--- a/doc/tdevelop/listplugins.sh
+++ b/doc/tdevelop/listplugins.sh
@@ -26,7 +26,7 @@ for defscope in Core Global Project; do
# echo $dfile | wc -w
if [ `echo $dfile | wc -w` -gt 1 ]; then continue; fi
if [ ! -f $dfile ]; then continue; fi
- scope=`cat $dfile | grep "X-KDevelop-Scope=" | cut -d= -f2-`
+ scope=`cat $dfile | grep "X-TDevelop-Scope=" | cut -d= -f2-`
if [ $scope != $defscope ]; then continue; fi
comment=`cat $dfile | grep "Comment=" | cut -d= -f2-`
name=`cat $dfile | egrep "^Name=" | cut -d= -f2- | tr " " _`
diff --git a/doc/tdevelop/plugin-tools.docbook b/doc/tdevelop/plugin-tools.docbook
index 35e2c206..a05c1e7c 100644
--- a/doc/tdevelop/plugin-tools.docbook
+++ b/doc/tdevelop/plugin-tools.docbook
@@ -18,8 +18,8 @@ it's enabled in the Project - Project Options dialog.
lib/interfaces/kdevplugin.h. The following is taken from a comment from there.</para>
<para>
-KDevPlugin is the base class for all KDevelop plugins.
-A plugin is a component which is loaded into KDevelop shell at startup or by request.
+KDevPlugin is the base class for all TDevelop plugins.
+A plugin is a component which is loaded into TDevelop shell at startup or by request.
A plugin has a scope that can be either:
<itemizedlist>
<listitem><simpara>Core</simpara></listitem>
diff --git a/doc/tdevelop/project-management.docbook b/doc/tdevelop/project-management.docbook
index 69ca9474..e70d07dc 100644
--- a/doc/tdevelop/project-management.docbook
+++ b/doc/tdevelop/project-management.docbook
@@ -126,7 +126,7 @@ One of these four alternatives must be chosen when you create a project and <emp
There are several tutorials available on the &GNU; Build System (<command>Autoconf</command>, <command>Automake</command> and <command>Libtool</command>) of which the &automanag; makes use.
</para>
<itemizedlist>
- <listitem><para>A short <ulink url="http://www.tdevelop.org/index.html?filename=tutorial_autoconf.html">autoconf tutorial</ulink> written by Christopher W. Curtis available on the &tdevelop; home page. It concentrates on some basic steps to modify a <filename>Makefile</filename>.
+ <listitem><para>A short <ulink url="http://www.kdevelop.org/index.html?filename=tutorial_autoconf.html">autoconf tutorial</ulink> written by Christopher W. Curtis available on the &tdevelop; home page. It concentrates on some basic steps to modify a <filename>Makefile</filename>.
</para></listitem>
<listitem><para>
A more detailed tutorial can be found in a greater set of tutorials on <ulink url="http://www.amath.washington.edu/~lf/tutorials/autoconf/toolsmanual_toc.html"><quote>Developing software with GNU</quote></ulink>.
diff --git a/doc/tdevelop/tdevelop-install.docbook b/doc/tdevelop/tdevelop-install.docbook
index 05f6ef5a..5e07b0b6 100644
--- a/doc/tdevelop/tdevelop-install.docbook
+++ b/doc/tdevelop/tdevelop-install.docbook
@@ -45,7 +45,7 @@ In this chapter we will discuss the steps necessary to compile and install the &
&tdevelop; is available in binary form from many different &Linux; distributions such as <!--&SuSE;, &RedHat;//--> 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.
</para>
<para>
-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 <ulink url="http://www.tdevelop.org"> http://www.tdevelop.org</ulink> or via the <ulink url="http://download.kde.org">&kde; ftp site</ulink>.
+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 <ulink url="http://www.kdevelop.org"> http://www.kdevelop.org</ulink> or via the <ulink url="http://download.kde.org">&kde; ftp site</ulink>.
</para>
<sect2 id="howto-svn">
@@ -699,7 +699,7 @@ The <command>kbuildsycoca</command> command does not run from within the root. Y
API is the short form of <quote>Application Program Interface</quote>. 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.
</para>
<para>
-There is a version of the most current API available at the <ulink url="http://www.tdevelop.org/HEAD/doc/api/html/index.html">KDevelop-Home website</ulink>. 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 <ulink url="http://www.kdevelop.org/HEAD/doc/api/html/index.html">KDevelop-Home website</ulink>. It will be automatically updated every 24 hours so you can keep up.
</para>
<para>
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 <option>--with-tdelibsdoxy-dir</option> in the <command>configure</command> command when you prepare to compile the &tdevelop; sources:
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-18 21:36:05 +0000