Difference between revisions of "Developer Meetings/20170314"

From Slicer Wiki
Jump to: navigation, search
(Created page with "<br> {{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit t...")
 
Line 8: Line 8:
  
 
= To Discuss =
 
= To Discuss =
* Maintenance of module and extension documentation. See http://slicer-devel.65872.n3.nabble.com/Module-list-in-documentation-not-updated-tt4038225.html
+
 
 +
Maintenance of module and extension documentation. See http://slicer-devel.65872.n3.nabble.com/Module-list-in-documentation-not-updated-tt4038225.html
 +
 
 +
Currently, the script [https://github.com/Slicer/slicer-wiki-scripts/blob/master/slicer_wiki_extension_module_listing.py slicer_wiki_extension_module_listing.py] is used to automatically create the listing of Slicer modules and extensions available on the Slicer wiki user documentation.
 +
 
 +
The creation of the listing is a two-step process:
 +
 
 +
* Step 1: On each factory (Linux, MacOSX, Windows):
 +
** the list of modules built in every extension is generated
 +
** Slicer is started to find out which modules can be loaded successfully into Slicer, the list of modules (as associated metadata) is then published into a github repository: https://github.com/Slicer/slicer-packages-metadata
 +
 
 +
* Step 2: Creation of consolidated listing of modules and extensions by downloading the metadata generated in the previous step and downloading the associated list of extension description files.

Revision as of 13:49, 14 March 2017

Home < Developer Meetings < 20170314



To Discuss

Maintenance of module and extension documentation. See http://slicer-devel.65872.n3.nabble.com/Module-list-in-documentation-not-updated-tt4038225.html

Currently, the script slicer_wiki_extension_module_listing.py is used to automatically create the listing of Slicer modules and extensions available on the Slicer wiki user documentation.

The creation of the listing is a two-step process:

  • Step 1: On each factory (Linux, MacOSX, Windows):
    • the list of modules built in every extension is generated
    • Slicer is started to find out which modules can be loaded successfully into Slicer, the list of modules (as associated metadata) is then published into a github repository: https://github.com/Slicer/slicer-packages-metadata
  • Step 2: Creation of consolidated listing of modules and extensions by downloading the metadata generated in the previous step and downloading the associated list of extension description files.