Hi there, can someone remind me (I’m getting old..or older at least), why the CTK plugins used in MITK are not just like the normal Qt plugins (image formats, databases etc), and why they therefore require a provisioning file to load.
It seems that the MITK Autoloaded Modules are great for having nicely extensible functionality, with no link-time dependency, where people could just add drop in modules etc.. But would it be possible to do the same for plugins? Im wondering if it would be possible to provide a pre-compiled GUI application, and the user just creates a standalone project for each new plugin that they can deploy to their app, much like new Osirix plugins, (or Mevis I think). Just a thought. Thanks M ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
