To me it's a bit difficult to digest in its current format. I would prefer to see a list of design patterns with descriptions of concrete problems and proposed solutions. This doc could be PAYG in itself. You come across a problem, solve it with PAYG, add an item in the doc, if the idea isn't already there.
-- View this message in context: http://apache-flex-development.2333347.n4.nabble.com/FlexJS-PAYG-definitions-and-guidance-Please-participate-tp62738p62760.html Sent from the Apache Flex Development mailing list archive at Nabble.com.
