Slicer Day October 2008 - Revision history

Wjp at 18:34, 7 October 2008

2008-10-07T18:34:31Z

Wjp at 18:31, 7 October 2008

2008-10-07T18:31:22Z

Wjp at 18:25, 7 October 2008

2008-10-07T18:25:47Z

Wjp at 18:24, 7 October 2008

2008-10-07T18:24:04Z

Wjp at 18:23, 7 October 2008

2008-10-07T18:23:05Z

Wjp at 18:22, 7 October 2008

2008-10-07T18:22:40Z

Wjp at 18:20, 7 October 2008

2008-10-07T18:20:30Z

Wjp at 18:19, 7 October 2008

2008-10-07T18:19:58Z

Wjp at 18:18, 7 October 2008

2008-10-07T18:18:23Z

Pieper at 13:07, 7 October 2008

2008-10-07T13:07:10Z

@@ Line 21: / Line 21: @@
 ** Widgets and data objects will have different but related selectable and selected behavior
 *** how do we communicate that a widget's handles are selectable (change color or size on mouseover)?
-*** how do we communicate that data objects are 'selectable' on mousover? Karthik's idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object. This 'context menu' will enable us to get rid of the "PICK" mouse mode.
+*** how do we communicate that data objects are 'selectable' on mousover? Karthik's idea -- to have hover widget that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object. This 'context menu' will enable us to get rid of the "PICK" mouse mode.
 *** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active"; this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.
 *** How will we handle Multiple selections that define multiple active datasets (command line modules operate on these)?

@@ Line 21: / Line 21: @@
 ** Widgets and data objects will have different but related selectable and selected behavior
 *** how do we communicate that a widget's handles are selectable (change color or size on mouseover)?
-*** how do we communicate that data objects are 'selectable' on mousover? Kartik's idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object. This 'context menu' will enable us to get rid of the "PICK" mouse mode.
+*** how do we communicate that data objects are 'selectable' on mousover? Karthik's idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object. This 'context menu' will enable us to get rid of the "PICK" mouse mode.
 *** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active"; this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.
 *** How will we handle Multiple selections that define multiple active datasets (command line modules operate on these)?

@@ Line 21: / Line 21: @@
 ** Widgets and data objects will have different but related selectable and selected behavior
 *** how do we communicate that a widget's handles are selectable (change color or size on mouseover)?
-*** how do we communicate that data objects are 'selectable' on mousover? Idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object. This 'context menu' will enable us to get rid of the "PICK" mouse mode.
+*** how do we communicate that data objects are 'selectable' on mousover? Kartik's idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object. This 'context menu' will enable us to get rid of the "PICK" mouse mode.
 *** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active"; this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.
 *** How will we handle Multiple selections that define multiple active datasets (command line modules operate on these)?

@@ Line 21: / Line 21: @@
 ** Widgets and data objects will have different but related selectable and selected behavior
 *** how do we communicate that a widget's handles are selectable (change color or size on mouseover)?
-*** how do we communicate that data objects are 'selectable' on mousover? Idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object.
+*** how do we communicate that data objects are 'selectable' on mousover? Idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object. This 'context menu' will enable us to get rid of the "PICK" mouse mode.
 *** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active"; this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.
 *** How will we handle Multiple selections that define multiple active datasets (command line modules operate on these)?

@@ Line 22: / Line 22: @@
 *** how do we communicate that a widget's handles are selectable (change color or size on mouseover)?
 *** how do we communicate that data objects are 'selectable' on mousover? Idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Directly manipuate the widget, but manipulate a data object by proxy (widget): Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object.
-*** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active", this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.
+*** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active"; this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.
 *** How will we handle Multiple selections that define multiple active datasets (command line modules operate on these)?

@@ Line 20: / Line 20: @@
 * design: clear & consistent selection behavior in slicer
 ** Widgets and data objects will have different but related selectable and selected behavior
-*** how do we communicate that a widget's handles are selectable (change color on mouseover)?
+*** how do we communicate that a widget's handles are selectable (change color or size on mouseover)?
 *** how do we communicate that data objects are 'selectable' on mousover? Idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object.
 *** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active", this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.

@@ Line 16: / Line 16: @@
 * input widget interface behavior: eg. number input in transformation module
 * design: create and delete widgets in slicer
-** should be a consistent pattern for creating and positioning a widget in slice viewer or 3D viewer, and deleting or hiding a created widget (see reformat widget currently -- one widget, hidden or exposed).
+** should be a consistent pattern for creating and positioning a widget in slice viewer or 3D viewer, and deleting or hiding a created widget (see reformat widget currently -- one widget, hidden or exposed thru a toggle button in SliceController).
-** what options do we have to work with?
+** how do we position? Automatically or interactively (click to place)?
 * design: clear & consistent selection behavior in slicer
-** from user's point of view, what's a widget and what not (fiducials?)
+** all 'selectable' things should behave consistently. Widgets and data objects will behave a little differently.
-** all 'selectable' things should behave consistently (what will be good?)
+*** how do we communicate that a widget's handles are selectable (change color on mouseover)?
-*** how do we communicate 'selectable' on mousover?
+*** how do we communicate that data objects are 'selectable' on mousover? Idea -- to have hover actor that displays the name of the pickable data object that mouse is over. To keep the main viewer clean, could display this name in the view control gui as user mouses around. Could also display name of widget when mouse is over a handle. Right click while over an object (model, for instance) brings up a menu with options that might include 'show transform widget, set visibility, set color, etc.', appropriate for that object.
-*** how do we communicate 'active' once selected?
+*** "Select" versus "active"? Selecting is an explicit action. "Selected" = "Active", this state is the result of selecting. Users select a data object either via a NodeSelectorWidget, OR by invoking a proxy that manipulates the data object. For instance, to select a model for transforming, mouse over model, right click and select 'show transform widget' from menu, and get a transform widget attached to that object. Now manipulate the model via the widget -- this model is 'active'. Right click again to say 'hide transform widget' to stop transforming. Is model still the 'active' model? If so, this sometimes leads to operating on an 'active' dataset that's gone stale in the user's head.
-** are datasets (like models) selectable?
+*** Multiple selections?
-*** if yes, how can we make their selection behavior consistent with widgets?
 * MRML

← Older revision		Revision as of 13:07, 7 October 2008
Line 30:		Line 30:
	** Discussion of Generality (what's pure MRML vs. MRMLSlicer?)		** Discussion of Generality (what's pure MRML vs. MRMLSlicer?)
	** Efficiency Issues		** Efficiency Issues
		+
		+	* Other ongoing topics to touch on
		+	** Build machines -
		+	*** Module building
		+	*** Platforms - old compilers (VS2003.NET), Solaris...
		+	** Python
		+	** BatchMake and Grids
		+
		+	**