[Paraview] New ParaView

[Arash Jahangir]

Thank you Andy and Berk.

It is almost a certainty that I will write an alternative GUI to the new 
ParaView.  This is not a poor reflection of the quality of Kitware's 
design or robustness of Qt...it is just that I am not keen of Qt 
license, especially for publicly funded projects like ParaView.

If the separation between the GUI and engine is clear enough in both the 
current and future versions of ParaView, then it should be fairly easy, 
if not trivial, to link the new releases with the current GUI.

I'd be willing to buy the documentation on the how to use the engine 
with alternate UI...but signing up for a developer course takes too much 
of the time I do not have.

regards,
Arash

PS does the new release of ParaView book discuss this topic?
PPS  When does the book discussing new ParaView will be released?


Berk Geveci wrote:
> For the record, there is a page on ParaView 3 and Qt licensing on the 
> ParaView Wiki:
> http://www.paraview.org/Wiki/ParaView_III_and_Qt_licensing.
>
> There is a very clear separation between GUI and engine codes. For 
> example, it is possible to drive the engine through python without 
> linking in any Qt dependent code. However, there is no good 
> documentation for developers at this time.
> I would not say it is an easy task to write an alternative GUI for 
> ParaView. ParaView III has 5 or more full-time, experienced developers 
> and it is taking us months (probably more than a year) to develop a 
> replacement for ParaView/Tk. Most of this effort is focused on the 
> GUI. ParaView/Tk GUI has a lot of man-years of effort as well.
>
> -Berk
>
> On 6/16/06, *Arash Jahangir* <arash at vije.ca <mailto:arash at vije.ca>> 
> wrote:
>
>     Hi,
>     As I understand it, the next version of ParaView will be Qt
>     based.  Personally I find the Qt license wanting and I wish
>     Kitware had chosen wxWidgets or FLTK, but it is probably too late
>     to ask for this...so I cut to the chase:
>
>     Will version 3 of ParaView provide clear separation between UI and
>     the functional code so that it is a relatively easy task to write
>     an alternate GUI for ParaView?  If so, how can I find
>     documentation on linking another GUI to the ParaView engine?
>
>     thanks,
>     Arash
>
>
>     _______________________________________________
>     ParaView mailing list
>     ParaView at paraview.org <mailto:ParaView at paraview.org>
>     http://www.paraview.org/mailman/listinfo/paraview
>
>
>

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