Rename utility class nt* related files to equivalent tq*

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 20 insertions, 20 deletions

diff --git a/doc/html/shclass.html b/doc/html/shclass.html
index 844d639b1..eba64fcf6 100644
--- a/doc/html/shclass.html
+++ b/doc/html/shclass.html
@@ -72,7 +72,7 @@ very fast, because it only involves setting a pointer and incrementing
 the reference count.
 <p> Object assignment (with operator=()) for implicitly and explicitly
 shared objects is implemented using shallow copies. A deep copy can be
-made by calling a copy() function or by using <a href="ntqdeepcopy.html">TQDeepCopy</a>.
+made by calling a copy() function or by using <a href="tqdeepcopy.html">TQDeepCopy</a>.
 <p> The benefit of sharing is that a program does not need to duplicate
 data unnecessarily, which results in lower memory use and less copying
 of data. Objects can easily be assigned, sent as function arguments,
@@ -82,20 +82,20 @@ Explicit sharing means that the programmer must be aware of the fact
 that objects share common data. Implicit sharing means that the
 sharing mechanism takes place behind the scenes and the programmer
 does not need to worry about it.
-<p> <h2> A <a href="qbytearray.html">TQByteArray</a> Example
+<p> <h2> A <a href="tqbytearray.html">TQByteArray</a> Example
 </h2>
 <a name="2"></a><p> TQByteArray is an example of a shared class that uses explicit sharing.
 Example:
 <pre>
                           //Line    a=         b=         c=
-    <a href="qbytearray.html">TQByteArray</a> a(3),b(2)  // 1:     {?,?,?}    {?,?}
+    <a href="tqbytearray.html">TQByteArray</a> a(3),b(2)  // 1:     {?,?,?}    {?,?}
     b[0] = 12; b[1] = 34; // 2:     {?,?,?}    {12,34}
     a = b;                // 3:     {12,34}    {12,34}
     a[1] = 56;            // 4:     {12,56}    {12,56}
-    <a href="qbytearray.html">TQByteArray</a> c = a;     // 5:     {12,56}    {12,56}    {12,56}
-    a.<a href="ntqmemarray.html#detach">detach</a>();           // 6:     {12,56}    {12,56}    {12,56}
+    <a href="tqbytearray.html">TQByteArray</a> c = a;     // 5:     {12,56}    {12,56}    {12,56}
+    a.<a href="tqmemarray.html#detach">detach</a>();           // 6:     {12,56}    {12,56}    {12,56}
     a[1] = 78;            // 7:     {12,78}    {12,56}    {12,56}
-    b = a.<a href="ntqmemarray.html#copy">copy</a>();         // 8:     {12,78}    {12,78}    {12,56}
+    b = a.<a href="tqmemarray.html#copy">copy</a>();         // 8:     {12,78}    {12,78}    {12,56}
     a[1] = 90;            // 9:     {12,90}    {12,78}    {12,56}
 </pre>
  
@@ -122,7 +122,7 @@ refer to the same data.
 <p> Implicit sharing optimizes memory use and copying of data without
 this side effect. So why didn't we implement implicit sharing for all
 shared classes? The answer is that a class that allows direct access
-to its internal data (for efficiency reasons), like <a href="qbytearray.html">TQByteArray</a>, cannot
+to its internal data (for efficiency reasons), like <a href="tqbytearray.html">TQByteArray</a>, cannot
 be implicitly shared, because it can be changed without letting
 TQByteArray know.
 <p> An implicitly shared class has total control of its internal data. In
@@ -148,23 +148,23 @@ data in all member functions that change the internal data.
 <p> This is clearly not possible for TQByteArray, because the programmer
 can do the following:
 <p> <pre>
-    <a href="qbytearray.html">TQByteArray</a> array( 10 );
-    array.<a href="ntqmemarray.html#fill">fill</a>( 'a' );
+    <a href="tqbytearray.html">TQByteArray</a> array( 10 );
+    array.<a href="tqmemarray.html#fill">fill</a>( 'a' );
     array[0] = 'f';        // will modify array
-    array.<a href="ntqmemarray.html#data">data</a>()[1] = 'i'; // will modify array
+    array.<a href="tqmemarray.html#data">data</a>()[1] = 'i'; // will modify array
 </pre>
  
-<p> If we monitor changes in a <a href="qbytearray.html">TQByteArray</a>, the TQByteArray class would
+<p> If we monitor changes in a <a href="tqbytearray.html">TQByteArray</a>, the TQByteArray class would
 become unacceptably slow.
 <p> <h2> Explicitly Shared Classes
 </h2>
-<a name="4"></a><p> All classes that are instances of the <a href="ntqmemarray.html">TQMemArray</a> template class are
+<a name="4"></a><p> All classes that are instances of the <a href="tqmemarray.html">TQMemArray</a> template class are
 explicitly shared:
 <p> <ul>
-<li> <a href="ntqbitarray.html">TQBitArray</a>
+<li> <a href="tqbitarray.html">TQBitArray</a>
 <li> <a href="ntqpointarray.html">TQPointArray</a>
-<li> <a href="qbytearray.html">TQByteArray</a>
-<li> Any other instantiation of <a href="ntqmemarray.html">TQMemArray&lt;type&gt;</a>
+<li> <a href="tqbytearray.html">TQByteArray</a>
+<li> Any other instantiation of <a href="tqmemarray.html">TQMemArray&lt;type&gt;</a>
 </ul>
 <p> These classes have a detach() function that can be called if you want
 your object to get a private copy of the shared data. They also have a
@@ -175,7 +175,7 @@ copy().
 </h2>
 <a name="5"></a><p> The TQt classes that are implicitly shared are:
 <ul>
-<li> <a href="ntqbitmap.html">TQBitmap</a>
+<li> <a href="tqbitmap.html">TQBitmap</a>
 <li> <a href="ntqbrush.html">TQBrush</a>
 <li> <a href="ntqcursor.html">TQCursor</a>
 <li> <a href="ntqfont.html">TQFont</a>
@@ -188,7 +188,7 @@ copy().
 <li> <a href="ntqpicture.html">TQPicture</a>
 <li> <a href="ntqpixmap.html">TQPixmap</a>
 <li> <a href="ntqregion.html">TQRegion</a>
-<li> <a href="ntqregexp.html">TQRegExp</a>
+<li> <a href="tqregexp.html">TQRegExp</a>
 <li> <a href="tqstring.html">TQString</a>
 <li> <a href="tqstringlist.html">TQStringList</a>
 <li> <a href="tqvaluelist.html">TQValueList</a>
@@ -220,9 +220,9 @@ also happens if anything is <a href="tqimage.html#bitBlt">bitBlt()</a>'ed into
 <a href="tqvaluevector.html">TQValueVector</a>, etc.) while you are iterating over it.
 <p> <h2> TQCString: implicit or explicit?
 </h2>
-<a name="6"></a><p> <a href="ntqcstring.html">TQCString</a> uses a mixture of implicit and explicit sharing. Functions
-inherited from <a href="qbytearray.html">TQByteArray</a>, such as data(), employ explicit sharing, while
-those only in <a href="ntqcstring.html">TQCString</a> detach automatically. Thus, TQCString is rather an
+<a name="6"></a><p> <a href="tqcstring.html">TQCString</a> uses a mixture of implicit and explicit sharing. Functions
+inherited from <a href="tqbytearray.html">TQByteArray</a>, such as data(), employ explicit sharing, while
+those only in <a href="tqcstring.html">TQCString</a> detach automatically. Thus, TQCString is rather an
 "experts only" class, provided mainly to ease porting from TQt 1.x to TQt 2.0.
 We recommend that you use <a href="tqstring.html">TQString</a>, a purely implicitly shared class.
 <p>