[Paraview] ANN: Upcoming changes to ParaView Server Manager

[Sven Buijssen]

Hi Seb,

http://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_an_object_panel shows
a trivial example of how to tweak a panel with some custom GUI elements. For
convenience, I've put the necessary code together in the attached archive.

With the Collaboration branch, this plugin's text "This is from a plugin" won't
get displayed any more in the panel of the Cone source for release builds.
A debug build of the code still compiles just fine against a Collaboration
branch debug build, even loads into it, but when creating a cone source,
ParaView crashes with

ERROR: In
/ParaViewCollaboration.git/ParaViewCore/ServerManager/vtkSMRemoteObject.cxx,
line 124
vtkSMSourceProxy (0x11a4730): GlobalID must NOT be changed once it has been
assigned.
Try to set 145 to replace the current 289 value.

Any idea what might need to be changed in order to get this working?
A different syntax for the ADD_PARAVIEW_OBJECT_PANEL in CMakeLists.txt maybe?

Thanks for any hint.

Sven


Sebastien Jourdain wrote, On 03/28/11 21:29:
> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: conepanel.zip
Type: application/zip
Size: 1340 bytes
Desc: not available
URL: <http://www.paraview.org/pipermail/paraview/attachments/20110330/b4c99f8f/attachment-0001.zip>