"Collaborative editing on any document, Easy data sharing between applications, Everything is searchable, past and present"
"On any document" doesn't sound like Objective-C any more. One of the videos shows drawing shapes not source code. If it had "library" in big and bold somewhere then I would probably be like "Ah I see". But the word library is not found on the page except in the description of a minor feature.
Bottom line: I was (still am) confused what this thing is other than it does some cool version-controlled, collaborative editing.
For every commit on a versioned document (or branch more precisely), CoreObject will compute an object graph diff, and save it as a new revision in the store.
For the collaborative editing, we have a distinct and optional synchronization layer, that can observe in-memory changes to versioned documents, and push the latest object graph diffs over XMPP, between a server (the person sharing the document) and some clients (the invited persons).
For some more explanations, you can check: http://coreobject.org/technotes/#collaborative-editing
Also CoreObject is not strictly limited to GUI or traditional desktop applications, we plan to port it to iOS, and nothing prevents you to use it in a command-line application.
I think many programmers in the open source world are put off by custom file formats and custom network protocols that are only supported by one library. Of course, basing the file format on SqlLite certainly helps, but that's only the bottom level.
It would be nice to have a design doc that explains the SqlLite schema and network protocol, and least a proof of concept for another library that speaks the same protocol that's not written in Objective C. Perhaps this would be the start of a standard that more people would use?
> CoreObject is a version-controlled object database for Objective-C that supports powerful undo, semantic merging, and real-time collaborative editing.