Create a file format for defining procedural meshes

[GoogleCodeExporter]

A file format which could define procedural meshes could be great in order to 
move mesh description away from code.
However, once this format is defined, it should always be in sync with features 
available from plain code.

Original issue reported on code.google.com by michael.broutin@gmail.com on 28 Oct 2010 at 9:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by michael.broutin@gmail.com on 28 Feb 2011 at 4:45

• Added labels: Milestone-0.4
• Removed labels: Milestone-0.3

[GoogleCodeExporter]

Set it to version 0-3 as Thomas already started working on it...

Original comment by michael.broutin@gmail.com on 3 Aug 2011 at 7:38

• Added labels: Milestone-0.3
• Removed labels: Milestone-0.4

[GoogleCodeExporter]

I'm suggesting yaml. I recently learned to use the yaml-cpp lib, it was quite 
easy

Original comment by ezjonas on 29 Mar 2012 at 4:12

[GoogleCodeExporter]

I'm not sure yet what format I'll adopt, but I'm definitely in favor of a text 
based format, like JSON or YAML...
Maybe something like the ogre material scripts.. or something like the demo 
Miguel Cepero made on his "procedural world" blog.

Required qualities are :
- easily human readable and editable
- concise
- easy to parse and to extend

Original comment by michael.broutin@gmail.com on 29 Mar 2012 at 4:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I started writing a wiki page about requirements and use cases for this file 
format.
Here it is : http://code.google.com/p/ogre-procedural/wiki/ScriptingSystem

Original comment by michael.broutin@gmail.com on 29 May 2012 at 3:43

[GoogleCodeExporter]

Betajaen has started working on a C++ reflection library... it may be a good 
start to bind both getters/setters and attributes.

Original comment by michael.broutin@gmail.com on 31 Aug 2012 at 4:44

[GoogleCodeExporter]

[deleted comment]