summaryrefslogtreecommitdiffstats
path: root/lib/interfaces/external
diff options
context:
space:
mode:
authorDarrell Anderson <humanreadable@yahoo.com>2012-07-04 16:46:19 -0500
committerDarrell Anderson <humanreadable@yahoo.com>2012-07-04 16:46:19 -0500
commit998ebd2e683e45140493910f76e692e96887b5d2 (patch)
tree4d75be7d82ab9ba5ebd7c95c5b64a265971183d2 /lib/interfaces/external
parent9ba3adb356665bc27c3416c0b916efa89b366bde (diff)
downloadtdevelop-998ebd2e683e45140493910f76e692e96887b5d2.tar.gz
tdevelop-998ebd2e683e45140493910f76e692e96887b5d2.zip
Fix help files, kdevelop->tdevelop branding, fix startup.
Diffstat (limited to 'lib/interfaces/external')
-rw-r--r--lib/interfaces/external/Mainpage.dox8
-rw-r--r--lib/interfaces/external/designer.h2
2 files changed, 5 insertions, 5 deletions
diff --git a/lib/interfaces/external/Mainpage.dox b/lib/interfaces/external/Mainpage.dox
index 89d89b66..b66b8795 100644
--- a/lib/interfaces/external/Mainpage.dox
+++ b/lib/interfaces/external/Mainpage.dox
@@ -15,9 +15,9 @@ functions to determine designer type.
If a part which can "design" user interface files of a certain mimetype
implements this interface and sets itself as a default handler for that
-mimetype then it becomes automatically integrated into KDevelop IDE.
+mimetype then it becomes automatically integrated into TDevelop IDE.
-When a part is embedded into KDevelop shell, its Q_SIGNALS (defined in @ref
+When a part is embedded into TDevelop shell, its Q_SIGNALS (defined in @ref
KInterfaceDesigner::Designer interface):
@code
void addedFunction(DesignerType type, const QString &formName, Function function)
@@ -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 KDevelop 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 KDevelop language support plugin.
Each language support which wants to use integrated designer, must reimplement
@code
@@ -41,7 +41,7 @@ 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:
-- KDevDesigner provides a read/write KPart which can be embedded into any application which wants to edit .ui files. KDevelop IDE embeds KDevDesigner this way.
+- 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/interfaces/external/designer.h b/lib/interfaces/external/designer.h
index 936ae810..4396c1ab 100644
--- a/lib/interfaces/external/designer.h
+++ b/lib/interfaces/external/designer.h
@@ -61,7 +61,7 @@ See signals documentation for an explanation on when to emit those.
If a part which can "design" user interface files of a certain mimetype
implements this interface and sets itself as a default handler for that
-mimetype then it becomes automatically integrated into KDevelop IDE.
+mimetype then it becomes automatically integrated into TDevelop IDE.
*/
class Designer: public KParts::ReadWritePart{
Q_OBJECT