1. I/O Functions
I/O functions would not only be useful in general for Scratch, but could also eliminate the need for arrays. (Just write variable data to a file and read it later!). This is one of the less kid-friendly things, but it would be extremely useful.
Block ideas for this:
Make a new file [filename]
Write [something] to file [filename]*
Write [something] to line [number] of [filename]
Read file [filename]*
Read line [number] of [filename]
* Reads/writes with the last line of the file
-----------------------------------
2. X/Y Scaling
Seperate scaling for X and Y would also be useful. It would help in faking 3D sprites in Scratch, and could also add area for more visual effects in projects. To make this more kid-friendly, instead of using "X scale" and "Y scale", say "X stretch" and "Y stretch".
Block ideas for this:
Set X stretch to [number]
Set Y stretch to [number]
Change X stretch by [number]
Change Y stretch by [number]
Last edited by S65 (2008-05-31 12:27:36)
Offline
I am not sure I get the first suggestions because I don't make very complex projects. It sounds smart so I support it though!
Offline
Yeah, that would be nice. for IO, i think Jen's list may do what you want.
It works in memory, then you can choose when you want to save or load the list from a file. This should be faster then just file save and load.
I like the stretch idea. Taper would be nice too. or 4 point deform for texture mapping.
A 3 or 4 point filled polygon drawing would be nice too!
Maybe those could be made with the "build your own block"- if there's access to lower level functions.
Last edited by AddZero (2008-05-31 14:00:44)
Offline
AddZero wrote:
Yeah, that would be nice. for IO, i think Jen's list may do what you want.
It works in memory, then you can choose when you want to save or load the list from a file. This should be faster then just file save and load.
I like the stretch idea. Taper would be nice too. or 4 point deform for texture mapping.
A 3 or 4 point filled polygon drawing would be nice too!
I know about Jens' lists; I just want a supported solution that will also work online. And yes, filled polygon drawing would be extremely useful, especially for 3D.
Offline
Which reminds me, also one more thing:
3. New layering system
As I understand it, the current layering system works like this:
If you go back more layers than the # of sprites, the spriteautomatically get sent to the back. This means that if the sprite is already at the back, this does nothing.
It would be very useful if each sprite was assigned a built-in "layer" variable. When the display functions are called, each sprite's layer variable can be tested against each other sprite's layer variables, to determine the order to draw them in. This would also automatically solve the Z-ordering problem which is hindering progress in "fake" 3D effects.
Offline
I really like the strech-idea. Funny thing is, when I looked for this in the source code it's already in there (just disabled). Seems like the Scratch Team deliberately *took it out* from a previous version...
Offline
Jens wrote:
I really like the strech-idea. Funny thing is, when I looked for this in the source code it's already in there (just disabled). Seems like the Scratch Team deliberately *took it out* from a previous version...
Really!? I've wanted a stretch/skew block for ages!
Offline