When it comes to creating mobile applications there is still no argument that native is without a doubt the best approach. But if you are trying to recreate the Great Wall of China, using nothing but a bucket and spade, Appcelerator could be your light at the end of the sand filled tunnel.
While working with Three.js on CubeWall and various other projects and experiments I often found myself getting a little frustrated having to repeat various tasks over and over again.
I have always found myself wanting to play around with 3D ever since Flash’s 10.0 player release gave us 2.5 3D but up till now I have only ever managed to skim the surface. So I figured it was time to delve deeper
When working on small-scale projects, applications or experiments I prefer to take on a ‘do it yourself’ attitude and try to leave third party libraries well alone wherever possible. This may be a daunting thought at first but it will give you a more intricate knowledge of how things work.
FDT 5.5’s recent release has dramatically changed the way that FDT now compiles AIR applications. They have added in a plethora of options and tick boxes, to amuse and bewilder you for many an hour
When getting to grips with a new programming language it’s easy to feel lost and confused; like standing at a busy cross road in a foreign county not knowing which way to turn, getting no help from your iPhone and funny looks from the locals.
Since I first read Kieth Peters “Foundation ActionScript Animation”, a book I strongly suggest you read, I have wanted to make a Particle NodeGarden. So one Sunday afternoon I decide to treat myself and do that very thing.
One of AIR 3.3’s new features enables you to test your applications directly on the iOS Simulator shipped with Xcode. This dramatically increases the speed in which you can preview your applications, eradicating that tedious pause between shifting a pixel in your code and seeing the result on device.
AIR has come a long way in helping developers bridge the gap between desktop and mobile development at the touch of a button, which of course is all dependent on your IDE.
Being quite new to native iOS development, and having previously tried to steer clear of anything Xcode and Objective C related, mainly because of its essay-style method calls, but also because I had to constantly try and remember how to access the hash key on my mac.