[vtk-developers] ANN: Deprecation/removal of Qt-based charts in VTK

[Bill Lorensen]

I don't think VTK has a policy. I have never (from day 1) been happy
about this. But, in the past, the developers priorities always seem to
be higher than the customers'.

Bill

On Tue, Oct 12, 2010 at 5:58 PM, Marcus D. Hanwell
<marcus.hanwell at kitware.com> wrote:
> Bill,
>
> They were part of previous VTK releases, and used by ParaView. I looked into
> it, and they are in 5.4 and 5.6, not built by default. They were never really
> integrated into the main VTK API, but sat alongside it.
>
> I guess they could all be marked as deprecated in 5.8 (I thought you might
> have concerns), and then removed in 6.0 if we need to do that for them. They
> are unlikely to have any development effort spent on them, and I don't think
> they are used in any projects.
>
> Where is the current policy regarding deprecating classes, and eventually
> removing them? It would be good to know what is required, but I take your
> point about backward compatibility.
>
> Marcus
>
> On Tuesday 12 October 2010 17:23:01 Bill Lorensen wrote:
>> Marcus,
>>
>> Were these classes ever part of a VTK release? If not, I don't see a
>> problem. If they were part of a release, then we have do deal with
>> backward compatibility.
>>
>> Bill
>>
>> On Tue, Oct 12, 2010 at 5:18 PM, Marcus D. Hanwell
>>
>> <marcus.hanwell at kitware.com> wrote:
>> > Hi,
>> >
>> > The Qt charts are being deprecated and removed from VTK. They are no
>> > longer being used in ParaView, and have been replaced by the new OpenGL
>> > based charts in VTK. The Qt charts have not been actively developed in
>> > quite some time now, but could be used outside of VTK if they are used
>> > in your applications. The next release will not have the Qt charts.
>> >
>> > The existing QVTKWidget etc will all continue to be used and supported,
>> > this just affects the Qt based charts/views. I intend to remove the code
>> > from VTK's master branch in Git on or after October 26 - please let me
>> > know before then if you have any specific concerns.
>> >
>