Both conventions, for Flex 3 and Flex 4, are very similar.
1) you recommended tabs in CSS where I think we use spaces throughout.
Well ... I prefer tabs everywhere, because, a tab requires less
characters to keep the indention in order.
2) you want properties before constructor in AS files w
On 1/8/12 12:26 AM, "Sebastian Mohr" wrote:
> I would only extend these Coding Conventions with a few rules for Flex
> 3:
I only skimmed the Flex 3 one, but I see a couple of issues:
1) you recommended tabs in CSS where I think we use spaces throughout.
2) you want properties before construc
I also would be happy to move forward
with the existing Flex Coding Conventions:
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
I would only extend these Coding Conventions with a few rules for Flex
3:
http://code.google.com/p/masuland/wiki/Flex3CodingConventions
... an
I agree on keeping on the current conventions. An added bonus is that all
of our editors (or at least the ones I use) have them setup as defaults, so
we don't have to worry about mucking with those preferences. :)
-Nick
On Sat, Jan 7, 2012 at 7:57 PM, Jonathan Campos wrote:
> On Sat, Jan 7, 2
On Sat, Jan 7, 2012 at 6:42 PM, Joel Hooks wrote:
> > http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
>
> Emphatically agree with this.
I like this too. I've been keeping to this for a few years. Work will need
to be done to finish it up. It should be committed via SVN, not
On Jan 7, 2012, at 18:16, Carlos Nazareno wrote:
> Why not adopt the already existing official flex coding conventions &
> best practices?
>
> http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
Emphatically agree with this.
Why not adopt the already existing official flex coding conventions &
best practices?
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
This article already exists and is pretty well written.
Trust me on this, code format consistency is very important for people
with OCD and it
