Title

Names

David Gobbi: Option to turn off modules for OR
Steve Pieper: Needs refactoring so it will be as flexible as Slicer 2 (runtime). Slicer 3 is cMake based (pre-compilation). I would prefer run-time dynamic. This would allow distributing modules independent of the base.
Louis Ibanez: The benefit would be a standard Slicer for everybody. How about testing?
Peter Kazanzides: It's the user's responsibility to make it sure it was tested before going to OR
David: and turn off the loading of modules at startup.
Louis: Versioning?
Steve Aylward: It's useful to have this versioning, for ex. VTK/ITK.
Steve P.: The nightly build should build the modules also, and test them together.
Csaba Csoma: So we all agree that dynamic modules is a good thing. Question: what is module, what is basic functionality?
Steve P: Base Features vs. Modules. Csaba's right, we should make for ex. Diffusion Imaging modular, because it's pretty specific.
Noby Hata: There are classes that can go only to base, like tracker?
Steve P: Theoretically we can make it generic enough. Should the concept of tracker be a base, or just the transform?
Steve A: Can a module bring in any library?
Steve P: Yes. The base can't depend on Matlab, but a module can.
Steve P: Static modules are restrictive, because you can't extend for ex. for full VTK/ITK library if you have a limited one compiled in.
S Barre: Start up time?
Steve P: Might not be affected.