[vtkusers] [EXTERNAL] [vtk-developers] vtk 6.3 and vtk 7.0

[Gerrick Bivins]

“* deprecate the existing zero copy array API in preparation for a significant refactoring that will come in 7.0. The refactor will make zero copy arrays both simpler to use and perform better.”

Where can I find more information about this?
Does the “Zero copy array refactor” expose this framework to wrapped languages, Java in particular?
Currently the duplication of data is one of the things holding up adoption of VTK in our application.

Gerrick

From: vtk-developers [mailto:vtk-developers-bounces at vtk.org] On Behalf Of David E DeMarle
Sent: Monday, June 29, 2015 9:42 AM
To: vtkdev; vtkusers at vtk.org
Subject: [EXTERNAL] [vtk-developers] vtk 6.3 and vtk 7.0

Hey vtkers,

We are hoping to do a vtk 6.3 release in the next couple of weeks and then immediately follow that up with a 7.0 release.

We'd are putting out a 6.3 out in order to:
* deprecate the existing zero copy array API in preparation for a significant refactoring that will come in 7.0. The refactor will make zero copy arrays both simpler to use and perform better.
* package up all of the progress that has been made in the master branch's OpenGL2 surface and volume rendering. The vtkpython binaries will switch over to using the OpenGL2 back end this release.

Please let us know if you have any feedback, critical bugs especially, and developers let us know if there is any work you have in a partially finished state that we should be sure to get into 6.3.

If all goes well we'll have a release candidate for 6.3 next week.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

----------------------------------------------------------------------
This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient.  Any review, use, distribution, or disclosure by others is strictly prohibited.  If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20150629/2a573746/attachment.html>