Inter plugin communication
Andras Mantia
amantia at kde.org
Fri May 20 12:24:04 UTC 2005
Hi,
I'm having some problems with KDevelop interfaces. ;-) The main problem
is that I don't know how can I communicate between two plugins. Here
are two examples:
1) Let's have a global plugin called A which wants to print out some
text to a message view. We have plugin B, which is a message-view
plugin who is able to process some text and print it out in a nice
form. Plugins A and B are completely independent, plugin A should
compile without plugin B being present and vice versa.
Taking the above into the account, how can:
- plugin A send some data to plugin B?
- plugin A request the showing of the main widget of plugin B?
I'm afraid this won't work without creating another KDevelop interface
for "message-view" style plugins, am I right?
If it is so, I think we will need this and possibly more such
interfaces. Am I allowed to add those to the platform?
2) The same plugin A wants to send some data to a languagesupport
plugin. How can this be done? I mean the data might be processed
differently depending on what part is active (editor, VPL widget, HTML
widget) and it might depend also on the type of the language/project
(C++, Quanta, whatever).
This is about executing a user action. A user action can output some
text which can be:
- inserted as-is in the currently edited document
- as HTML in our VPL widget
- inserted in the currently edited document, but further steps made
(like bringing up a dialog to edit the inserted tag).
It is clear that it is not wise to do all the above stuff in plugin A
(the user toolbars) as this way the plugin will not be a generic one.
Any idea how to solve it?
Andras
--
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20050520/de449526/attachment.sig>
More information about the KDevelop-devel
mailing list