As someone else mentioned... isn't this beyond the scope
of oglbase? I think this information better fits in
the scope of something like glean/isfast.
I (as a software developer) would rather see effort put
into [an | a set of] extension[s] that glean then uses
to get information about the device. Those that wish to
support queriable device/renderer information should support
the appropriate extensions[s].
Paul
> -----Original Message-----
> From: Thomas Roell [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 10, 2000 2:02 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [oglbase-discuss] GL_RENDERER strings
>
>
> In your message of 10 February 2000 you write:
>
> > Ralph Giles writes:
> > > I'm not sure we can come up with something sufficiently
> broad to make
> > > everyone happy though,
> >
> > We can try. Where's the daring spirit that brought us
> > context-independend entry points?
> >
> > Seriously: it's worth it, and easily abandoned if we can't even
> > agree on a list of mandatory tokens and their order.
>
> Ok, let's pick up the idea an first ask a few questions:
>
> What would be the goal of such a "standard naming scheme" ?
>
> What components do matter:
>
> Hightlevel-backed (Mesa, SI, EV ...)
> Lowlevel driver (g400, permedia3 ...)
> Chip-Name (86C397P ...)
> Memory on board (32MB ...)
> AGP Texture memory (32MB ...)
> DMA memory (2048k ...)
> Rendering Method (direct vs. indirect)
> 2D driver (??? ...)
> CPU used (K6, K7, PentiumII ... MMX, SMID, 3Dnow)
> Board Vendor (Hercules ...)
> Board Name (Xterminator-Whizbang-3D-Ultra)
>
> How does the render-string imply when SW only vs. accelerated
> rendering is being used ?
>
> - Thomas
> --
> Thomas Roell /\ An imperfect plan
> executed violently
> Xi Graphics / \/\ _ is far superior to a
> perfect plan.
> [EMAIL PROTECTED] / / \ \
> / Oelch! \ \ George Patton
>
