Scratch

...so I'll post again the idea: the .m3w (or .m3ow) project file will be a .zip file with changed extension (like Quake 3's .pk3 files). Below is a structure in the archive, where <this> denotes a folder.

<ProjectName>
index.xml
thumbnail.png
<Sprites>
  <Sprite>
    spritedata.xml
    <Spinnets>
      //spinnets, the sprite scripts go here. Eg. spinnet.m3owscript
    <Costumes>
      //costumes go here.
    <Sounds>
      //sounds go here
  <Stage>
    <GlobalScripts>
      //global scripts & stage scripts go here
    <Stages>
      //backgrounds go here.
    <Sounds>
      //stage sounds go here.

Last edited by filo5 (2010-01-03 10:52:11)

Files:
index.xml - project descriptor. All project data go here - name, author, save log, sprite list and stage settings. Root node: <Project>.

thumbnail.png - project thumbnail.

Sprite/spritedata.xml - sprite info: costumes, sounds, spinnets. It's a link between project descriptor and sprite itself. Root node: <Sprite>.

.m3owscript files - script files.

.m3w or .m3ow files - project files. Actually .zip archives.

index.xml example:

<Project name="Welcome to M3OW" author="M3OWMakerz" version="3" stage-size="600x400" last-saved="20100815101204" created="20100705211841" id="WelcomeToM3OW">
  <Save-Log>
    <log-entry type="saved" datetime="20100815101204" />
    <log-entry type="published" datetime="20100814105200" />
    <!-- etc. -->
  </Save-Log>
  <Sprite-List>
    <Sprite id="WelcomeToM3OW-SPRITE-1" name="Welcome-Stamper" sprite-data="/Sprites/Welcome-Stamper/spritedata.xml" />
    <Sprite id="WelcomeToM3OW-SPRITE-2 name="Cat" sprite-data="/Sprites/Cat/spritedata.xml" />
  </Sprite-List>
  <Stage>
    <Script id="WelcomeToM3OW-STAGE-SCRIPT-1" location="/Stage/GlobalScripts/Program.m3owscript" exclude="false" />
    <Costume id="WelcomeToM3OW-STAGE-COSTUME-1" location="/Stage/Stages/welcome-stage.bmp" exclude="false" />
     <Sound id="WelcomeToM3OW-STAGE-SOUND-1" location="/Stage/Sounds/snd1.mp3" exclude="false" />
     <Sound id="WelcomeToM3OW-STAGE-SOUND-2" location="/Stage/Sounds/meow-flanged.mp3" exclude="false" />
  </Stage>
</Project>

Yes. Let's assume you have a proper .m3ow file. Now change its extension to .zip (project.m3ow -> project.zip), and open it in your archive reader. That's it. Now you can see all the structure and data.

that's smart.

But complicated.

How are we uh, going to read this file?

I was having a hard enough time with reading plain text, let alone a zip archive in a clever guise.

I still dunno what about opening file in python.
but there is probably a lib for that.

Hmm... The way the 'sample' project was... is really confusing. 

holy carp that's overcomplicated!

but, very nice diagram there.

Most big video games only have one file per save. and usually it's not an archive.
but, if this is what we're doing, then, uh, I don't know.

I can just understand that, Slightly confused with the first one though.
The difference between run and edit are? If its like Scratch, then it all go into 1, unless we're adding an external complier?

Run mode is done by M3OW Player only. For M3OW itself, user, in order to edit the project, will have to click "edit" button from "project" menu, to go to the editor. Temporary folder will be moved to M3OW folder. The reason I designed the architecture like this, is simple: some people want only to run the project (watch animation, play game, etc.) - then, after running the project, user will get an option - go remix, or switch off. Go remix will do the same as project->edit. Switch off will close the project and delete temporary folder.

The module which runs the project.

correct.

Lets get the editor up and running, then when we add in sprites we start on the viewer (Offline) and once we've got to V1, we start on the online viewer.

Where are these names coming from?!