Re: Core Data Applications
Re: Core Data Applications
- Subject: Re: Core Data Applications
- From: Bill Bumgarner <email@hidden>
- Date: Tue, 17 Oct 2006 11:02:45 -0700
On Oct 15, 2006, at 3:38 AM, Jakob Olesen wrote:
On 15/10/2006, at 12.05, Uli Kusterer wrote:
Considering how new and complex CoreData is and how much of it is
done through special UI
What do you mean, special UI? The data modeler?
I would love to see a textual file format for data models. I think
the current situation is untenable: Graphical editor saves to
undocumented binary .xcdatamodel format, momc compiler translates
to undocumented binary .mom format.
The data model is one of the most important things to keep under
strict version control. What happened to diff? svn blame?
There is a huge difference between a textual file format and a
textual file format that is diffable, blameable and ponderable.
(Though I fully agree that a diff/blame/ponder compatible textual
file format would be really *really* valuable).
There is nothing particular proprietary about the contents of a
model. The momc basically takes the inbound .xcdatamodel and strips
out down to a minimal binary representation of exactly what is needed
at runtime (layout of the entity diagram is not needed, for example).
The Core Data API includes everything you need to fully read/write
models. As such, it wouldn't be hard to read a model -- maybe even
passing the model through momc first -- and generate a text file
describing the model from there. You could even do it so that
diffing two version of a model from svn was trivial -- automatic even.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden