Scratch

That's a very ambitious solution... However, I'm sure that there is a better language to use. I have even contemplated scratch to javascript!

Yes. Here's the basics of how it would run:
> All variables are read and parsed, the 'var XXX' code is added to the beginning of a head section script. XXX being the variable name in scratch.
> The user is prompted for the root loction of all required media.
> There is a folder created in the root directory for every sprite, and one for the background.
> There are three folders in each of these: costumes, sounds, and scripts.
> All costumes are exported to png format into the correct costumes directory. (png is high quality, and supports the alpha channel)
> All sounds are exported to the sounds directory.
> all scripts are converted to javascript files. details below.
> A javascript object is created for each sprite.
> each script is loaded from the scripts folder, and a method is created for each.
> a 'return "done"' statement is added to the end, so allow the 'broadcast and wait' block to work properly.
> each object loads the first costume as an image. It is positioned absolute, at the coordinates 0,0 (left:240;top:180).
> Here are how some blocks will work:
- set x to [0] : document.getElementById('sprite').style.top='0'.
- switch to costume [costume1] : document.getElementById('sprite').src='ROOT/sprite/costumes/costume1'.
- if <boolean> code1 else code2 : if (boolean) {code1} else {code2};
- repeat(#) code : for (i=0;i<=#;i++) {code}
- ask[pick a number...] : var ASK1 = prompt('pick a number',' ');
- answer : ASK1
- ( + ) : +
- < or > : ||
> The rest of the blocks would be implemented similarly.

Some notes for extracted resources:

(*) Resource root directory and its sub-directories for each type of resource are auto-generated by this tool. So the "destination folder" doesn't need exist before running this tool.

(*) Command line interface is also available, which means, "source SB filename" and "destination folder" could be provided in parameters. e.g., java -jar Extract.jar Test\FishChomp.sb Test\FishChomp

(*) All sounds are saved in WAV format.

(*) All images are saved in PNG format (as billyedward suggested ^_^)

(*) All color values are generated as "RGB(red, green, blue)"

(*) All string values are covered by double quotation marks.

(*) All boolean values are presented as "true" or "false"

(*) A thumbnail image is generated for the project and placed in root dir.

(*) An attribs.txt file is generated for the project, which includes information about author, comment, scratch-version, history, language, etc. Multi-line values are using "<br>" as the line breaker.

(*) A sub-dir "stages" is created, which includes all stages in the project. (Even so far as I know, there's only 1 stage supported in Scratch. correct?)

(*) In all resource directories, items are stored in separated sub-directories, with a numeric folder name, starting from 1.

(*) For a stage, following resources are extracted: backgrounds, lists, scripts, sounds, sprites and variables in separate sub-dirs.

(*) An attribs.txt file is generated for a stage, which includes information about position and size (left, top, right, bottom), background color, name, default_background (the name of one of its backgrounds), sound attr (volume and tempo).

(**) For a background, a named PNG image file and a attribs.txt are generated. File attribs.txt includes information about background name and image file name.

(**) An attribs.txt is generated for a list, which includes information about name, position and size (left, top, right, bottom), visible (boolean), background color, shadow color and items list. Items list is a set of string values, e.g. ["first item", "second item", "third item"]

(**) For a script, attribs.txt and codes.txt are generated. In attribs.txt, position info is generated (left and top), which is only used in Scratch SDE. Script codes are saved in codes.txt.

(***) Also, a script may have sub-script(s), and these sub-scripts may have their sub-scripts... e.g. doForever(subScript[1]), where subScript[1] means the script placed in codes.txt under sub-dir "scripts/1/" of current directory.

(***) All sub-scripts are generated as elements of array subScript[], e.g. "subScript[index]"

(**) For a sound, an attribs.txt and a named wav file are generated. File attribs.txt includes information about name, sound file name and rate.

(**) For a sprite, an attribs.txt is generated as well as following sub-dirs: costumes, scripts and sounds. File attribs.txt includes information about position and size (left, top, right, bottom), name, rotate_degree, rotate_method ("normal" or "leftRight" or "none") and draggable (boolean).

(***) For a costume, an attribs.txt and a named image file are generated.File attribs.txt includes information about costume name and image file name.

(**) An attribs.txt is generated for a variable, which includes information about name, value, visible (boolean), position and size (left, top, right, bottom), name_visible (boolean).

Last edited by menway (2009-08-21 04:38:17)