[Seaside] Meta models

[Todd Blanchard]

>I'd like to have a meta-data framwork in the next week or so (I'll be working hard).  Do you have time to work on Sagan in the next week?

I have to ask which data's meta you are modeling?

If its domain objects - what do you need to describe about them?  

EOModels are great meta models for storing information about entities, attributes, relationships, inheritance, data types, and mapping to tables, columns, and keys.  NextStep had great tools that could derive a whole UI from an EOModel (rather pedestrian and generally data structure oriented rather than task oriented but it did master-detail navigation nicely).

If an EOModel contains all the info you need it would be great if we could agree to use that.  What I like about eomodels is that they are easy to read, there are tools for editing them graphically, and there are now 3 object-relational libs that understand them (glorp, tantalus, and of course EOF).