Difference between revisions of "The opentaps Way of Coding"
From Opentaps Wiki
Jump to navigationJump to search (→Why the opentaps Way of Coding) |
(→Why the opentaps Way of Coding) |
||
| Line 9: | Line 9: | ||
The opentaps Way follows these principles: | The opentaps Way follows these principles: | ||
* Write clean object-oriented code | * Write clean object-oriented code | ||
| + | * Support your code with automated tests | ||
* Maintain your code with compile time checking | * Maintain your code with compile time checking | ||
| − | * Separate your code cleanly versus existing opentaps code base | + | * Separate your code cleanly versus existing opentaps code base |
==How It Works== | ==How It Works== | ||
Revision as of 22:49, 21 February 2011
Why the opentaps Way of Coding
If you're reading this, you're probably either planning to customize opentaps Open Source ERP + CRM or build extensions with additional features for it.
Having done both many times, we've gradually developed a distinctly "opentaps Way of Coding" to help you do these things. Our goal is to make it easier for you to write your code with IDE's such as Eclipse and maintain your code through future versions of opentaps as they are released.
The opentaps Way follows these principles:
- Write clean object-oriented code
- Support your code with automated tests
- Maintain your code with compile time checking
- Separate your code cleanly versus existing opentaps code base
