diff options
Diffstat (limited to 'doc/api')
| -rw-r--r-- | doc/api/HowToAddPlugins.dox | 6 | ||||
| -rw-r--r-- | doc/api/HowToAddProgrammingLanguages.dox | 8 | ||||
| -rw-r--r-- | doc/api/PropEditor.dox | 4 |
3 files changed, 9 insertions, 9 deletions
diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox index 3f9d1b20..e40840a8 100644 --- a/doc/api/HowToAddPlugins.dox +++ b/doc/api/HowToAddPlugins.dox @@ -85,7 +85,7 @@ Your part must be derived from <code>KDevPlugin</code>. - KDevPlugin takes two arguments: - 1) A <i>parent</i> argument. This also comes from <code>createPartObject()</code>. - - 2) A <i>name</i>, which in turn is given to the <code>QObject</code> + - 2) A <i>name</i>, which in turn is given to the <code>TQObject</code> constructor. . . @@ -134,7 +134,7 @@ rooted in the <code>dom</code> document node. For example, the <code>autoproject</code> part uses the statement <code><pre> - QString cflags = DomUtil::readEntry( *part->document(), + TQString cflags = DomUtil::readEntry( *part->document(), "/kdevautoproject/cflags" ); </pre></code> @@ -181,7 +181,7 @@ void GDBBreakpointWidget::savePartialProjectSession(QDomElement* el) { BreakpointTableRow* btr = (BreakpointTableRow *) m_table->item(row, Control); Breakpoint* bp = btr->breakpoint(); - QDomElement breakpointEl = domDoc.createElement("breakpoint"+QString::number(row)); + QDomElement breakpointEl = domDoc.createElement("breakpoint"+TQString::number(row)); breakpointEl.setAttribute("type", bp->type()); breakpointEl.setAttribute("location", bp->location(false)); breakpointEl.setAttribute("enabled", bp->isEnabled()); diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox index 9ef228e2..78091009 100644 --- a/doc/api/HowToAddProgrammingLanguages.dox +++ b/doc/api/HowToAddProgrammingLanguages.dox @@ -71,10 +71,10 @@ Language support can offer additional features: \subsection sectionAttributeMethodWizard Attribute/Method wizard - add method dialog: (See <code>cpp</code> or <code>java</code>) - - <code>virtual void addMethod(const QString &className);</code> + - <code>virtual void addMethod(const TQString &className);</code> . - add attribute dialog: (See <code>cpp</code> or <code>java</code>) - - <code>virtual void addAttribute(const QString &className);</code> + - <code>virtual void addAttribute(const TQString &className);</code> . . @@ -82,8 +82,8 @@ Language support can offer additional features: If there is a Qt bindings for your language and there is a possibility to use QtDesigner ui files, you could implement ui subclassing feature: - - <code>virtual QStringList subclassWidget(const QString& formName);</code> - - <code>virtual QStringList updateWidget(const QString& formName, const QString& + - <code>virtual QStringList subclassWidget(const TQString& formName);</code> + - <code>virtual QStringList updateWidget(const TQString& formName, const TQString& fileName);</code> . diff --git a/doc/api/PropEditor.dox b/doc/api/PropEditor.dox index 40ce4261..a0bd38a5 100644 --- a/doc/api/PropEditor.dox +++ b/doc/api/PropEditor.dox @@ -73,7 +73,7 @@ A simple example on how to create a property editor and use it with one property list->addProperty("My Group", new Property(String, "Second Property", "This is my second property", "Hello")); list->addProperty(new Property(Color, "Third Property", - "This is my third property", QColor("green"))); + "This is my third property", TQColor("green"))); m_editor->populateProperties(*list); \endcode @@ -88,7 +88,7 @@ More advanced example with property accessors and list intersection: list->addProperty("My Group", new Property(String, "Second Property", "This is my second property", "Hello")); list->addProperty(new Property(Color, "Third Property", - "This is my third property", QColor("green"))); + "This is my third property", TQColor("green"))); PropertyList *list2 = new PropertyList; list2->addProperty("My Group", new Property(Integer, "First Property", |