Menu

#15 Refactor: Class naming conventions : SRM

v3.0.0-beta-2
open-accepted
3
2010-03-27
2009-06-10
No

"Class names should be nouns, in mixed case with the first letter of each
internal word capitalized. Try to keep your class names simple and
descriptive. Use whole words-avoid acronyms and abbreviations (unless the
abbreviation is much more widely used than the long form, such as URL or
HTML)."
2 Challenges:
1) On Windows svn cannot change from mg.Java to Mg.java for example, may
need to change an intermediate step eg mg to Mg2, commit, then Mg2 to Mg,
or find a more descriptive name, for example mg.java to Messages.java
2) the form and panel classes, *have* to have the corresponding *.form file
changed together. I think that NetBeans 6.5 can do the refactor correctly,
but still need to verify.

Discussion

  • A. MacKenzie

    A. MacKenzie - 2009-06-10
    • priority: 5 --> 3
     
  • A. MacKenzie

    A. MacKenzie - 2010-03-27
    • labels: --> Service Request Manager
    • milestone: --> v3.0.0-beta-2
    • assigned_to: nobody --> mack77
    • status: open --> open-accepted
     

Log in to post a comment.