[Paraview] ParaView 3 and PARAVIEW_EXTRA_EXTERNAL_MODULE

[Berk Geveci]

> The generated GUI cannot possibly know the labels, defaults and other
> particulars that are best for the GUI so I guess I'll have to write a plugin.

Actually, all of this is encoded into the server manager xml so there
is no need to write a plugin. Very few of the built-in filters have
custom gui, most use automatically generated panels. If you look at
the server manager xml, you will see default values, ranges (through
domains) and things to help the gui such as labels, hints etc...

-berk

>
> How do I do that and build the code into paraview during compilation? Loading
> things at every execution seems less reliable and could be difficult on
> parallel systems with no shared disk.
>
> Would I still use PARAVIEW_EXTRA_EXTERNAL_MODULE?
>
> TIA
> Kent
> Pittsburgh Supercomputing Center
>
> clinton at elemtech.com wrote:
> > On Friday 07 December 2007 12:24:44 pm Kent Eschenberg wrote:
> >> Clint,
> >>
> >> Thanks but those Wiki pages don't answer 2 important questions. I assume
> >> references to "GUI xml" and "client xml" are equivalent.
> >>
> >> 1) Where does all the information shown in the "Extend" example go, that
> >> gives the name of the C++ class and describes the GUI?
> >
> > Nowhere.  That is a Paraview 2.6 thing.
> >
> >> The example from
> >> "Plugin" (which you provided in your message, below) doesn't show any of
> >> that.
> >
> > ParaView3 generates the GUI automatically.  If the generated GUI isn't what
> > you want, you have to write a plugin.  The GUI/client xml I gave below is to
> > tell the file dialogs what file extensions go with what readers.
> >
> >> 2) What if the custom module is a filter not a reader?
> >
> > Then you don't have any GUI side xml or code at all.
> >
> > Clint
> >
> >> TIA
> >> Kent
> >> Pittsburgh Supercomputing Center
> >>
> >> linton at elemtech.com wrote:
> >>  > It is still supported.
> >>  > http://paraview.org/Wiki/ParaView:Extend
> >>  >
> >>  > On minor difference:  the GUI XML files give to
> >>  > PARAVIEW_INCLUDE_GUI_RESOURCES are as shown on
> >>  > http://paraview.org/Wiki/Plugin_HowTo#Adding_a_custom_filter.2C_reader_o
> >>  >r_writer
> >>  >
> >>  > <ParaViewReaders>
> >>  >   <Reader name="MyReader"
> >>  >           extensions="myreader mr"
> >>  >           file_description="My Reader Files">
> >>  >   </Reader>
> >>  > </ParaViewReaders>
> >>  >
> >>  > Clint
> >>  >
> >>  > On Thursday 06 December 2007 11:39:41 am Mike Jackson wrote:
> >>  >> Does ParaView 3.2.1 use the PARAVIEW_EXTRA_EXTERNAL_MODULE any more?
> >>  >> In previous versions (PV 2.6.x) I would set this to my reader/writer/
> >>  >> filter projects and directly build my code into the ParaView
> >>  >> Compilation. Is this still possible? From reading the wiki it seems
> >>  >> that you have to build ParaView first, then create the plugins?
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>