[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] extension registry markup/split for webgl 1, 2 or both
I don't mean to split the actual extension. I mean to split (or at least mark up) the pages indexing the extensions.
If you want to present a clean picture for instance, you should filter the landing page for extensions which are <api version="2.0">. But people will still be interested in extensions which are <api version="1.0"> and which are not <core version="2.0"> because they still have to support these profiles. On the other hand, people will also be interested about extensions which are only <core version="2.0"> because it gives them a good overview about which extensions they should bother about to provide backwards compatible applications.
I see these meaningful changes that could be made:
- Add "tags" to the extension overview derived from their <depends> specification so you can get a view at a glance what they are.
- Add a filtering widget (checkboxes, what have you) that blends out those extensions which you've filtered out
I'd default the filter to extensions which are <api version="2.0"> because that gives the cleanest picture for newcomers.