Blog Posts by Tom
The new iPhone 5S, iPad Air and iPad Mini all now use Apple’s A7 64 bit processor. Just like the introduction of the 64 bit Intel Macs, developers need to update their apps for 64 bit compatibility. If your app was coded well, this means minimal effort and not requiring many code changes.
I’m currently writing a program which takes input and simulates it back out as keyboard presses.
It’s quite easy, and can be done like so.
Safari applications seem to have a different scope between your target html page and main.js end script. This means that if you wish to inject a control onto your screen which calls a function in your main.js script it will not work because the two can’t see each other.
There’s a lot of MD5 iOS solutions floating around out there. From the ones I’ve seen, they all have a common problem. They all assume you want to MD5 an NSData instance, meaning all of the data must be in memory in order to digest it.
Now this will work in most cases, but say you want to MD5 a 1 gigabyte file… on an iPhone. You’re probably going to have a few problems.
Over the Christmas holidays I was building an app in my own time and came across a bit of a common problem I wanted to solve – multiple PNG exports all at different sizes for graphics in an iOS app.
In iOS7 a view controller now positions it’s view from the top of itself compared to previously starting below the navigation bar. If you use a single scroll view you can set automaticallyAdjustsScrollViewInsets to YES to automatically handle things for you, however if your UI is more complicated then you may need to do things manually. The view controller has a topLayoutGuide property which is useful in some cases, but unfortunately doesn’t take parent view controllers into consideration, or the view’s origin inside the view controller.
I’ve always been interested in app file size and the overall app’s performance. When dealing with images, these sometimes go hand in hand…
In this weeks performance comparison I will be comparing convering a number to a string.
There are two common ways of doing this.
This post will compare the time taken to concatenate strings using common NSString and NSMutableString methods. Often I see people using initWithFormat: to paste together all their strings, but is this the fastest?
In one of my recent projects I added a content inset on the top of my table to push the start of the content down. Unfortuantely when you set the content inset the table assumes that all your sticky section headers now also start from the end of the content inset. This was not the behaviour I wanted, and instead I needed them to stick to the top of the table where the cells start to go out of bounds.