Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update extension status table. #1762

Merged
merged 2 commits into from
Feb 13, 2020
Merged

Conversation

donmccurdy
Copy link
Contributor

Updates the various PBR next extensions (https://github.com/KhronosGroup/glTF/milestone/2), and removes extensions we aren't currently working on.

@zeux
Copy link
Contributor

zeux commented Feb 12, 2020

Should the "tabled" status be reflected in the extension files for each individual extension, to discourage implementation?

@donmccurdy
Copy link
Contributor Author

donmccurdy commented Feb 13, 2020

I'll close the KHR_blend PR (#1302). I'm not sure what to do with KHR_techniques_webgl... it's already merged, but hasn't been ratified, and I don't think we're prioritizing it at the moment. I'm inclined to say we should delete the folder (which is still in version history of course), and create a new PR when and if appropriate.

The other PRs are already closed.

@emackey
Copy link
Member

emackey commented Feb 13, 2020

I think Cesium and gltf-pipeline use KHR_techniques_webgl internally, as a means of accepting both glTF 1.0 and 2.0 (IIRC, 1.0 models are upgraded to 2.0 with KHR_techniques_webgl). But I don't think the extension needs to stay published in an un-ratified form, maybe it could be parked on a branch instead of master. Losing the extension could mean losing a loss-less upgrade path from glTF 1.0, but I'm not sure how much demand there is for that outside of some legacy 3D Tilesets.

Anyway this README update looks great, thanks @donmccurdy. Merging.

@emackey emackey merged commit 47a1110 into master Feb 13, 2020
@emackey emackey deleted the donmccurdy-extensions-status-feb2020 branch February 13, 2020 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants