diff options
Diffstat (limited to 'lib/interfaces/external/Mainpage.dox')
| -rw-r--r-- | lib/interfaces/external/Mainpage.dox | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lib/interfaces/external/Mainpage.dox b/lib/interfaces/external/Mainpage.dox index 4618c3d5..8b91bf8c 100644 --- a/lib/interfaces/external/Mainpage.dox +++ b/lib/interfaces/external/Mainpage.dox @@ -10,14 +10,14 @@ GUI Designer integration framework. \section designerintegration Overview of GUI designer integration process Each KPart that wants to act as a GUI Designer must implement @ref KInterfaceDesigner::Designer -interface. It defines necessary signals to communicate with an IDE and abstract virtual +interface. It defines necessary Q_SIGNALS to communicate with an IDE and abstract virtual functions to determine designer type. If a part which can "design" user interface files of a certain mimetype implements this interface and sets itself as a default handler for that mimetype then it becomes automatically integrated into KDevelop IDE. -When a part is embedded into KDevelop shell, its signals (defined in @ref +When a part is embedded into KDevelop shell, its Q_SIGNALS (defined in @ref KInterfaceDesigner::Designer interface): @code void addedFunction(DesignerType type, const QString &formName, Function function) @@ -26,7 +26,7 @@ KInterfaceDesigner::Designer interface): void editFunction(DesignerType type, const QString &formName, const QString &functionName) void editSource(DesignerType type, const QString &formName); @endcode -are connected to corresponding slots of KDevelop designer integration engine which can be implemented in KDevelop language support plugin. +are connected to corresponding Q_SLOTS of KDevelop designer integration engine which can be implemented in KDevelop language support plugin. Each language support which wants to use integrated designer, must reimplement @code |