[Paraview-developers] ANN: ParaView Views and Representations Refactoring

[Utkarsh Ayachit]

John,

There's a branch on the ParaView stage named
paraview_views_refactoring. You should be able to check it out.
Therein there are tons of examples Just look at
vtkPVDataRepresentation subclasses. I have converted the existing
point sprite/surface lic representations to the new style as well. So
they can serve as examples. The Wiki page is still under construction.
I am going to put more details on the wiki page soon (hopefully by
this weekend).

Utkarsh

On Thu, Oct 14, 2010 at 12:13 AM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> Utkarsh
>
> I have a number of custom paraview representations under various stages of development at the moment. Are there any existing examples which use the newer vtkDataRepresentation style from which I can copy. I have one fully implemented representation which would benefit greatly from simplification (and others at earlier stages). (Any more detailed documentation than the wiki page you mentioned?)
>
> I'd be happy to be an early tester. I am interacting with the server manager directly to setup parameters so that I can render within the coprocessing framework - but without the python baggage - and have found it quite hard work to control everything.
>
> JB
>
> -----Original Message-----
> From: paraview-developers-bounces at paraview.org [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Utkarsh Ayachit
> Sent: 13 October 2010 16:24
> To: ParaView Developers
> Subject: [Paraview-developers] ANN: ParaView Views and Representations Refactoring
>
> Folks,
>
> Some of the most complicated components of the ParaView ServerManager
> have always been the Views and Repressentations. Now, that's not
> without good reason, they are indeed complex given the different
> scenarios and configurations and settings and modes that they are
> supposed to operate in. Developers writing views esp. render views and
> representation indeed have to be aware of all the nuances regarding
> data movement and distribution. Additionally developers had to
> construct complicated pipelines in ServerManager level making the code
> hard to read and customize. If anyone has undertaken an exercise of
> creating a special render view type, you'll know exactly what I am
> talking about.
>
> As the most recent avatar of the Views and Representations was being
> developed, VTK, inspired by ParaView views, built its own set of views
> and representations. It became apparent that even though
> views/representations will never be free of complex pipelines, the
> pipelines and much easier to understand and debug in the VTK world for
> the developers.
>
> For the past few weeks, we have been working on revising ParaView's
> views and representations to be more VTK-centric and minimize the
> complexity in the ServerManager layer. I'll be committing those
> changes soon. This does imply that any existing view and
> representations you may have developed will no longer work, however it
> should be fairly easy to convert them to the new style.
>
> I've started writing a Wiki page:
> http://paraview.org/ParaView3/index.php/Views_And_Representations
>
> More details to follow.
>
> There are some know regressions with this commit eg. outline/LOD
> delivery to client in tile-display mode isn't working, save geometry
> isn't working etc. These issues will be ironed out before the next
> release.
>
> If you see any other regressions, please let us know. Some turmoil is
> indeed expected on the dashboard for a few days after a commit of this
> magnitude.
>
> Utkarsh
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>