Difference between revisions of "Slicer3:Loadable Modules"
From Slicer Wiki
Line 21: | Line 21: | ||
ExampleModule1,homepage {http:example1.com} | ExampleModule1,homepage {http:example1.com} | ||
ExampleModule1,binaryURL {http:example1.com/bin} | ExampleModule1,binaryURL {http:example1.com/bin} | ||
− | ExampleModule1,build {darwin-x86-2008-12-25} | + | ExampleModule1,build {darwin-x86-2008-12-25} |
− | + | # here's a comment | |
ExampleModule2,name {Second Example Loadable Module} | ExampleModule2,name {Second Example Loadable Module} | ||
ExampleModule2,category {Example} | ExampleModule2,category {Example} |
Revision as of 21:11, 9 December 2008
Home < Slicer3:Loadable ModulesIntroduction
This feature allows Slicer3 modules to be detected and loaded at run-time. This enables module binaries to be added to Slicer3 without having to be compiled and linked with the main binary.
Module authors should create their modules based on templates like the GAD Module found in the Slicer3 Modules/ subdirectory. There will be a future version of Slicer3 that allows users to download and use modules from an online module archive.
For information on how to make your module loadable: Slicer3:Loadable_Modules:HOWTO
Loadable modules in Slicer3: Slicer3:Loadable_Modules:Current
For Developers
Slicer3:Loadable_Modules:Working_Plans
The manifest file to describe downloadable modules:
ExampleModule1,name {Example Loadable Module1} ExampleModule1,category {Example} ExampleModule1,description {This is our first example} ExampleModule1,homepage {http:example1.com} ExampleModule1,binaryURL {http:example1.com/bin} ExampleModule1,build {darwin-x86-2008-12-25} # here's a comment ExampleModule2,name {Second Example Loadable Module} ExampleModule2,category {Example} ExampleModule2,description {This is our second example} ExampleModule2,homepage {http:example2.com} ExampleModule2,binaryURL {http:example2.com/bin} ExampleModule2,build {darwin-x86-2008-12-25}