between the Scratch 2.0 build your own blocks stack blocks and using broadcast and receive? The whole new build your own block can already be replicated with broadcast and receive, so why are they implementing it? (2 questions, so hopefully 2 answers)
Offline
Well, they do function pretty much the same. With 1S1S projects though, you can't do broadcast and receive. It also builds good programming practice, using functions.
Offline
So the only actual difference is the number of scripts that would show up on the Scratch website?
Offline
bump
Offline
TorbyFork234 wrote:
So the only actual difference is the number of scripts that would show up on the Scratch website?
I think so. It's still a useful function, and especially if they implement recursion!
Offline
scimonster wrote:
TorbyFork234 wrote:
So the only actual difference is the number of scripts that would show up on the Scratch website?
I think so. It's still a useful function, and especially if they implement recursion!
How is it useful if it can already be used with broadcast and receive?
Offline
TorbyFork234 wrote:
scimonster wrote:
TorbyFork234 wrote:
So the only actual difference is the number of scripts that would show up on the Scratch website?
I think so. It's still a useful function, and especially if they implement recursion!
How is it useful if it can already be used with broadcast and receive?
Well, recursion can't be done with that. It also makes scripts more readable.
Offline
scimonster wrote:
TorbyFork234 wrote:
scimonster wrote:
I think so. It's still a useful function, and especially if they implement recursion!
How is it useful if it can already be used with broadcast and receive?
Well, recursion can't be done with that. It also makes scripts more readable.
recursion can be done, like this. But of course, for it to be useful, you would have to have a more complicated script then the one shone.
when gf clicked set [a v] to [0] wait until <you're ready?> broadcast [I made a block v]
when I receive [I made a block v] change [a v] by [1] set x to (a) broadcast [I made a block v]
Offline
TorbyFork234 wrote:
scimonster wrote:
TorbyFork234 wrote:
How is it useful if it can already be used with broadcast and receive?Well, recursion can't be done with that. It also makes scripts more readable.
recursion can be done, like this. But of course, for it to be useful, you would have to have a more complicated script then the one shone.
when gf clicked set [a v] to [0] wait until <you're ready?> broadcast [I made a block v]when I receive [I made a block v] change [a v] by [1] set x to (a) broadcast [I made a block v]
Ah, but that's only tail recursion. Try looking at the the wiki. Here's the direct link. BYOB has full recursion, as explained later on.
Offline
Yes, but you could just make another broadcast with exactly the same thing for each time you want it to be used in the script.
Offline
Can get complicated. Did you see the tree example? Image for a depth of 25!
Offline
But that was with the ability to add in numbers that you change the input of, I wouldn't be asking about the difference if there were input numbers you could put in like in BYOB.
Offline
Well, there will be a space for input.
Offline
scimonster wrote:
Well, there will be a space for input.
I thought it was only going to be stuff like this
when gf clicked forever if <key [space v] pressed?> jump //where it's just a block, no inputs end
When I receive [jump v] //really the trigger block that will contain the definition of "jump" repeat (20) change y by [1] end repeat (20) change y by [-1] endNo inputs allowed. Well, that just made my day!
Offline
Well, I'm 95% sure.
Offline
scimonster wrote:
Well, I'm 95% sure.
Do you have a source saying it will have inputs?
Offline
Yay! Will there be multiple inputs though?
Offline
TorbyFork234 wrote:
Yay! Will there be multiple inputs though?
I think so! I'm very inclined to think that it will work similarly to Squeak's blockspec definitions, where any number of %s will become string inputs, %n numbers, etc!
Offline
Awesome! Reporting to be closed since it's answered.
Offline