Brian,
I scratched an itch and made this dynamic. You can see it at:
http://lfm.sourceforge.net/dritest/dri_driver_features.phtml
and of course grab it if you want from: /home/groups/l/lf/lfm/htdocs/dritest/dri_driver_features.phtml
Neat - I like it.
I was thinking it would be nice to color code it even more and add a legend to distinguish at least the following states:
+----------------------------+ given a | the chip has hw support | feature: +--------------+-------------+ | Y | N | -----------+----+----+----+------+------+ the driver | hw | sw | no | sw | no | supports | | | | | | -----------+----+----+----+------+------+ case 1 2 3 4 5
Right now as it is, the page is ambiguous between 1,2 and 4, and between 3 and 5. (1) might even have two colors--one for yes, the other to indicate some exception such as mutual exclusion with some other feature such as fog and alpha or other specific limitations.
This can get complicated. Sometimes a feature like GL_ARB_texture_env_combine can be partially implemented in hardware, but not fully. Sometimes we have to fall back to software because of a completely unrelated reason, like not having polygon smoothing in hardware.
As far as color scheme, I really don't care too much, but the colors make it a lot easier to visualize.
Perhaps: 1 green --nothing else to be done, and optimal 2 pink or yellow --indicate work to be done 3 yellow or red --indicate work to be done 4 light green --nothing else can be done, but not as good as hw 5 white? --indicate no work can be/to be done?
I don't intend for this to be overly granular, no sense in creating anything more to maintain.
I'm actually content with the table as-is in this regard. Either we have a feature or we don't. Sometimes a footnote will indicate that the feature is always done in software. The more complicated the table is, the less likely I'm going to bother updating it, unfortunately.
I also hope you find the underlying code a little bit easier to read and maintain than the static html table was.
My main itch was to eliminate the nasty horizontal scrolling. By only selecting the cards I care about that's now easy.
I haven't looked at the code behind the dynamic table. I'll try to get to it later.
-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
