From 48d4a26399959121f33d2bc3bfe51c7827b654fc Mon Sep 17 00:00:00 2001 From: tpearson Date: Tue, 14 Jun 2011 16:45:05 +0000 Subject: TQt4 port kdevelop This enables compilation under both Qt3 and Qt4 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdevelop@1236710 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- lib/interfaces/external/Mainpage.dox | 6 +++--- lib/interfaces/external/designer.cpp | 4 ++-- lib/interfaces/external/designer.h | 9 +++++---- 3 files changed, 10 insertions(+), 9 deletions(-) (limited to 'lib/interfaces/external') diff --git a/lib/interfaces/external/Mainpage.dox b/lib/interfaces/external/Mainpage.dox index 4618c3d5..8b91bf8c 100644 --- a/lib/interfaces/external/Mainpage.dox +++ b/lib/interfaces/external/Mainpage.dox @@ -10,14 +10,14 @@ GUI Designer integration framework. \section designerintegration Overview of GUI designer integration process Each KPart that wants to act as a GUI Designer must implement @ref KInterfaceDesigner::Designer -interface. It defines necessary signals to communicate with an IDE and abstract virtual +interface. It defines necessary Q_SIGNALS to communicate with an IDE and abstract virtual 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. -When a part is embedded into KDevelop shell, its signals (defined in @ref +When a part is embedded into KDevelop 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 slots of KDevelop designer integration engine which can be implemented in KDevelop language support plugin. +are connected to corresponding Q_SLOTS of KDevelop designer integration engine which can be implemented in KDevelop language support plugin. Each language support which wants to use integrated designer, must reimplement @code diff --git a/lib/interfaces/external/designer.cpp b/lib/interfaces/external/designer.cpp index 606fd2b4..06c28d50 100644 --- a/lib/interfaces/external/designer.cpp +++ b/lib/interfaces/external/designer.cpp @@ -20,8 +20,8 @@ namespace KInterfaceDesigner{ -Designer::Designer(TQObject *parent, const char *name) - :KParts::ReadWritePart(parent, name) +Designer::Designer(TQObject *tqparent, const char *name) + :KParts::ReadWritePart(tqparent, name) { } diff --git a/lib/interfaces/external/designer.h b/lib/interfaces/external/designer.h index c254ab07..72d7508a 100644 --- a/lib/interfaces/external/designer.h +++ b/lib/interfaces/external/designer.h @@ -26,14 +26,14 @@ namespace KInterfaceDesigner{ /**The type of a GUI Designer.*/ enum DesignerType { - QtDesigner /**= 3).*/ }; /**Function type.*/ enum FunctionType { ftFunction /**