ahem
Oh.
I propose a new name: isStop attribute blocks (/j)
how about just "end stack"
Or 'Flat-bottom blocks'
Oh. Just realized that sounds weird. Never mind.
'Flat Blocks', maybe?
Blocks such as the [scratchblocks] when green flag clicked [/scratchblocks] block are hat blocks, and blocks such as
[scratchblocks]stop this [script v]::cap control[/scratchblocks] are end blocks
Or, Start and end blocks?
i suppose but it doesnt actually explain what its ment to do
you can have a reporter thats only use is to move a sprite, thats bad practice hence the name "reporter" this explains what their intended use case is
Good idea
Which is why you would get an error that says
"Hmm.. Inside a custom block: Reporter didn't report"
hat blocks are offically their names and i just took a look at the scratch souce code and they are offically called "end" shapped blocks
so having it be called "end stack" would be more correct than cap
Yeah, but this isn't Scratch.
Also it would make more sense for them to be end stack blocks
What do you think, Jens?
(It took me FOREVER to figure out the what people meant when they said "Hat Blocks")
and "end stack" is more descriptive
if you put one of these in a C block then if the end block doesnt stop the script then it will continue running under the c block. and C block inputs are usally interprited as seperate stacks therefore "end stack" is better than "end script" as the block itself doesnt actually need to end the script its inside of
were talking about what the name of the toggle option would be not what the block would actually be called internally
yep, back in 2008 / 2009 I was part of the Scratch dev team (at that time it was John Maloney, Evelyn Eastmond, and moi) and worked on Scratch 1.2-1.4. Mitch had tasked me with coming up with new features for Scratch, and John and I thought "Build Your Own Blocks" would be a nice next feature to add - in part because Brian had rallied hard for it - , and we jokingly named it BYOB. Mitch told me that they didn't know how to visually represent block inputs, so I "invented" the inline-variable-template gimmick and the block definition hat blocks for the headers. John suggested a dialog box for editing custom block definitions, because hiding it is an important aspect of abstraction. So, after I'd designed the UI for a make-a-block gimmick I decided to also tweak Scratch's process-interpreter to make them actually work. That was fun! However, custom blocks - and my design for definition hat blocks with "peel-off" input variables - didn't make it into Scratch for a looooong time, but a few weeks afterwards some profs from UC Berkeley got in touch with us and offered to help us implement custom procedures. John showed them my "BYOB" prototype. And thus Snap! began...
this is a gramatical mess
i ment to say "it shouldnt be called end script because the block itself doesnt actually need to end the script its in, it just denotes the end of the current stack of blocks"
Woah, thats cool! It's amazing that Snap! started from a Scratch mod to suggest features.
yeah snap has a really long history
ik