Difference between revisions of "Sept-2009-SlicerWidgetsBrainstorm"
From NAMIC Wiki
| Line 24: | Line 24: | ||
== Things to Consider == | == Things to Consider == | ||
Our current plan is to move to QT. However, there are some alternates which should be looked at as a due diligence: | Our current plan is to move to QT. However, there are some alternates which should be looked at as a due diligence: | ||
| + | ===Widgets that are needed=== | ||
| + | * http://my-trac.assembla.com/protoctk/wiki/WidgetPlans | ||
| + | |||
===Javascript family=== | ===Javascript family=== | ||
| − | + | ||
| − | * http://code.google.com/webtoolkit/ | + | * Java layer atop JavaScript http://code.google.com/webtoolkit/ |
** http://gwt.google.com/samples/Mail/Mail.html | ** http://gwt.google.com/samples/Mail/Mail.html | ||
** http://earth-api-samples.googlecode.com/svn/trunk/demos/drive-simulator/index.html | ** http://earth-api-samples.googlecode.com/svn/trunk/demos/drive-simulator/index.html | ||
| − | * Phyton wrappings around | + | * Phyton wrappings around JavaScript |
**http://pyjs.org | **http://pyjs.org | ||
| − | ** http://pyjs.org/examples/ | + | *** http://pyjs.org/examples/ |
| − | ** http://pyjs.org/examples/mail/output/Mail.html | + | *** http://pyjs.org/examples/mail/output/Mail.html |
== Attendance == | == Attendance == | ||
Revision as of 17:09, 1 September 2009
Home < Sept-2009-SlicerWidgetsBrainstormContents
Logistics
- Tentative date: Wednesday and Thursday, September 16 and 17, 2009
- Location: 1249 Boylston Street, 2nd floor conference room
Goals
The purpose of this meeting is to discuss development strategies to migrate Slicer to a new GUI layer. For some background and discussion of our experiments with Qt and a possible development plan 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?
- How much work have comparable project required (by people with what skills and experience?)
- What resources do we have to devote to this project compared with other demands?
- Are we comfortable that we have considered all the viable alternatives?
- What are the trends in GUI interface development for applications like ours
- What are the risks/benefits/complexity trade offs of various approaches
Things to Consider
Our current plan is to move to QT. However, there are some alternates which should be looked at as a due diligence:
Widgets that are needed
Javascript family
- Java layer atop JavaScript http://code.google.com/webtoolkit/
- Phyton wrappings around JavaScript
Attendance
- Open to all self-declared Slicer developers:
- Will Schroeder
- Steve Pieper
- Ron Kikinis
- Nicole Aucoin
