[Paraview-developers] Upcoming changes to ParaView Server Manager

[Utkarsh Ayachit]

John,

In my mind, SI* stuff is simply the vtkClientServerStream part from
vtkSMProperty subclass moved to a separate class. Now SMProperty and
SIProperty need to talk to each other and that's done using protobuf
state messages.

Are your property subclasses adding new API or simply changing how the
stream is being constructed to update the VTK object? If latter then
you can get by with just using the SIProperty subclass.

In the xml, you tell which SI* class to create using the si_class attribute.

If you have any specific questions, feel free to holler.

Utkarsh

On Thu, Apr 21, 2011 at 8:17 AM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> I have some customized properties
> vtkSMCommandProperty (subclass of vtkIntVectorProperty)
> vtkSMDataExportProperty (subclass of vtkStringVectorProperty)
>
> which now need accompanying
> vtkSICommandProperty
> vtkSIDataExportProperty
>
> I'm not sure what goes in the vtkSIXXXProperty classes. Do I need to move the xml stuff from SM to SI or anything?
> I have read http://paraview.org/ParaView3/images/2/24/ParaViewCollaborationChanges.pdf
> but am a little unsure of where my code should go.
>
> I will of course pick it up by trial and error, but if there are any things I ought to know. Please let me know.
> (we're taking known unknowns here, as opposed to unknown unknowns)
>
> thanks
>
> JB
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>