OAC:HowToImproveTheCompatibilityAddon

# VII. How to improve the compatibility addon

Project OAC uses Git as source control (SC) system for the development.

You can:

• download the complete source with Git
• improve the existing code
• add new class mappings

and upload your changes again for everyone to use and improve.

Repository access

Send kju your ssh key. Check the ssh guide how to create one for you.

Repository URL:

git@git.dev-heaven.net:oac.git

Coding standards

• Get a proper text editor like notepad++ or editpadpro.
• Do not mess up the code:
  • Preceding tabs - NO spaces! - before the code.
  • Correct number of preceding tabs.
  • NO tabs or spaces at the end of the line.
  • Spaces around an equal sign are standard.
  • One space after a colon, not before it.
  • Do not forget a semicolon to end definitions.
  • Use quotes for strings.
  • Correct placement of brackets.
• Use comments where they are meaningful.
• Use empty lines to separate code.
• Order lists alphabetically - use editor functions!
• Create a file header for addons according to the standard.
• Name addons according to the standard.

Back to OAC Home

The seven roads to OAC - subpage link overview