[Paraview] Re: ParaView Digest, Vol 32, Issue 23

[James P. Ahrens]

> Message: 1
> Date: Fri, 29 Dec 2006 09:05:35 -0600
> From: "Randall Hand" <randall.hand at gmail.com>
> Subject: Re: [Paraview] RE: [vtkusers] MangledMesa & VTK
> To: "Sean Ziegeler" <seanzig at users.sourceforge.net>
> Cc: paraview-developers at public.kitware.com, VTK Users
> 	<vtkusers at vtk.org>,	paraview at paraview.org
> Message-ID:
> 	<b02264720612290705h54bc20a6yf45d6b335f1f644e at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> >
> So maybe mangling isn't really necessary anymore, except for those times
> where you need to switch between Hardware OpengL & Mesa on the fly..
> Anyone
> actually doing that tho?
>

The original purpose of the mangled mesa extension was a heterogeneous
configuration with hardware acceleration and OS rendering at the same
time. It was a long time ago, so I've forgotten the exact configuration. I
know SGI pipes were part of the mix. This was in the parallel VTK days;
ParaView did not exist, therefore no client/server architecture etc...

One application is rendering extremely large offscreen imagery using
mangled Mesa (limited by memory)  and hardware accelerated rendering
smaller imagery for onscreen interactive use. This requires both libraries
in the same executable.

Brian, what is the maintainence issue? What is the current cost etc.?

--Jim