Difference between revisions of "Slicer3:Developers"
Line 77: | Line 77: | ||
* Integrate Slicer3 into a development environment | * Integrate Slicer3 into a development environment | ||
** [[Slicer3::Eclipse | Eclipse]] (keilhack) | ** [[Slicer3::Eclipse | Eclipse]] (keilhack) | ||
− | ** Microsoft Visual Studio 200x | + | ** [[Slicer3::MSVS200X | Microsoft Visual Studio 200x]] |
* Where to go for help (Steve) | * Where to go for help (Steve) | ||
* Status Review and Plan (Steve) | * Status Review and Plan (Steve) |
Revision as of 21:42, 7 February 2007
Home < Slicer3:DevelopersSlicer3 |
---|
Developers |
Contents
Slicer 3 Overview
- For more details on the slicer architecture see: Architecture Slides.
- Highlights of the new architecture
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.
- Introduction to Slicer3 (Steve)
- Slicer3 Historical Timeline
- Status overview and Demo
- Schematic of application interface & functionality: Media:GUIMap.png
- Schematic of slice GUI: Media:SliceGUI.png
- Getting the software and troubleshooting
- Overall Architecture and Slicer 3 Coding Style
- Contributing codes to Slicer3
- Two module types (Command line and Interactive)
- Command line modules and how to implement one (Jim and Bill) Intro
- How to add an interactive module (wjp)
- MRML MRML Slides(Alex)
- GUI
- Engineering
- Tips for avoiding memory leaks
- Current Practice (Steve)
- Suggested change to SmartPointers (Jim)
- Generating tests (Bill)
- Tips for avoiding memory leaks
- Integrate Slicer3 into a development environment
- Eclipse (keilhack)
- Microsoft Visual Studio 200x
- Where to go for help (Steve)
- Status Review and Plan (Steve)
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
- 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/svn/Slicer3/trunk Slicer3
Use ViewVC to browse the repository
Doxygen documentation for Slicer3.
The 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
- Official release at AHM January 2007
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.