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

1 files changed, 6 insertions, 5 deletions

diff --git a/lib/interfaces/kdevdesignerintegration.h b/lib/interfaces/kdevdesignerintegration.h
index c1604a4a..6cd8fffb 100644
--- a/lib/interfaces/kdevdesignerintegration.h
+++ b/lib/interfaces/kdevdesignerintegration.h
@@ -40,22 +40,23 @@ into KDevelop GUI designers:
 Designer integration is a layer between visual form (GUI) designer of any type
 and the current language support. Usually designers create some kind of forms
 and allow developers to define actions which are executed upon some GUI events
-(for example, Qt Designer allows to define slots connected to GUI signals).
+(for example, TQt Designer allows to define slots connected to GUI signals).
 The actual code with action implementations needs to be written by hand in source
 files. Designer integration captures such implementation requests and opens
 necessary files at desired line numbers and adds (edits, removes) code for implementations.
 
-For example, Qt Designer integration should be able to create an subclass for a form
+For example, TQt Designer integration should be able to create an subclass for a form
 and reimplement slots defined in the form.
 */
-class KDevDesignerIntegration : public QObject
+class KDevDesignerIntegration : public TQObject
 {
 Q_OBJECT
+  TQ_OBJECT
 public:
     /**Constructor.
-    @param parent Parent object.
+    @param tqparent Parent object.
     @param name Internal name.*/
-    KDevDesignerIntegration(TQObject *parent = 0, const char *name = 0);
+    KDevDesignerIntegration(TQObject *tqparent = 0, const char *name = 0);
     /**Destructor.*/
     ~KDevDesignerIntegration();