I’m likely to be doing more Flex programming in the relatively near future, so I’m gathering interesting posts.

http://www.zeuslabs.us/archives/87/separating-layout-from-style-and-functionality/

My only problem with this example (and it is primarily because it is just an example) is that it makes it much harder to see the direct consequence of an action - you have to go hunting for it - the button and its clickAction are loosely coupled, which is a good thing in many cases, but harder to understand when you’re trying to support or maintain.

I suspect that better naming strategies would help here.  And certainly I’m not blaming the author of the post - he was focused on demonstrating separation, not maintainability.