Documentation/Labs/Slicer5-roadmap - Revision history

Lasso: /* Removal of Charts based infrastructure */

2022-04-17T22:19:39Z

Removal of Charts based infrastructure

Pinter: /* Revisit MRML Copy API */ Done

2020-05-01T10:41:13Z

Revisit MRML Copy API: Done

JChris.FillionR: /* Revisit MRML Copy API */

2020-01-22T11:51:54Z

Revisit MRML Copy API

JChris.FillionR at 11:09, 22 January 2020

2020-01-22T11:09:29Z

JChris.FillionR at 11:07, 22 January 2020

2020-01-22T11:07:40Z

Pinter: /* Coordinate system in files */

2020-01-21T11:09:08Z

Coordinate system in files

Pinter: /* Specific Change Proposals */ Mark Model Hierarchies task as done

2020-01-13T10:20:17Z

Specific Change Proposals: Mark Model Hierarchies task as done

JChris.FillionR at 22:30, 26 November 2019

2019-11-26T22:30:05Z

JChris.FillionR at 22:08, 26 November 2019

2019-11-26T22:08:35Z

JChris.FillionR at 22:06, 26 November 2019

2019-11-26T22:06:09Z

Show changes

@@ Line 224: / Line 224: @@
 With Slicer 5.0, the idea is to remove the [[Documentation/Nightly/Developers/Charts|Charts]] infrastructure based on jqPlot, and only keep
-the [[Documentation/Nightly/Developers/Plots|Plots]] infrastructure based on VTK Charts.
+the [https://slicer.readthedocs.io/en/latest/user_guide/modules/plots.html Plots] infrastructure based on VTK Charts.
 Ron's request: enable anti-aliasing (MSAA or FXAA) and use less subtle default colors (https://www.slicer.org/wiki/Slicer4:2012_GenericChartColors) to improve appearance.

@@ Line 77: / Line 77: @@
 See also https://issues.slicer.org/view.php?id=2608.
-Assign to Andras Lasso.  Estimated time 2-3 weeks
+Assign to Andras Lasso. - '''DONE''' {{done}}
 ====Coordinate system in files====

← Older revision		Revision as of 11:51, 22 January 2020
Line 76:		Line 76:

	See also https://issues.slicer.org/view.php?id=2608.		See also https://issues.slicer.org/view.php?id=2608.
		+
		+	Assign to Andras Lasso. Estimated time 2-3 weeks

	====Coordinate system in files====		====Coordinate system in files====

@@ Line 170: / Line 170: @@
 ====Remove BTX/ETX pairs====
 Once VTK7 is no longer supported, the old way for disabling python wrapping is no longer needed. According to my tests (Csaba), wrapping works fine in all of those cases, so the new way (#ifndef __VTK_WRAP__) is not needed either.
 ===Slicer 5.2: Backward incompatible changes===
@@ Line 237: / Line 225: @@
 Ron's request: enable anti-aliasing (MSAA or FXAA) and use less subtle default colors (https://www.slicer.org/wiki/Slicer4:2012_GenericChartColors) to improve appearance.

@@ Line 89: / Line 89: @@
 Remove Model Hierarchy feature and make sure that Subject Hierarchy covers all use cases.  This will impact ModelMaker, which should be converted to a simpler version that only returns models and not semantics.  Need to check extensions, especially SlicerDMRI, for any dependencies on Model Hierarchy. - '''DONE''' {{done}}
-==== Extension description file format ====
+====Extension description file format====
 Transition from [[Documentation/Nightly/Developers/Extensions/DescriptionFile|`.s4ext` text file]] to a json or yaml.
 ===Remove deprecated modules and/or Migrate to extension===
@@ Line 238: / Line 182: @@
 *Remove DICOM Networking (DIMSE) code https://discourse.slicer.org/t/dicom-retrieve-on-windows-10-there-is-no-service-listening-dicom-communications-no-telnet-connection-to-ports
 *Update the logo along [https://discourse.slicer.org/t/slicer-module-panel-icon-in-dark-mode/8353/3 as discussed here].

@@ Line 79: / Line 79: @@
 ====Coordinate system in files====
-To be consistent with the rest of the world: Save models and markups in LPS coordinate system by default. If no coordinate system is specified in input file, assume LPS.
+To be consistent with the rest of the world: Save models and markups in LPS coordinate system by default. If no coordinate system is specified in input file, assume LPS. See https://issues.slicer.org/view.php?id=4445
 ====Acquisition transform====

← Older revision		Revision as of 22:30, 26 November 2019
Line 88:		Line 88:

	Remove Model Hierarchy feature and make sure that Subject Hierarchy covers all use cases. This will impact ModelMaker, which should be converted to a simpler version that only returns models and not semantics. Need to check extensions, especially SlicerDMRI, for any dependencies on Model Hierarchy.		Remove Model Hierarchy feature and make sure that Subject Hierarchy covers all use cases. This will impact ModelMaker, which should be converted to a simpler version that only returns models and not semantics. Need to check extensions, especially SlicerDMRI, for any dependencies on Model Hierarchy.
		+
		+	==== Extension description file format ====
		+
		+	Transition from [[Documentation/Nightly/Developers/Extensions/DescriptionFile\|`.s4ext` text file]] to a json or yaml.

@@ Line 39: / Line 39: @@
 ===Slicer 5.0: Backward incompatible changes===
 ====Third-party library updates====
@@ Line 76: / Line 68: @@
 *GitHub PR: https://github.com/Slicer/Slicer/pull/1118
-The scene views feature does not work well for a long time now, and there is no consensus about what should be the scope it supports.
+====Revisit MRML Copy API====
-Suggestion:
+Copy method does not perform complete deep-copy in some classes. For Sequences, we need both DeepCopy (for node modifications) and ShallowCopy (for fast replay possible).
-*Do not save the state of all nodes: Support only display, view and hierarchy nodes.
+There are also too many variants of node copy methods, which makes it difficult to use them correctly.
-Notes:
+See also https://issues.slicer.org/view.php?id=2608.
-*2018-12-13: Jc: Following discussion with Ron, we should keep the SceneView functionality. All data should be associated with the "master" view, and scene view should be different combination of viewing parameters (layout, camera, visibility, etc ...). A mrb to consider for testing is the [http://slicer.kitware.com/midas3/slicerdatastore/view?itemId=126553&layout=layout LungSegments_scene.mrb]
+====Coordinate system in files====
-====Undo/Redo====
+To be consistent with the rest of the world: Save models and markups in LPS coordinate system by default. If no coordinate system is specified in input file, assume LPS.
-Potential fix (currently being tested by Kyle Sunderland and Andras Lasso): Add an "undo enabled" flag to vtkMRMLNode, disable it by default, only enable it for nodes that undo/redo has tested to work correctly. Preliminary tests show that the feature largely works, but there are complications with undo/redo of node add/remove actions and node references.
+====Acquisition transform====
-Notes:
+Enable acquisition transform by default, to show correct loading of tilted gantry images. It has proven to work well.  See https://github.com/Slicer/Slicer/commit/b7650af3c27f34fc894bfdd587f2a4c02ba62a8b
-*2018-12-13: Jc: Following discussion with Ron, would be nice to also have undo/redo for camera settings, field of view, etc ... within a given view. It is easy to inadvertently modify settings ... (e.g when trying to pan using a trackpad with shift+left click but inadvertently using only left click)
+====Model Hierarchies====
-====Removal of Charts based infrastructure====
+Remove Model Hierarchy feature and make sure that Subject Hierarchy covers all use cases.  This will impact ModelMaker, which should be converted to a simpler version that only returns models and not semantics.  Need to check extensions, especially SlicerDMRI, for any dependencies on Model Hierarchy.
-Ron's request: enable anti-aliasing (MSAA or FXAA) and use less subtle default colors (https://www.slicer.org/wiki/Slicer4:2012_GenericChartColors) to improve appearance.
+===Slicer 5.2: Backward incompatible changes===
-====Revisit MRML Copy API====
+====Build System Simplification====
-Copy method does not perform complete deep-copy in some classes. For Sequences, we need both DeepCopy (for node modifications) and ShallowCopy (for fast replay possible).
+*Pick the most recent reasonable CMake version and remove any complexities in the build system are only there to work around limitations of old CMake versions.
-There are also too many variants of node copy methods, which makes it difficult to use them correctly.
+*Consider any ways to streamline/simplify the configure and build process, even it if may require changing extensions.
-See also https://issues.slicer.org/view.php?id=2608.
+*Look for ways to minimize the effect of long directory path-related build issues.  Currently on mac and windows we are pushing the limit of path length unless very short paths are used (e.g. /s5 or d:\s5).  Reorganizing the build tree might give us more headroom.
 ====Remove remote data support from MRML====
@@ Line 129: / Line 113: @@
 *View layout IDs: View layout IDs are currently integer values, which makes it difficult to ensure that modules always choose unique IDs. We should switch to using string IDs. String IDs can may be prefixed with modulename+"." as we do it for singleton tags and node attributes. We may remain somewhat backward compatible by having SetLayoutID(int) method that maps known layout integer IDs to the new string IDs. See discussion here: https://github.com/Slicer/Slicer/pull/1061#discussion_r241825827
-====Coordinate system in files====
+====SceneViews====
-To be consistent with the rest of the world: Save models and markups in LPS coordinate system by default. If no coordinate system is specified in input file, assume LPS.
+Notes:
-====Acquisition transform====
+*2018-12-13: Jc: Following discussion with Ron, would be nice to also have undo/redo for camera settings, field of view, etc ... within a given view. It is easy to inadvertently modify settings ... (e.g when trying to pan using a trackpad with shift+left click but inadvertently using only left click)
-Enable acquisition transform by default, to show correct loading of tilted gantry images. It has proven to work well.  See https://github.com/Slicer/Slicer/commit/b7650af3c27f34fc894bfdd587f2a4c02ba62a8b
+====Removal of Charts based infrastructure====
-====Model Hierarchies====
+With Slicer 5.0, the idea is to remove the [[Documentation/Nightly/Developers/Charts|Charts]] infrastructure based on jqPlot, and only keep
-Remove Model Hierarchy feature and make sure that Subject Hierarchy covers all use cases.  This will impact ModelMaker, which should be converted to a simpler version that only returns models and not semantics.  Need to check extensions, especially SlicerDMRI, for any dependencies on Model Hierarchy.
+Ron's request: enable anti-aliasing (MSAA or FXAA) and use less subtle default colors (https://www.slicer.org/wiki/Slicer4:2012_GenericChartColors) to improve appearance.
 ===Remove deprecated modules and/or Migrate to extension===