Hi Nils, if I understood you correctly, you might want to consider using extension points. This is a mechanism (borrowed from Eclipse) where your "main plug-in" can declare an "extension point" and discovers all "extensions" (from other plug-ins) at runtime. Those "extensions" can contain meta data or point to executable code. An example for such an extension point is http://docs.mitk.org/nightly-qt4/BlueBerry/reference/extension-points/org_blueberry_ui_views.html it is used to discover all views at runtime and add menu entries for them in the workbench window.
For more information, you can read the Eclipse extension point articles. For example: http://wiki.eclipse.org/FAQ_What_are_extensions_and_extension_points%3F http://www.vogella.de/articles/EclipseExtensionPoint/article.html http://swtxml.com/rcpbuch/extensions/ (in German) Let me know if you have more questions. Best, Sascha On 08/13/2010 01:51 PM, Ritter, Nils wrote: > Thanks for your reply. > > What we are planning to do is to implement some kind of state machine that > uses other, previously known plug-ins (by name or id or ...). A "main > plug-in" gives an overview of the whole process and offers buttons to open > another part. Each button causes a search for a group of possible plug-ins > that are opened on demand by the program, not by the user. Whether this state > machine will be MITKs internal one or something hand-crafted is not decided > yet. By dividing the functionality of the whole program into several > plug-ins, distributed development is made easy and the GUI is kept clean. > Also by minimizing user interaction with MITK itself (the container extapp, > not the functionality of the plug-ins) we can guide the user towards his goal. > > Could you provide some example code that shows how to interact with MITK's > mechanism? Most of the examples I found up to now are pretty straight > forward. Open something, process it, save it. But there is almost no MITK > mechanism involved. > > Best regards, > Nils > > > -----Ursprüngliche Nachricht----- > Von: Sascha Zelzer [mailto:[email protected]] > Gesendet: Donnerstag, 12. August 2010 12:33 > An: [email protected] > Betreff: Re: [mitk-users] How to acces other MITK Plug-ins from > > Hi, > > there is a sophisticated API for controlling the OSGi plug-in system and > the BlueBerry workbench. For controll over the workbench, see for > example the IWorkbenchPage interface: > > http://docs.mitk.org/nightly-qt4/BlueBerry/reference/api/html/structberry_1_1IWorkbenchPage.html > > If you can give us a concrete problem description of what you want to > achieve, I may be able to help you more specifically. > > Best, > Sascha > > On 08/10/2010 09:52 PM, Ritter, Nils wrote: > >> Hi, >> I'm looking for a way to gain some control over MITKs plug-in mechanisms >> from my own plug-in. It would be very helpful for the project I'm currently >> working on, to divide functionality into several plug-ins and open or stop >> them from a main control. Also some control over the view aspects would be >> nice. Could someone point me in the right direction with this, or even >> provide some code that simply explains how to approach this problem? Thanks >> in advance. >> >> Best regards, >> Nils >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> mitk-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/mitk-users >> >> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > mitk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mitk-users > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > mitk-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mitk-users > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
