We need mesh blocks. Bopitman99 has some great conceptual block renderings:
We need a Boolean sensor for broadcasts. I'm too lazy to whip up any photos.
Anything else you want? Post here.
Offline
For the <I receive> block:
The block:
The block being used in a script:
Offline
The Host Mesh block wouldn't be useful unless someone else is using the Join Mesh IP block at the exact same time. I think it should just be a built in feature, not an actual block.
Offline
I personally want a "cap block" that can stop the script under it when certain parameters you set at the top are filled (it has a little slot at the top so it would read; when green flag clicked, go until ( ). )
Offline
We need a "Draw line" block.
It should allow us to define:
Color
Thickness
Length (*Very* useful)
Offline
Ace-of-Spades wrote:
The Host Mesh block wouldn't be useful unless someone else is using the Join Mesh IP block at the exact same time. I think it should just be a built in feature, not an actual block.
Yeah, now I see your point. I was thinking you would have a host in the center, and all the project connect to that host, but now that seems unreasonable.
Offline
Offline
Clear SPRITE's pen
Variable go to
Sorry, I'm not good at mockups.
Offline
juststickman wrote:
Clear SPRITE's pen
Variable go to
Sorry, I'm not good at mockups.
You mean like this:
Offline
Bopitman99 wrote:
juststickman wrote:
Clear SPRITE's pen
Variable go to
Sorry, I'm not good at mockups.You mean like this:
http://img43.imageshack.us/img43/8692/example2o.png
Yeah. although if you put "pen" next to the drop down menu, new people wouldn't be as confused.
EDIT: also, a set name to would be nice, to go with this:
[blocks]
<go to[ <{ }>
[/blocks]
Last edited by juststickman (2010-03-14 06:03:26)
Offline
All of these in this thread too: http://scratch.mit.edu/forums/viewtopic.php?id=32172
Offline