[Paraview] ANN: Upcoming changes to ParaView Server Manager

[Takuya OSHIMA]

Hi,

I think it would be helpful if there is a quick guidance about what
changes to what in typical cases, for example what I have figured out
for my plugin are (am I correct about all these?):

OLD: pxy->Set/GetServers() (where pxy is a vtkSMProxy)
NEW: pxy->Set/GetLocation()

OLD: pxy->Set/GetConnectionID()
NEW: pxy->Set/GetSession()

OLD: pxy->GetID()
NEW: VTKOBJECT(pxy) (a stream operator in client-server stream)

OLD: pm->SendSteram(this->GetConnectionID(), this->GetServers(), stream)
NEW: this->ExecuteStream(stream) (where this is a vtkSMProxy)

OLD: pm->SendStream(pxy->GetConnectionID(), pxy->GetServers(), stream)
NEW: pxy->GetSession()->ExecuteStream(pxy->GetLocation(), stream)
(where pm is a vtkProcessModule)

Also, what I noticed so far are
* CoProcessing module does not build due to some missing headers.
* ParaViewCore/ServerManager/vtkSMDataSourceProxy.{cxx,h} are orphaned
  (have no reference from other sources or CMakeLists).

Takuya

Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN

From: Sebastien Jourdain <sebastien.jourdain at kitware.com>
Subject: [Paraview] ANN: Upcoming changes to ParaView Server Manager
Date: Mon, 28 Mar 2011 15:29:14 -0400

> Folks,
> 
> For those of you who haven't follow the topic in the
> paraview-developers mailing list here is a quick summary on what's
> going on in the coming weeks.
> We've been working for a while now on restructuring the Server Manager
> of ParaView to make it more efficient as well as allowing it to
> support collaborative workflows.
> The API has undergone major changes and may cause some minor rewrite
> of your own code. Before we merge these changes to master, please try
> out the Collaboration branch with your code and let us know if you
> experience any issue.
> Please see below for the details on how to checkout the Collaboration branch.
> 
> Thanks for your support,
> 
> Seb
> 
> ============= From the ParaView-developer list ===============
> 
> Following up the mail from Utkarsh on the changes to ParaView Server Manager :
> 
> http://public.kitware.com/pipermail/paraview-developers/2011-February/000951.html
> 
> We finally push our branch to the stage. That branch will only be
> merged to master in the coming month.
> But if you have developed a plugin or any code based on ParaView and
> you want to test it against
> that major update, please follow the coming instructions and don't
> hesitate to send us your feed back.
> 
> In order to fetch our ParaView branch from stage, you will need to
> execute the following command line:
> 
> $ git clone --recursive git://paraview.org/stage/ParaView.git -b Collaboration
> 
> Then, as any regular ParaView source directory, you should be able to
> configure and build it.
> As some directory and kit renaming occurred, you may need to update
> the name of the ParaView library that you are linking against. Now the
> ParaViewCore package which used to be called "Servers" contains the
> following kits:
> vtkPVCommon, vtkPVClientServerCore, vtkPVServerImplementation,
> vtkPVServerManager, vtkPVVTKExtensions.
> 
> Please remember, these do not affect 3.10 or even 3.10.1. These will
> make into the
> official ParaView 4.0 release, nothing sooner.
> 
> Seb
> 
> PS: Additional informations on those changes are available here
> http://paraview.org/ParaView3/images/2/24/ParaViewCollaborationChanges.pdf
> _______________________________________________
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview