While doing mobile development, one of the most frustrating things has been form input.
If you’ve looked at any Playbook development, you’ll see QNX has something called ReturnKeyType specifically for this reason.
Being as stubborn as I am, I wanted a plain Flex approach at accomplishing what I wanted, and not to use the QNX library.
Most of this actually is related to Mobile development with AIR, considering there isn’t a bunch of desktop development focus in the SDK.
Adobe released an early version of Flex 4.5 (Flex Her0) just before Adobe MAX last year, and tons of people grabbed it and started writing mobile apps with it.
Since then, quite a bit has changed both in common functionality, and under-the-hood things like List scrolling.
I couldn’t find any clear documentation about migrating your applications, so I figured I’d try to throw together as much information as I could think of.
I will be updating this frequently as I find more changes or caveats while converting my apps, or from what I hear from others.
Read the rest of this entry
So, I partook in the free Playbook offer sponsored by RIM, and developed a few applications for it.
This post is NOT about my apps, but rather touches on the process, as well as what I think about the Playbook as a device, and platform.
Read the rest of this entry
There’s a few good use-cases for serialization; for me the first and foremost is the performance combined with ease of use.
In AIR we have SQLite access, or in a bad case we can write some format to a file and recover it later somehow via parsing. But why? That’s a lot of work… And it’s not the fastest approach either.
And what about if we’re doing a browser application that we want to save a state of something, but don’t want to host the storage and write a web service to handle data?
We don’t have stealth access to the filesystem directly, which makes it hard (errr, impossible) to silently store things on behalf of the user.
We can actually tackle both easily using serialization.
I was playing with the Geolocation API, and have been having the hardest time getting it working. It would activate the GPS on my device (a Droid2), but would never trigger any updates and hit my breakpoint.
I knew this had to be something I was doing, because I’ve seen it working, have examples of working source, and can’t get it to work on my device…
Sorry for a jump in session numbers, but I was called to look at a bug and ended up missing my third session!!!
As for THIS session, we get a nice organized view of the new features of the Flex 4 SDK. While it is all very exciting, they seemed to have taken an approach to not overwhelm developers moving into this new construct.
Adobe AIR is Adobe’s response to multi-platform applications that can interchangeably be ran as a Flash component. With this flexibility, Flex developers can quickly and easily produce applications that can traverse many platforms.