Difference between revisions of "Developer Meetings/20140128"

From Slicer Wiki
Jump to: navigation, search
m
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== To discuss ==
 
== To discuss ==
 
* New SlicerWizard to create extension (Matthew Woehlke). See [https://github.com/mwoehlke-kitware/Slicer/tree/3566-refactor-wizard mwoehlke-kitware/Slicer@3566-refactor-wizard ]
 
* New SlicerWizard to create extension (Matthew Woehlke). See [https://github.com/mwoehlke-kitware/Slicer/tree/3566-refactor-wizard mwoehlke-kitware/Slicer@3566-refactor-wizard ]
 +
 
* VTK6 integration status update (Yuzheng Zhou). See [https://docs.google.com/a/kitware.com/document/d/1tT4VBJtt6U0LUEyaNaW7hJIVbb2XqBdyEbQyfsmUq9I/edit integration status]
 
* VTK6 integration status update (Yuzheng Zhou). See [https://docs.google.com/a/kitware.com/document/d/1tT4VBJtt6U0LUEyaNaW7hJIVbb2XqBdyEbQyfsmUq9I/edit integration status]
 
** Why?
 
** Why?
−
*** VTK6 doesn't provide backwards compatibility for lots of API with VTK 4 and 5.
+
*** VTK 6 doesn't provide backwards compatibility for lots of APIs with VTK 4 and 5.
−
*** In VTK6, data and execution “models” are seperated. So vtkDataObject doesn't contain the pipeline information anymore.  
+
*** In VTK 6, data and execution “models” (algorithms) are seperated. A vtkDataObject doesn't contain the pipeline information anymore.  
 
** What are needed to do:
 
** What are needed to do:
−
*** Done: Build system migration (conditional build (VTK 5 or VTK 6) in Slicer and CTK)
+
*** Done: build system migration (conditional build Slicer and dependency projects using VTK 5 or VTK 6)
−
*** Done: Removal of VTK 4 backwards compatibility superclasses (vtkProcessObject, vtkSource and all of their subclasses)
+
*** Done: removal of VTK 4 backwards compatibility superclasses (vtkProcessObject, vtkSource and all of their subclasses)
−
*** In progress(90% done): Removal of the pipeline meta-data API from vtkDataObject (E.g. AllocateScalars(), SetWholeExtent(), etc.)
+
*** In progress (90% done): removal of the pipeline meta-data API from vtkDataObject (E.g. AllocateScalars(), SetWholeExtent(), etc.)
−
*** In progress(90% done): Removal of Data Objects’ Dependency on the Pipeline (RequestData(), ExecuteData(), SetInput(), etc.)
+
*** In progress (90% done): removal of Data Objects’ Dependency on the Pipeline (E.g. RequestData(), ExecuteData(), SetInput(), Update() etc.)
−
*** Testing (TODO)
+
*** TODO: testing
 +
 
 +
* vtkITK simplification:
 +
** https://github.com/blowekamp/Slicer/blob/2a0d0a8dffc5c0fe196724b9526c2a2a6e47ca27/Libs/vtkITK/vtkITKDistanceTransform.cxx
  
 
== Conclusion ==
 
== Conclusion ==
 +
 +
* vtkITK: VTKGlue ?

Latest revision as of 19:25, 28 January 2014

Home < Developer Meetings < 20140128

To discuss

  • VTK6 integration status update (Yuzheng Zhou). See integration status
    • Why?
      • VTK 6 doesn't provide backwards compatibility for lots of APIs with VTK 4 and 5.
      • In VTK 6, data and execution “models” (algorithms) are seperated. A vtkDataObject doesn't contain the pipeline information anymore.
    • What are needed to do:
      • Done: build system migration (conditional build Slicer and dependency projects using VTK 5 or VTK 6)
      • Done: removal of VTK 4 backwards compatibility superclasses (vtkProcessObject, vtkSource and all of their subclasses)
      • In progress (90% done): removal of the pipeline meta-data API from vtkDataObject (E.g. AllocateScalars(), SetWholeExtent(), etc.)
      • In progress (90% done): removal of Data Objects’ Dependency on the Pipeline (E.g. RequestData(), ExecuteData(), SetInput(), Update() etc.)
      • TODO: testing

Conclusion

  • vtkITK: VTKGlue ?
Retrieved from "https://www.slicer.org/w/index.php?title=Developer_Meetings/20140128&oldid=37158"