Slicer3 FlexibleLayouts - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T18:07:09Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2009-06-26T15:47:23Z

Key Investigators

2009-06-26T11:13:28Z

Key Investigators

2009-06-26T11:12:53Z

Key Investigators

2009-06-26T11:02:53Z

Key Investigators

2009-06-26T10:59:29Z

Key Investigators

2009-06-24T19:08:10Z

NOTES:

2009-06-24T19:07:37Z

NOTES:

2009-06-24T19:07:19Z

NOTES:

2009-06-24T19:06:38Z

NOTES:

@@ Line 54: / Line 54: @@
 ==References==
-* [http://www.slicer.org/slicerWiki/index.php/Slicer3:UIDesign:WorkingProblems:SlicerFlexibleLayout:UXP#User_experience_design_for_Slicer_flexible_layouts  User Experience Design]
+* [https://www.slicer.org/wiki/Slicer3:UIDesign:WorkingProblems:SlicerFlexibleLayout:UXP#User_experience_design_for_Slicer_flexible_layouts  User Experience Design]
-* [http://www.slicer.org/slicerWiki/index.php/Slicer3:UIDesign:WorkingProblems:SlicerFlexibleLayout:Architecture  Representation]
+* [https://www.slicer.org/wiki/Slicer3:UIDesign:WorkingProblems:SlicerFlexibleLayout:Architecture  Representation]
 ==NOTES:==

@@ Line 41: / Line 41: @@
 * Sebastien has mature implementation in vtkMRMLViewNode and vtkMRMLCameraNode to provide multiple views of the MRMLScene.
 * Alex and Andreas will be looking at the current implementation of vtkSlicerViewerWidget and designing an appropriate superclass for this widget
 * Custom Layout MRML/Logic maturing and will be checked in to trunk soon
 * Custom Layout GUI will follow
-* New class hierarchy will be developed (diagram) to generalize layout representation
 [[image:SlicerCustomLayoutFramework.png]]

@@ Line 38: / Line 38: @@
 <h3>Progress</h3>
+* We had a nice design meeting, some notes from it are captured below
 * Sebastien has mature implementation in vtkMRMLViewNode and vtkMRMLCameraNode to provide multiple views of the MRMLScene.
 * Alex and Andreas will be looking at the current implementation of vtkSlicerViewerWidget and designing an appropriate superclass for this widget

← Older revision		Revision as of 11:12, 26 June 2009
Line 38:		Line 38:

	<h3>Progress</h3>		<h3>Progress</h3>
		+
		+	* Sebastien has mature implementation in vtkMRMLViewNode and vtkMRMLCameraNode to provide multiple views of the MRMLScene.
		+	* Alex and Andreas will be looking at the current implementation of vtkSlicerViewerWidget and designing an appropriate superclass for this widget
		+	* Custom Layout MRML/Logic maturing and will be checked in to trunk soon
		+	* Custom Layout GUI will follow
		+	* New class hierarchy will be developed (diagram) to generalize layout representation

	[[image:SlicerCustomLayoutFramework.png]]		[[image:SlicerCustomLayoutFramework.png]]

@@ Line 38: / Line 38: @@
 <h3>Progress</h3>
-[[image:SlicerCustomLayoutPlan.png]]
 </div>

@@ Line 61: / Line 61: @@
 * When populating custom layout, will have to count number of vtkMRMLViewNodes and assign to panes
 * '''Representation for view: vtkMRMLViewNode:''' state for a 3D view vtkSlicerViewerWidget
-* '''Rep for camera: vtkMRMLCameraNode:''' vtkMRMLViewNodes have vtkMRMLCameraNodes; ViewNodes can swap CameraNodes.
+* '''Rep for camera: vtkMRMLCameraNode:'''
 ** Seb mentions problem with a render being called in a viewer that has (temporarily) no camera, due to a swap -- vtk will create a new camera that has no MRML counterpart. This is addressed as described below.
-* A viewNode can use the camera from another viewNode (but in this case, a camera swap is implemented under the hood so that no viewer is without a camera.) '''--Can we generate an event when this swap happens in case we want to notify a user?'''
+** A viewNode can use the camera from another viewNode (but in this case, a camera swap is implemented under the hood so that no viewer is without a camera.) '''--Can we generate an event when this swap happens in case we want to notify a user?'''
-* Many cameras can be created and a single ViewNode can switch to use any of them.
+** Many cameras can be created and a single ViewNode can switch to use any of them.
 * Single scene contains all datasets; different datasets can be exposed/hidden in each view.
 * How will this work in use: how to configure a node's display parameters for each defined view on the scene?

@@ Line 60: / Line 60: @@
 * In current implementation, new 3D views will populate tabbed 3D views...
 * When populating custom layout, will have to count number of vtkMRMLViewNodes and assign to panes
-* Representation: vtkMRMLViewNode: state for a 3D view vtkSlicerViewerWidget, knows
+* '''Representation: vtkMRMLViewNode:''' state for a 3D view vtkSlicerViewerWidget
-* Rep for cameras: vtkMRMLCameraNode: vtkMRMLViewNodes have vtkMRMLCameraNodes; ViewNodes can swap CameraNodes.
+* '''Rep for cameras: vtkMRMLCameraNode:''' vtkMRMLViewNodes have vtkMRMLCameraNodes; ViewNodes can swap CameraNodes.
 ** Seb mentions problem with a render being called in a viewer that has (temporarily) no camera, due to a swap -- vtk will create a new camera that has no MRML counterpart. This is addressed as described below.
 * A viewNode can use the camera from another viewNode (but in this case, a camera swap is implemented under the hood so that no viewer is without a camera.) '''--Can we generate an event when this swap happens in case we want to notify a user?'''

@@ Line 73: / Line 73: @@
 * How to encapsulate the presentation mechanism for content in any "pane" in a layout.
 * IGT toplevel  has had to overload too many methods -- so would be good to have a better constructed superclass for vtkSlicerViewerWidget. (Alex & Andreas) will restructure this architecture a little bit to clean it up.
-* Goal: vtkKWWidget <- vtkSlicerLayoutableWidget <- vtkSlicerWidget <- vtkSlicerSliceViewerWidget
+* Goal: '''vtkKWWidget <- vtkSlicerLayoutableWidget <- vtkSlicerWidget <- vtkSlicerSliceViewerWidget '''
 * TableViewers, plot viewers would all be subclassed from vtkSlicerLayoutableWidget.
 * Layout logic/mrml underway and will be checked in soon.; Layout GUI will take a bit more time.
 * Each vertex in layout tree should point to a vtkSlicerLayoutableWidgetNode