Today began like any other day... I sat down to ROCK THE WORLD WITH FLEX and noticed that Adobe was pushing me an update for Flexbuilder; 3.0.1 to be exact. Puzzling... I didn't see any info about this and there are no changelogs to be found detailing what is in this update.

I received an email in response to my blog post on creating an image marquee component... "Could you do something similar with text?" - they asked.

The real power behind Flex isn't in the base components... the real power is found in extending them.

Implementing complex behaviors/relationships requires flexible structures/types to make things happen... which is where covariant return types come into play.

Merapi is not just a volcano on the island of Java... it is a technology that bridges the AIR / Java gap.

Does a particular feature have you 'living large' in for-loops? Do you spend more time in the day typing 'for each (blah... blah..' than you do brushing your teeth in the morning? If you answered yes to these questions... implementing a specialized collection may help.

For anyone that is interested / active on LinkedIn – there is a group for Flex coders in the US.

LinkedIn: Flex US Developers

So... I just ran across this article. It's been around for a while - but it's worth the read if you haven't already seen it.

Ah, the irony! Microsoft says Safari isn't safe on Windows

Passing any kind of data in HTTP headers can be a tricky business - especially for Flash based technologies.

As developers gain more experience in Flex - it is natural that they will want to squeeze more and more out of the mxmlc and compc compilers. Here is a bucket-load of settings originally posted by Vadim Melnik which seems to have fallen out of grace with Google - or maybe he just changed the link. At any rate...