I just had the absolutely horrible experience pleasure of using Flex again.  For details why, check Appcelerant in the next few days.  However, there were a few things that I couldn’t help but get off my chest.
- The documentation sucks, especially for their command line tools.  I will readily admit that this is partially my fault, but I don’t quite understand the relationship between ActionScript, MXML and Flex. I spent about a day just getting bogged down in figuring out what I need to get things done. Â
- Related to above, there aren’t enough good examples.  At least on pages that are easily accessible for free, there wasn’t very much actual code that was helpful.  Most of what I was presented with, I couldn’t make heads or tails of.
- Flex/Flash (Flesh?)Â is actually quite good when you want to do something visually snazzy. Â It should be used in these cases.
- ActionScript is adequate when you don’t know Javascript.  However, it is piss poor when you get accustomed to the power stemming from javascript’s dynamic nature.  It’s not long before you really start to miss things such as being able to bind variables to a function that will be called by an event handler. Â
- c.verticalScrollPolicy = ScrollPolicy.off; c.horizontalScrollPolicy = ScrollPolicy.off;Â Are the most crucial lines when it comes to developing in Flex. Â Otherwise, Flex will put ugly scrollbars oneverything.
- The Flex-Ajax Bridge is really cool. While this does suffer from the same documentation pitfall as Flex proper, the bridge is really neat.  The biggest benefit is that it allows a developer to use Flex for it’s strengths (snazzy visuals, scrollbars, etc) and use something else for the rest.
- You can’t index a Flash Movie.  If it’s not on Google, it doesn’t exist. Â