Scratch

shadow_7283 wrote:

maybe I can convince nXIII to make a BYOB project upload site... 

You know, we (folks at Berkeley) keep talking about wanting to do that.  But in these paranoid days it's only a matter of time until someone uploads a project full of pornographic pictures, and then some parent will have a fit, and the next thing you know we're all arrested or sued or something.  MIT puts this huge effort into policing the Scratch site that we couldn't match.  So, it's not convincing nXIII to write the code; that's the easy part.  It's convincing nXIII's parents that they want to take on that kind of liability.

What we're going to do soon, I hope, is allow for local sharing sites, just using scp.

EvilGenius wrote:

Why is clone of a reporter, when it performs an action more like a command?

We actually had a long discussion about this.  We started with different opinions and each of us convinced the other.     (Really!) 

We're thinking that people will want to make a bunch of children of a sprite, and then be able to tell them all what to do, so you'll say



(CASCADE is in the tools project) and then use FOR EACH (also a tool) to send a message to all the children.

P.S. You can use the IGNORE tool to ignore the reported value if you don't need a handle on the child.

P.P.S.  We're planning to eliminate the dropdown menu in CLONE, so it'll just clone the sprite that runs it, and you'll have to use OF to clone a different sprite, same as anything else you want to do to a different sprite.

bharvey wrote:

Hey, everybody, what's your opinion about having a command block (namely DELETE) in the Operators menu?  The object stuff is mostly there because it's about data, like the text operations and the numeric operations.  The other current command block there, namely SET, should, I think, be merged into the Variables SET block.  Should DELETE be under Variables, too?  It isn't exactly about variables, although you will be able to delete variables with it, among other things, but mainly it's about sprites.  What's your vote on where to put it?

Bump!

bharvey wrote:

bharvey wrote:

Hey, everybody, what's your opinion about having a command block (namely DELETE) in the Operators menu?  The object stuff is mostly there because it's about data, like the text operations and the numeric operations.  The other current command block there, namely SET, should, I think, be merged into the Variables SET block.  Should DELETE be under Variables, too?  It isn't exactly about variables, although you will be able to delete variables with it, among other things, but mainly it's about sprites.  What's your vote on where to put it?

Bump!

I am of the opinion that Operators should remain free of command blocks. One vote for Variables.

If I were being really picky, I might argue that THE SCRIPT and THE BLOCK don't belong in Operators either...they should join their cousin, the first-class list constructor, in the Variables palette. But please don't change this, since I like the green Operators color much better than red. 

14God wrote:

Plz don't delete the drop down for convenience sake.

I agree.

bharvey wrote:

14God wrote:

It would be cool if you could pass an argument to the '() key pressed?' block.

The argument would be a one-character text string?

yeah

Question:

Could you make a:
When [Greenflag, _ Key pressed, Sprite pressed?]

I don't know i it's possible, i'm using it for RKT

Last edited by ssss (2011-02-11 03:40:58)

14God wrote:

xly wrote:

@ bharvey, Jens and other byobers...

See my project using the "before last Byob features" at ...
http://www.xleroy.net/ByobTuto/thumbnails.html

Where are all your other BYOB projects? Did you delete them?

I've fixed the issue. Everything is available for the moment.

xly wrote:

Some instructions like <Broadcast>, <OF>, <Object> accept "composed strings" input like <join Sprite + n°> but not the following : <When received ...>, <Delete>, <Clone>

In the case of Delete and Clone, the input isn't supposed to be the name of something, but rather the thing itself, or rather its getter block.  So let's say FOO is a variable; you say DELETE [THE [FOO] BLOCK] to delete it.  For a sprite, you say DELETE [OBJECT [Sprite23]] or, more likely, you have a variable whose value is that sprite (kept when you made it in the first place) and you DELETE [MYVAR].  So if anything, it's OBJECT that should take a text string input, not DELETE or CLONE.

Pedagogically (and remember, we're in the business of teaching college students computer science here), we want to wean people away from using names and instead get familiar with first class objects.  So, you're building an Adventure game; you don't make a list of the names of the things in this room, but rather a list of the things themselves.  This is better because if you have the things and need the names, you can

MAP [[ATTRIBUTE <NAME>] OF < >] OVER <objlist>

whereas if you have the names and need to send the things a message, you're out of luck.

P.S. Another problem with names is that Scratch allows two things of different types to have the same name,  So, e.g., you can have a sprite Sprite23 and also a variable Sprite23, and a block like DELETE that can delete a sprite or delete a variable won't know which you meant if you just give it a name.

Last edited by bharvey (2011-02-11 10:44:13)

Thanks to everyone who answered my DELETE question.  Your responses gave us an eye-opening view of how differently you understand the palette categories from each other and from us!  The bad news is that there's no clear winner -- you're just as confused about this question as I am.     Back to the drawing board....

bharvey wrote:

A new experimental build and sample project:

Jens wrote:

This weekend build

- lets you delete variables via the DELETE block,
- updates watcher colors (ghosting / unghosting) in presentation mode

Sorry if development seems somewhat sluggish, but we're quite figuratively turning every stone of the Scratch source code around for this insanity 

Enjoy!
--Jens

-_- I just updated 5 minutes ago and now there's another one...

bharvey wrote:

EDIT: Or, for that matter, someone who calls himself 14God;

Let me clarify, the name was meant to be 'one for God' It wasn't me calling myself God    My Sister thought that would be confusing & I guess I shoulda believed her 

Last edited by 14God (2011-02-11 15:19:58)