Developer Meetings/20130205

From Slicer Wiki
Jump to: navigation, search
Home < Developer Meetings < 20130205

To discuss

  • Hide from editors flag on mrml nodes, bug 2906
    • model hierarchy optimizations causing unexpected behaviour
  • Failing tests - ITKv4 and otherwise
  • Wiki updates
    • Re-organized FAQs
      • Sub section of FAQ (UserInterface, DICOM, ...) can be included where it matters. For example see here and here
      • Created a developer FAQ. See here
      • FAQ page now redirect to Documentation/Nightly/FAQ. See here
    • Added a Roadmap & priority page - See http://www.slicer.org/wiki/Roadmap
  • Build instruction: Pre-requisites are not included directly in the page. (Still need to consolidate Qt prereqs)
  • CMake'ified python - Making progress

Conclusion

  • Discussed issue bug 2906
    • After 4.3.0 is released, the default value associated with HideFromEditor will be set to false in the base class.
    • This is captured in the "API changes roadmap". See http://www.slicer.org/wiki/Roadmap#4.4.0_2
    • Also discuss that the search/filter box associated with the data model could be extended to understand more complex expression. This would allow to easily hide or show element of the tree based on regular expression.
  • Discuss MRML scene versionning
    • Since Sept 2012, there is a property named MRML_SUPPORT_VERSION in Libs/MRML. See here
    • Possibility of having a XSD schema for MRML scene that would be updated for each change in MRML API. Would the introduction of such a schema imply major change in the current XML structure ?
  • Nicole discussed the recent changes associated with ModelMaker.
    • It can now take a "template model hierarchy" as an argument. More details associated with the commit message: here
  • Discussed issue that Steve was having when running CTest
    • This was due to the fact he updated PATH manually to include some other tools that were conflicting with ctest.
  • Worked on issue 2915
    • Identified some design flaw in the way "Shared library" CLI are executed. Investigation are on-going. Make sure to follow the issue to get update.