<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#009900">
Thank you Andy and Berk.<br>
<br>
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.<br>
<br>
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.<br>
<br>
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.<br>
<br>
regards,<br>
Arash<br>
<br>
PS does the new release of ParaView book discuss this topic?<br>
PPS When does the book discussing new ParaView will be released?<br>
<br>
<br>
Berk Geveci wrote:
<blockquote
cite="mida2ab21560606190739w36c9abaie068ee41dc496134@mail.gmail.com"
type="cite">For the record, there is a page on ParaView 3 and Qt
licensing on the ParaView Wiki:<br>
<a href="http://www.paraview.org/Wiki/ParaView_III_and_Qt_licensing">http://www.paraview.org/Wiki/ParaView_III_and_Qt_licensing</a>.<br>
<br>
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. <br>
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. <br>
<br>
-Berk<br>
<br>
<div><span class="gmail_quote">On 6/16/06, <b
class="gmail_sendername">Arash Jahangir</b> <<a
href="mailto:arash@vije.ca">arash@vije.ca</a>> wrote:</span>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div bgcolor="#ffffff" text="#009900">Hi,<br>
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:<br>
<br>
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?<br>
<br>
thanks,<br>
Arash<br>
<br>
</div>
</div>
<br>
_______________________________________________<br>
ParaView mailing list<br>
<a onclick="return top.js.OpenExtLink(window,event,this)"
href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)"
href="http://www.paraview.org/mailman/listinfo/paraview"
target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
<br>
<br>
</blockquote>
</div>
<br>
</blockquote>
<br>
</body>
</html>