Difference between revisions of "Sept-2009-SlicerWidgetsBrainstorm"
From NAMIC Wiki
(Created page with '*For some background see [http://wiki.slicer.org/slicerWiki/index.php/Qt_in_Slicer3 here] *Location: 1249 Boylston Street *Attendance: #Will Schroeder #Steve Pieper #Ron Kikinis') |
|||
| Line 1: | Line 1: | ||
| − | |||
*Location: 1249 Boylston Street | *Location: 1249 Boylston Street | ||
*Attendance: | *Attendance: | ||
| Line 5: | Line 4: | ||
#Steve Pieper | #Steve Pieper | ||
#Ron Kikinis | #Ron Kikinis | ||
| + | |||
| + | == Goals == | ||
| + | |||
| + | The purpose of this meeting is to discuss development strategies to migrate Slicer to a new GUI layer. For some background see [http://wiki.slicer.org/slicerWiki/index.php/Qt_in_Slicer3 here]. | ||
| + | |||
| + | Important questions to consider at this meeting are: | ||
| + | * What functionality does the application need to have in order to accomplish the needs of our DBP and clinical collaborations over the next several years? | ||
| + | * What look and feel should the application have? | ||
| + | * What capabilities will help us build the community of developers and users | ||
| + | ** Standard tools - well supported with ample documentation, support, etc | ||
| + | ** Flexibility to run in many environments | ||
| + | ** Ease of use and productivity for developers | ||
| + | * Can we get a realistic estimate of the workload required and what skills are required to do the work? | ||
| + | * Are we comfortable that we have considered all the viable alternatives? | ||
Revision as of 18:05, 31 August 2009
Home < Sept-2009-SlicerWidgetsBrainstorm- Location: 1249 Boylston Street
- Attendance:
- Will Schroeder
- Steve Pieper
- Ron Kikinis
Goals
The purpose of this meeting is to discuss development strategies to migrate Slicer to a new GUI layer. For some background see here.
Important questions to consider at this meeting are:
- What functionality does the application need to have in order to accomplish the needs of our DBP and clinical collaborations over the next several years?
- What look and feel should the application have?
- What capabilities will help us build the community of developers and users
- Standard tools - well supported with ample documentation, support, etc
- Flexibility to run in many environments
- Ease of use and productivity for developers
- Can we get a realistic estimate of the workload required and what skills are required to do the work?
- Are we comfortable that we have considered all the viable alternatives?
