1 files changed, 16 insertions, 16 deletions

diff --git a/kdejava/koala/org/kde/koala/KLibFactory.java b/kdejava/koala/org/kde/koala/KLibFactory.java
index bb9c9a19..4aac16e3 100644
--- a/kdejava/koala/org/kde/koala/KLibFactory.java
+++ b/kdejava/koala/org/kde/koala/KLibFactory.java
@@ -2,10 +2,10 @@
 package org.kde.koala;
 
 import org.kde.qt.Qt;
-import org.kde.qt.QMetaObject;
+import org.kde.qt.TQMetaObject;
 import org.kde.qt.QtSupport;
-import org.kde.qt.QObject;
-import org.kde.qt.QObject;
+import org.kde.qt.TQObject;
+import org.kde.qt.TQObject;
 
 /**
 
@@ -33,7 +33,7 @@ import org.kde.qt.QObject;
  The KLibFactory is used to create the components, the library has to offer.
  The factory of KSpread for example will create instances of KSpreadDoc,
  while the Konqueror factory will create KonqView widgets.
- All objects created by the factory must be derived from QObject, since QObject
+ All objects created by the factory must be derived from TQObject, since TQObject
  offers type safe casting.
  KLibFactory is an abstract class. Reimplement the
  createObject() method to give it functionality.
@@ -43,14 +43,14 @@ import org.kde.qt.QObject;
 		@short    If you develop a library that is to be loaded dynamically at runtime, then  you should return a pointer to your factory.
 
 */
-public class KLibFactory extends QObject  {
+public class KLibFactory extends TQObject  {
 	protected KLibFactory(Class dummy){super((Class) null);}
-	public native QMetaObject metaObject();
+	public native TQMetaObject metaObject();
 	public native String className();
 	/**	
 		 Create a new factory.
-			@param parent the parent of the QObject, 0 for no parent
-			@param name the name of the QObject, 0 for no name
+			@param parent the parent of the TQObject, 0 for no parent
+			@param name the name of the TQObject, 0 for no name
 		     		@short    Create a new factory.
 	*/
 	/**	
@@ -59,21 +59,21 @@ public class KLibFactory extends QObject  {
 			 It is valid behavior to create different kinds of objects
 		 depending on the requested <code>classname.</code> For example a koffice
 		 library may usually return a pointer to KoDocument.  But
-		 if asked for a "QWidget", it could create a wrapper widget,
+		 if asked for a "TQWidget", it could create a wrapper widget,
 		 that encapsulates the Koffice specific features.
 			 create() automatically emits a signal objectCreated to tell
 		 the library about its newly created object.  This is very
 		 important for reference counting, and allows unloading the
 		 library automatically once all its objects have been destroyed.
-			@param parent the parent of the QObject, 0 for no parent
-			@param name the name of the QObject, 0 for no name
+			@param parent the parent of the TQObject, 0 for no parent
+			@param name the name of the TQObject, 0 for no name
 			@param classname the name of the class
 			@param args a list of arguments
 		     		@short    Creates a new object.
 	*/
-	public native QObject create(QObject parent, String name, String classname, String[] args);
-	public native QObject create(QObject parent, String name, String classname);
-	public native QObject create(QObject parent, String name);
-	public native QObject create(QObject parent);
-	public native QObject create();
+	public native TQObject create(TQObject parent, String name, String classname, String[] args);
+	public native TQObject create(TQObject parent, String name, String classname);
+	public native TQObject create(TQObject parent, String name);
+	public native TQObject create(TQObject parent);
+	public native TQObject create();
 }