Core Data in Motion - the Gems
Jan 23, 2015At long last, Core Data in Motion, my book that helps RubyMotion developers get up to speed with Core Data in their RubyMotion projects, is complete.
At long last, Core Data in Motion, my book that helps RubyMotion developers get up to speed with Core Data in their RubyMotion projects, is complete.
Last year was just crazy. I was attempting to finish writing my book, work some contracts, speak at two conferences, teach my Rails workshop, mentor and teach at a couple of Ladies Learning Code/ChicGeekYYC events, and just for shiggles, my husband and I picked up and moved to a new (old) city - Lethbridge.
I’ve been a Rogers customer since my first cell phone, which was a very long time ago. Sure, every once in a while, I get this twinge because their coverage sucks in rural areas (like where all my in-laws live), but I’ve put up with that, because when I am visiting family I mostly don’t want to be interrupted by work anyway.
While there are a lot of great gems and tools to help us with creating great looking user interfaces in code in RubyMotion, sometimes I still like to explore how to do stuff at the iOS API level without using all the magic. Especially when just writing the code turns out to be pretty straightforward and elegant all on its own.
After my last post, there was an interesting side discussion on Twitter (with @macfanatic and @kastiglione) about some alternatives. It was interesting enough that I thought it would make good material for another post. So here ya go!
So, Core Data and relationships. Lots of iOS apps are small, so why wouldn’t you just smoosh all your data into one big model?
Updated July 12, 2015.
Updated July 13, 2015