Comments for Chris Boyd

Comment on Quicknote: Use Spotify with the Nike+ app by Ryan

Ryan — Mon, 23 Jan 2012 23:03:22 +0000

Thank you! You just made my afternoon.

Comment on Girl Walk by Chris Boyd

Chris Boyd — Thu, 19 Jan 2012 15:23:38 +0000

The Girl, man. You will fall in love with the Girl. Watch #8.

Comment on Girl Walk by Wylie

Wylie — Thu, 19 Jan 2012 15:21:47 +0000

so at frst i ws all ehhhh then i was all THIS LOOKS TOTALLY BITCHIN’!

Comment on Quicknote: Use Spotify with the Nike+ app by Andrew Bonham

Andrew Bonham — Sat, 14 Jan 2012 13:59:10 +0000

I wondered how to get around this and a quick search yielded your solution which is great, thank you.

Comment on Things I Use: Sidestep by Matt

Matt — Wed, 11 Jan 2012 17:53:00 +0000

This software looks great. It’s a step in the right direction for your average computer user, but it’s still falls just a little short. If I had to tell any of my non-techie family to use this software, I think most of them would figure out how… all the way up until I said “Oh, and you need a proxy server”.

Comment on 2011: A Year in MP3s by Chris Boyd

Chris Boyd — Mon, 09 Jan 2012 18:50:17 +0000

Do it!

Comment on 2011: A Year in MP3s by Wylie

Wylie — Mon, 09 Jan 2012 17:58:54 +0000

I am so gonna do this this year!

Comment on iCloud and the new iOS Data Storage Guidelines by Sjors Provoost

Sjors Provoost — Fri, 23 Dec 2011 07:27:48 +0000

Thanks for the suggestion. But what if we want do want our “critical data” to be included in the backup? The only solution then seems to be splitting the database to use two sqlite files; both in /Documents and one of them marked as “no backup”.

That creates a whole set of new problems though…

Comment on iCloud and the new iOS Data Storage Guidelines by Chris Boyd

Chris Boyd — Fri, 23 Dec 2011 06:28:48 +0000

I hear you on reading things earlier. I've read a lot of blog posts that would've saved me TONS of time, and it's always like...facepalm. Such is life as a developer. There's always room for improvement. Yes, I am storing images inside of Core Data, as NSData. It's actually really easy, because UIImage can convert from NSData with one line. So what I ended up doing (and this reminds me I should probably update the post) is putting the sqllite file back in Documents, but marking it as a file that should not be backed up. This fulfilled both requirements: That the data be persistent, not cleared out when iOS is low on space and trashing cache files, and the App Store review requirement that large files not be backed up by iCloud. In other words, you can keep your stuff in the main Documents folder, but be sure to mark it as not to be backed up. You can do that by using the method from the example here: http://developer.apple.com/library/ios/#qa/qa1719/_index.html#//apple_ref/doc/uid/DTS40011342-CH1-DontLinkElementID_4

Comment on iCloud and the new iOS Data Storage Guidelines by Sjors Provoost

Sjors Provoost — Fri, 23 Dec 2011 06:15:11 +0000

I should have read this earlier

Do I understand correctly that you are storing images inside Core Data? That’s safe to put in the cache directory, but what if you also store other things in the database? I.e. “critical data”.

Do you have to split the database and use two NSPersistentDocuments, one in the documents directory and one elsewhere?

I posted the same question on the Apple forum:
https://devforums.apple.com/message/595188#595188