The theme I’m using on Cocoanetics.com has gone to version 1.6.6 which is to say that over the past 2 years our designer has done an awesome job to polish the look. I think it is about time that I give a shout-out to Jeremiah Tolbert from Clockpunk Studios who is in charge of this all.
The updated linker and libtool that come with Xcode 4.6 apparently contain some changes that are causing problem when building projects that link and depend on static libraries. One appears to be a bug, the other is an annoyance. Fortunately we found workarounds for both.
Update: Not a bug after all. Rather a “learning experience”. Details below.
For a long time I had links to Sensible Cocoa, BinPress, Dropbox and Mobfox in the footer of every page on Cocoanetics.com. I also had two entries for other people’s components in my parts store section that linked to another company’s store via affiliate links.
I had established the links because I was hoping to earn a bit of passive income from these links, with the exception of Dropbox where I wanted just wanted to increase my free storage. This was the only successful part, I raised my storage to just under 25 GB over the past year.
When creating image files via CGImageDestination if found something weird. I’m setting the DPIHeight and DPIWidth fields in the meta info to 72. When outputting as PNG format there are some programs that will show the image resolution as 72.009 DPI, whereas TIFF and JPEG for example would display as 72.
Turns out that this is neither a problem of CGImageDestination, libpng nor any specific viewer app. The problem is in the PNG specification.
Here are three small pieces that I discovered while working on my second major Mac app. It’s for internal use by a client, so I cannot tell you about it, but it is a great place for me to learn more about the various oddities you find when developing for the Mac platform.
I noticed the bug when I re-added an Edit menu to a Mac app that I had earlier removed. Turns out that all your NSTextFields lose their ability to cut/copy/paste and undo if you don’t have corresponding menu items.
So after I copied the menu over for another app I found that I couldn’t find the redo: action to connect to the Redo menu item. Filed as Radar rdar://13113666 and cross-posted on Open Radar.
If you use CoreData then you will probably face the problem of database migration sooner or later. Automatic migration is turned on easily, but how can you be reasonably sure that your fresh app update will still be able to open databases using the old schema? Like when people were using the app and are now installing your update that needs more entities.
We were beginning to face this scenario in multiple apps, so we started unit testing CoreData automatic migrations like I’m going to show in this article.
Funny Story: right after I published my findings on how to work CocoaPods I received a couple of pull requests. Should it be actually be the case that fellow developers are beginning to take notice of DTCoreText?
I admit, that for the first few tags/versions of DTCoreText I didn’t take CocoaPods seriously. But since I got down how to work with sub-modules and sub-specs I find that it gives me a great deal of pleasure to keep my specs current.
There are a few trailblazing developers out there who intentionally set their app’s deployment target to iOS 6. When dealing with open source libraries like DTCoreText this might give you a fair share of deprecation warnings. But there is also another problem caused by this that library vendors need to address.
The SDK used should always be the Latest iOS, but the Deployment Target setting tells the compiler and linker at what level of fanciness it can enable the turbo features.