[Paraview] Multi-core custom applications

[Utkarsh Ayachit]

No, it doesn't need the path. It will just allow you to pick a name of
known configurations. You can make ParaView aware of the pvsc
configuration by importing it in the "Add Server" option in the
"Connect" dialog.
Actually, ParaView already support specifying the configuration to
connect to on startup as a command line argument. If have a
configuration named "miranda", I can run ParaView as:

> ./bin/paraview --server=miranda

and than will connect using the configuration on launch.

Utkarsh

On Mon, Feb 10, 2014 at 4:54 PM, Burlen Loring <bloring at lbl.gov> wrote:
> so then the multicore config in the setting menu has an entry for a pvsc
> path? If so, that sounds wonderful!
>
>
> On 02/10/2014 01:17 PM, Utkarsh Ayachit wrote:
>>
>> On Mon, Feb 10, 2014 at 4:13 PM, Burlen Loring <burlen.loring at gmail.com>
>> wrote:
>>>
>>> right, but just as the current multicore makes it easy for the user, this
>>> would all happen automatically as PV starts. So when multicore is on, the
>>> baked in multicore pvsc dialog is presented as pv starts, the user
>>> reviews
>>> the defaults, and hits OK, and pv starts up connected to a server. same
>>> as
>>> multicore is now, but with the possibility to review the run parameters.
>>
>> That is pretty much what I meant by adding support for a "default
>> server". Only difference being the user could change that from the
>> settings dialog after which when paraview starts up, it will
>> automatically try to connect to the "default server" selected, instead
>> of builtin, complete with all the prompts etc.
>
>