Comments on: OmniFocus: What We’ve Learned So Far (Engineering) http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/ The Omni Mouth: standing outside your bedroom window playing \"In Your Eyes\" since 2006. Tue, 08 Jul 2008 21:28:46 +0000 http://wordpress.org/?v=2.2.3 By: Tim http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63587 Tim Wed, 26 Sep 2007 16:50:11 +0000 http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63587 Thanks for the pointer; I'll check it out! Thanks for the pointer; I’ll check it out!

]]> By: Nigelito http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63572 Nigelito Fri, 21 Sep 2007 16:28:25 +0000 http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63572 Sounds pretty smart. Regarding the sync... once you've got the XML data store format going, you might want to look at SSE (simple sharing extensions) for doing a lightweight sync. http://en.wikipedia.org/wiki/Simple_Sharing_Extensions Sounds pretty smart. Regarding the sync… once you’ve got the XML data store format going, you might want to look at SSE (simple sharing extensions) for doing a lightweight sync. http://en.wikipedia.org/wiki/Simple_Sharing_Extensions

]]> By: Greg http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63570 Greg Fri, 21 Sep 2007 04:12:56 +0000 http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63570 Technically, if you say the letters (like RTFM) then it is an initialism, and if you pronounce it as if it is a word (like NASA) then it is an acronym. Technically, if you say the letters (like RTFM) then it is an initialism, and if you pronounce it as if it is a word (like NASA) then it is an acronym.

]]> By: Tim http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63539 Tim Mon, 17 Sep 2007 22:48:06 +0000 http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63539 Capturing the inserts/updates/deletes is done via the notification, as you guessed. CoreData could use more API to make this easier -- right now you can just ask it for its inserted, updated and deleted objects, but these sets can get modified during -save: due to the -willFoo and -validateForFoo: hooks. It would be really nice to have some sort of -prepareForSave: on NSManagedObjectContext that would do all the validation & delete propagation. Then, assuming you didn't make any more edits, you could trust those sets. So, we use a silly little approach were we subscribe to the notification, call -save: and in the notification capture the inserts, updates and deletes that *actually* happened in our XMLOperationSet instance. This then gets used when serializing the transaction. Of course, by this point, we've optimistically committed to SQLite, hence the comparison check at launch time on the latest transaction identifier on both CoreData and Our .ofocus file; if we crash between saving to CoreData and saving our XML transaction, we'll catch it there and rebuild the CoreData cache. Capturing the inserts/updates/deletes is done via the notification, as you guessed. CoreData could use more API to make this easier — right now you can just ask it for its inserted, updated and deleted objects, but these sets can get modified during -save: due to the -willFoo and -validateForFoo: hooks. It would be really nice to have some sort of -prepareForSave: on NSManagedObjectContext that would do all the validation & delete propagation. Then, assuming you didn’t make any more edits, you could trust those sets.

So, we use a silly little approach were we subscribe to the notification, call -save: and in the notification capture the inserts, updates and deletes that *actually* happened in our XMLOperationSet instance. This then gets used when serializing the transaction.

Of course, by this point, we’ve optimistically committed to SQLite, hence the comparison check at launch time on the latest transaction identifier on both CoreData and Our .ofocus file; if we crash between saving to CoreData and saving our XML transaction, we’ll catch it there and rebuild the CoreData cache.

]]> By: Linda http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63538 Linda Mon, 17 Sep 2007 22:04:18 +0000 http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63538 What, our documentation guru has never heard of RTFM? ; ) What, our documentation guru has never heard of RTFM? ; )

]]> By: wvh http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63537 wvh Mon, 17 Sep 2007 22:01:08 +0000 http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63537 I don't think it counts as an acronym if you can't pronounce it. I'm just sayin'. I don’t think it counts as an acronym if you can’t pronounce it. I’m just sayin’.

]]> By: Erik M. Buck http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63536 Erik M. Buck Mon, 17 Sep 2007 21:23:35 +0000 http://blog.omnigroup.com/2007/09/17/omnifocus-what-weve-learned-so-far-engineering/#comment-63536 "Given that, I tweaked our XML archiving to support writing a set of CoreData inserts, updates and deletes as a transaction." Cool! How did you do it ? Do you plug into Core Data with a custom store or use notifications to capture the information? Do you instruments all of your entity inserts, updates, and deletes in code ? “Given that, I tweaked our XML archiving to support writing a set of CoreData inserts, updates and deletes as a transaction.”

Cool! How did you do it ? Do you plug into Core Data with a custom store or use notifications to capture the information? Do you instruments all of your entity inserts, updates, and deletes in code ?

]]>