Tuesday, May 10, 2011
Scratch 2.0 will be “all in the cloud” -- meaning that the Scratch programming editor will become part of the Scratch website. We’re excited about this transition because it has a lot of great benefits. For one thing, it won’t be necessary to download and install Scratch to try it out. For another, it will be easier to see the scripts that show how a project works. Instead of downloading the project file, all you need to do is click a button to see inside and play with the code -- then click another button to remix it. Once the transition to “the cloud” is complete, it’ll be easier for us to continually add new features to Scratch, without releasing an entire new version.
But moving the Scratch editor to the website raises some tough questions. For example:
Should you be able to see other people’s Scratch projects that aren’t yet finished?
If a Scratcher starts a new project and gets halfway through before stopping to do something else, should others be able to see their work in progress? Or should it be hidden until the Scratcher decides they are ready to share it with everyone else?
There are advantages and disadvantages to both approaches. Being able to see a project that’s only halfway finished could ruin the surprise of a newly released project. On the other hand, some Scratchers might like to get constructive advice and feedback on their unfinished, draft projects.
Right now, we’re imagining that Scratchers will work on their projects in their own private section of the Scratch website. Their project will only become visible when they click a button to “share” it with the rest of the Scratch community. But because we’re still in the early stages of developing Scratch 2.0, this could still change.
What do you think? Should Scratchers be able to see each other’s draft projects? Post your thoughts on this forum thread.
Edit: Don't worry, we are still planning to make a downloadable Scratch application, so it will still be possible to work on projects "offline." See more about this in the Scratch 2.0 FAQ.