I'm making WebGL 2 extension #378
Replies: 7 comments 3 replies
-
200+ blocks?!? |
Beta Was this translation helpful? Give feedback.
-
Do you want to include everything?? |
Beta Was this translation helpful? Give feedback.
-
This looks awesome!! |
Beta Was this translation helpful? Give feedback.
-
Good lord. Best of luck, and well done on what you have so far! |
Beta Was this translation helpful? Give feedback.
-
very cool |
Beta Was this translation helpful? Give feedback.
-
ooh. please keep me updated |
Beta Was this translation helpful? Give feedback.
-
If I end up finishing this extension, it will not be submitted here. It's too much of a maintenance burden for something that almost no-one knows how to or wants to use. It has been superseded by much more practical and user-friendly Simple 3D extension. |
Beta Was this translation helpful? Give feedback.
-
I'm making an extension that will let projects access WebGL 2.
200+ blocks are planned. 130 are implemented so far.
Is this a bad idea?
Everything happens on a separate canvas.
A new drawable with custom skin is used to show that canvas. The drawable is located on a new
webgl2
layer, which is drawn between video layer and pen layer. This does not require overwriting or wrapping any functions.It wraps
renderer.draw
to refresh skin if needed before frame is drawn.It wraps
runtime.getBlocksXML
to show multiple categories in the block palette.During development I also temporarily made it overwrite
ScratchBlocks.defineBlocksWithJsonArray
to stopBlock definition #... in JSON array overwrites prior definition of ...
warningsIt doesn't wrap or overwrite anything else.
(Unfinished source code)
webglext-2023-05-03_22.54.14.mp4
Beta Was this translation helpful? Give feedback.
All reactions