[Paraview] adding existing VTK filter without recompiling
Sean Ziegeler
seanzig at users.sourceforge.net
Fri Apr 25 15:47:37 EDT 2008
That looks exactly like what I need. I just did a cvs update in my
ParaView3 working copy, but I don't see HelixSource. Is it in another
cvs branch?
clinton at elemtech.com wrote:
> Perhaps you'd like the new example in ParaView3/Examples/Plugins/HelixSource.
> See the attached screen shot. The panel for the HelixSource has a python
> script under it. And it didn't require compiling any plugins.
>
> Clint
>
> On Friday 25 April 2008 1:11:46 pm Sean Ziegeler wrote:
>> Yes, that takes care of part of it. However, it's not clear to me if or
>> how one might add extra parameters for the script, so that the script
>> itself doesn't need to be edited for simple parameters. Is that possible?
>>
>> -Sean
>>
>> Moreland, Kenneth wrote:
>>> Have you tried created a custom filter containing the programmable filter
>>> with your script? Once it is a custom filter you can export that to XML
>>> and let other users import it.
>>>
>>> -Ken
>>>
>>>> -----Original Message-----
>>>> From: paraview-bounces at paraview.org
>>>> [mailto:paraview-bounces at paraview.org] On Behalf Of Sean Ziegeler
>>>> Sent: Friday, April 25, 2008 9:30 AM
>>>> To: clinton at elemtech.com
>>>> Cc: paraview at paraview.org
>>>> Subject: Re: [Paraview] adding existing VTK filter without recompiling
>>>>
>>>> I wonder, would the ability to load server manager XML and client QRC
>>>> files at run time allow me to distribute, e.g., a specific python
>>>> script, to others and it show up as a unique reader/filter/writer with
>>>> its own GUI widgets?
>>>>
>>>> That would be more elegant and less tedious than the current way of
>>>> doing things, in which I just tell them "paste the following script into
>>>> the Programmable Filter and modify the parameters inside the script as
>>>> needed."
>>>>
>>>> Thanks,
>>>> Sean
>>>>
>>>> clinton at elemtech.com wrote:
>>>>> On Thursday 24 April 2008 4:20:46 pm Moreland, Kenneth wrote:
>>>>>> Clint,
>>>>>>
>>>>>> Great job as usual. If you have not already, please add a description
>>>> of
>>>>
>>>>>> this new functionality to the Wiki.
>>>>> Its already there:
>>>>> http://paraview.org/Wiki/ExtendingParaView#Loading_XML_at_runtime
>>>>>
>>>>> Clint
>>>>>
>>>>>> -Ken
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: paraview-bounces at paraview.org
>>>>>>> [mailto:paraview-bounces at paraview.org] On Behalf Of
>>>> clinton at elemtech.com
>>>>
>>>>>>> Sent: Thursday, April 24, 2008 2:10 PM
>>>>>>> To: paraview at paraview.org
>>>>>>> Subject: Re: [Paraview] adding existing VTK filter without
>>>>>>> recompiling
>>>>>>>
>>>>>>>
>>>>>>> The CVS version of ParaView will allow you to load server manager xml
>>>>>>> files
>>>>>>> without building plugins. It also supports loading Client side qrc
>>>> files
>>>>
>>>>>>> to
>>>>>>> add readers and writers without building plugins.
>>>>>>>
>>>>>>> Clint
>>>>>>>
>>>>>>> On Wednesday 23 April 2008 8:52:29 pm Greg Ushomirsky wrote:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> I'm trying to add an existing VTK filter to Paraview 3.2.1 for
>>>> Windows
>>>>
>>>>>>>> that I downloaded from Paraview.org. I'm trying to follow the
>>>>>>>> instructions on the wiki page
>>>>>>>> http://www.paraview.org/Wiki/ParaView:Extend. That page gives an
>>>>>>>> example of two XML files that would be needed to make the existing
>>>>>>>> vtkCellDerivatives filter accessible through the menus. I followed
>>>>>>>> the instructions, made the two XML files, and them, as the
>>>>>>>> instructions suggest:
>>>>>>>>
>>>>>>>> To load the XML file into the ParaView, we will go to menu File and
>>>>>>>> select Import Package. This will popup a dialog in which we can
>>>> select
>>>>
>>>>>>>> the appropriate XML file.
>>>>>>>>
>>>>>>>> Well, I go to the File menu, but there is no Import Package option!!
>>>>>>>>
>>>>>>>> So, do I really need to build paraview myself in order to add an
>>>>>>>> existing filter? Or am I missing something in the instructions??
>>>>>>>> Sure, I could build a plugin, but that requires building paraview
>>>> from
>>>>
>>>>>>>> source as well.
>>>>>>>>
>>>>>>>> thanks for the help,
>>>>>>>> Greg
>>>>>>>> _______________________________________________
>>>>>>>> ParaView mailing list
>>>>>>>> ParaView at paraview.org
>>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>>> _______________________________________________
>>>>>>> ParaView mailing list
>>>>>>> ParaView at paraview.org
>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>> _______________________________________________
>>>>> ParaView mailing list
>>>>> ParaView at paraview.org
>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>> _______________________________________________
>>>> ParaView mailing list
>>>> ParaView at paraview.org
>>>> http://www.paraview.org/mailman/listinfo/paraview
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
> ------------------------------------------------------------------------
>
More information about the ParaView
mailing list