Speaking for myself, my problems haven't been with layouts not being flex-like but rather with unpredictable behavior. Off the top of my head, x=0 now sets positioning to absolute, which changes behavior in more than one way. This is a big side effect, and to me unpredictable side effects are a pain.
I don't think we should be too worried about keeping the feel of either CSS or Flex. If the layout has sound internal logic, if it's consistent and well documented, people will take the time to learn about the rules and use them. If the user has to think whether x == 10 one line after he s/he set it to 10, I think we lose intuitiveness and usability. People who want CSS like behavior can just use CSS, not sure why they would need a layout bead at all. Maybe on the SWF side, but that sounds like an edge case to me. -- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Coordinate-Space-tp59924p59964.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
