Triage

The main challenges stand in our way: Pinch/Zoom, Optimization, iOS inconsistency's.

The Pinch/Zoom function I wrote two weeks ago was a good stop gap, however its not what people who are used to the feature would find usable. Now with Matt back in the office, I'm going to let him take his shot at the code.

This functionality is not easy folks, a decent amount of geometry is needed to correctly translate an object to the specified zoom in location & above all it needs to be lean enough to run on iPhone's. We are looking at examples of how other dev's have tackled the problem for some inspiration.

Optimization is a on-going challenge that continually appears right after you think you nailed the issue. Making sure that all artifacts are cleared up at the end of every state change is REALLY important, not to mention time consuming. I would love to use Adobe Scout, but we don't have any 64bit OS's in the office.... Until that point in time I'm stuck using Flash Builders own profiling tool.

& finally there are some super bizarre differences between PC & when we deploy to iOS in certain circumstances...

Some UI elements like a text field are strangely shifted out of place by a margin of 10 or so pixels... This is breaking the nice neat & tidy alignment we had of our UI elements. I cannot explain it, neither can Matt. The code is perfectly sound. Not to mention the fact that the issue affects one element, but not an identical element right next to it. And as I said these inconsistencies only appear on iOS, which means we need to build, deploy & test on device which drastically slows down the debug process.

At this moment in time its time to surrender to the fact we don't know whats going on & go get the duck tape. For each of the issues we will make a custom, specific fix to address the alignment issue. Is it excessive? Yes, absolutely, but we have run out of time to re-write our button class from the ground up again. So its time to bite the bullet.