Hi,
On 08/02/2010 01:31 PM, Michael Xanadu wrote:
Hi Sascha,
I don't quite understand what you mean here. Even with the old
"Functionality" concept, you had to use some framework classes to
build your own application in order to manage the functionalities.
I just thought - maybe there's a possibility to merge a
blueberry-plugin with the old functionality concept to integrate that
plugin easier in my own apllication.
The two differ too much in their design. I don't see a way how to do it...
There is no tutorial explaining how to use MITK Plugins in
applications which do not use the BlueBerry workbench because this
is just not possible.
You may want to consider using the BlueBerry workbench and to
integrate your own post-processing code as a plugin. This way you
could easily benefit from other MITK Plugins.
The "SlicedBaseSegmentation" plugin, which is called
"org.mitk.gui.qt.segmentation" in the current code base is an
example of a more complex plugin which can not be used outside of
BlueBerry.
The idea of using the BlueBerry workbench and to integrate my own
plugin already crossed my mind, too. We think that it would be a nice
Plan B.
To summarize: The only possibility to integrate a plugin in my own
application would be to implement the architecture of Blueberry
workbench in my application (reverse engineering)? How extensive would
it be?
Just to make things clear, the Blueberry workbench is a GUI container
for plug-ins providing user interface contributions. As such, the
workbench itself manages the main window and orchestrates the so called
"views" and "editors" contributed by plug-ins. Hence I think the
approach of "implementing the BlueBerry workbench architecture in your
own application" will not work. To effectively integrate your
functionality and make it compatible with existing MITK plug-ins, the
only way right now is to use the Blueberry workbench and restructure
your code into BlueBerry plugins (bundles). Then starting the workbench
is as easy as calling:
int main(int argc, char** argv)
{
Poco::Util::MapConfiguration* coreConfig(new Poco::Util::MapConfiguration());
coreConfig->setString(berry::Platform::ARG_APPLICATION,
"org.mitk.qt.application");
return berry::Starter::Run(argc, argv, coreConfig);
}
See for example the code created with the BundleGenerator:
http://docs.mitk.org/nightly-qt4/NewPluginPage.html if you supply a
value for the variable "CUSTOM_PROJECT_NAME".
Best,
Sascha
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
