Mantis Bugtracker

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0002033 [Slicer4] Core: Documentation & Wiki feature N/A 2012-05-14 11:40 2012-08-21 13:39
Reporter kikinis View Status public  
Assigned To jcfr
Priority normal Resolution open  
Status assigned   Product Version
Summary 0002033: Mechanism to list extensions on top of Documentation page
Description Ron - May 14, 2012:
 See http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1 [^]
 How should extensions show up in the listing on top and actually be listed?
Additional Information
Tags No tags attached.
Attached Files

- Relationships

-  Notes
(0004373)
jcfr (administrator)
2012-05-14 11:48

1) From the user perspective, the fact a given module is delivered through the "extensions manager" could be considered an "implementation details". If probably means that at the top of the page "Modules category" could remain as it is. We could also think about changing it into "Modules or Extensions cateogory"

2) After clicking on a category, the user would be able to see the associated module and click on the documentation of a given module.

3) The concept of "provenance" or "delivery mechanism" could be associated with a module. In case of a module belonging to an extension, it should be possible to click on the associated extension description page.

4) I also believe the list of modules display at the top of [1] should be generated automatically.

5) It should probably be possible to filter this list by module "provenance": "built-in" or "extensions"

[1] http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1 [^]
(0004399)
pieper (administrator)
2012-05-15 13:13

A key thing about extensions is making it clear to the user where the extension comes from. From that perspective there are two kinds:

Kind A: ones that the slicer developers offer as optional downloads, either because they are large or overly specialized

Kind B: ones that are provided and supported by third parties.

I like the idea of letting the B extensions leverage all our infrastructure but we need to make clear where users need to go with questions (and where to give credit).

- Issue History
Date Modified Username Field Change
2012-05-14 11:40 jcfr New Issue
2012-05-14 11:40 jcfr Status new => assigned
2012-05-14 11:40 jcfr Assigned To => jcfr
2012-05-14 11:41 jcfr Reporter jcfr => kikinis
2012-05-14 11:41 jcfr Summary Mechanism to list extension on top of Documentation page => Mechanism to list extensions on top of Documentation page
2012-05-14 11:41 jcfr Severity minor => feature
2012-05-14 11:41 jcfr Reproducibility have not tried => N/A
2012-05-14 11:41 jcfr Target Version => Slicer 4.2.0 AHM Summer 2012
2012-05-14 11:48 jcfr Note Added: 0004373
2012-05-15 13:13 pieper Note Added: 0004399
2012-05-15 18:56 jcfr Category Slicer Wiki => Documentation & Wiki
2012-08-20 14:07 jcfr Target Version Slicer 4.2.0 - Feature freeze Sept 1st 2012 => Slicer 4.2.5
2012-08-21 13:39 jcfr Target Version Slicer 4.2.5 => Slicer 4.3.0


Mantis 1.1.4[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker