summaryrefslogtreecommitdiffstats
path: root/kjsembed/design.h
diff options
context:
space:
mode:
Diffstat (limited to 'kjsembed/design.h')
-rw-r--r--kjsembed/design.h20
1 files changed, 10 insertions, 10 deletions
diff --git a/kjsembed/design.h b/kjsembed/design.h
index d255aeef..cf156222 100644
--- a/kjsembed/design.h
+++ b/kjsembed/design.h
@@ -38,7 +38,7 @@
* A widget that provides an interactive JS console.
*
* @ref KJSEmbed::JSObjectProxy :
- * A Javascript object that can access the properties of a QObject,
+ * A Javascript object that can access the properties of a TQObject,
*
* @ref KJSEmbed::SecurityPolicy :
* Defines a security policy for @ref JSObjectProxy.
@@ -71,12 +71,12 @@
* class, but is more easily used via the addObject(...) methods of @ref KJSEmbedPart.
*
* The following code shows how easy it is to make an object available for
- * scripting. It creates a QVBox containing two QLabels then makes them visible
+ * scripting. It creates a TQVBox containing two QLabels then makes them visible
* to KJSEmbed:
* <pre>
- * QVBox *toplevel = new QVBox( 0, "box" );
- * QLabel *title = new QLabel( "Some Title", toplevel, "title");
- * QLabel *main = new QLabel( "Some text, more text.", toplevel, "main" );
+ * TQVBox *toplevel = new TQVBox( 0, "box" );
+ * TQLabel *title = new TQLabel( "Some Title", toplevel, "title");
+ * TQLabel *main = new TQLabel( "Some text, more text.", toplevel, "main" );
*
* js->addObject( title );
* js->addObject( main, "text" );
@@ -92,14 +92,14 @@
* </pre>
* The script above would set the text of the label to 'Hello World'.
*
- * The slots of a QObject bound to the interpreter are made available to
+ * The slots of a TQObject bound to the interpreter are made available to
* scripts as if they normal methods. In the example above, we could conceal
* the label 'main' entirely by calling its hide() slot:
* <pre>
* main.hide()
* </pre>
*
- * @section tree Access To the QObject Tree
+ * @section tree Access To the TQObject Tree
*
* As well as providing script access to an individual widget, KJSEmbed
* allows scripts to walk the object tree and access others. If we
@@ -134,7 +134,7 @@
* To embed the interpreter we can just create a new KJSEmbed part.
* @skipline m_part
* To publish the objects we can then call @ref KJSEmbed::KJSEmbedPart::addObject on our part.
- * This will then add any QObject based class the the global scope of the
+ * This will then add any TQObject based class the the global scope of the
* javascript interperter.
* @skipline addObject
* Once you have your objects published you can then execute javascript code from a file.
@@ -148,10 +148,10 @@
* @ref KJS::List. This is just a list of @ref KJS::Value objects and can be created from
* QVariants or from custom @ref KJS::Object based classes.
* Once you have the data back from the method you can convert it easily from the @ref KJS::Value
- * type to a QVariant with the @ref KJSEmbed::convertToVariant method.
+ * type to a TQVariant with the @ref KJSEmbed::convertToVariant method.
* @line personalData
* @until notes:
- * Complex arrays or @ref KJS::Objects are transparently converted to QVariant::Map types so
+ * Complex arrays or @ref KJS::Objects are transparently converted to TQVariant::Map types so
* they can easily be manipulated from C++.
* The KJSEmbed::console is also easy to add to applications. An example of a method that
* will toggle the console is below.