From ab2599a71564597ae0a994454ffe19f3e5c99c78 Mon Sep 17 00:00:00 2001 From: Darrell Anderson Date: Thu, 7 Jun 2012 14:23:10 -0500 Subject: Revert patch pushed in GIT hash 2b84a5e. The patch is good but pushed prematurely --- needing another patch set not yet pushed to GIT. --- doc/kdearch/index.docbook | 30 +++++++++++++++--------------- doc/tdevelop/index.docbook | 6 +++--- 2 files changed, 18 insertions(+), 18 deletions(-) (limited to 'doc') diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook index 3a01f193..8b3a2453 100644 --- a/doc/kdearch/index.docbook +++ b/doc/kdearch/index.docbook @@ -1870,8 +1870,8 @@ embedable component that implements the service types KParts/ReadOnlyPart and Browser/View. -In TDevelop HEAD, most functionality is packaged in -plugins with the service type TDevelop/Part. At startup, +In KDevelop HEAD, most functionality is packaged in +plugins with the service type KDevelop/Part. At startup, all services with this type are loaded, such that you can extend the IDE in a very flexible way. @@ -1890,10 +1890,10 @@ Obviously, a service is not only characterized by the service types it implements, but also by some properties. For example, a ThumbCreator does not only claim to implement the C++ class with the type ThumbCreator, it also has a list of MIME types it is -responsible for. Similarly, TDevelop parts have the programming language they +responsible for. Similarly, KDevelop parts have the programming language they support as a property. When an application requests a service type, it can also list constraints on the properties of the service. In the above example, -when TDevelop loads the plugins for a Java project, it asks only for the +when KDevelop loads the plugins for a Java project, it asks only for the plugins which have Java as the programming language property. For this purpose, KDE contains a full-blown CORBA-like trader with a complex query language. @@ -1919,22 +1919,22 @@ EXTRA_DIST = $(kde_servicetypesdir_DATA) The definition tdeveloppart.desktop of a -TDevelop part looks as follows: +KDevelop part looks as follows: [Desktop Entry] Type=ServiceType -X-KDE-ServiceType=TDevelop/Part -Name=TDevelop Part +X-KDE-ServiceType=KDevelop/Part +Name=KDevelop Part -[PropertyDef::X-TDevelop-Scope] +[PropertyDef::X-KDevelop-Scope] Type=QString -[PropertyDef::X-TDevelop-ProgrammingLanguages] +[PropertyDef::X-KDevelop-ProgrammingLanguages] Type=QStringList -[PropertyDef::X-TDevelop-Args] +[PropertyDef::X-KDevelop-Args] Type=QString @@ -1967,7 +1967,7 @@ EXTRA_DIST = $(kde_servicesdir_DATA) The content of the following example file kdevdoxygen.desktop defines the KDevDoxygen plugin with the service type -TDevelop/Part: +KDevelop/Part: @@ -1975,10 +1975,10 @@ The content of the following example file Type=Service Comment=Doxygen Name=KDevDoxygen -ServiceTypes=TDevelop/Part +ServiceTypes=KDevelop/Part X-KDE-Library=libkdevdoxygen -X-TDevelop-ProgrammingLanguages=C,C++,Java -X-TDevelop-Scope=Project +X-KDevelop-ProgrammingLanguages=C,C++,Java +X-KDevelop-Scope=Project @@ -2001,7 +2001,7 @@ extern "C" { The type of the factory class DoxygenFactory depends on -the specific service type the service implements. In our example of a TDevelop +the specific service type the service implements. In our example of a KDevelop plugin, the factory must be a KDevFactory (which inherits KLibFactory). More common examples are KParts::Factory diff --git a/doc/tdevelop/index.docbook b/doc/tdevelop/index.docbook index 30ac2531..a21a3b38 100644 --- a/doc/tdevelop/index.docbook +++ b/doc/tdevelop/index.docbook @@ -1,7 +1,7 @@ TDevelop"> --> - + + @@ -142,7 +142,7 @@ Entries which require special treatment are marked with comments starting with ' KDE - TDevelop + KDevelop IDE development programming -- cgit v1.2.1