No subject
Wed Oct 7 22:37:18 EDT 2009
mporary distros would it make any sense at all to perhaps maintain backward=
compatibility for some small window of time? eg: if in early 2009 qt 4.5 i=
s commonly used by the KDE distro's then for all of 2010 paraview supports =
at a minimum qt4.5.
If it were just for developers I'd say no, but since anyone who wants to ta=
ke advantage of parallel pv has to compile. this type of thing has potentia=
l to affect a bunch of users as well.
Utkarsh Ayachit wrote:
Folks,
As we are approaching 3.8 branch, what does everyone think of making
Qt 4.6 the officially supported version? Quite a few of us have been
using Qt 4.6 for quite some time now and don't think there are any
issues.
Utkarsh
_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org <mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers <http://publ=
ic.kitware.com/mailman/listinfo/paraview-developers>
_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org <mailto:Paraview-developers at paraview.org>
http://public.kitware.com/mailman/listinfo/paraview-developers <http://publ=
ic.kitware.com/mailman/listinfo/paraview-developers>
_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org
http://public.kitware.com/mailman/listinfo/paraview-developers
Ce message et toutes les pi=E8ces jointes (ci-apr=E8s le 'Message') sont =
=E9tablis =E0 l'intention exclusive des destinataires et les informations q=
ui y figurent sont strictement confidentielles. Toute utilisation de ce Mes=
sage non conforme =E0 sa destination, toute diffusion ou toute publication =
totale ou partielle, est interdite sauf autorisation expresse.
Si vous n'=EAtes pas le destinataire de ce Message, il vous est interdit de=
le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou pa=
rtie. Si vous avez re=E7u ce Message par erreur, merci de le supprimer de v=
otre syst=E8me, ainsi que toutes ses copies, et de n'en garder aucune trace=
sur quelque support que ce soit. Nous vous remercions =E9galement d'en ave=
rtir imm=E9diatement l'exp=E9diteur par retour du message.
Il est impossible de garantir que les communications par messagerie =E9lect=
ronique arrivent en temps utile, sont s=E9curis=E9es ou d=E9nu=E9es de tout=
e erreur ou virus.
____________________________________________________
This message and any attachments (the 'Message') are intended solely for th=
e addressees. The information contained in this Message is confidential. An=
y use of information contained in this Message not in accord with its purpo=
se, any dissemination or disclosure, either whole or partial, is prohibited=
except formal approval.
If you are not the addressee, you may not copy, forward, disclose or use an=
y part of it. If you have received this message in error, please delete it =
and all copies from your system and notify the sender immediately by return=
message.
E-mail communication cannot be guaranteed to be timely secure, error or vir=
us-free.
_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org
http://public.kitware.com/mailman/listinfo/paraview-developers
**** Kenneth Moreland
*** Sandia National Laboratories
***********
*** *** *** email: kmorel at sandia.gov
** *** ** phone: (505) 844-8919
*** web: http://www.cs.unm.edu/~kmorel
--_000_C7958A6B11A5Akmorelsandiagov_
Content-Type: text/html;
charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
<HTML>
<HEAD>
<TITLE>Re: [Paraview-developers] Requiring Qt 4.6 for ParaView 3.8</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>How good is Qt at maintaining forward compatibility with, for example=
, its ui file format. If all the developers are on 4.6 and someone ma=
kes a change with Qt Designer to one of the ui files, will the change break=
all the 4.5 builds?<BR>
<BR>
-Ken<BR>
<BR>
<BR>
On 2/8/10 8:21 AM, "Utkarsh Ayachit" <<a href=3D"utkarsh.ayach=
it at kitware.com">utkarsh.ayachit at kitware.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Those are indeed good and valid points. We =
were discussing a possible policy and here's what we have. What does everyb=
ody think?<BR>
<BR>
* There will 1 officially supported Qt version. This is the Qt version our =
binaries will be released with. The officially supported Qt version will re=
main fixed for 2 revisions e.g. 3.8 and 3.10 both will officially support t=
he same Qt version. There will be a minimum Qt version below which it canno=
t compile (for 3.8 this will be Qt 4.5). However the minimum version may go=
higher in every release (but <=3D the official Qt version) depending on=
whether we end up using some latest Qt functionality =A0provided by the of=
ficially supported release.<BR>
<BR>
* Let Qt 4.6 be an exception, since Qt 4.6 is required to build on Snow Leo=
pard and it's a nightmare to support different versions on different platfo=
rms. So 3.8 and 3.10, will be requiring Qt 4.6 (with min. Qt 4.5)<BR>
<BR>
* CMake will flag an error when the Qt version is below the minimum; a warn=
ing when the Qt version is below the official =A0(but above the min.) and b=
e silent with the Qt version is same as the official or above.<BR>
<BR>
* Any user-interface related issues for any Qt version, but the official ve=
rsion may not be addressed.<BR>
<BR>
* We'll always have a dashboard machine compiling with the latest Qt so tha=
t there will be no surprises when we switch to the latest Qt.<BR>
<BR>
* After two consecutive major releases (not patch releases) have stuck with=
the same QT version and it's time to upgrade to a newer Qt version, we'll =
pick the latest Qt version released at least 3 months prior to the release.=
<BR>
<BR>
How does that sound? If it's acceptable, I can post it to the Wiki as the o=
fficial policy for Qt version updating.<BR>
<BR>
Utkarsh<BR>
<BR>
<BR>
On Mon, Feb 8, 2010 at 3:32 AM, Stephane PLOIX <<a href=3D"stephane.ploi=
x at edf.fr">stephane.ploix at edf.fr</a>> wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'><BR>
Hi, <BR>
<BR>
I think that we have to be carefull : with the branding refactoring making =
it easy to build applications on top of ParaView components, and the PV_INS=
TALL_DEVELOPMENT options, ParaView should now be considered more like an SD=
K than a stand-alone application. <BR>
<BR>
As more and more applications are built on top of PV, changing the version =
of Qt will impact all those applications, you should then have a clear poli=
cy regarding those versions, and give a advanced warning of any changed to =
come. <BR>
<BR>
Some possible policy would be : <BR>
at each release of a new stable version of Qt, PV will support both the new=
and the old versions for 1 year, and drop the previous version after that =
<BR>
or <BR>
each stable version of ParaView will support both the lastest stable versio=
n of Qt and the previous one <BR>
<BR>
or whatever, but please make it a public policy so that we know what to exp=
ect. <BR>
<BR>
Best <BR>
Stephane<BR>
<BR>
<BR>
<BR>
<BR>
</SPAN><FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'><B><a href=3D"berk.g=
eveci at kitware.com">berk.geveci at kitware.com</a></B></SPAN></FONT><SPAN STYLE=
=3D'font-size:11pt'> <BR>
</SPAN><FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'>Envoyé par : =
<a href=3D"paraview-developers-bounces at paraview.org">paraview-developers-bo=
unces at paraview.org</a></SPAN></FONT><SPAN STYLE=3D'font-size:11pt'> </SPAN>=
<FONT SIZE=3D"2"><SPAN STYLE=3D'font-size:10pt'>07/02/2010 21:48</SPAN></FO=
NT><SPAN STYLE=3D'font-size:11pt'>=20
</SPAN></FONT>
<P ALIGN=3DRIGHT>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><FONT SIZE=3D"2"><SPAN ST=
YLE=3D'font-size:10pt'>A
</SPAN></FONT></FONT>
<P>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><FONT SIZE=3D"2"><SPAN ST=
YLE=3D'font-size:10pt'><a href=3D"burlen.loring at gmail.com">burlen.loring at gm=
ail.com</a></SPAN></FONT><SPAN STYLE=3D'font-size:11pt'>=20
</SPAN></FONT>
<P ALIGN=3DRIGHT>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><FONT SIZE=3D"2"><SPAN ST=
YLE=3D'font-size:10pt'>cc
</SPAN></FONT></FONT>
<P>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><FONT SIZE=3D"2"><SPAN ST=
YLE=3D'font-size:10pt'><a href=3D"paraview-developers at paraview.org">paravie=
w-developers at paraview.org</a></SPAN></FONT><SPAN STYLE=3D'font-size:11pt'>=
=20
</SPAN></FONT>
<P ALIGN=3DRIGHT>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><FONT SIZE=3D"2"><SPAN ST=
YLE=3D'font-size:10pt'>Objet
</SPAN></FONT></FONT>
<P>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><FONT SIZE=3D"2"><SPAN ST=
YLE=3D'font-size:10pt'>Re: [Paraview-developers] Requiring Qt 4.6 for ParaV=
iew 3.8</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'> <BR>
<BR>
<BR>
<BR>
<BR>
</SPAN><FONT SIZE=3D"4"><SPAN STYLE=3D'font-size:14pt'>I wouldn't object to=
supporting 4.5 and 4.6. I think setting up 1-2 dashboards to verify buildi=
ng with 4.5 would be enough. We don't run into Qt specific bugs too often a=
nyway. I defer to Utkarsh though.<BR>
<BR>
Also, if there is an attractive feature on the latest version of Qt that wi=
ll make our lives much easier, we are likely to move to it and not support =
the previous version. So, I don't want to have an official rule about suppo=
rting more than 1 version.<BR>
<BR>
-berk<BR>
<BR>
</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN><FONT SIZE=3D"4"><SPAN STYLE=3D'font-size:14pt'>On Sun, Feb 7, 2010 =
at 3:08 PM, burlen <<FONT COLOR=3D"#0000FF"><U><a href=3D"burlen.loring@=
gmail.com">burlen.loring at gmail.com</a></U></FONT></SPAN></FONT><SPAN STYLE=
=3D'font-size:11pt'> <<a href=3D"mailto:burlen.loring at gmail.com">mailto:=
burlen.loring at gmail.com</a>> </SPAN><FONT SIZE=3D"4"><SPAN STYLE=3D'font=
-size:14pt'>> wrote:</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'> <BR>
</SPAN><FONT SIZE=3D"4"><SPAN STYLE=3D'font-size:14pt'>Will this mean that =
PV won't build with any thing less than Qt 4.6?<BR>
I wonder if it would make sense to have a small range of supported versions=
rather than a single one?<BR>
<BR>
It's currently the case that with qt anything less than 4.5 pv fails to com=
pile (even if you remove the version test in cmakelists) because pv uses so=
me qt classes that were only added to 4.5. In my opinion it would be a burd=
en to pv users to get too far ahead of the various KDE supported distro's p=
ackages. eg. Kubuntu 9.10 reports qt version 4.5.2. KUbuntu 8.04.4 LTS repo=
rts qt version 4.3.4.<BR>
<BR>
More information about the Paraview-developers
mailing list