summaryrefslogtreecommitdiffstats
path: root/doc/html/plugins-howto.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/plugins-howto.html')
-rw-r--r--doc/html/plugins-howto.html12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/html/plugins-howto.html b/doc/html/plugins-howto.html
index 320c694f3..62f7d6bbd 100644
--- a/doc/html/plugins-howto.html
+++ b/doc/html/plugins-howto.html
@@ -52,7 +52,7 @@ by default in the standard plugin directory.
<td valign="top"><a href="tqsqldriverplugin.html">TQSqlDriverPlugin</a>
<td valign="top"><tt>pluginsbase/sqldrivers</tt> <sup>*</sup>
<tr bgcolor="#f0f0f0">
-<td valign="top"><a href="ntqstyleplugin.html">TQStylePlugin</a>
+<td valign="top"><a href="tqstyleplugin.html">TQStylePlugin</a>
<td valign="top"><tt>pluginsbase/styles</tt> <sup>*</sup>
<tr bgcolor="#d0d0d0">
<td valign="top"><a href="tqtextcodecplugin.html">TQTextCodecPlugin</a>
@@ -73,7 +73,7 @@ set your own path or paths you can use
<p> Suppose that you have a new style class called 'MyStyle' that you want
to make available as a plugin. The required code is straightforward:
<pre>
- class MyStylePlugin : public <a href="ntqstyleplugin.html">TQStylePlugin</a>
+ class MyStylePlugin : public <a href="tqstyleplugin.html">TQStylePlugin</a>
{
public:
MyStylePlugin() {}
@@ -83,7 +83,7 @@ to make available as a plugin. The required code is straightforward:
return TQStringList() &lt;&lt; "mystyle";
}
- <a href="ntqstyle.html">TQStyle</a>* create( const <a href="tqstring.html">TQString</a>&amp; key ) {
+ <a href="tqstyle.html">TQStyle</a>* create( const <a href="tqstring.html">TQString</a>&amp; key ) {
if ( key == "mystyle" )
return new MyStyle;
return 0;
@@ -93,7 +93,7 @@ to make available as a plugin. The required code is straightforward:
TQ_EXPORT_PLUGIN( MyStylePlugin )
</pre>
-<p> (Note that <a href="ntqstylefactory.html">TQStyleFactory</a> is case-insensitive, and the lower case
+<p> (Note that <a href="tqstylefactory.html">TQStyleFactory</a> is case-insensitive, and the lower case
version of the key is used; other factories, e.g. <a href="tqwidgetfactory.html">TQWidgetFactory</a>, are
case sensitive.)
<p> The constructor and destructor do not need to do anything, so are left
@@ -102,7 +102,7 @@ The first is keys() which returns a string list of the classes
implemented in the plugin. (We've just implemented one class in the
example above.) The second is a function that returns an object of the
required class (or 0 if the plugin is asked to create an object of a
-class that it doesn't implement). For <a href="ntqstyleplugin.html">TQStylePlugin</a>, this second
+class that it doesn't implement). For <a href="tqstyleplugin.html">TQStylePlugin</a>, this second
function is called create().
<p> It is possible to implement any number of plugin subclasses in a
single plugin, providing they are all derived from the same base
@@ -112,7 +112,7 @@ no explicit object creation is required. TQt will find and create them
as required. Styles are an exception, since you might want to set a
style explicitly in code. To apply a style, use code like this:
<pre>
- TQApplication::<a href="ntqapplication.html#setStyle">setStyle</a>( TQStyleFactory::<a href="ntqstylefactory.html#create">create</a>( "MyStyle" ) );
+ TQApplication::<a href="ntqapplication.html#setStyle">setStyle</a>( TQStyleFactory::<a href="tqstylefactory.html#create">create</a>( "MyStyle" ) );
</pre>
<p> Some plugin classes require additional functions to be implemented.