I would wait a few months until the release of 3.0. We are likely to make changes to the python interface.<br><br>-berk<br><br><div><span class="gmail_quote">On 2/13/07, <b class="gmail_sendername">Milan Frank</b> <<a href="mailto:milan.frank@gmail.com">
milan.frank@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi all,<br><br>recently I have tested my Python script with ParaView 3 executive. The
<br>script has been developed with Python interface of ParaView 2.6.<br><br>So far, I have noticed several changes in the interface (from 2.6 to 2.9) :<br>1) I was in need to explicitly specify render interactor style (there
<br>is no longer a default one).<br>2) UpdateDataInformation method is no longer part of the vtkSMSourceProxy.<br>3) I am getting "RenderModuleHelper not set" error from vtkSMLODDisplayProxy.<br><br>At this point I have stopped my experiments and decided to post my question.
<br><br>Is now the right time to migrate to the ParaView 3?<br><br>I guess there is several more things different. So it will cost me not<br>negligible effort to accommodate my code to the changes. I am<br>concerned about the amount of modification most likely to happen in
<br>the near future in the server manager part (and its python interface)<br>of ParaView 3.<br><br>Any hints will be appreciated as they will help me to plan my work better.<br><br>Thanks,<br>Milan<br>_______________________________________________
<br>ParaView mailing list<br><a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br><a href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</a><br></blockquote>
</div><br><br clear="all"><br>-- <br> Berk Geveci<br> Kitware Inc.<br> 28 Corporate Drive<br> Clifton Park, NY, 12065