diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/kdearch/index.docbook | 40 | ||||
| -rw-r--r-- | doc/tde_app_devel/index.docbook | 16 | ||||
| -rw-r--r-- | doc/tdevelop/setup.docbook | 3 |
3 files changed, 29 insertions, 30 deletions
diff --git a/doc/kdearch/index.docbook b/doc/kdearch/index.docbook index fc21e33a..517d90b0 100644 --- a/doc/kdearch/index.docbook +++ b/doc/kdearch/index.docbook @@ -116,7 +116,7 @@ Initializes and controls a KDE application. </formalpara></listitem> <listitem><formalpara> -<title><ulink url="kdeapi:tdecore/KUniqueApplication">KUniqueApplication</ulink></title> +<title><ulink url="kdeapi:tdecore/TDEUniqueApplication">TDEUniqueApplication</ulink></title> <para> Makes sure only one instance of an application can run simultaneously. </para> @@ -149,13 +149,13 @@ Provides access to KDE's configuration database. </para> </formalpara></listitem> -<listitem><formalpara><title><ulink url="kdeapi:tdecore/KSimpleConfig">KSimpleConfig</ulink></title> +<listitem><formalpara><title><ulink url="kdeapi:tdecore/TDESimpleConfig">TDESimpleConfig</ulink></title> <para> Access to simple, non-hierarchical configuration files. </para> </formalpara></listitem> -<listitem><formalpara><title><ulink url="kdeapi:tdecore/KDesktopFile">KDesktopFile</ulink></title> +<listitem><formalpara><title><ulink url="kdeapi:tdecore/TDEDesktopFile">TDEDesktopFile</ulink></title> <para> Access to <literal>.desktop</literal> files. </para> @@ -1420,23 +1420,23 @@ The corresponding part of the setup in C++ is: </para> <programlisting> - KStdAction::zoomIn ( this, SLOT(slotZoomIn()), actionCollection() ); - KStdAction::zoomOut ( this, SLOT(slotZoomOut()), actionCollection() ); - KStdAction::zoom ( this, SLOT(slotZoom()), actionCollection() ); + KStdAction::zoomIn ( this, TQ_SLOT(slotZoomIn()), actionCollection() ); + KStdAction::zoomOut ( this, TQ_SLOT(slotZoomOut()), actionCollection() ); + KStdAction::zoom ( this, TQ_SLOT(slotZoom()), actionCollection() ); new TDEAction ( i18n("&Half size"), ALT+Key_0, - this, SLOT(slotHalfSize()), + this, TQ_SLOT(slotHalfSize()), actionCollection(), "zoom50" ); new TDEAction ( i18n("&Normal size"), ALT+Key_1, - this, SLOT(slotDoubleSize()), + this, TQ_SLOT(slotDoubleSize()), actionCollection(), "zoom100" ); new TDEAction ( i18n("&Double size"), ALT+Key_2, - this, SLOT(slotDoubleSize()), + this, TQ_SLOT(slotDoubleSize()), actionCollection(), "zoom200" ); new TDEAction ( i18n("&Fill Screen"), ALT+Key_3, - this, SLOT(slotFillScreen()), + this, TQ_SLOT(slotFillScreen()), actionCollection(), "zoomMaxpect" ); new TDEAction ( i18n("Fullscreen &Mode"), CTRL+SHIFT+Key_F, - this, SLOT(slotFullScreen()), + this, TQ_SLOT(slotFullScreen()), actionCollection(), "fullscreen" ); </programlisting> @@ -1814,7 +1814,7 @@ class. In order to show the manual of your application, just use </para> <programlisting> -kapp->invokeHelp() +tdeApp->invokeHelp() </programlisting> <para> @@ -2097,7 +2097,7 @@ registered with DCOP and uses the running service. If it is not registered yet, KDE will start it up and wait until is registered. Thus, you can immediately send DCOP calls to the service. In such a case, the service should be implemented as a -<ulink url="kdeapi:tdecore/KUniqueApplication.html">KUniqueApplication</ulink>. +<ulink url="kdeapi:tdecore/TDEUniqueApplication.html">TDEUniqueApplication</ulink>. </para> <para> @@ -2139,7 +2139,7 @@ class: </para> <programlisting> -DCOPClient *client = kapp->dcopClient(); +DCOPClient *client = tdeApp->dcopClient(); client->attach(); if (!client->isApplicationRegistered("tdeio_uiserver")) { TQString error; @@ -2409,8 +2409,8 @@ void FooClass::findType() { KURL url("http://developer.kde.org/favicon.ico"); TDEIO::MimetypeJob *job = TDEIO::mimetype(url); - connect( job, SIGNAL(result(TDEIO::Job*)), - this, SLOT(mimeResult(TDEIO::Job*)) ); + connect( job, TQ_SIGNAL(result(TDEIO::Job*)), + this, TQ_SLOT(mimeResult(TDEIO::Job*)) ); } void FooClass::mimeResult(TDEIO::Job *job) @@ -2603,8 +2603,8 @@ deletes itself. Thus, a typical use case will look like this: void FooClass::makeDirectory() { SimpleJob *job = TDEIO::mkdir(KURL("file:/home/bernd/tdeiodir")); - connect( job, SIGNAL(result(TDEIO::Job*)), - this, SLOT(mkdirResult(TDEIO::Job*)) ); + connect( job, TQ_SIGNAL(result(TDEIO::Job*)), + this, TQ_SLOT(mkdirResult(TDEIO::Job*)) ); } void FooClass::mkdirResult(TDEIO::Job *job) @@ -2942,8 +2942,8 @@ void FooClass::printModifiedDate() { KURL url("http://developer.kde.org/documentation/kde2arch/index.html"); TDEIO::TransferJob *job = TDEIO::get(url, true, false); - connect( job, SIGNAL(result(TDEIO::Job*)), - this, SLOT(transferResult(TDEIO::Job*)) ); + connect( job, TQ_SIGNAL(result(TDEIO::Job*)), + this, TQ_SLOT(transferResult(TDEIO::Job*)) ); } void FooClass::transferResult(TDEIO::Job *job) diff --git a/doc/tde_app_devel/index.docbook b/doc/tde_app_devel/index.docbook index 4ab2cd22..32a16a42 100644 --- a/doc/tde_app_devel/index.docbook +++ b/doc/tde_app_devel/index.docbook @@ -479,7 +479,7 @@ hello.resize( 100, 30 ); a.setMainWidget( &hello ); -TQObject::connect(&hello, SIGNAL( clicked() ), &a, SLOT( quit() )); +TQObject::connect(&hello, TQ_SIGNAL( clicked() ), &a, TQ_SLOT( quit() )); hello.show(); return a.exec(); @@ -488,7 +488,7 @@ return a.exec(); </para> <para> You see, the only addition to give the button more interaction is to use a <methodname>connect() -</methodname> method: <methodname>connect(&hello, SIGNAL( clicked() ), &a, SLOT( quit() ))</methodname>; +</methodname> method: <methodname>connect(&hello, TQ_SIGNAL( clicked() ), &a, TQ_SLOT( quit() ))</methodname>; is all you have to add. What is the meaning now? The class declaration of TQObject says about the <methodname>connect()</methodname> method: </para> @@ -573,7 +573,7 @@ hello.resize( 100, 30 ); a.setTopWidget( &hello ); -TQObject::connect(&hello, SIGNAL( clicked() ), &a, SLOT( quit() )); +TQObject::connect(&hello, TQ_SIGNAL( clicked() ), &a, TQ_SLOT( quit() )); hello.show(); return a.exec(); @@ -924,10 +924,10 @@ Let's have a look at the constructor and see how this instance is called 16 statusBar()->show(); 17 18 // allow the view to change the statusbar and caption -19 connect(m_view, SIGNAL(signalChangeStatusbar(const TQString&)), -20 this, SLOT(changeStatusbar(const TQString&))); -21 connect(m_view, SIGNAL(signalChangeCaption(const TQString&)), -22 this, SLOT(changeCaption(const TQString&))); +19 connect(m_view, TQ_SIGNAL(signalChangeStatusbar(const TQString&)), +20 this, TQ_SLOT(changeStatusbar(const TQString&))); +21 connect(m_view, TQ_SIGNAL(signalChangeCaption(const TQString&)), +22 this, TQ_SLOT(changeCaption(const TQString&))); 23 24 } </programlisting> @@ -1276,7 +1276,7 @@ As an example, we have a look at the "New File" button in a generic application: </para> <para> There, the part i18n("New File") provides a tool-tip message. It is enclosed by the i18n() -macro provided by kapp.h to translate the tool-tip towards the currently selected language. +macro provided by tdeapplication.h to translate the tool-tip towards the currently selected language. </para> <para> Tool-tips can also be added to any custom widget by using the <classname>QToolTip</classname> diff --git a/doc/tdevelop/setup.docbook b/doc/tdevelop/setup.docbook index 0c078a3b..6f217c27 100644 --- a/doc/tdevelop/setup.docbook +++ b/doc/tdevelop/setup.docbook @@ -344,8 +344,7 @@ A typical example of this user interface mode is KDEStudio, our friend C++-IDE i <listitem><para> <link linkend="toplevel-desc">Toplevel window mode</link> </para><para>All editor, browser and tool views will be toplevel windows (directly on desktop). -The main widget contains the menu, toolbars and statusbar only. -A typical example of this user interface mode is Borland Delphi 6.0.</para></listitem> +The main widget contains the menu, toolbars and statusbar only.</para></listitem> </itemizedlist> <para> |