Difference between revisions of "Slicer3:Loadable Modules:Status"

From Slicer Wiki
Jump to: navigation, search
Line 1: Line 1:
 +
[[Slicer3:Loadable_Modules:Status_2009-01-20]]
 +
 +
Status - updated 2009-03-30
 +
 +
== Overview ==
  
[[Slicer3:Loadable_Modules:Status_2009-01-20]]
+
* Implementation
 +
** Run slicer
 +
** View->Module Search
 +
*** Wizard searches http://ext.slicer.org/ext/...
 +
**** Subdirectories define which version of slicer they contents are built against.
 +
***** first level named based on svn directory of Slicer3 (i.e. trunk/ branches/Slicer-3-2 ...)
 +
***** next level contains svn revision number and build platform
 +
***** Module names encode cvs/svn version, build date, and platform:
 +
****** e.g. BubbleMaker-cvs2009-03-30-2009-03-30-darwin-x86.zip (cvs version from March 30, 2009 built on March 30, 2009 for darwin x86)
 +
****** ExampleLoadableGuiLessModule-svn31-2009-03-30-darwin-x86.zip (svn version 31 built on March 30, 2009 for darwin x86)
 +
*** Archived of precompiled shared libraries (platform specific)
 +
** Select modules
 +
*** TODO: wizard checks for newer versions of existing modules (later: give user option of always checking during slicer boot)
 +
*** TODO: wizard grabs .s3ext file (uploaded by the extend script)
 +
*** TODO: add Category, Description, Homepage to .s3ext file (SP)
 +
*** TODO: make home page hot linked
 +
*** TODO: support python and tcl scripted modules and make examples in nitrc
 +
*** TODO: make dependencies in .s3ext (SP) Update to manifest like [[Slicer3:Loadable_Modules]]
 +
*** TODO: make 'logic-only' modules (essentially just a shared library of classes)
 +
** Modules are downloaded and unpacked into user-specific Slicer install cache directory
 +
** Restart Slicer
 +
** Can remove modules
 +
 
 +
* Developer
 +
** make slicer build tree locally
 +
** create module from a template (GUI, Logic, MRML) see NITRC example modules
 +
** test locally on their platform
 +
** create .s3ext file and test with slicer's extend script
 +
***      specify: svn/cvs repository, dependencies, homepage...
 +
*** Commit .s3ext file or ask a slicer developer to do so
 +
** Nightly build gets uploaded to ext.slicer.org
 +
 
 +
* Phase 1: (finished) [[Slicer3:Loadable_Modules:Phase1|Slicer internals]]
 +
** runtime module discovery
 +
** module template
 +
** like CommandLineModuleFactory
 +
 
 +
* Phase 2: (in process) web development, deployment
 +
** prototype on wiki
 +
** versions, download,
 +
** upload

Revision as of 12:04, 30 March 2009

Home < Slicer3:Loadable Modules:Status

Slicer3:Loadable_Modules:Status_2009-01-20

Status - updated 2009-03-30

Overview

  • Implementation
    • Run slicer
    • View->Module Search
      • Wizard searches http://ext.slicer.org/ext/...
        • Subdirectories define which version of slicer they contents are built against.
          • first level named based on svn directory of Slicer3 (i.e. trunk/ branches/Slicer-3-2 ...)
          • next level contains svn revision number and build platform
          • Module names encode cvs/svn version, build date, and platform:
            • e.g. BubbleMaker-cvs2009-03-30-2009-03-30-darwin-x86.zip (cvs version from March 30, 2009 built on March 30, 2009 for darwin x86)
            • ExampleLoadableGuiLessModule-svn31-2009-03-30-darwin-x86.zip (svn version 31 built on March 30, 2009 for darwin x86)
      • Archived of precompiled shared libraries (platform specific)
    • Select modules
      • TODO: wizard checks for newer versions of existing modules (later: give user option of always checking during slicer boot)
      • TODO: wizard grabs .s3ext file (uploaded by the extend script)
      • TODO: add Category, Description, Homepage to .s3ext file (SP)
      • TODO: make home page hot linked
      • TODO: support python and tcl scripted modules and make examples in nitrc
      • TODO: make dependencies in .s3ext (SP) Update to manifest like Slicer3:Loadable_Modules
      • TODO: make 'logic-only' modules (essentially just a shared library of classes)
    • Modules are downloaded and unpacked into user-specific Slicer install cache directory
    • Restart Slicer
    • Can remove modules
  • Developer
    • make slicer build tree locally
    • create module from a template (GUI, Logic, MRML) see NITRC example modules
    • test locally on their platform
    • create .s3ext file and test with slicer's extend script
      • specify: svn/cvs repository, dependencies, homepage...
      • Commit .s3ext file or ask a slicer developer to do so
    • Nightly build gets uploaded to ext.slicer.org
  • Phase 1: (finished) Slicer internals
    • runtime module discovery
    • module template
    • like CommandLineModuleFactory
  • Phase 2: (in process) web development, deployment
    • prototype on wiki
    • versions, download,
    • upload