Proposals::Plugin IO mechanisms: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
Basic idea is to have the RegisterDefaultFactories look in some plugin directory for dlls. Load all dlls in the plugin directory and call some standard entry point. Entry point implementation would call RegisterFactory() for the ImageIO types in that dll. | Basic idea is to have the RegisterDefaultFactories look in some plugin directory for dlls. Load all dlls in the plugin directory and call some standard entry point. Entry point implementation would call RegisterFactory() for the ImageIO types in that dll. | ||
{{ITK/Template/Footer}} | |||
Latest revision as of 20:38, 20 December 2005
Plugin IO mechanism
I propose we add a mechanism so that ImageIO dlls can be added to some sort of plugin directory and loaded by the RegisterDefaultFactories. This will allow ITK-based projects that have their own ImageIO classes to run existing ITK compiled executables without editing the code for those executables.
Basic idea is to have the RegisterDefaultFactories look in some plugin directory for dlls. Load all dlls in the plugin directory and call some standard entry point. Entry point implementation would call RegisterFactory() for the ImageIO types in that dll.
