[vtk-developers] [vtkusers] VTK Roadmap

[Andrew Maclean]

David, Berk,
    That's good news about Python3.

Let me know what I can do to help with Python 3 when the time comes. I
think there will need to be some minor changes to the tests to make them
work Ok in python 3.x/2.7.

    David, aside from the wrapping are you also looking at the
FindPythonLibs.cmake and FindPythonModules.cmake? For instance if Anaconda
Python is installed in a user's directory in Windows then VTK requires the
user to manually set PYTHON_INCLUDE_DIR and PYTHON_LIBRARY. This does not
seem to be the case with the CMake versions.

   All the Tcl tests that are currently running (except for Tcl specific
ones)  have now been converted to Python. So we are in a good position
there.

Regards
   Andrew.

---------- Forwarded message ----------
> From: Berk Geveci <berk.geveci at kitware.com>
> To: David Gobbi <david.gobbi at gmail.com>
> Cc: VTK Developers <vtk-developers at vtk.org>, VTK Users <vtkusers at vtk.org>
> Date: Tue, 30 Jun 2015 16:24:17 -0400
> Subject: Re: [vtk-developers] [vtkusers] VTK Roadmap
> Yup. Python 3 is now on the roadmap. Probably the first release after 7,
>  in a few months.
>
> -berk
>
> On Tue, Jun 30, 2015 at 3:48 PM, David Gobbi <david.gobbi at gmail.com>
> wrote:
>
>> On Tue, Jun 30, 2015 at 12:47 PM, Matthew Brett <matthew.brett at gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> On Tue, Jun 30, 2015 at 10:58 AM, 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.
>>>
>>> I would like to put in a humble plea to add Python 3 compatibility to
>>> that list:
>>>
>>> http://astrofrog.github.io/blog/2015/05/09/2015-survey-results
>>
>>
>> Python 3 is being worked on (right now by me, and others can join in a
>> couple weeks once the core pieces are in place).  No, it won't be part of
>> 6.3, however.
>>
>>  - David
>>
>> _______________________________________________
>>
>
-- 
___________________________________________
Andrew J. P. Maclean

___________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20150701/457d4350/attachment.html>