Difference between revisions of "Developer Meetings/20130226"
From Slicer Wiki
Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
+ | The listing of modules should be organized from the vantage point of an '''early stage end user'''. Power users know what module they want and usually look in the alphabetic listing. Developer oriented tools should not be prominent and should not crowd the listings. Developers should be directed as much as possible to the wiki as a start point. | ||
+ | |||
*We should reorganize the listing of modules in such a way that each category has only one choice per category/subcategory presented initially and everything else is under a tab called "Advanced". This is consistent with the way modules in Slicer should be organized. | *We should reorganize the listing of modules in such a way that each category has only one choice per category/subcategory presented initially and everything else is under a tab called "Advanced". This is consistent with the way modules in Slicer should be organized. | ||
*We should come up with guidance for developers on how to organize extensions. In some cases it makes sense for them to be in their own category and some cases, individual modules should be spread out to existing categories. Modules derived from extensions should have the extension acronym inside the module name. As a general rule, extension derived modules should be under the "advanced" section of a category so that the top level is not "messed up" | *We should come up with guidance for developers on how to organize extensions. In some cases it makes sense for them to be in their own category and some cases, individual modules should be spread out to existing categories. Modules derived from extensions should have the extension acronym inside the module name. As a general rule, extension derived modules should be under the "advanced" section of a category so that the top level is not "messed up" |
Revision as of 13:53, 21 February 2013
Home < Developer Meetings < 20130226Introduction
The listing of modules should be organized from the vantage point of an early stage end user. Power users know what module they want and usually look in the alphabetic listing. Developer oriented tools should not be prominent and should not crowd the listings. Developers should be directed as much as possible to the wiki as a start point.
- We should reorganize the listing of modules in such a way that each category has only one choice per category/subcategory presented initially and everything else is under a tab called "Advanced". This is consistent with the way modules in Slicer should be organized.
- We should come up with guidance for developers on how to organize extensions. In some cases it makes sense for them to be in their own category and some cases, individual modules should be spread out to existing categories. Modules derived from extensions should have the extension acronym inside the module name. As a general rule, extension derived modules should be under the "advanced" section of a category so that the top level is not "messed up"