Difference between revisions of "The opentaps Way of Coding"

From Opentaps Wiki
Jump to navigationJump to search
m (Protected "The opentaps Way of Coding": Sysop page [edit=sysop:move=sysop])
(→‎Why the opentaps Way of Coding)
Line 3: Line 3:
 
==Why the opentaps Way of Coding==
 
==Why the opentaps Way of Coding==
  
−
Writing code is easy.
+
If you're reading this, you're probably either planning to customize [http://www.opentaps.org opentaps Open Source ERP + CRM] or build extensions with additional features for it.
  
−
Maintaining that code through its entire lifecycle is much, much more complicated.
+
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 [http://www.eclipse.org/ Eclipse] and maintain your code through future versions of opentaps as they are released.
  
−
We are always thinking of how to create code that is easy to maintain and extend.  Over time, we have developed a distinctly "opentaps Way of Coding" to help maintain your customizations through multiple versions of opentaps.  Our goal is to give you a way to separate your code, whether it's customizations to the base system or enhancements on top of it, cleanly and to keep your code compatible with future versions as they are released.
+
The opentaps Way follows these principles:
 +
* Write clean object-oriented code
 +
* Maintain your code with compile time checking
 +
* Separate your code cleanly versus existing opentaps code base
  
−
The opentaps Way follows these principles:
+
==How It Works==
−
* Segregate your code
 
−
* Use the compiler to maintain your code
 
−
*
 

Revision as of 22:48, 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
  • Maintain your code with compile time checking
  • Separate your code cleanly versus existing opentaps code base

How It Works

Retrieved from "https://docs.opentaps.org/docs/index.php?title=The_opentaps_Way_of_Coding&oldid=6994"