Initial TQt conversion

1 files changed, 11 insertions, 11 deletions

diff --git a/kjsembed/docs/examples/html2text/test.htm b/kjsembed/docs/examples/html2text/test.htm
index 2a060c2d..af257805 100644
--- a/kjsembed/docs/examples/html2text/test.htm
+++ b/kjsembed/docs/examples/html2text/test.htm
@@ -38,7 +38,7 @@ pre {
   been designed with this in mind thanks to a KParts plugin. In addition, KJSEmbed 
   provides a command line tool for running scripts so users can easily create 
   simple applications of their own in Javascript. KJSEmbed scripts are surprisingly 
-  powerful because they access the properties and slots of QObjects, and can even 
+  powerful because they access the properties and slots of TQObjects, and can even 
   load widgets and dialogs created with Qt's graphical dialog editor.</p>
 <h3>Features</h3>
 <p>To give you an idea of what KJSEmbed provides, here is a brief summary of the 
@@ -50,16 +50,16 @@ pre {
   <li>Command line tool for running scripts (this can even operate without an 
     X server if you don't need to display a GUI).</li>
   <li>Define new KActions using XML.</li>
-  <li>Scripts can access the properties and slots of QObjects as if they were 
+  <li>Scripts can access the properties and slots of TQObjects as if they were 
     normal Javascript properties and methods.</li>
   <li>Scripts can load dialogs and widgets created with Qt Designer.</li>
-  <li>Scripts can create instances of anu TQWidget subclass supported by TQWidgetFactory.</li>
-  <li>Making your own QObjects/QWidgets available for scripting is one-liner.</li>
+  <li>Scripts can create instances of anu TTQWidget subclass supported by TTQWidgetFactory.</li>
+  <li>Making your own TQObjects/TQWidgets available for scripting is one-liner.</li>
   <li>Scripts can traverse the widget tree, so your entire application can be 
     made scriptable without explicitly binding every object.</li>
 </ul>
 <h3>First Steps - The Console Dialog</h3>
-<p>The quickest way to see what KJSEmbed can do is with kjscmd, a tool for running 
+<p>The tquickest way to see what KJSEmbed can do is with kjscmd, a tool for running 
   scripts from the command line. To begin, we'll run kjscmd without any parameters 
   which brings up the KJSEmbed console dialog. The console provides an easy way 
   to run short (one line) scripts, as you can see in figure 1 the scripts have 
@@ -87,11 +87,11 @@ JSConsoleWidget (KJSEmbed::JSConsoleWidget)
 kjs> console.childCount()
 4
 kjs> console.childAt(1)
-CmdEdit (TQComboBox)
+CmdEdit (TTQComboBox)
 kjs> console.childAt(2)
-RunButton (TQPushButton)
+RunButton (TTQPushButton)
 kjs> console.child("RunButton")
-RunButton (TQPushButton)
+RunButton (TTQPushButton)
 kjs> console.child("RunButton").text = "Go!"
 Go!
 kjs> console.caption = "Different Title"
@@ -145,12 +145,12 @@ print( cmd );
 <p class="precaption">Listing 1: A Script That Displays the Grep Dialog</p>
 <p>In order to find out what the user asked us to search for we need to extract 
   the contents of the various fields in our dialog. We know that the field for 
-  entering the text to be searched for is a TQLineEdit called 'search_edit', so 
+  entering the text to be searched for is a TTQLineEdit called 'search_edit', so 
   we can use the child() method to get hold of it (this method searches through 
   the children of an object until it finds one with a matching name). Once we've 
-  found the right object getting hold of the text is easy because all QLineEdits 
+  found the right object getting hold of the text is easy because all TQLineEdits 
   make their contents available as a property called 'text'. The code that gets 
-  the value of the check boxes is almost identical, except that these are QCheckBoxes 
+  the value of the check boxes is almost identical, except that these are TQCheckBoxes 
   so it's the 'checked' property we're interested in.</p>
 <p align="center"><img src="grepdlg.png" alt="Grep Dialog Screenshot" width="327" height="241"></p>
 <p class="imgcaption">Figure 3: The Grep Dialog</p>