android 编程规范（Android编程规范）.docVIP

android 编程规范（Android编程规范） Why coding specifications are needed? Coding specifications are especially important for programmers for several reasons: 80% of the cost of a software life cycle is maintenance Almost none of the software is maintained by the original developer throughout its lifecycle Coding standards can improve the readability of software and allow programmers to understand new code as quickly and thoroughly as possible If you release the source code as a product, you need to make sure that it is packaged well and clearly, just like any other product you have built name Packet naming Naming rule: the prefix of a unique package name is always all lowercase ASCII letters and is a top-level domain name, usually com, edu, gov, mil, net, org. The subsequent section of the package name is not the same according to the internal naming conventions of the different organizations. Such naming conventions may distinguish between departments (Department), projects (project), machines (machine), or login (names) names in the form of a specific directory name. For example: com.moleader.nloc.activities Specification: packet naming must begin with com.moleader, followed by a project name (or abbreviation), followed by a module name or a hierarchical name. For example: com.moleader. project abbreviation. Module name com.moleader.nloc.bookmark Such as: abbreviation for com.moleader. project. Name of hierarchy com.moleader.nloc.activities Class and interface naming Naming rule: the class name is a noun, and the uppercase of each word is capitalized by case mixing. Try to make your class name concise and descriptive. Use full words to avoid abbreviations (unless the abbreviation is more widely used, such as URL, HTML) Interfaces generally use able, ible, ER and other suffixes For example: class Raster; class ImageSprite; Specification: the class name must use the hump rule, that is, the initial letter must be capitalized. If it is a phrase, the initial letter of each word