It’s that time of year again, and I’m lucky enough to be in San Francisco representing the b2cloud team at Google IO conference. I’ll be live blogging during the day so stay tuned for all
We are thrilled to announce that b2cloud has won the Mobile Design Award for Best Wearable Technology for our work with Telstra. The award recognises our innovative work using Google Glass to help empower the visually
So today I realised it was Earth Hour. The event didn’t have much hype this year so I suppose you can forgive me for forgetting about it. The only reason I remembered it was because
When developing on the Mac and using custom frameworks in your application, when you compile the frameworks are copied into your applications bundle then linked at runtime. These frameworks will most likely be bundled up with their headers. Some of the frameworks you include may not be things you want to make public to the world, which you are essentially doing by including the headers with the framework.
Since Xcode 4.1 when your application throws an exception your console just prints a list of function pointers and you don’t get a proper stack trace. This isn’t helpful if you’re trying to find the exact line the error occurred on.
In Xcode the build settings screen can be pretty daunting for some people, especially when you start iOS/Mac development. Knowing which settings to pick can be tricky, but I still see a lot of people that do this individually for each of their projects, which makes it easy to miss crucial build parameters you don’t want to distribute your app without. Using a .xcconfig file is extremely useful for solving this problem, it is a type of file for determining build parameters, meaning you can have this file sitting in one spot and have each of your projects referencing it. If you need to make a build setting change to all your projects, you can just add it to this one file and the next time you compile each of the projects the change will be taken into account.
This is an email sent to our clients on launch of the New iPad today Team, You may have heard that a “New iPad” (that’s the name) was released overnight. This will impact clients with native
In Objective-C most things that get passed around inherit from NSObject. Because of this when you want to add a primative type to an array or dictionary you need to wrap it in an NSObject, usually an NSNumber. If you have specifically set an NSNumber's value/type you can easily just use intValue, floatValue etc etc to pull out which ever type you put back in, but how do you know which type should be pulled out if your code is dynamic and uses any type of NSNumber.