I’ve been having a major issue with Flex/Adobe AIR over the last week or so when serializing my data to files. I use a FileStream and call writeObject() on an ArrayCollection of my data. Pretty simple. Serializing seems to run fine, deserialization as well. The problem arises when I try to cast items in the collection to their appropriate type. It seems the objects have lost their type information and are plain Objects.

After a while of thumbing through the documentation it finally hits me. FileStream uses AMF3. Usually when using AMF3 you define RemoteClass metadata for each of your classes that mirror server-side classes. I had just assumed that since AIR knew I would be loading the object back in AIR again, it would do that stuff automatically. Turns out it doesn’t. A few lines of RemoteClass metadata later it’s working fine. You just need to define the alias as being your class with the full namespace typed out. Not in the documentation (or if it is, it needs to be in a more obvious spot such as here or here). Although knowing its was AMF3 format, I probably should have realized this sooner.

Hope this saves someone else some time.

Click here to see more information, but the gist of it is meetings on the first Tuesday of each month!

The first meeting is April 8th at 7PM at Adobe’s offices in Newton, MA. Topic will be the open sourcing of the Flex SDK.

I’ll be there, and if any of my readers will be too, drop me a line.

In the past week or so I’ve begun development on a Flex-based Blog Engine. I don’t have any screenshots or videos of it yet, as it is not entirely functional yet.

It uses Flex,PureMVC, PHP, MySQL, and WebOrb for PHP.

In the meantime, check out the preliminary information and keep an eye out for updates!

I had an interesting thought tonight that I thought I’d share. Most of the recent Flash/Flex website fall into three primary categories in terms of interaction: applications, web page emulation or the ever-loathed eccentric designs. Obviously, applications are Flash sites that behave much more like traditional desktop applications. However, the other category is usually seen when someone is making a flash site in lieu of an HTML site, so we get a design that has behavior similar to HTML pages. Click button (Request), go to “page” with content (Response). “Page” transitions are pretty, but the use of these transitions usually add an extra unnecessary 200-300kb on the download. We’ve all seen our fair share of these sites, some hit some miss. The last category is the eccentric design category. These are the Flash sites you go to and spend 5 minutes trying to figure out how to navigate (or read instructions) and when you do, you get an experience worse than category 2.

Everyone hates the last category, tolerates, the second, and are usually very accepting of the last (only for those applications that follow typical application behaviors). There has to be some middle ground between the second two. Interaction that is neither entirely Request-Response nor eccentric. What would that be? I think what I’m looking for here is a paradigm that allows for standardized navigation but also asymmetrical flow of information. I’m not saying it would work, but it would certainly be worth exploring. Possibly some type of AI could be used that acts as a broker between the user and the content. How’s that for out of the box? An AI driven website?