Hi Utkarsh,

this looks great.

One thing I have encountered and that you may want to think about is that a single static pvsc is not going to work for all users as pvsc's depend on external components such as xterm, ssh, and plink. These are in different places on different user's systems, maybe not present on the user's system leading to the pvsc not working.

I could see a couple of different avenues to solve this: Probably the best would be to integrate ssh tunneling into PV via libssh so that these dependencies are not needed. An aleternative would be to include a configure step in your new pvsc import process (like cmake) where dependencies are located and a system specific pvcs is generated. Something far easier and less intrusive might be to add a file dialog element to the pvsc syntax so that the user could easily browse for these files. That's not as nice as the other approaches because it clutters the UI and the user still has to hunt down the files, but it at least gives them a method to do so.

Burlen

On 08/19/2011 02:15 PM, Utkarsh Ayachit wrote:
Folks,

A feature we are thinking of implementing for ParaView 4.0 is to make
it easier to distribute pvsc files to connect to various HPC
resources. I've sketched out a rough proposal for the same at
http://paraview.org/ParaView3/index.php/Distributing_Server_Configuration_Scripts

Any comments/suggestions are always welcome.

Utkarsh
_______________________________________________
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

_______________________________________________
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

Reply via email to