[Paraview-developers] Deprecating old-panels from ParaView

[burlen]

Thanks Utkarsh,

Please, post the final decision when it's made, if you decide to remove 
those classes I'lll have to rewrite a few classes in the SQ Plugin.

Burlen

On 08/14/2013 10:28 AM, Utkarsh Ayachit wrote:
> I meant removing, more than deprecating. The rough list of classes
> would include:
>
> * pqProxyPanel and subclasses (including pqObjectPanel,
> pqAutoGeneratedObjectPanel)
> (http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classpqObjectPanel.html)
> * pqSMAdaptor
>
> If plugins used old panels, they'd fail to build since they would more
> likely than not depend on one of these removed classes. I fear that as
> time progresses, these classes would decay since they are not actively
> used in ParaView and plugins would start failing in unexpected ways.
>
> Utkarsh
>
>
> On Wed, Aug 14, 2013 at 1:25 PM, burlen <burlen.loring at gmail.com> wrote:
>> Hi Utkarsh,
>>
>> deprecating or removing? is there a list of classes on the chopping block?
>> About the plugins included in PV would these be disabled if they use the old
>> widgets for custom panel?
>>
>> Burlen
>>
>>
>> On 08/14/2013 06:42 AM, Utkarsh Ayachit wrote:
>>> Folks,
>>>
>>> I wanted to get a feel for what people think about deprecating the
>>> support for old style panels from the next release of ParaView. The
>>> new panels have been around for 3 releases now (since Dec 2012). We
>>> are working on several cleanups to domains and other server manager
>>> level components to better integrate with Python and it would be nice
>>> to get rid of some of these obsolete components (which are quite a few
>>> classes that are now primarily unused).
>>>
>>> The next release is being targeted for Oct/Nov time frame.
>>>
>>> Utkarsh
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>