[Paraview] 3.2 Plugin loading

[Mike Jackson]

Sounds Great. What type of plugins can I put in there? Things that  
add custom GUIS? Custom Readers/Writers? Do you happen to have a  
sample project to go with the code?


-- 
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services


On Dec 5, 2007, at 3:26 PM, Sean Ziegeler wrote:

> Just wanted to let everyone know that I've finished and tested (on  
> Linux  x86_64 g++) the plugin directory feature.  Clint suggests  
> that I attach it to a bug report.  I must admit that I haven't  
> filed a bug report before.  I went to https://www.kitware.com/Bug/  
> and signed up for an account (I'm just waiting on the confirmation  
> email).  Anyway, someone let me know if that's not the right place  
> to do it.
>
> Thanks,
> Sean
>
> clinton at elemtech.com wrote:
>> Or you can attach it to a bug report, and I'll get it in the  
>> repository.
>> It should have a bug report anyway, if you want it in 3.2.2.
>> Thanks,
>> Clint
>> On Wednesday 05 December 2007 10:21:50 am Sean Ziegeler wrote:
>>> Actually, I recently finished the changes.  There was a little  
>>> more to
>>> it than I originally suspected, but it still wasn't that hard.  I  
>>> just
>>> need to test it now and then I'll be ready to send a patch to the  
>>> list.
>>>
>>> Thanks,
>>> Sean
>>>
>>> clinton at elemtech.com wrote:
>>>> I wonder if you still plan to do this?  Otherwise, I'll probably  
>>>> end up
>>>> doing it.
>>>>
>>>> Clint
>>>>
>>>> On Thursday 08 November 2007 12:42:53 pm Sean Ziegeler wrote:
>>>>> What do you all think of adding a minor convenience to the plugin
>>>>> loading process?  I know it isn't that hard, but many of my  
>>>>> users don't
>>>>> remember to use Plugin Manager or PV_PLUGIN_PATH, and don't  
>>>>> want to
>>>>> bother adding it to their dot-files.  Thus I am forced to wrap  
>>>>> all the
>>>>> executables with scripts that set it.
>>>>>
>>>>> What about the following alternative:
>>>>> Modify pqPluginManager::loadPlugins() to also load plugins from
>>>>> CMAKE_INSTALL_PREFIX/plugins  (where CMAKE_INSTALL_PREFIX gets  
>>>>> set in
>>>>> CMake).
>>>>>
>>>>> That way (assuming I do a make install) any plugins that I  
>>>>> place in the
>>>>> plugins directory get loaded.
>>>>>
>>>>> If you like it, what chance is there of getting it into the 3.2.1
>>>>> release?  I'm willing to try it myself and make a patch for you  
>>>>> all at
>>>>> Kitware.
>>>>>
>>>>> Thanks,
>>>>> Sean
>>>>>
>>>>> _______________________________________________
>>>>> 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