<br><font size=2 face="sans-serif">Thanks for these infos, I managed to get my reader on.</font>
<br>
<br><font size=2 face="sans-serif">For those interested, the file you need to touch to recompile the ParaViewReaders.xml file into pqComponents is the pqResources.qrc file<br>
<br>
Stephane</font>
<br>
<br>
<br>
<br>
<br>
<br><font size=2 face="Courier New">Stephane<br>
<br>
I have managed this morning to integrate our CFX reader into ParaQ (or <br>
Paraview III - which name is the official one?). Inside <br>
ParaViewReaders.xml you can add a brief name="myReader" and this can <br>
refer to the name in the provided servermanager XML file which is the <br>
same as for Paraview OLD. As you correctly discovered, the <br>
paraviewreaders.xml is bound into the ui resources of the mainwindow and <br>
so you need to regenerate/rebuild the qt interface.<br>
using the PARAVIEW_EXTERNAL_MODULES to include our modules at build time <br>
- they are linked in and working. (I always used this method in the past <br>
because when you tried to dynamically load modules at run time, they <br>
never worked in parallel (for me))<br>
<br>
The clever bit is that with no Client xml file used, it was able to <br>
create this panel!<br>
<br>
ftp://ftp.cscs.ch/out/biddisco/paraview/cfx_panel.jpg<br>
<br>
This is going to save so much time. Thank you very much for adding this <br>
feature.<br>
<br>
JB<br>
<br>
><br>
> Thanks for the reply,<br>
><br>
> >>ParaView3 can create "panels" automatically based on the contents of <br>
> the server manager XML, which allows you to focus on creating filters <br>
> instead of writing UI. You also have the option to >>create custom <br>
> panels using varying combinations of C++, Qt, and Qt designer if an <br>
> auto-generated panel doesn't meet your needs.<br>
><br>
> I looked some more into the code, and it appears that we have to <br>
> modify the source code (or the source xml files) if we want to add any <br>
> new filter :<br>
> My conclusions come from the fact that panels are generated as static <br>
> Qt interfaces (cf comment in pqObjectPanelLoader.h), and the xml files <br>
> are included into the vtkSMGeneratedModules.h file, which is the only <br>
> file used to initialize the application ( the method <br>
> addConfigurationFile is never called).<br>
> Will we have the possibility to dynamically import package (via the <br>
> menu or the env variables)?<br>
><br>
> The other point is that I can't find a xml file for the client as <br>
> those that where in the old GUI/Client/Resources dir.<br>
> You say that the interface is generated from the SM xml, that means <br>
> that we can't choose specify the GUI other than by coding it in C++/Qt?<br>
> What are the Qt/Components/Resources/XML/... files for?<br>
><br>
> Many questions, because I am really interested by what you are doing <br>
> on Paraview3 ;-)<br>
> Cheers,<br>
> Stephane<br>
><br>
><br>
> --------------------------------------------------------------------------------------------------------<br>
> Stéphane Ploix<br>
> Ingénieur Chercheur EDF R&D - Sinetics<br>
> 1 avenue du Général de Gaulle<br>
> F-91141 Clamart Cedex<br>
> Tél : 01 47 65 51 10<br>
> Messagerie : stephane.ploix@edf.fr<br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> ParaView mailing list<br>
> ParaView@paraview.org<br>
> http://www.paraview.org/mailman/listinfo/paraview<br>
> </font>
<br><font size=2 face="Courier New"><br>
<br>
-- <br>
John Biddiscombe, email:biddisco @ cscs.ch<br>
http://www.cscs.ch/about/BJohn.php<br>
CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07<br>
Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82<br>
<br>
<br>
</font>
<br>
<br>