([hello world]@>)
This block has a bug. There is a command ring behind the text input
I don’t really want to support regular inputs in grey rings cause it doesn’t really make sense, so I’m fine with that bug.
What’s your plan for custom type notations?
I don’t know
I feel like Snapblocks (in the scratch 3 theme) could use some Split! symbols, especially for blocks like PIPE that use arrowRight and multi-inputs.
To me, the Split! symbols fit with the round Scratch 3 asthetic
Can there be a notation for return bubbles? I’m not saying to add a whole new syntax to create all the Snap! types, but there should be notation for strings, numbers, booleans, and scripts since they have syntax anyway.
Maybe <(..stuff here..)?
It was rejected due to causing confusion from users being able to make a block report impossible things I think.
If a bunch of people are going to misuse the feature, that doesn’t mean it should be rejected…
I don’t want the feature, because of the missuse and also how people are going to request some kind of ability to show more data types like lists, even though that’s not what you’re asking. I also just generally don’t think it’s necessary when it’s almost always better to just use script pics.
Currently I’m messing around with something in my random Snap! mod I had to create a organization for because of GitHub’s stupid fork rules, which will allow people to generate snapblocks from any script. And actually, I’m pretty much done with it. I’ve also done custom block definitions, but I don’t know to syntax block variables. Is there a way to do this or nah?
Yes, there is a way to do block variables (which I forgot about when I made my converter)
{test :: motion} \
block variables ((var)) @<> :: define+
{test :: motion} \
block variables ((var)) @<> :: define+Now that I’m thinking about it, I probably should make this work as well (this is just an off-the-cuff idea I just had, so it probably won’t be implemented in a while)
{test :: motion} :: define+
block variables ((var)) @<>
About the scratch3 theme, it doesn’t work well for large block wrapping:
To be honest, scratch 3 really isn’t a priority because this is for snap, so I’m fine with scratch 3 breaking or not looking as good. I do like the icon shapes used in split, but I don’t really like the white color of the arrows. If you want to fix scratch 3, submit a PR.
Yeah, I know it isn’t very important. I’ll see what I can do next week.
what is this “Snapblocks” thing about?
It’s this: https://snap-blocks.github.io/
If you’ve ever used scratchblocks, you’ll find this familiar
:Sigh: it’s blocked. what happened when i tried too use “Split!”. i’ll have too ask my parents.
You’ll need to ask to use this site
If you want to, just send a request to an adult in your family.
you can :: control hat
use {
snapblocks :: sensing
} in [the forums V] :: control(put text between the [snapblocks] and [/snapblocks] tags)
oh ok
If the website is blocked, you can instead look at How to write snapblocks (on the forum) to learn about all the stuff snapblocks has. You can test it on the forum, but don’t post random stuff, just look at the message preview. You also need to be in the source editor to actually use it (snapblocks doesn’t support the visual editor). Basically just make sure this button is in this state
