1. The Ability to Save _ to _.ssd (Scratch Save Data)
Then you could make a fully fleged game - Example:
[When Save Clicked]
[Save _Battle Chips_ to Chips.ssd]
[Save _Items_ to Items.ssd]
[Save _Location_ to Location.ssd]
[When Green Flag clicked]
[Reset All]
[Import Chips.ssd to _Battle Chips_]
[Import Items.ssd to _Items]
[Import Location.ssd to _Location_]
2. The ability to open _ project
This would be great - I could have a single project as the main menu of my Phoenix Wright fangame. Clicking on New Game - Episode 1 would open a certain file, Episode 2 would open another file, etc.
3. Make EXE File (Scratch Player Presentation Mode)
Basically it creates an embedded game inside a Scratch VM - but only the interpreter.
It would probably run smoothly, and allow developers to release games without fear of the source code being discovered (or allow people to play the game without installing Scratch).
4. Network Transmission
This has been suggested time and time again, but it deserves a mention. Network Broadcasts and data transmission is a must.
But then again, it would have to be limited to Four Connections. Anymore then that, with data flying all around, the network would be brought to a halt. Guaranteed.
Everything from MMORPG to voIP has been visualized - people believe it's possible to code in Scratch.
5. Ditch the VM - Make a more efficient editor
If we code something to read the scratch project files, but have it run directly - not as a VM but as a stand-alone program - we can eliminate plenty of lag.
Why not change the project files to an XML based architecture - something that can be easily edited with a text editor and read by other programs. All you'd need to do would be to write the definition file for the Scratch editor so it understands what each block means.
Last edited by tinoesroho (2010-06-04 19:10:02)
Offline
Should it be implemented under a Data Block section...? Or something else.... I just lurve the idea.
Offline
Basically, we need several new block categories:
Data
Network
Data would include the following (for starters):
[Save _ to _]
[Import _ to _]
[Load _ project]
[Set _ to SpriteX Costume]
As for what goes under network, it's up to the community to come up with ideas for blocks - or the staff.
Offline
Great idea! I fear, however, that this might add to the almost nonexistent learning curve involved with Scratch - if you can find a way to make this ultra-easy to learn, then great! I definitely support this, though, I'm just pretty sure the Scratch team won't unless it's simpler.
Offline