How is antialiasing implemented in the Rive renderer? It doesn't appear to be using MSAA. I took a look at the source code, I found some shaders that mention coverage and AA, but I cannot figure out how it works.
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).
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?
EtoileFoundation is a still a bit work-in-progress, and we include some features that only work with the GNUstep Objective-C runtime (e.g. prototypes).
But beside this, it is well supported on iOS and OS X. The test suite runs on our three target platforms: GNUstep, Mac OS X and iOS, and we use it daily on both OS X and GNUstep.
The EtoileFoundation version bundled with CoreObject is also a special snapshot just for the CoreObject release.
