|
|
|
|
@ -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 Q_SIGNALS to communicate with an IDE and abstract virtual
|
|
|
|
|
interface. It defines necessary 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 TDevelop IDE.
|
|
|
|
|
|
|
|
|
|
When a part is embedded into TDevelop shell, its Q_SIGNALS (defined in @ref
|
|
|
|
|
When a part is embedded into TDevelop shell, its signals (defined in @ref
|
|
|
|
|
KInterfaceDesigner::Designer interface):
|
|
|
|
|
@code
|
|
|
|
|
void addedFunction(DesignerType type, const TQString &formName, Function function)
|
|
|
|
|
@ -26,7 +26,7 @@ KInterfaceDesigner::Designer interface):
|
|
|
|
|
void editFunction(DesignerType type, const TQString &formName, const TQString &functionName)
|
|
|
|
|
void editSource(DesignerType type, const TQString &formName);
|
|
|
|
|
@endcode
|
|
|
|
|
are connected to corresponding Q_SLOTS of TDevelop designer integration engine which can be implemented in TDevelop language support plugin.
|
|
|
|
|
are connected to corresponding slots of TDevelop designer integration engine which can be implemented in TDevelop language support plugin.
|
|
|
|
|
|
|
|
|
|
Each language support which wants to use integrated designer, must reimplement
|
|
|
|
|
@code
|
|
|
|
|
|
