Difference between revisions of "2008 Winter Project Week:3DWWidgets"
| Line 1: | Line 1: | ||
{| | {| | ||
|[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2008_Winter_Project_Week]] ]] | |[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2008_Winter_Project_Week]] ]] | ||
| + | |valign="top"|[[Image:slicer-uneditable-bbox.jpg |thumb|320px|FE Module Prototype in Slicer3]] | ||
|} | |} | ||
| − | |||
| − | |||
| − | |||
__NOTOC__ | __NOTOC__ | ||
| Line 18: | Line 16: | ||
<h1>Objective</h1> | <h1>Objective</h1> | ||
| − | + | Several different module developers have asked to insert and operate with VTK-style 3D widgets in the Slicer 3D view window. This project will study the implications of different ways to insert 3D widgets and how the design of VTK 3D widgets can best interact with Slicer's MRML tree. Widget interaction may require an extension to the MRML observer paradigm. | |
</div> | </div> | ||
| Line 30: | Line 28: | ||
[http://www.na-mic.org/Wiki/index.php/Projects/Slicer3/2007_Project_Week_Support_for_Unstructured_Grids 2007 Project Week - Support for Unstructured Grids]<br> | [http://www.na-mic.org/Wiki/index.php/Projects/Slicer3/2007_Project_Week_Support_for_Unstructured_Grids 2007 Project Week - Support for Unstructured Grids]<br> | ||
| − | + | Update the picking routines to allow selection and manipulation of both 3d and 2d widgets? | |
| − | Update the picking routines to allow selection and manipulation of both 3d and 2d widgets. | + | |
| + | The Univ. of Iowa Finite Element collaboration project has added 3D widgets using direct manipulation and custom callbacks. We will discuss the strengths and weaknesses of this approach as a case study. At the end of the week, our objective is to have additional clarity on the design approach that modules should take when they want to interact with 3D widgets in Slicer3. | ||
</div> | </div> | ||
| Line 41: | Line 40: | ||
====Jan 2008 Project Half Week==== | ====Jan 2008 Project Half Week==== | ||
| + | |||
| + | ====June 2007 Boston Project Week==== | ||
| + | A class of MRML nodes to correspond to VTK-style 3D widgets were created (based on fiducials) as an experiment during this project week. It was decided that this was not the way to integrate 3D widgets because of its inconsistency with MRML storing geometry and dataset state variables. 3D widgets, in contrast, are transitory and are designed to be created by applications just when needed. The MRML-based 3D widgets node design was abandoned. | ||
</div> | </div> | ||
Revision as of 23:01, 21 December 2007
Home < 2008 Winter Project Week:3DWWidgets Return to 2008_Winter_Project_Week |
Key Investigators
- Kitware: Will Schroeder
- BWH: Nicole Aucoin
- KnowledgeVis, LLC: Curtis Lisle
- U of Iowa: Kiran Shivann
Objective
Several different module developers have asked to insert and operate with VTK-style 3D widgets in the Slicer 3D view window. This project will study the implications of different ways to insert 3D widgets and how the design of VTK 3D widgets can best interact with Slicer's MRML tree. Widget interaction may require an extension to the MRML observer paradigm.
Approach, Plan
Build on work from meshing integration:
Slicer Interactive Module
2007 Project Week - Support for Unstructured Grids
Update the picking routines to allow selection and manipulation of both 3d and 2d widgets?
The Univ. of Iowa Finite Element collaboration project has added 3D widgets using direct manipulation and custom callbacks. We will discuss the strengths and weaknesses of this approach as a case study. At the end of the week, our objective is to have additional clarity on the design approach that modules should take when they want to interact with 3D widgets in Slicer3.
Progress
Jan 2008 Project Half Week
June 2007 Boston Project Week
A class of MRML nodes to correspond to VTK-style 3D widgets were created (based on fiducials) as an experiment during this project week. It was decided that this was not the way to integrate 3D widgets because of its inconsistency with MRML storing geometry and dataset state variables. 3D widgets, in contrast, are transitory and are designed to be created by applications just when needed. The MRML-based 3D widgets node design was abandoned.
