You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After 0.1.0 there should be significantly less API churn, but we need to implement more features before stabilizing anything - to find out what the "final" API looks like. Apart from features and API changes, we need better test coverage and documentation.
After implementing Cubemap and Renderbuffer decide, whether uniforms and textures should really be separate
Nope, the implementation can tell them apart, no need to separate them in the API. This also plays well with the new uniform types introduced in the Cubemap branch
After
0.1.0
there should be significantly less API churn, but we need to implement more features before stabilizing anything - to find out what the "final" API looks like. Apart from features and API changes, we need better test coverage and documentation.We need at least:
Cubemap
s (Add Cubemap #19)Renderbuffer
s (Add Renderbuffer #18)Cubemap
andRenderbuffer
decide, whetheruniforms
andtextures
should really be separateCubemap
branchCommand.locate()
withAttributeLocation
(Add AttributeLocation and remove Command.locate() #36)0.1.0
, but may revisit laterThe text was updated successfully, but these errors were encountered: