Re: [flexcoders] Re: Flex Coding Guidelines
I'm looking for a plug-in like this too (Java has one). You can use any XML formatter to format your MXML files, but I haven't find anything to format AS 3 classes. Maybe in FB 3? -- Fabio On 2/12/07, Adam Royle [EMAIL PROTECTED] wrote: I don't understand why there isn't a feature in Eclipse that formats the code exactly how *YOU* want it. When you open up someone else's code it should just auto-format to how you prefer. You can make changes to the code, and when another coder opens it up, it formats it according to their preferences. It could even save it back into the generic format so it doesn't screw around with version control. Maybe this exists already?? I prefer hugging curly braces, FWIW. Adam - Original Message - *From:* Matt Chotin [EMAIL PROTECTED] *To:* flexcoders@yahoogroups.com *Sent:* Monday, February 12, 2007 2:49 PM *Subject:* RE: [flexcoders] Re: Flex Coding Guidelines I'm not sure there's a single engineering organization that doesn't get into fights about curly brace placement. To each their own J I personally like separate lines. -- *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On Behalf Of *lepusmars *Sent:* Sunday, February 11, 2007 6:37 PM *To:* flexcoders@yahoogroups.com *Subject:* [flexcoders] Re: Flex Coding Guidelines I've seen more Java developers do it they way proposed with the curly braces on the next line. It's always bothered me... I'm an old dog I guess (actually I'm only 30), and a bit Obsessive Compulsive. --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Michael Schmalle [EMAIL PROTECTED] wrote: I think it makes code less readable and Oh lets all agree to disagree on this one. Which side do you butter your bread? On the top or bottom, what??? On the sides!!! ? I can't stand curly braces on the method line, doesn't allow a space from the method signature to fully read and seems cramped to me. But that is my point, you will never get people to agree on spaces, braces and whatever else developers have a habit doing. ... Just because Java / C++ does it, doesn't mean its right. Things always evolve. just kidding, maybe. Peace, Mike
Re: [flexcoders] Re: Flex Coding Guidelines
Be sure of that! ;-) There's always a fight on this. We used to place curly braces in the method/block line but since we're often extending Adobe components (that use curly braces in its own line) we thought we should stick that way. There's no right or wrong on this. There's conventions, there's standards. []s Fabio Terracini On 2/12/07, Matt Chotin [EMAIL PROTECTED] wrote: I'm not sure there's a single engineering organization that doesn't get into fights about curly brace placement. To each their own J I personally like separate lines. -- *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On Behalf Of *lepusmars *Sent:* Sunday, February 11, 2007 6:37 PM *To:* flexcoders@yahoogroups.com *Subject:* [flexcoders] Re: Flex Coding Guidelines I've seen more Java developers do it they way proposed with the curly braces on the next line. It's always bothered me... I'm an old dog I guess (actually I'm only 30), and a bit Obsessive Compulsive. --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Michael Schmalle [EMAIL PROTECTED] wrote: I think it makes code less readable and Oh lets all agree to disagree on this one. Which side do you butter your bread? On the top or bottom, what??? On the sides!!! ? I can't stand curly braces on the method line, doesn't allow a space from the method signature to fully read and seems cramped to me. But that is my point, you will never get people to agree on spaces, braces and whatever else developers have a habit doing. ... Just because Java / C++ does it, doesn't mean its right. Things always evolve. just kidding, maybe. Peace, Mike
Re: [flexcoders] Re: Flex Coding Guidelines
On Monday 12 Feb 2007, Fabio Terracini wrote: formatter to format your MXML files, but I haven't find anything to format AS 3 classes. Maybe in FB 3? The ActionScript 2 plugin from SourceForge works well enough. -- Tom Chiverton Helping to synergistically unleash world-class paradigms This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. For more information about Halliwells LLP visit www.halliwells.com. -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/flexcoders/join (Yahoo! ID required) * To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] * To unsubscribe from this group, send an email to: [EMAIL PROTECTED] * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
Re: [flexcoders] Re: Flex Coding Guidelines
Hi, I was expecting to get ready and fight over this stuff, but hey, you are sticking with Adobe's conventions. I don't think there is really anything I disagree with. Although I do use in my component classes, dragButton_mouseDownHandler(event:MouseEvent):void When you start getting the same event handlers for differnet instances you need this way to separate them. IE systemManager_mouseMouseDownHandler(event:MouseEvent):void Thanks for getting this out. Peace, Mike On 2/10/07, jer_ela [EMAIL PROTECTED] wrote: Fabio, great work. --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Fabio Terracini [EMAIL PROTECTED] wrote: Folks, As my commitment to community I'm releasing, with DClick support, our Adobe Flex Coding Guidelines, a document about Flex (MXML and ActionScript) coding conventions that we use on a regular basis. The objective is clear: provide a common and consistent language to help code comprehension between developers. The practices established in this document are based on Java conventions, Flex 2 SDK and DClick team experience (including myself). By releasing this document, the idea is to help the community improve their Flex code by using coding conventions as well and hear feedback from community to continuously improve this document, that by now is a community asset. I'll be happy to have volunteers to form a committee or something to evolve this project further. This way, comments on this document (including the best practices) are very welcome! Involve yourself in this flexcoders thread, at the flexdev (listaflexdev.org - portuguese list on Flex) or at DClick weblog (http://blog.dclick.com.br/2007/02/10/adobe-flex-coding-guidelines/) English version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-english.pdf Portuguese version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-portugues.pdf Thanks, Fabio Terracini -- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
[flexcoders] Re: Flex Coding Guidelines
I agree, a very interesting read, but one thing I have to disagree with and bothers me a lot that Flex Builder does this when it creates classes. Close curly braces in its own line at the same position in which the open curly brace is... nothing bothers me more than a curly brace on it's own line, I think it makes code less readable and contributes to excessive scrolling when editing and reviewing code. Oh and curly braces on case statements is weird, but actually a good convention... that will take some relearning to work into my code. For the most part I like what you have, I'd like to use it as a starting point for my own organization. I think I've come from a different wing of the java development community, since there is a lot that bucks my own traditions. Paul --- In flexcoders@yahoogroups.com, Ralf Bokelberg [EMAIL PROTECTED] wrote: Hi Fabio I think it is a good document, beside the whitespace paragraphs. Distribution of whitespace is always worth a discussion :) There is only one thing, that makes me wonder. If methods should start with a verb, why don't you prefer handleMouseClick() over mouseClickHandler() ? Cheers, Ralf. On 2/10/07, Fabio Terracini [EMAIL PROTECTED] wrote: Folks, As my commitment to community I'm releasing, with DClick support, our Adobe Flex Coding Guidelines, a document about Flex (MXML and ActionScript) coding conventions that we use on a regular basis. The objective is clear: provide a common and consistent language to help code comprehension between developers. The practices established in this document are based on Java conventions, Flex 2 SDK and DClick team experience (including myself). By releasing this document, the idea is to help the community improve their Flex code by using coding conventions as well and hear feedback from community to continuously improve this document, that by now is a community asset. I'll be happy to have volunteers to form a committee or something to evolve this project further. This way, comments on this document (including the best practices) are very welcome! Involve yourself in this flexcoders thread, at the flexdev (listaflexdev.org - portuguese list on Flex) or at DClick weblog (http://blog.dclick.com.br/2007/02/10/adobe-flex-coding-guidelines/ ) English version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-english.pdf Portuguese version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-portugues.pdf Thanks, Fabio Terracini -- Ralf Bokelberg [EMAIL PROTECTED] Flex Flash Consultant based in Cologne/Germany Phone +49 (0) 221 530 15 35
Re: [flexcoders] Re: Flex Coding Guidelines
I think it makes code less readable and Oh lets all agree to disagree on this one. Which side do you butter your bread? On the top or bottom, what??? On the sides!!! ? I can't stand curly braces on the method line, doesn't allow a space from the method signature to fully read and seems cramped to me. But that is my point, you will never get people to agree on spaces, braces and whatever else developers have a habit doing. ... Just because Java / C++ does it, doesn't mean its right. Things always evolve. just kidding, maybe. Peace, Mike On 2/11/07, lepusmars [EMAIL PROTECTED] wrote: I agree, a very interesting read, but one thing I have to disagree with and bothers me a lot that Flex Builder does this when it creates classes. Close curly braces in its own line at the same position in which the open curly brace is... nothing bothers me more than a curly brace on it's own line, I think it makes code less readable and contributes to excessive scrolling when editing and reviewing code. Oh and curly braces on case statements is weird, but actually a good convention... that will take some relearning to work into my code. For the most part I like what you have, I'd like to use it as a starting point for my own organization. I think I've come from a different wing of the java development community, since there is a lot that bucks my own traditions. Paul --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Ralf Bokelberg [EMAIL PROTECTED] wrote: Hi Fabio I think it is a good document, beside the whitespace paragraphs. Distribution of whitespace is always worth a discussion :) There is only one thing, that makes me wonder. If methods should start with a verb, why don't you prefer handleMouseClick() over mouseClickHandler() ? Cheers, Ralf. On 2/10/07, Fabio Terracini [EMAIL PROTECTED] wrote: Folks, As my commitment to community I'm releasing, with DClick support, our Adobe Flex Coding Guidelines, a document about Flex (MXML and ActionScript) coding conventions that we use on a regular basis. The objective is clear: provide a common and consistent language to help code comprehension between developers. The practices established in this document are based on Java conventions, Flex 2 SDK and DClick team experience (including myself). By releasing this document, the idea is to help the community improve their Flex code by using coding conventions as well and hear feedback from community to continuously improve this document, that by now is a community asset. I'll be happy to have volunteers to form a committee or something to evolve this project further. This way, comments on this document (including the best practices) are very welcome! Involve yourself in this flexcoders thread, at the flexdev (listaflexdev.org - portuguese list on Flex) or at DClick weblog (http://blog.dclick.com.br/2007/02/10/adobe-flex-coding-guidelines/ ) English version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-english.pdf Portuguese version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-portugues.pdf Thanks, Fabio Terracini -- Ralf Bokelberg [EMAIL PROTECTED] Flex Flash Consultant based in Cologne/Germany Phone +49 (0) 221 530 15 35 -- Teoti Graphix http://www.teotigraphix.com Blog - Flex2Components http://www.flex2components.com You can find more by solving the problem then by 'asking the question'.
[flexcoders] Re: Flex Coding Guidelines
I've seen more Java developers do it they way proposed with the curly braces on the next line. It's always bothered me... I'm an old dog I guess (actually I'm only 30), and a bit Obsessive Compulsive. --- In flexcoders@yahoogroups.com, Michael Schmalle [EMAIL PROTECTED] wrote: I think it makes code less readable and Oh lets all agree to disagree on this one. Which side do you butter your bread? On the top or bottom, what??? On the sides!!! ? I can't stand curly braces on the method line, doesn't allow a space from the method signature to fully read and seems cramped to me. But that is my point, you will never get people to agree on spaces, braces and whatever else developers have a habit doing. ... Just because Java / C++ does it, doesn't mean its right. Things always evolve. just kidding, maybe. Peace, Mike
RE: [flexcoders] Re: Flex Coding Guidelines
I'm not sure there's a single engineering organization that doesn't get into fights about curly brace placement. To each their own :-) I personally like separate lines. From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of lepusmars Sent: Sunday, February 11, 2007 6:37 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Flex Coding Guidelines I've seen more Java developers do it they way proposed with the curly braces on the next line. It's always bothered me... I'm an old dog I guess (actually I'm only 30), and a bit Obsessive Compulsive. --- In flexcoders@yahoogroups.com mailto:flexcoders%40yahoogroups.com , Michael Schmalle [EMAIL PROTECTED] wrote: I think it makes code less readable and Oh lets all agree to disagree on this one. Which side do you butter your bread? On the top or bottom, what??? On the sides!!! ? I can't stand curly braces on the method line, doesn't allow a space from the method signature to fully read and seems cramped to me. But that is my point, you will never get people to agree on spaces, braces and whatever else developers have a habit doing. ... Just because Java / C++ does it, doesn't mean its right. Things always evolve. just kidding, maybe. Peace, Mike
Re: [flexcoders] Re: Flex Coding Guidelines
I don't understand why there isn't a feature in Eclipse that formats the code exactly how *YOU* want it. When you open up someone else's code it should just auto-format to how you prefer. You can make changes to the code, and when another coder opens it up, it formats it according to their preferences. It could even save it back into the generic format so it doesn't screw around with version control. Maybe this exists already?? I prefer hugging curly braces, FWIW. Adam - Original Message - From: Matt Chotin To: flexcoders@yahoogroups.com Sent: Monday, February 12, 2007 2:49 PM Subject: RE: [flexcoders] Re: Flex Coding Guidelines I'm not sure there's a single engineering organization that doesn't get into fights about curly brace placement. To each their own J I personally like separate lines. -- From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of lepusmars Sent: Sunday, February 11, 2007 6:37 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Flex Coding Guidelines I've seen more Java developers do it they way proposed with the curly braces on the next line. It's always bothered me... I'm an old dog I guess (actually I'm only 30), and a bit Obsessive Compulsive. --- In flexcoders@yahoogroups.com, Michael Schmalle [EMAIL PROTECTED] wrote: I think it makes code less readable and Oh lets all agree to disagree on this one. Which side do you butter your bread? On the top or bottom, what??? On the sides!!! ? I can't stand curly braces on the method line, doesn't allow a space from the method signature to fully read and seems cramped to me. But that is my point, you will never get people to agree on spaces, braces and whatever else developers have a habit doing. ... Just because Java / C++ does it, doesn't mean its right. Things always evolve. just kidding, maybe. Peace, Mike
[flexcoders] Re: Flex Coding Guidelines
Fabio, great work. --- In flexcoders@yahoogroups.com, Fabio Terracini [EMAIL PROTECTED] wrote: Folks, As my commitment to community I'm releasing, with DClick support, our Adobe Flex Coding Guidelines, a document about Flex (MXML and ActionScript) coding conventions that we use on a regular basis. The objective is clear: provide a common and consistent language to help code comprehension between developers. The practices established in this document are based on Java conventions, Flex 2 SDK and DClick team experience (including myself). By releasing this document, the idea is to help the community improve their Flex code by using coding conventions as well and hear feedback from community to continuously improve this document, that by now is a community asset. I'll be happy to have volunteers to form a committee or something to evolve this project further. This way, comments on this document (including the best practices) are very welcome! Involve yourself in this flexcoders thread, at the flexdev (listaflexdev.org - portuguese list on Flex) or at DClick weblog (http://blog.dclick.com.br/2007/02/10/adobe-flex-coding-guidelines/) English version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-english.pdf Portuguese version: http://blog.dclick.com.br/wp-content/uploads/adobe-flex-coding-guidelines-v12-portugues.pdf Thanks, Fabio Terracini
