Changes between Version 9 and Version 10 of CodingConventions


Ignore:
Timestamp:
May 1, 2009, 12:48:20 PM (13 years ago)
Author:
Gavin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodingConventions

    v9 v10  
    55'''Files'''
    66
    7  * Although Grails can handle both dos (\r\n) and *nix (\r) line ends *nix is preffered.
    8  * It is project policy not to include developer names in the source files, recognition will be given in better and more visible ways.
     7 * Although Grails can handle both dos (\r\n) and *nix (\r) line ends *nix is preferred.
     8 * It is project policy not to include developer's names in the source files, recognition will be given in better and more visible ways.
    99
    1010'''Format'''
     
    2020  * Create a copy of the '''whole''' views folder called ''!TaskDetailed/show.gsp etc''
    2121  * Create a copy of the controller called ''!TaskDetailedController.groovy'' and edit the class inside to match.
    22   * Then detail to your harts content.
     22  * Then detail to your hearts content.
    2323
    24 This way the original views are available as direct access to the data for administration. If the domain changes enough a "grails generate-all" can be performed on most domains without losing the customisations. Proposed suffix 'Detailed as in detailing a car, customised or air-brushed, unless a better suffix is suggested.
     24This way the original views are available as direct access to the data for administration. If the domain changes enough a "grails generate-all" can be performed on most domains without losing the customisations.
     25
     26Proposed suffix 'Detailed as in detailing a car, customised or air-brushed, unless a better suffix is suggested.
     27
     28A notable exception to this is '''Person''' and '''Authority''' use 'svn revert' if you accidentally regenerate these.
    2529
    2630'''Documentation'''