ITK/Release 4/Modularization/Goals: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
No edit summary
Line 13: Line 13:
** Package manager that allows user to choose exactly what functionality is desired
** Package manager that allows user to choose exactly what functionality is desired
** Modules exist along logical boundaries
** Modules exist along logical boundaries
* '''Thrid-party dependencies'''
** Bring outside libraries in as modules
** No more Utilities/ directory

Revision as of 17:50, 10 November 2010

Goals

The following are the goals of modularizing the toolkit:

  • Organize the continuous growth of the Toolkit
    • Create system with a kernel of base-level code and topic modules
      • Hierarchy of modules?
    • Kernel very rigorously supported and developed
    • Possibly two classes of modules: Core and Extra
    • Core modules also rigorously supported
    • Extra modules less so
  • Simplify usage for application developers
    • Package manager that allows user to choose exactly what functionality is desired
    • Modules exist along logical boundaries
  • Thrid-party dependencies
    • Bring outside libraries in as modules
    • No more Utilities/ directory