Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1C45CB49F for ; Wed, 4 Jan 2012 22:13:53 +0000 (UTC) Received: (qmail 81672 invoked by uid 500); 4 Jan 2012 22:13:52 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 81646 invoked by uid 500); 4 Jan 2012 22:13:52 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 81612 invoked by uid 99); 4 Jan 2012 22:13:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 22:13:52 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [69.167.147.50] (HELO franklin.liquidweb.com) (69.167.147.50) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 22:13:45 +0000 Received: from localhost ([127.0.0.1]:44205) by franklin.liquidweb.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1RiZ5F-0004vU-9r for flex-dev@incubator.apache.org; Wed, 04 Jan 2012 17:13:21 -0500 Received: from 66.153.67.167 ([66.153.67.167]) by www.teotigraphix.com (Horde Framework) with HTTP; Wed, 04 Jan 2012 17:13:21 -0500 Message-ID: <20120104171321.82151tjgbtatbk01@www.teotigraphix.com> Date: Wed, 04 Jan 2012 17:13:21 -0500 From: Michael Schmalle To: flex-dev@incubator.apache.org Subject: Re: Flex SDK code conventions References: <20120104164825.76442cnpt5zssw15@www.teotigraphix.com> <21F668673FA0C04AB9042388AC13A414037EE9DC6F@exch-mbx-111.vmware.com> <20120104165709.213004zeg922u4ad@www.teotigraphix.com> <5097C62C-539B-4096-BE9C-0EB52A7B6AF9@rogeliocastillo.com> In-Reply-To: <5097C62C-539B-4096-BE9C-0EB52A7B6AF9@rogeliocastillo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.9) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - franklin.liquidweb.com X-AntiAbuse: Original Domain - incubator.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - teotigraphix.com X-Source: X-Source-Args: X-Source-Dir: X-Virus-Checked: Checked by ClamAV on apache.org This is likely not an option due to lexical errors, a lot of formatters out there aren't perfect since they parse and re-emit code. If there was a formatter that was written that hooked into the flex compiler's AST, that is another animal. I would love to work on that. :) Mike Quoting Rogelio Castillo Aqueveque : > maybe a pre-commit hook into svn client that run the formatter just > before the commit happens would work. > > --- > Rogelio Castillo Aqueveque > rogelio@rogeliocastillo.com > > > > > On 4/01/2012, at 6:57 PM, Michael Schmalle wrote: > >> 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 : >> >>> 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=Preferences >>> >>> >>> - Doug >>> >>> -----Original Message----- >>> From: Michael Schmalle [mailto:mike@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 >>> >>> >> >> >> > >