I need help with this project.
In another one I have no idea what blocks I need (shown in a comment).
also I need help with a block that reports blocks from scratchblocks code. (100% requires JS because you can do things in scratchblocks that are not possible in
If anyone could help me that would be great!
you could use my script builder library
https://snap.berkeley.edu/snap/snap.html#present:Username=pumpkinhead&ProjectName=script%20builder
to use this block:
(Unforunately multiargs aren't supported (yet, maybe?))
good
does anyone know how to debug the blockspec custom block?
The blockspec of
block doesn't have to be so complicated.
You can just do:
(block spec ((block)::sensing)::sensing)::events hat report (call (JavaScript function [block] [return block.expression.blockSpec;]::operators)with inputs (block)::control)::control cap
i don't know what the bugs are supposed to be
dont worry @helicoptur fixed them
just need help with the scratchblocks script
There is a Shift menu "to scratchblocks..." Snap! Build Your Own Blocks
Based on this PR Add [scratchblocks] export by tjvr · Pull Request #1646 · jmoenig/Snap · GitHub
no there isn't
nope
If it's not that you are trying to achieve
then sorry to bother you...
I am
we can't put hat blocks in rings :~(
I made some progress!
Now it's pretty much done except I don't know how to get the category of a block.
Edit: Found out how to do that, though it requires javascript.
I see no way to reference the hat block other than by index in the scripts array of the sprite
I need help with a block that reports blocks from scratchblocks code.
(if it is possible it requires JS since you can do things in scratchblocks that you can't do in )
anyone?
Scratchblocks parser can be build based on Tim Radvan & Co scratchblocks to SVG GitHub - scratchblocks/scratchblocks: Make pictures of Scratch blocks from text..
It should be quite easy to get blockSpec list instead of SVG but there still will be a problem to create a real Snap! blocks.
Snap natively supports XML export and import so probably it's a better choice if You try to build something like a network shared backpack or coeditor.