Super quick post… I’ve created a simple LayoutHelper for Josh Tynjala’s FoxholeControls.
This will help simple containers lay out their components without having to do a ton of custom property/member inspection for each child you want to lay out!
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…
This is a seemingly trivial task, but attempt to tackle it and you’ll quickly find yourself scratching your head wondering what the hell you’re doing…