Fair enough. I hadn't considered other ide's. Maybe there are alternatives that could be setup for other ide's with supporting documentation of code guidance, rather than "standards". I agree we can't make everyone follow the same coding conventions, but we can highly encourage them.
>From my experience it's really hard to find multiple coders that completely >agree on a convention, because everyone has their own. But if we can at least >agree on a subset, and publish it into a guideline and/or some sort of >formatting utility, then it's better for the collaborative efforts on large >projects. - Doug -----Original Message----- From: Michael Schmalle [mailto:m...@teotigraphix.com] Sent: Wednesday, January 04, 2012 2:57 PM To: flex-dev@incubator.apache.org Subject: RE: Flex SDK code conventions This is kind of what I was getting at. The problem with the Flex Formatter is it's an Eclipse plugin that last time I looked. The dev might have abstracted it but I don't know. The problem is Flash Builder is not the only ide in town. Mike Quoting Douglas Arthur <dart...@vmware.com>: > I for one vote that we suggest developers to use FlexFormatter and > publish a settings file for public consumption. I believe Adobe uses > it in-house, please someone correct me if I'm wrong? And I even > believe there's a settings file floating around from Adobe. > > http://sourceforge.net/apps/mediawiki/flexformatter/index.php?title=Pr > eferences > > > - Doug > > -----Original Message----- > From: Michael Schmalle [mailto:m...@teotigraphix.com] > Sent: Wednesday, January 04, 2012 2:48 PM > To: flex-dev@incubator.apache.org > Subject: Flex SDK code conventions > > I hate this topic but it needs to be asked to the community. > > Since I am an initial committer I will stand by whatever the consensus > is with the code I commit. > > But then the question, what are we doing about this? > > There is already ALOT of code in the sdk that uses different > conventions. I think this is ridiculous because it slows down > development switching from this format to that format (reading and > writing). > > I don't have an opinion on conventions, just proposing there needs to > be protocol with committers on this sooner than later. And this > protocol needs to be documented on a public page visible to any one > that has this same question creating patches. > > Mike > >
