Difference between revisions of "2011 Winter Project Week:Breakout Slicer"
From NAMIC Wiki
Line 35: | Line 35: | ||
===ITK4 Integration - Bill=== | ===ITK4 Integration - Bill=== | ||
[[2011_Winter_Project_Week:_Slicer4-ITK4_Continuous_Integration| Slicer4/ITK4 integration]] | [[2011_Winter_Project_Week:_Slicer4-ITK4_Continuous_Integration| Slicer4/ITK4 integration]] | ||
+ | ===Afternoon Qt Loadable Module Tutorial=== | ||
+ | [http://wiki.slicer.org/slicerWiki/index.php/Slicer3:Developers:Projects:QtSlicer/Tutorials/ModuleWriting How to write a loadable module] | ||
=Plans= | =Plans= | ||
Plans for the time between Jan 2011 and June 2011. Identify a list of modules that are still missing and must be available, when we roll out Slicer 4 for end users. | Plans for the time between Jan 2011 and June 2011. Identify a list of modules that are still missing and must be available, when we roll out Slicer 4 for end users. |
Revision as of 01:31, 12 January 2011
Home < 2011 Winter Project Week:Breakout SlicerBack to Project Week Agenda
Session Leaders: Steve Pieper, Julien Finet
This session looks at the development of Slicer4.
People interested in the use of Slicer3.6 should consider attending the Monday breakout session with Ron.
Contents
Slicer4 Architecture & Status - Steve
This talk will provide an overview of the technologies included in slicer4 and the transition path from slicer3 to slicer4. slides
See this page for status of slicer4 development and the Qt port.
Creating a Loadable C++ Module - J2
- File:2011 01-AHM-QtPortInSlicer.ppt
- Other resources
- Slicer 4.0 beta binaries
- Progress report
- SlicerQt image gallery
- Qt port Wiki pages
- Qt port tutorials
- Previous presentations
Python Scripting - Jc
Command line modules / Slicer Execution Model - Jim
- What can it do?
- What do we have plans for?
- What do you want?
- Slides
ITK4 Integration - Bill
Afternoon Qt Loadable Module Tutorial
How to write a loadable module
Plans
Plans for the time between Jan 2011 and June 2011. Identify a list of modules that are still missing and must be available, when we roll out Slicer 4 for end users. We need to identify owners for each of these:
Scheduled For Porting or Already Ported
- Colors
- Data/Dicom import/load
- Editor
- Models
- ROI
- SlicerWelcome
- Slices
- Transforms
- Volume rendering: Redesign?
- GPU mappers (NCI: Yanling; Kitware: J2)
- Nodes and Displayable Managers (Alex Y)
- Qt GUI (J2)
- Volumes
- Diffusion frame work: Redesign?
- Brainsfit
- EM segementation
- Fast Marching
- GrowCutSegement
- RSS?
- CompareView
- Wizards
- NeuroIGT
- Prostate IGT?
- ChangeTracker?
- Extensions
- VMTK?
Not Currently Scheduled For Porting
- QueryAtlas?
New Modules
- Annotation
- SceneViews
- TubeTK?