On Thursday 06 March 2003 08:26 am, Suzy Deffeyes wrote:
Who is the audience for the table? Is it the end user checking to see if a feature is available and/or has some form of HW acceleration? Or is the audience the DRI developer, looking to see what pieces need implementing? That might dictate how much you put in the table, especially color coding.
That's a very good question that I didn't have the answer to when I reworked it. I'm still not sure. I get the impression from what Brian has said that he feels it's more for the end user (gl app programmer) to let them know whether a feature is available for use since he doesn't care to distinguish any further.
I would prefer to at least distinguishing between hw and sw support, but it's Brian's baby. :)
I think that if you want to get into more detail about hw vs. sw features, etc that it should be put below in the "Driver-specific Notes" section below. But if someone feels strongly about it and will do all the work to do something fancier, that's fine. I just don't have time for it.
Nice looking table, I like it.
Thanks.
So, how do I install it on the Mesa site? Just copy the
dri_driver_features.phtml file? That doesn't seem to work. I don't know anything about dynamic html or html widgets.
-Brian
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
