Scratch

Cool. It looks like the broadcast and wait block.

Set variable to X
Broadcast "Jump" and wait



When Jump recieved
Change Y by 10
Wait 0.1
Change Y by -10

Awesome. This feature will make things much easier.

With every update I get more excited! Any thoughts on a release date?

Will you be able to share blocks online. So can you upload custom blocks?

LS97 wrote:

johnnydean1 wrote:

Will you be able to share blocks online. So can you upload custom blocks?

I do believe the program will implement a BYOB type block making system, meaning the blocks will be shared within the project. Looking at the mockups they have made this theory seems even more probable.

Lightnin wrote:

LS97 wrote:

johnnydean1 wrote:

Will you be able to share blocks online. So can you upload custom blocks?

I do believe the program will implement a BYOB type block making system, meaning the blocks will be shared within the project. Looking at the mockups they have made this theory seems even more probable.

Yes - I assume you are referring to blocks that are made from existing Scratch blocks (and not custom created Squeak based blocks)? In that case, yes - we'll definitely be including the definition of the customized block *somewhere* in the project itself, so you can share and remix it.

The question is: where? BYOB uses a script area within a dialog box as the place to define your customized block. In many ways, that's a good approach - but we're looking for alternatives. For one thing, it's nice to be able to see the custom block and its definition scripts on the same screen.

But this brings up questions  - like: Should custom blocks be "global" (i.e. all "Jump" blocks are the same across the entire project. If you change one, you've changed them all) or "local" to the sprite (each sprite can have their own unique "jump" block).   And of course: where should the script definition live?

i.e. If I make a scratch project with gobo and Scratch cat in which both use "jump" but the definition of jump lives in the cat, what happens when I export the gobo sprite? Does it just get a copy of the jump definition? What happens if I make changes to the jump definition in Gobo and then import it back to the same project - then you have a conflict between the definitions of Jump on Gobo and on the Jump on Scratch Cat (assuming everything is global).  Actually, that's making me think we should have the concept of global / local: It's better to try to explain that concept than to have people try to merge different definitions for custom blocks when importing sprites. Does BYOB have a way of addressing that kind of conflict?

As to the question of where the block's definition scripts should live: maybe in a separate sub-window of the script area? I should follow the advice I'm always giving other Scratchers and just make a mockup.... 

I like the idea of a sub pane.
No, here's something better:
Under the stage will be a "sprite" called "definitions." That is where all the block definitions will be stored.  Every sprite can access them all, and if one got exported, it would take the definitions "sprite" with it. If a duplicate got imported, it would automatically be renamed "[name] 2."
Like?

Lightnin wrote:

scimonster wrote:

I like the idea of a sub pane.
No, here's something better:
Under the stage will be a "sprite" called "definitions." That is where all the block definitions will be stored.  Every sprite can access them all, and if one got exported, it would take the definitions "sprite" with it. If a duplicate got imported, it would automatically be renamed "[name] 2."
Like?

I kinda like --- it's definitely worth mocking up to play with the idea! The thing to be careful of is that you don't want Scratchers getting confused and trying to work the "definitions" sprite like a regular sprite. So it'd have to visually indicate that it's something different from a normal sprite - kinda like the Stage is kind of a sprite, but kind of not really a sprite - know what I mean?

Yes. Under the stage, not changeable name, no costumes/sounds tab.

BoltBait wrote:

Lightnin wrote:

Here's the latest Scratch 2.0 Progress Report

Check it out, and then join in the discussion about the best way to do 'Create your own block' in Scratch 2.0 here:

Create your own block blog post wrote:

We’re still in the process of figuring out the best way for Scratchers to create their own blocks, and there are still many questions. For example, if you create a jump block in one sprite, would other sprites be able to use the jump block too? Should the definition script appear in only one sprite -- and, if so, how would people find it? Should you be able to define “jump” differently in different sprites? These are few of the questions we have to think through before we’re ready to put this cool feature in the next version of Scratch.

Perhaps, blocks defined in the stage could be used in any sprites and blocks defined in a sprite could only be used in that sprite.

Hmm, I like that idea!
But instead of stage, definitions (see above).

BoltBait wrote:

Lightnin wrote:

Here's the latest Scratch 2.0 Progress Report

Check it out, and then join in the discussion about the best way to do 'Create your own block' in Scratch 2.0 here:

Create your own block blog post wrote:

We’re still in the process of figuring out the best way for Scratchers to create their own blocks, and there are still many questions. For example, if you create a jump block in one sprite, would other sprites be able to use the jump block too? Should the definition script appear in only one sprite -- and, if so, how would people find it? Should you be able to define “jump” differently in different sprites? These are few of the questions we have to think through before we’re ready to put this cool feature in the next version of Scratch.

Perhaps, blocks defined in the stage could be used in any sprites and blocks defined in a sprite could only be used in that sprite.

Ah -- interesting. So the block definition script's position would indicate if it was global or not global? If it's on a sprite with the rest of the scripts, it's local. Or you can drag it to the "global pane" and then it would apply to all... hmm.. need a good mockup of this.

Lucario621 wrote:

My current perspective without too much thought is that it should be fine to have all blocks as being global. People won't be making blocks as much as they are making variables - at least I assume. By that I mean it's more likely for somebody to have 20 variables in a project than 20 custom blocks. That's just my opinion however.

That was my initial take too - but what happens with sprite importing / exporting?

What happens if I export my gobo sprite, change the global custom block it uses, and then re-import it into the same original project (that already has a global custom block with the same name)?

I guess we'd have to have a way to sort out the conflicts.... or at least pick which global custom block gets to overwrite the other. Not impossible, but kinda ugly....

Whereas if we have local and global blocks, you'd just be importing / exporting local blocks. Not sure what you'd do if the sprite you were exporting used / depended on a global custom block.... maybe change it to a local block and copy it to the sprite? That's not very pretty either...

what about a block that turns a bit of pen drawing into a sprite? it would make drawing stuff like moving platforms (you could draw a bubble round something and it would float up?) in-game alot easier

Lightnin wrote:

BoltBait wrote:

Lightnin wrote:

Here's the latest Scratch 2.0 Progress Report

Check it out, and then join in the discussion about the best way to do 'Create your own block' in Scratch 2.0 here:

Perhaps, blocks defined in the stage could be used in any sprites and blocks defined in a sprite could only be used in that sprite.

Ah -- interesting. So the block definition script's position would indicate if it was global or not global? If it's on a sprite with the rest of the scripts, it's local. Or you can drag it to the "global pane" and then it would apply to all... hmm.. need a good mockup of this.

Yes.  You would need to remember when exporting a sprite, if it uses a global block, it would be included in the export.

Last edited by BoltBait (2011-03-31 16:22:25)