summaryrefslogtreecommitdiffstats
path: root/doc/html/templates.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/templates.html')
-rw-r--r--doc/html/templates.html14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/html/templates.html b/doc/html/templates.html
index 624f1208f..41371c5d8 100644
--- a/doc/html/templates.html
+++ b/doc/html/templates.html
@@ -59,15 +59,15 @@ the signals are protected in the sense of protected C++ member
functions. This helps programmers get their design right from the very
beginning, without even having to think about design patterns.
<p> <h3>2. Precompilers are good</h3>
-<p> TQt's <tt><a href="moc.html#moc">moc</a></tt> (Meta Object Compiler) provides a clean way to go
+<p> TQt's <tt><a href="tqmoc.html#tqmoc">tqmoc</a></tt> (Meta Object Compiler) provides a clean way to go
beyond the compiled language's facilities. It does so by generating
additional C++ code which can be compiled by any standard C++ compiler.
-The <tt>moc</tt> reads C++ source files. If it finds one or more class
+<tt>TQMoc</tt> reads C++ source files. If it finds one or more class
declarations that contain the "TQ_OBJECT" macro, it produces another C++
source file which contains the meta object code for those classes. The
-C++ source file generated by the <tt>moc</tt> must be compiled and
+C++ source file generated by <tt>tqmoc</tt> must be compiled and
linked with the implementation of the class (or it can be
-<tt>#included</tt> into the class's source file). Typically <tt>moc</tt>
+<tt>#included</tt> into the class's source file). Typically <tt>tqmoc</tt>
is not called manually, but automatically by the build system, so it
requires no additional effort by the programmer.
<p> There are other precompilers, for example, <tt>rpc</tt> and
@@ -94,7 +94,7 @@ object model is a clear disadvantage over the dynamic messaging approach
of Objective C when it comes to component-based graphical user interface
programming. What's good for a high end database server or an operating
system isn't necessarily the right design choice for a GUI frontend.
-With <tt>moc</tt>, we have turned this disadvantage into an advantage,
+With <tt>tqmoc</tt>, we have turned this disadvantage into an advantage,
and added the flexibility required to meet the challenge of safe and
efficient graphical user interface programming.
<p> Our approach goes far beyond anything you can do with templates. For
@@ -146,7 +146,7 @@ to use a signal to indicate that the requested data arrived. But if you
need to send out every single byte one by one to a consumer, use a
listener interface rather than signals and slots.
<p> <h3>5. No limits</h3>
-<p> Because we had the <tt>moc</tt> for signals and slots, we could add
+<p> Because we had <tt>tqmoc</tt> for signals and slots, we could add
other useful things to it that could not not be done with templates.
Among these are scoped translations via a generated <tt>tr()</tt>
function, and an advanced property system with introspection and
@@ -154,7 +154,7 @@ extended runtime type information. The property system alone is a great
advantage: a powerful and generic user interface design tool like TQt
Designer would be a lot harder to write - if not impossible - without a
powerful and introspective property system.
-<p> C++ with the <tt>moc</tt> preprocessor essentially gives us the
+<p> C++ with <tt>tqmoc</tt> preprocessor essentially gives us the
flexibility of Objective-C or of a Java Runtime Environment, while
maintaining C++'s unique performance and scalability advantages. It is
what makes TQt the flexible and comfortable tool we have today.