Difference between revisions of "Documentation/Labs/SampleDataModuleImprovements"

From SlicerWiki
Jump to: navigation, search
(Initial discussions)
(Initial discussions)
 
Line 21: Line 21:
 
== Initial discussions ==
 
== Initial discussions ==
  
* Add <tt>setCategoryVisible(categoryName, visible)</tt> function to <tt>SampleData.SampleDataWidget</tt>
+
=== Meeting of June 11th, 2019 ===
 +
Attendees: Mateo, Jc
 +
 
 +
* Steps:
 +
** (1) Add <tt>setCategoryVisible(categoryName, visible)</tt> function to <tt>SampleData.SampleDataWidget</tt>
 +
** (2) Register the custom sample data source from the SlicerSALT home module. Create an issue named "Collect SampleData sources" into SlicerSALT where the info for each module will be collected. Link to https://github.com/Kitware/SlicerSALT/issues/119
 +
** (3) Improve presentation of SampleData by adding a new tab in the module panel. Two approaches
 +
*** "Workaround" specific to SlicerSALT done by injecting the tab after the onModuleSelected signal. [https://github.com/Slicer/Slicer/blob/master/Base/QTGUI/qSlicerModulePanel.h qSlicerModulePanel] class is responsible to display tab with acknowledgement and help
 +
*** "Integrated" approach where the module base class [https://github.com/Slicer/Slicer/blob/master/Base/QTCore/qSlicerAbstractCoreModule.h qSlicerAbstractCoreModule] would be updated to also return list of SampleData. This is more challenging as we have no C++ way to represent a SampleDataSource

Latest revision as of 10:06, 11 June 2019

Home < Documentation < Labs < SampleDataModuleImprovements

Overview

As part of the SALT project we are working on improving the Sample Data module as a way to help new SALT users jump-start using our software. The first person to suggest this was Andras Lasso

The plan involves:

  1. Improving the infrastructure of the Sample Data module, so it is possible to hide the default datasets in the Module.
  2. Add custom datasets to the Sample Data Module in SALT, built-in category will be hidden
  3. Improve the infrastructure of the Sample Data module so it can be included in modules as a tab

Team

  • JC Fillon-Robin
  • Bea Paniagua
  • Jared Vicory
  • Mateo Lopez (UNC)

Definitions

Initial discussions

Meeting of June 11th, 2019

Attendees: Mateo, Jc

  • Steps:
    • (1) Add setCategoryVisible(categoryName, visible) function to SampleData.SampleDataWidget
    • (2) Register the custom sample data source from the SlicerSALT home module. Create an issue named "Collect SampleData sources" into SlicerSALT where the info for each module will be collected. Link to https://github.com/Kitware/SlicerSALT/issues/119
    • (3) Improve presentation of SampleData by adding a new tab in the module panel. Two approaches
      • "Workaround" specific to SlicerSALT done by injecting the tab after the onModuleSelected signal. qSlicerModulePanel class is responsible to display tab with acknowledgement and help
      • "Integrated" approach where the module base class qSlicerAbstractCoreModule would be updated to also return list of SampleData. This is more challenging as we have no C++ way to represent a SampleDataSource