content inside:
This document aims to establish coding guidelines to application written with Adobe Flex 2 and ActionScript 3. Establish a coding convention matters in the context that the most part of the time in software development life cycle is maintenance. This way, helping the comprehension of code passages is a must, considering that not always who’s going to perform the maintenance is the same person who built it in the first time. With a common language, developers can rapidly understand other person’s code. Besides, the application or components code can be distributed or sold to third party. The practices established in this document are based on DClick work way, Java coding conventions and conventions seen at Adobe Flex 2 SDK. Here you’ll learn about: Files, files suffix, files names, encoding, action script 3.0, file organization, style, line and line wrap, declarations, curly braces and parentheses, statement, spaces, comments, document comments, implementation comment, MXML, file organization, attribute, general rules, langage, package, classes, interfaces, methods, variables, constants, name spaces, general practice. Use the keyword FIXME inside comments (MXML and ActionScript) to flag something that’s broken and should be fixed. Use TODO to flag something that works but can be improved by a refactoring. For this, use the Flex Builder 2 Task Plugin.
Tags : software development life cycle, curly braces, file organization, flex 2, files names, java coding, language developers, action script, refactoring, actionscript, parentheses, constants, development life cycle, suffix, declarations
If you see unrelated pdf files with the description or copyrighted material published, please report to us, we'll correct/delete it it as soon as possible.NONE OF THOSE MATERIALS ARE HOSTED IN THIS SERVER NOR UPLOADED BY ME IN SOMEONE'S SERVERS. Read our DISCLAIMER for more detail.
We are neither affiliated with authors and brands nor responsible for its content and change of content.
Information contained herein is provided "as is" without warranty of any kind, either expressed or implied, including any warranty of merchantability or fitness for a particular purpose. In no event shall ANYONE be held liable for any loss of profit, special, incidental, consequential, or other similar claims.