[vtk-developers] [vtkusers] VTK 4 compatibility removal - update

[Berk Geveci]

The changes that I am making will live on its own branch for a while -
I suspect 2-3 months.
I'd recommend making the necessary fixes to Slicer master during that
time. That way, by
the time I merge, there would be no need to change Slicer. And this
would prevent any
divergence of code. This would probably require regularly merging from
VTK master to
my branch (or at least some sort of integration branch) and that can
be arranged.

-berk


On Thu, May 12, 2011 at 2:35 PM, Steve Pieper <pieper at ibility.net> wrote:
> Hi Guys -
>
> An informal poll of slicer developers the other day raised a lot of concerns
> along the lines Bill is raising.
>
> For slicer 3.x, our current release, we can stick with vtk older releases so
> that's not a problem.
>
> But for slicer 4.x, Jc and Julien have been trying to keep slicer's version
> of vtk (https://github.com/Slicer/VTK) pretty close to the vtk master since
> there's a lot of joint development on charts, widgets, volume rendering and
> so forth.  Once Berk's changes go into the vtk master, the Slicer/VTK
> version will end up diverging until the few thousand issues Bill found can
> be dealt with.  This is not ideal, but probably manageable for a while.
>
> -Steve
>
>
> On Thu, May 12, 2011 at 2:16 PM, Bill Lorensen <bill.lorensen at gmail.com>
> wrote:
>>
>> Berk,
>>
>> I realize that the ARB did talk about this. I suggest that after you
>> finish your pass through VTK and Paraview, that you describe your experience
>> to the ARB so that we can understand the impact on VTK customers.
>>
>> Bill
>>
>
>