Scratch

I would like to see a message sending syntax a little bit nearer to Smalltalk classic syntax

< send to [ sprite ] [message]>

Not just broadcasting

Why? Well, a broadcasted message points clearly to more than 1 sprite understand a message. But one message send to just one sprite could help to understand quickly certain projects, and may be to write them.

I'm absolutely agree with HiGuy about this:

Add and delete sprite blocks.
<deletesprite{sprite}>
<newsprite[name](x)(y)(costume)> Maybe better like copy [sprite1] to [sprite2]

Local file access (offline only).
<exporttextbox{textbox}asfilename[name.txt]where[path]>
<loadproject[path]>
<saveproject>
<loadtextfile[path]totextbox{textbox}>

it would make linking projects not just in the website, even in local projects, like hiperdocuments in Squeak.

How about the ability to break the fourth wall like Metal Gear Solid sometimes does? Like with the Psycho Mantis fights, being able to check EVERY file on the computer being used and telling the player his favorite games (including emulated games!)
Also, a creepy twist would be to let scratch do commands... for you, like Psycho Mantis does! Psycho could tell you to remove your (what ever is connected in the the usb drives or a disk) and watch them carefully, and watch them do some crazy stuff, like vibrating, and a mysterious text appearing on your favorite game disc!

Who is Psycho Mantis? It's this guy who is creepier than Giygas! At least Giygas can't tell you if you played Legend of Zelda alot! But this guy tells you what's on your memory card, and even moves your controller! Even more creepily, he knows EVERYTHING YOU WILL DO!  The only way to defeat him, is to switch controller slots. Also, he may make a black out with HIDEO where Video would be to make it look like he switched channels!

Last edited by FiremariomkiZX (2009-07-21 14:04:53)

Mesh and also, being able to treat variables like sprites. You can tell them to hide or show after a certain amount of time, tell it to move out of the way in a game, etc. I would also enjoy to see a few missed blocks: the comment block, the 'clone this sprite' block, and the 'delete this sprite' block.





And did I mention MESH?!?!?!?!

The top features I want in 1.5 are:
The ability to hide/show lists
an "If touching (BLANK), bounce" block
an "If color (BLANK) touching (BLANK)" block
and more tools on the paint a sprite thing.

[make new variable [text]]

[make new list [text]]

<I receive [broadcast]>

([graphic effect] effect)

[broadcast [broadcast] for (number) secs]

[point to x:(number) y:(number)]

[if touching [sprite], bounce]

[  do at speed [speed]  ]
| |
| |___________________                <-- In the shape of a forever block.
| |___________________]

[show list [list]]

[hide list [list]]

[when [backspace, enter, shift] key pressed]    <-- In shape of hat block

<key [backspace, enter, shift] pressed>           <-- Same as hat block except in boolean
                                                                       form

The ability to create libraries. I made a topic on it already though. Also, allowing scratch to display HTML and PHP pages. You could create a web browser in Scratch or an HTML editor that let's you preveiw the HTML you write.

Last edited by keikij (2009-07-24 03:26:41)

filo5 wrote:

Yes, this would be great. I also want to have multi-line strings, like this from Ruby:
"this is line 1\nand this is line 2", and it appears as:
this is line 1
and this is line 2

I also like the libraries and more object-oriented functions. Did you know that Scratch 0.1 was more object-oriented?

such as?

A block count would be awesome! You could access it from the File menu, and it would show how many blocks you used of a certain type. For example:

2<move( 10 )steps>
3<turn cw( 15 )degrees>
1<point in direction( 90 )>

And so on...

Last edited by bigreader (2009-07-24 16:24:24)

Objects and Classes and physical text output. The showing of variables would be nice too.

For example, say, instead of having a sprite collection box, you had a class collection box under the screen. The class could then supply all the sprites that an object of that class would have.

The syntax for creating an object would be like <set{ AnObject }to( <{ create object of class _______ }>. The whole assigning the object's value to a variable is optional: you could create either a temp object (in which case, you wouldn't assign the returned value to a variable), or a malliable object (which would be assigned to a variable). Alternatively, instead of assigning the value to a variable, an option could be added under "Make a list" for "Make an object".

Also, a way to actually modify the script generated from the blocks would be nice.

Last edited by OmtraSpectral (2009-07-27 15:43:30)

if they make an easier way to make custom blocks, then there would almost be no more needs for updates.

the thing is...most of us can't make custom blocks so updates are easier than making our own updates

I noticed about 2 months ago, that scratch can't handle transparency per pixel, it can only hand net transparency for an object or Sprite.  This has been massively annoying me ever since!  Whenever I try an import a Sprite that I created in Photoshop or GIMP:  http://gimp.org/, Scratch turns that transparency around the edges into fade-to-black instead of fade-to-transparency.  I mean, everything uses transparency!  From the giant graphic image products like Photoshop to the everyday text you type (don't believe me, look close enough at any text on the internet or in Microsoft Word.  This change is my biggest hope for Scratch 1.5 or scratch 2.0!   
 
   -Mirror27studios

                             
                             http://mirror27studios.webs.com/

Random genorator? Like :
<when green flag clicked>
"Generate random letters"
or "Generate random Numbers"
Because you can't rally say-
<pick random(a  )to(z)>
,it would only pick a or z.