<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
color:#009900;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Courier New";
color:maroon;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>One thing that
has not been mentioned on this thread, but should be made explicit, is that the
license for ParaView is NOT changing. ParaView 3 will be released in its
entirety with the same BSD-like license for general use.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>The only caveat
here is that if you modify ParaView 3’s client code without a Qt
developer’s license, you will taint the code with the GPL (which is why
we will be careful with who has direct write access to that part of the
repository).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'>-Ken<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=maroon face="Courier New"><span
style='font-size:10.0pt;font-family:"Courier New";color:maroon'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt;color:windowtext'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 color=black face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight:bold'>From:</span></font></b><font
size=2 color=black face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
color:windowtext'> paraview-bounces+kmorel=sandia.gov@paraview.org
[mailto:paraview-bounces+kmorel=sandia.gov@paraview.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Arash Jahangir<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, June 19, 2006 8:59
AM<br>
<b><span style='font-weight:bold'>To:</span></b> Berk Geveci<br>
<b><span style='font-weight:bold'>Cc:</span></b> paraview@paraview.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [Paraview] New
ParaView</span></font><font color=black><span style='color:windowtext'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 color="#009900" face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color="#009900" face="Times New Roman"><span
style='font-size:12.0pt'>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: <o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color="#009900"
face="Times New Roman"><span style='font-size:12.0pt'>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<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><span class=gmailquote><font size=3 color="#009900"
face="Times New Roman"><span style='font-size:12.0pt'>On 6/16/06, <b><span
style='font-weight:bold'>Arash Jahangir</span></b> <<a
href="mailto:arash@vije.ca">arash@vije.ca</a>> wrote:</span></font></span> <o:p></o:p></p>
<div>
<div bgcolor="#ffffff" text="#009900">
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color="#009900"
face="Times New Roman"><span style='font-size:12.0pt'>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<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color="#009900"
face="Times New Roman"><span style='font-size:12.0pt'><br>
_______________________________________________<br>
ParaView mailing list<br>
<a href="mailto:ParaView@paraview.org">ParaView@paraview.org</a><br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
<br>
<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 color="#009900" face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color="#009900" face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
</body>
</html>