This has been discussed in mailing list before. I guess this is more related to personal style of coding than overall style.
To myself, the current way of Adobe code styles fits on our needs, we need to focus on concrete changes, not substantial ones. Writing a guide to help new contributors is much better than change hole code way of style. Like theses does here http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions and here http://www.dclick.com.br/2007/02/13/adobe_flex_coding_guidelines_english/ Regards ---------------------------- Igor Costa On Mon, Feb 27, 2012 at 8:34 AM, Justin Mclean <jus...@classsoftware.com>wrote: > Hi, > > I suggest we take the pragmatic path in that we take how the current code > is formatted. Constancy make it easier to work on the code. I'm sure on > occasion there will be valid reason for breaking those rules and over time > we may move to a new set of rules. > > Thanks, > Justin
