We could format the entire SDK after it's available. In doing so, we would gain initial uniformity.
If we decide to go this route, we can export all of the formatting settings and come to a consensus about the format on-list. Afterwards, it would be the responsibility of each developer to adhere to the standard, or, we could just keep formatting the SDK. On Fri, Feb 24, 2012 at 12:04 PM, Omar Gonzalez <omarg.develo...@gmail.com>wrote: > On Fri, Feb 24, 2012 at 9:00 AM, Yennick Trevels > <yennick.trev...@gmail.com>wrote: > > > I've got nothing against flexformatter, but it's an eclipse based plugin, > > so we have to make sure that we don't make the rules too strict (aka > > flexformatter specific) since also other IDE's are being used. > > > > On Fri, Feb 24, 2012 at 4:29 PM, Martin Heidegger <m...@leichtgewicht.at > > >wrote: > > > > > On 25/02/2012 00:26, David Francis Buhler wrote: > > > > > >> Can we use FlexFormatter (BSD License?) and share a formatting > > properties > > >> file that adheres to a format reached by consensus? > > >> > > >> [1] http://sourceforge.net/**projects/flexformatter/< > > http://sourceforge.net/projects/flexformatter/> > > >> > > > I don't see why not. The formatter properties could be hosted in the > > wiki! > > > > > > cheers > > > Martin. > > > > > > > I remember saying that the IntelliJ options pretty much can duplicate what > we set up with FlexFormatter. Personally, I'll be using IntelliJ. It would > be nice to come to an agreement on formatting rules though, it will make > the code easier to work with as we have more and more people contributing > code. It just takes a long time to set up the settings and I'm sure we'll > all have some strong opinions on which way those settings go. I think its a > good discussion to sort through before we get the rest of the donations > from Adobe and really start hacking away at the codebase. > > -- > Omar Gonzalez > s9tpep...@apache.org > Apache Flex PPMC Member >
