Keith Whitwell wrote:
>
> Brian Paul wrote:
> >
> > Keith, I'd like to hear what your longer-term coding plans are. Do
> > you see a milestone in your work for a 3.1 release?
>
> I think you could say that the latest batch of changes pretty much
> represents the end of a certain line of improvements. I know Holger is
> doing some 3dnow assembly in support of those changes, and there is
> other tweaking possible. Apart from those issues I'm happy to draw a
> line under what's been done so far and call it a unit.
>
> My next change to the Mesa core will probably be to provide some support
> for floating point colors if that is what we're getting from the API.
> I'm also interested in trying to clean up the way we handle vertex
> copying at the end of an immediate vb, opening up the fast path to the
> immediate pipeline, and fixing some other immediate mode issues of my
> own making. I don't think these changes are worth delaying a release
> for.
>
> So I think I've done my last major chunk of coding for this release -
> just clean-up, bugfixes and everybody else's work to go...
OK, great. Here's what's left, off the top of my head:
- conformance testing (I'll try to get back to this ASAP)
- 3Dfx driver bugs? (Joe Water's fog bug, for example)
- Windows driver bugs (Wilmot Theierry's list of May 28)
- put src-glut/ into CVS
- is Windows support still in need of tweaking?
- multi-byte font bug in GLX
- library naming issue: libMesaGL.so vs libGL.so (probably should switch
to the later for 3.1)
- should GL_SGIS_multitexture be removed? I say yes.
- configure-based building? Wait and see, I think.
Any additions?
-Brian
----------------------------------------------------------------------
Brian Paul Avid Technology / Softimage [EMAIL PROTECTED]
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
