3 | | * JavaScript is stored in /js/ |
4 | | * to reduce browser overhead we ''only'' use the jQuery JavaScript framework (so ''no'' mootools, yui, prototype, etc). jQuery is widely used by Google, Amazon, Microsoft, IBM, Twitter, etc... More information can be found [http://grails.org/jQuery+Plugin here]. |
5 | | * for fancy user interface widgets such as accordion or tabs, we use jQuery ui (http://jqueryui.com/). Currently the CSS and JS of jQuery UI 1.7.2 (theme Pepper Grinder) are put into the /js/ and /css/jquery-ui/ folders. To use for example the accordion widget for a div with id 'idAcc' in you GSP, specify in head: |
| 3 | * JavaScript is stored in /js/ |
| 4 | * to reduce browser overhead we ''only'' use the jQuery JavaScript framework (so ''no'' mootools, yui, prototype, etc). jQuery is widely used by Google, Amazon, Microsoft, IBM, Twitter, etc... More information can be found [http://grails.org/jQuery+Plugin here]. |
| 5 | * for fancy user interface widgets such as accordion or tabs, we use jQuery ui (http://jqueryui.com/). Currently the CSS and JS of jQuery UI 1.7.2 (theme Pepper Grinder) are put into the /js/ and /css/jquery-ui/ folders. To use for example the accordion widget for a div with id 'idAcc' in you GSP, specify in head: |
34 | | * Commit logical changesets |
35 | | * When you commit a change to the repository, make sure your change reflects a single purpose: the fixing of a specific bug, the addition of a new feature, or some particular task. Your commit will create a new revision number which can forever be used as a "name" for the change. |
36 | | * if you break the repository you have to get cake! |
| 34 | * Commit logical changesets |
| 35 | * When you commit a change to the repository, make sure your change reflects a single purpose: the fixing of a specific bug, the addition of a new feature, or some particular task. Your commit will create a new revision number which can forever be used as a "name" for the change. |
| 36 | * if you break the repository you have to get cake! |
39 | | * In Java, naming conventions for identifiers have been established and suggested by various Java communities such as Sun Microsystem<ref>"Code Conventions for the Java Programming Language", [http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html Section 9: "Naming Conventions"]</ref>, Netscape<ref>"NETSCAPE'S SOFTWARE CODING STANDARDS GUIDE FOR JAVA",[http://collaboratory.emsl.pnl.gov/docs/collab/sam/CodeStandards.html Collab Software Coding Standards Guide for Java]</ref>, AmbySoft<ref>"AmbySoft Inc. Coding Standards for Java v17.01d", [http://www.ambysoft.com/essays/javaCodingStandards.html]</ref> and etc. A sample of naming conventions set by Sun Microsystem are listed below: |
| 39 | * In Java, naming conventions for identifiers have been established and suggested by various Java communities such as Sun Microsystem<ref>"Code Conventions for the Java Programming Language", [http://java.sun.com/docs/codeconv/html/CodeConventions.doc8.html Section 9: "Naming Conventions"]</ref>, Netscape<ref>"NETSCAPE'S SOFTWARE CODING STANDARDS GUIDE FOR JAVA",[http://collaboratory.emsl.pnl.gov/docs/collab/sam/CodeStandards.html Collab Software Coding Standards Guide for Java]</ref>, AmbySoft<ref>"AmbySoft Inc. Coding Standards for Java v17.01d", [http://www.ambysoft.com/essays/javaCodingStandards.html]</ref> and etc. A sample of naming conventions set by Sun Microsystem are listed below: |