On Thu, 2009-03-05 at 11:13 +0000, Samuel Silva wrote: > Hello! > > I am trying to develop new tools (or customized versions of those > available in MITK) and got into a problem: > > I do not want to register my tool in the usual place in > CoreObjectFactory's constructor because I do not want to always have to > recompile the library for each change I do to the code. (Or for each new > tool I experiment with!). > > My first guess was that I could just get the CoreObjectFactory instance > at any place on my code and then register the tool. From that moment on, > any ToolManager would include the new tool. I did something like this in > the SampleApp constructor:
Hi Samuel, we explicitly planned a possibility to add new tools without touching the MITK libs. Please have a look at http://docs.mitk.org/nightly/toolextensions.html for an explanation. In the MITK source code, at QApplications/ToolExtensionsExample you'll find a source code example for a tool (including some minimal GUI) that does nothing useful but demonstrates the idea. If you have more questions, I'm happy to help you. Kind regards Daniel -- Dipl.-Inform. Med. Daniel Maleike Phone: +49 6221 42 2326 Deutsches Krebsforschungszentrum Im Neuenheimer Feld 280 Medical and Biological Informatics (E130) 69120 Heidelberg ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
