Coding Guidelines for Wings developers and tutorials

[micheus]

Coding Guidelines by bjorng
The guidelines can also be found in the source distribution (starting with the 1.1.12 release) in the file CodingGuidelines.

---

Tutorials

• Exploring Wings3D through the Erlang Shell (for beginners) by Scorpius
  
• How To Write Wings3D Plugins (for beginners) by Scorpius
  
• An example of how to write simple exporter plugin to wings by dgud
  
• Erlang for C, C++ and Java Programmers by chronosphere

[micheus]

About Wings3D coding and the Git repository
- https://github.com/dgud/wings/wiki (by bjorng)
- Coding Guidelines (by bjorng)

Some tips you need to know before make a pull request to the main repository at GitHub:
- Make one commit for every change/fix;
- A good commits should be as follow

- First line: What have you done max 60 characters!!!
- Second line: shall be empty:
- Then you should write why you did it.
- After that a note if a release note should be included, with possible thanks
i.g. NOTE: Added feature xxxxxxx, thanks <name>

*1. Don't start with: "It was ...". Write "Added ... feature" or "Fixed ..." instead;
*2. None lines should have more than 80 characters! Add a new line to continue writing.