Difference between revisions of "2017 Winter Project Week/SlicerGeometryModifier"

From NAMIC Wiki
Jump to: navigation, search
(First draft of SlicerGeometryModifier page)
Line 30: Line 30:
 
** At this point, we would ask for feedback to the community.  
 
** At this point, we would ask for feedback to the community.  
 
* Explore the addition of a simple markup type like a plane.
 
* Explore the addition of a simple markup type like a plane.
|
 
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
 
*
 
|}
 
 
==Background and References==
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
 
==Project Description==
 
{| class="wikitable"
 
! style="text-align: left; width:27%" |  Objective
 
! style="text-align: left; width:27%" |  Approach and Plan
 
! style="text-align: left; width:27%" |  Progress and Next Steps
 
|- style="vertical-align:top;"
 
|
 
<!-- Objective bullet points -->
 
*
 
|
 
<!-- Approach and Plan bullet points -->
 
*
 
 
|
 
|
 
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
 
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->

Revision as of 14:30, 3 January 2017

Home < 2017 Winter Project Week < SlicerGeometryModifier

Key Investigators

  • Johan Andruejol (Kitware, Inc.)
  • JC Fillon-Robin (Kitware, Inc.)
  • Beatriz Paniagua (Kitware, Inc.)

Project Description

Objective Approach and Plan Progress and Next Steps
  • Slicer lacks interactive support for moving, rotating and scaling objects in the user interface. It would be nice to be able to interact directly with an object.
  • The main objective of this project would be to allow user to change a transform parameters with through interaction. The objects under that transform should be automatically updated accordingly and the interaction representation should always match the transform properties.
  • We would also like to explore adding new markup types in Slicer such as planes and paths. Those would be integrated using the infrastructure in place.
  • Add a translation widget which:
    • Allows the user to move the objects under a transform.
    • Updates the transform interactively.
    • Updates itself whenever the transform is changed.
    • At this point, we would ask for feedback to the community.
  • Explore the addition of a simple markup type like a plane.

Background and References