Réf. : Re: [Paraview] Re: pv2.9 features...

[Stephane PLOIX]

Thanks for these infos, I managed to get my reader on.

For those interested, the file you need to touch to recompile the 
ParaViewReaders.xml file into pqComponents is the pqResources.qrc file

Stephane





Stephane

I have managed this morning to integrate our CFX reader into ParaQ (or 
Paraview III - which name is the official one?). Inside 
ParaViewReaders.xml you can add a brief name="myReader" and this can 
refer to the name in the provided servermanager XML file which is the 
same as for Paraview OLD. As you correctly discovered, the 
paraviewreaders.xml is bound into the ui resources of the mainwindow and 
so you need to regenerate/rebuild the qt interface.
using the PARAVIEW_EXTERNAL_MODULES to include our modules at build time 
- they are linked in and working. (I always used this method in the past 
because when you tried to dynamically load modules at run time, they 
never worked in parallel (for me))

The clever bit is that with no Client xml file used, it was able to 
create this panel!

ftp://ftp.cscs.ch/out/biddisco/paraview/cfx_panel.jpg

This is going to save so much time. Thank you very much for adding this 
feature.

JB

>
> Thanks for the reply,
>
> >>ParaView3 can create "panels" automatically based on the contents of 
> the server manager XML, which allows you to focus on creating filters 
> instead of writing UI.  You also have the option to >>create custom 
> panels using varying combinations of C++, Qt, and Qt designer if an 
> auto-generated panel doesn't meet your needs.
>
> I looked some more into the code, and it appears that we have to 
> modify the source code (or the source xml files) if we want to add any 
> new filter :
> My conclusions come from the fact that panels are generated as static 
> Qt interfaces (cf comment in pqObjectPanelLoader.h), and the xml files 
> are included into the vtkSMGeneratedModules.h file, which is the only 
> file used to initialize the application ( the method 
> addConfigurationFile is never called).
> Will we have the possibility to dynamically import package (via the 
> menu or the env variables)?
>
> The other point is that I can't find a xml file for the client as 
> those that where in the old GUI/Client/Resources dir.
> You say that the interface is generated from the SM xml, that means 
> that we can't choose specify the GUI other than by coding it in C++/Qt?
> What are the Qt/Components/Resources/XML/... files for?
>
> Many questions, because I am really interested by what you are doing 
> on Paraview3 ;-)
> Cheers,
> Stephane
>
>
> 
--------------------------------------------------------------------------------------------------------
> Stéphane Ploix
> Ingénieur Chercheur EDF R&D - Sinetics
> 1 avenue du Général de Gaulle
> F-91141 Clamart Cedex
> Tél : 01 47 65 51 10
> Messagerie : stephane.ploix at edf.fr
> ------------------------------------------------------------------------
>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
> 


-- 
John Biddiscombe,                            email:biddisco @ cscs.ch
http://www.cscs.ch/about/BJohn.php
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/paraview/attachments/20061010/c74a51f6/attachment.html