[vtk-developers] [vtkusers] VTK Roadmap

Will Schroeder will.schroeder at kitware.com
Wed Aug 5 15:33:27 EDT 2015


Berk let's not forget to add in interaction; e.g. multi-touch and more
advanced interaction techniques. There are also related topics such as the
impact on widgets, and potential changes to events/event processing

There are also some community support infrastructure, along the lines that
Bill is currently working on (remote modules) and other ways to contribute
and test code.

W

On Tue, Jun 30, 2015 at 1:58 PM, Berk Geveci <berk.geveci at kitware.com>
wrote:

> Hi folks,
>
> As Dave DeMarle mentioned, we are gearing towards a VTK 6.3 release. VTK 7
> will follow very shortly (in weeks). I'd like to shed some light here on
> our thinking and how we are planning to move forward.
>
> As was previously discussed in the VTK developers list [1] [2], we are
> considering maintaining VTK 6.x for a long time (3-5 years) while moving
> forward with VTK 7 and 8 in 2015 and 2016. There are some major changes
> happening in the computing and C++ worlds and we would like evolve VTK more
> quickly to stay up to date. Some of the major changes that we are
> considering and/or working on are:
>
> * Major refactoring of rendering (OpenGL as well as ray tracing etc.)
> * Multi/many-core support / SMP computing on CPUs and accelerators. VTK-m
> integration [3].
> * Changes to data model to support zero copy interface to other data
> layouts, more efficient APIs, more cell types, more dataset types etc.
> * Better separation of a public, wrapped API and toolkit/C++ internal API
> mainly to support efficiency
> * Introduction of C++ 11 features
>
> Much of this will require introducing changes that break backwards
> compatibility and also require newer compilers, graphics cards / drivers
> etc. So the idea is that we will do our best to support as much as possible
> a broad set of architectures and backwards compatibility but break things
> when necessary in VTK 7 and beyond. We will maintain VTK 6.x so that folks
> that are stuck on legacy systems or code bases can continue to benefit from
> bug fixes. We have a way of continuing to maintain a broad set of
> dashboards and also the same review process as VTK master so that we can
> continue to ensure the quality of VTK 6.x as well as new releases.
>
> What do you guys think? Please provide feedback so that we can adjust our
> plans to meet the needs of the community as much as possible.
>
> Best,
> -berk
>
> [1] : http://bit.ly/1BUHFKT
> [2] : http://bit.ly/1g7LSRG
> [3] : http://m.vtk.org/
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Search the list archives at: http://markmail.org/search/?q=vtkusers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/vtkusers
>
>


-- 
William J. Schroeder, PhD
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
will.schroeder at kitware.com
http://www.kitware.com
(518) 881-4902
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20150805/00704775/attachment.html>


More information about the vtk-developers mailing list