Difference between revisions of "VTKWidgets"

From KitwarePublic
Jump to navigationJump to search
 
Line 1: Line 1:
== Overview ==
== Overview ==
The VTK widgets are undergoing a redesign. This is mainly to add functionality and clean up some inconsistencies with the existing implementation. We also have limited funding (see acknowledgements) to add new widgets in support of medical image processing (i.e., segmentation and registration).
The VTK widgets are undergoing a redesign. This is mainly to add functionality and clean up some inconsistencies with the existing implementation. We also have limited funding (see acknowledgements) to add new widgets in support of medical image processing (i.e., segmentation and registration).
There are four major goals of this work:
# Support the ability to customize event bindings
# Decouple the widget representation (geometry) from the event processing
# Reduce redundant code; centralize common operations
# Add new widgets in support of medical image processing
The following sections discuss eash of these goals and the proposed implementation.
== Customized Event Binding
== Decouple Event Processing from Widget Geometry
== Code Refactoring
== New Widgets

Revision as of 13:36, 24 August 2005

Overview

The VTK widgets are undergoing a redesign. This is mainly to add functionality and clean up some inconsistencies with the existing implementation. We also have limited funding (see acknowledgements) to add new widgets in support of medical image processing (i.e., segmentation and registration).

There are four major goals of this work:

  1. Support the ability to customize event bindings
  2. Decouple the widget representation (geometry) from the event processing
  3. Reduce redundant code; centralize common operations
  4. Add new widgets in support of medical image processing

The following sections discuss eash of these goals and the proposed implementation.

== Customized Event Binding

== Decouple Event Processing from Widget Geometry

== Code Refactoring

== New Widgets