Topic: SaLiVA - new format

[BlinkenLights]

syntax shmintax....

we are not quite ready for code yet.. the file format idea is shaping up but its not in any way complete.

<thing>
    <parameter>value</parameter >
    <parameter2>value</parameter2>
</thing>

<thing2>
    <parameter>value</parameter >
    <parameter2>value</parameter2>
</thing2>

[James]

Once we have some syntax we have the bricks, mortar and cut stones to make our castle.

James. 

[Fanny Pack]

Until we know what the castle is supposed to look like the bricks are useless.

[James]

NOT TRUE !!!!

The syntax of a language breaks up the tokens. There are LOTS of things to decide that have NOTHING to do with the functionality of the language.

Is it case sensitive?
How do we deal with white space?
How do we deal with newlines?
Does a statement have to be on one line or can it be broken into many?
What symbol do we use for assignment?
How do you know the difference between a parameter and its value?
What limitations are there to variable names?
etc. etc. etc. etc. etc. etc....

Will there be a dynamic object model behind this code?
Can we reference the DOM like we do in HTML?

Could we jack a kind of JavaScript into that to do our animations and on-the-fly modifications?

These things are ALL ABOUT how to parse it back into actionable code!

You can just assume that we are going to take the "look and feel" of another language, but THAT is still a syntax choice!

James. 

[Fanny Pack]

We already decided on XML for now. All of that stuff is already defined.

[BlinkenLights]

none of the code you write in C++ will effect what gary does in .net or what someone else does in python..

the file structure has to be rigidly adhered to in the writing phase, otherwise the file will fail to be valid.

Now with the structure that XML uses , it can all be on one line because its just look for the next <word> or </word>

it could care less whats in between as long as its empty, spaces, or crlf

[BlinkenLights]

 <recipe name="bread" prep_time="5 mins" cook_time="3 hours">
   <title>Basic bread</title>
   <ingredient amount="8" unit="dL">Flour</ingredient>
   <ingredient amount="10" unit="grams">Yeast</ingredient>
   <ingredient amount="4" unit="dL" state="warm">Water</ingredient>
   <ingredient amount="1" unit="teaspoon">Salt</ingredient>
   <instructions>
     <step>Mix all ingredients together.</step>
     <step>Knead thoroughly.</step>
     <step>Cover with a cloth, and leave for one hour in warm room.</step>
     <step>Knead again.</step>
     <step>Place in a bread baking tin.</step>
     <step>Cover with a cloth, and leave for one hour in warm room.</step>
     <step>Bake in the oven at 180(degrees)C for 30 minutes.</step>
   </instructions>
 </recipe>

[James]

There are a lot of ways this could go... If we choose a code that looks enough like XML, SVG, VRML or whatever, we could then go on to develop a document object model and an active script language for it.............. AND.................

Actually create a new definition for Internet distributable content via HTTP !!!

So, a player application could be on any computing platform and convert the text and associated binary information (like MP3) into a laser show!

Laser shows could be served over the web to your "laser show enabled" browser!

The HTTP protocal was designed to be extensible to accomodate for new forms of information.

http://en.wikipedia.org/wiki/List_of_vector_graphics_markup_languages

A color laser vector projector could become a computer peripheral, like a raster video projector.

Check this out!!!

http://en.wikipedia.org/wiki/X3D

James. 

[BlinkenLights]

Pipe dreams

but the example is a great start.. x3d does kinda what we want.. and we are kinda creating our own markup language.

ever think about the file actually calling a separate file with instructions.. like a wave file that has an analog abstract stored in it..