Difference between revisions of "Slicer3:Developers"
Line 49: | Line 49: | ||
This section centrally locates many existing (and developing) wiki pages useful to Slicer3 developers. The content is currently being developed for the January AHM. | This section centrally locates many existing (and developing) wiki pages useful to Slicer3 developers. The content is currently being developed for the January AHM. | ||
− | * Getting the software and troubleshooting | + | * [[Slicer3:BuildInstructions | Getting the software and troubleshooting]] |
* Which kind of module (interactive or command line) to add (wjp) | * Which kind of module (interactive or command line) to add (wjp) | ||
* [[Slicer3:UIEngineering#How_to_draft_a_Slicer_module_.28MyModule.29_GUI_class | How to add an interactive module]] (wjp) | * [[Slicer3:UIEngineering#How_to_draft_a_Slicer_module_.28MyModule.29_GUI_class | How to add an interactive module]] (wjp) |
Revision as of 11:25, 24 December 2006
Home < Slicer3:DevelopersSlicer3 |
---|
Developers |
Contents
Slicer 3 Overview
- For more details on the slicer architecture see: Architecture Slides.
- Highlights of the new architecture
- GUI anatomy
Information for Developers
This section centrally locates many existing (and developing) wiki pages useful to Slicer3 developers. The content is currently being developed for the January AHM.
- Getting the software and troubleshooting
- Which kind of module (interactive or command line) to add (wjp)
- How to add an interactive module (wjp)
- Command line modules and how to implement one (already on wiki)
- How undo/redo works, and how to enable it in your code
- Creating and using new MRML node types
- Keeping the GUI stateless (wjp)
- Adding keyboard shortcuts (wjp)
- Tips for avoiding memory leaks
- Generating tests
- GUI style guidelines for consistent look & feel (wjp)
- Incorporating your group's logo and attributions
- Where to go for help
Slicer 3 Projects
Updated November 2006 to reflect activities in preparation for January 2007 AHM. Projects should correspond to the outstanding issues listed on the Status Summary. Please refer to the Feature Requests from users when planning your implementations.
If your name is in bold, you are responsible for that aspect of the project
- Architecture/Features (Steve Pieper, Group: Bill Lorensen, Ron Kikinis, Mike Halle, Noby Hata)
- Data Model / libMRML (Alex, Steve)
- Execution Model / Command Line Modules (Jim Miller, Bill Lorensen)
- Interface Design and Usability (Wendy Plesniak, KWWidgets: Sebastien Barre, Yumin Yuan)
- Transition of Selected Slicer2.x Modules to Slicer3 (Nicole, Katie, Wendy, Mathieu)
- DTMRI: Raul, LMI
- Editor: Steve
- Colors, Fiducials, FreeSurfer, ModelMaker: Nicole
- IGT, Trackers: Haiying
- Slicer3:ArchetypeReaders: Bill
- EMSegment Interface: Brad Davis
- SlicerDaemon Interface (for unu, matlab): Steve Pieper
- Build/Test/Deploy System (Andy, Katie)
- Pipeline Integration (Jags)
- Grid Integration (Jeff Grethe, Neil)
- Slicer3:Performance Analysis (Katie)
Slicer 3 Quick links
The Slicer3 svn repository:
svn co http://www.na-mic.org:8000/svn/Slicer3/trunk Slicer3
Slicer3 build instructions can be found on the wiki.
Doxygen documentation for Slicer3.
A Slicer3 VisualBlog shows screenshots of slicer developments.
Developers should follow the Slicer 3 Coding Style.
Discussion of slicer3 takes place on the slicer-devel@bwh.harvard.edu list. To join developer's mailing list, send a request to: slicer-devel-request@lists.bwh.harvard.edu with the keyword subscribe as the subject.
Design Information
May 23, 2006: Algorithm Core workshop.
April 3, 2006: Slicer 3 alpha technical powerpoint presentation.
Events
Upcoming
Slicer3.0 Beta by End of November 2006
- Official release at AHM January 2007
- This will include a draft of the new logo
Migration Tutorials (from Slicer 2.x to 3.0) by March 2007
- First set of Migration tutorials by Jan 1, 2007
- Second set of Migration tutorials by Feb 1, 2007
- Complete by March 2007
Past
April 3, 2006
There was a Slicer3 Alpha1 Design Review meeting.
Slicer3 Alpha2/Beta1 by End of July 2006
- Initial Testing with Core 3 participation
- Base functionality in place, but still subject to API changes and other improvements.
- Packaged versions not yet available, but testers are able to easily build their own versions.