> I'm fascinated by what makes sense declaratively, and what doesn't. Flex is > a great playground for the two styles.
That's exactly why I (and likely you) found the AS3-based event handler method distasteful (from your original post): you're forced to do something best expressed declaratively in the imperative language. I'd like to see Flex become even stricter in this distinction: - MXML is declarative and best represents *structure*. - AS3 is imperative and best represents *behavior*. - CSS best represents *styling*. The closer we can get to not being forced to muddy the 3 the better our code will be. This thread touches on a big place where I often have to muddy MXML and AS3 (view elements reacting to nested and/or complex model changes). While I'm on the subject (though it's unrelated to this thread), I'd love to see Flex really beef up the CSS, allowing for things like applying multiple styles to a single component (e.g. style="redBox bigFont" instead of just styleName="redBoxWithBigFont"), style shorthands (e.g. padding: 1 2 3 4 instead of paddingTop: 1 paddingRight: 2, etc...), and making more layout properties stylable (width, height, x, y, left, right, etc.). Troy.
