Difference between revisions of "Developer Meetings/20160719"
From Slicer Wiki
Line 54: | Line 54: | ||
** Glyph for existing modules | ** Glyph for existing modules | ||
** Glyph for actions | ** Glyph for actions | ||
− | ** Licensed under | + | ** Licensed under Open Font License |
+ | ** Could ask company to design them: | ||
+ | *** What do we do if we need more ? | ||
* Add icon to target different users: | * Add icon to target different users: |
Revision as of 14:53, 19 July 2016
Home < Developer Meetings < 20160719
If you would like to list your topic here, create a wiki account and edit this page. |
To Discuss
- Web infrastructure
- Ron front page mockup: http://wiki.slicer.org/slicerWiki/index.php/2016-User-Manual-Discussion
- Which issue should be listed as core modules ?
- Current core modules:
Volumes SubjectHierarchy DICOM DataStore Markups Segmentations Transforms VolumeRendering Welcome # Remove from list of "core" modules: Annotations -> Merge with Markups Editor -> Segmentation implement the feature Models -> SH module list them SceneViews ViewControllers Data -> SH implement this functionality.
List of core modules originally grabbed using:
mm = slicer.app.moduleManager() for name in mm.modulesNames(): if mm.module(name).categories[0] == '': print(name)
- SciPy conference
Updates
Conclusion
Idea:
- Create vectorial font for "concept" in Slicer:
- Glyph for "Core function"
- Glyph for existing modules
- Glyph for actions
- Licensed under Open Font License
- Could ask company to design them:
- What do we do if we need more ?
- Add icon to target different users:
- User
- Developer
- Csaba:
- Will add New_User page to the main page
- Jc:
- Ask Greb about module search
- Start update of Main_Page
- Merge concept of "Core" and "Favorite" Editor. Give the option to update them.