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

[webgl2] A separate package? #337

Open
stwind opened this issue Feb 10, 2022 · 2 comments
Open

[webgl2] A separate package? #337

stwind opened this issue Feb 10, 2022 · 2 comments

Comments

@stwind
Copy link
Contributor

stwind commented Feb 10, 2022

It is increasingly hard to use a single uniform compatible declaration for both WebGL 1 and 2 features (extensions, textures, UBO etc.). While WebGL2 achieving pervasive support now, would it be nice to have standalone package for WebGL2 only?

@stwind stwind changed the title [webgl2] A separate package [webgl2] A separate package? Feb 10, 2022
@postspectacular
Copy link
Member

Yeah, the moment has finally come for WebGL2. Instead of separating v2 I'd propose to extract the legacy v1 stuff into own package... What are your thoughts?

@stwind
Copy link
Contributor Author

stwind commented Feb 10, 2022

Yeah extracting legacy stuffs to its own package seems to be a better idea.

I am not quite sure how to do that yet, since there will be quite some overlaps/similarities between them. And as the "new" webgl package keep evolving to be more WebGL2, some common parts will almost eventually break for the legacy webgl1 package.

So I think the problem will be like how much or what should be kept in a common package, if any? Obviously the gl constants is the safest one to keep as common.

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

No branches or pull requests

2 participants