[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Addition of compressedTexImage2D entry points in WebGL 1.0.1
On Thu, Jan 26, 2012 at 3:07 PM, Gregg Tavares (勤) <email@example.com>
On Thu, Jan 26, 2012 at 12:00 PM, Kenneth Russell <firstname.lastname@example.org>
I think it makes sense to leave these enums as is, just in case it is
desired to allow one compressed texture extension to optionally
provide one or more formats.
The goal of WebGL so far has been if you get an extension you have that feature. Leaving those 2 queries opens up extensions to break that idea. Why not just get rid of them and their by not allow extensions that are likely to break for devs who forget to check?
It seems fine to have an extension that exposes two formats, as long as the extension requires both. An extension probably shouldn't define two formats while allowing just one or the other to be implemented. (More specifically, a single extension *string* shouldn't do that--a single extension spec might define more than one extension name, but that's just editorial.)