I was looking at
http://www.slicer.org/slicerWiki/index.php/Documentation/4.2#Cat_1
and at the mac stable version, 4.2.2-1

Jim 30/12/2012> I think the wiki ends up with extensions that are "under development".

We should make an official "under development" section on the wiki page to capture these. The rest of the wiki page should be made to mirror the extension manager.

Jc, any way we could have the list of extensions on the wiki be generated nightly by the list of extensions in the source tree?

Ron - 30/12/2012: Hi,

So the documentation could be started on the wiki and then migrated to the extension?

As an aside, there is still the issue that we need two types of documentation:
-"advertisement" showing up in the extension manager and telling potential users what the extension is good for
-"reference manual" explaining how to use the extension and the meaning and use of the different parameters.

As a non-developer, it is not clear to me where the end user can find this two type of documentation.

Jc - 07/01/2013: Hi Jim, Ron,

These are very good idea. We should discuss this during the week and make some plan. Make later this afternoon ?

Jim> To answer more specifically your question "any way we could have the list of extensions on the wiki be generated nightly by the list of extensions in the source tree?"

• Currently extension are not explicitly listed has category 1, 2 or 3. It should either be specified in the extension description file or specified externally. Assuming, there is a mechanism to know to which category an extension belong, the idea would be to generate a wiki page on a nightly basis and update the wiki.

Thanks
Jc

@Ron: I have now a script to automatically generate the listing, here is a preview:

http://wiki.slicer.org/slicerWiki/index.php/User:UpdateBot/Issue-2843-Consolidated-Extension-List

The idea would be to have the listing automatically generated and the wiki page automatically updated.

I would like to generalize the automatic generation to the list of modules, it doesn't make sense to maintain the list by hand.

Finally, I want to extend the extension description file so that extension developer specify the list of modules bundled in their extensions. That way we could have section like:

Modules by Category: List all module categories independently of their provenance (Slicer core, or extensions)

It doesnt really make sense to decouple both listing (core vs extension module)

Please see Steve P. comment in issue 0002033, 0004399
Taking a user centric vantage point:
-it is important whether a module ships with the initial download or whether I need to go to the extension manager and download it after the initial installation.
-We accept more responsibility for the initial download. Extensions are more of the don't blame us... variety.

This is addressed by the automatic generation of extension and module listing now in place.

Problems specific to the new listing are captured in specific issues.