<HTML dir=ltr><HEAD><TITLE>[Paraview] Re: ParaView Digest, Vol 32, Issue 23</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.5730.11" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText60160 dir=ltr>
<DIV dir=ltr><FONT face="Courier New" color=#000000 size=2>I'm pretty sure the current use of this feature at Sandia is zero. All of our distributions of ParaView use either a hardware driver or straight Mesa, not both. As several other members of these lists have just testified, it's much easier.</FONT></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>Concerning the maintenance overhead of maintaining the mangled Mesa stuff, I would rather have someone from Kitware speak to that since they are really the ones doing that. I recall Berk grumbling about it in the past. Perhaps he can elaborate.</FONT></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>I also cannot speak for any other organizations that may be using VTK/ParaView. If any of you out there use the vtkMesa* classes or otherwise compile with the mangled Mesa features, now would be a really good time to chime in.</FONT></DIV>
<DIV dir=ltr><FONT face="Courier New" size=2></FONT> </DIV>
<DIV dir=ltr><FONT face="Courier New" size=2>-Ken</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> paraview-bounces+kmorel=sandia.gov@paraview.org on behalf of James P. Ahrens<BR><B>Sent:</B> Sat 12/30/2006 4:35 PM<BR><B>To:</B> paraview@paraview.org<BR><B>Cc:</B> ahrens@lanl.gov<BR><B>Subject:</B> [Paraview] Re: ParaView Digest, Vol 32, Issue 23<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>> Message: 1<BR>> Date: Fri, 29 Dec 2006 09:05:35 -0600<BR>> From: "Randall Hand" <randall.hand@gmail.com><BR>> Subject: Re: [Paraview] RE: [vtkusers] MangledMesa & VTK<BR>> To: "Sean Ziegeler" <seanzig@users.sourceforge.net><BR>> Cc: paraview-developers@public.kitware.com, VTK Users<BR>> <vtkusers@vtk.org>, paraview@paraview.org<BR>> Message-ID:<BR>> <b02264720612290705h54bc20a6yf45d6b335f1f644e@mail.gmail.com><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> ><BR>> So maybe mangling isn't really necessary anymore, except for those times<BR>> where you need to switch between Hardware OpengL & Mesa on the fly..<BR>> Anyone<BR>> actually doing that tho?<BR>><BR><BR>The original purpose of the mangled mesa extension was a heterogeneous<BR>configuration with hardware acceleration and OS rendering at the same<BR>time. It was a long time ago, so I've forgotten the exact configuration. I<BR>know SGI pipes were part of the mix. This was in the parallel VTK days;<BR>ParaView did not exist, therefore no client/server architecture etc...<BR><BR>One application is rendering extremely large offscreen imagery using<BR>mangled Mesa (limited by memory) and hardware accelerated rendering<BR>smaller imagery for onscreen interactive use. This requires both libraries<BR>in the same executable.<BR><BR>Brian, what is the maintainence issue? What is the current cost etc.?<BR><BR>--Jim<BR><BR><BR><BR>_______________________________________________<BR>ParaView mailing list<BR>ParaView@paraview.org<BR><A href="http://www.paraview.org/mailman/listinfo/paraview">http://www.paraview.org/mailman/listinfo/paraview</A><BR><BR></FONT></P></DIV></BODY></HTML>