Embryo Systems

Yes already 0.0.1.

That version is just a tag I added because the current code is already showing one of the main important features :

• be able to create ADT (limited to Class/Attribute/Link/Object).
• change the state of an existing ADT
• few checks to make sure of the existence/non existence before processing (still need to work on that).
• basic persistence (in fact, the dummy storage store the ADTs in memory …).

The next step I think would be first to add a way to report any error during the process of a request instead of sending exception in the wild. Then make sure the parents are in the proper state and check for HADR than the current state is compatible with the operation.

The storage part and the fact that the current architecture is somehow too simple doesn’t matter for now. It can be changed veery easily later on. The goal is to have a working ADT manager.

The biggest leap will be to add object attribute and object link …

I moved the project to Google Code for the management and remove the trac system.

Lighter to manage. And easier to focus on development.

Happy New Year 2009 !

The infrastructure is there … finally.

A read-only subversion access is now in place: http://embryo-systems.info/subversion .

The skeleton of the project is there too. I will soon push the first build scripts and add more substance to it

Welcome to Embryo Systems.

Embryo Systems will be a simulation engine able to define anything in the system at any moment (runtime or not). It will be written mostly in Java with pieces of Ruby, Shell or Python.

The main idea behind this project came from a university project initiated by M. Francois Bouille, which was director of the L.I.S.T. section at university Paris VI when I was a student there in 1998.

I will post in details later on the plan.

Thank you

Nicolas Dufour