+- Wings 3D Development Forum (https://www.wings3d.com/forum)
+-- Forum: Wings 3D (https://www.wings3d.com/forum/forumdisplay.php?fid=1)
+--- Forum: Programming (https://www.wings3d.com/forum/forumdisplay.php?fid=7)
+--- Thread: Coding Guidelines for Wings developers and tutorials (/showthread.php?tid=1105)
Coding Guidelines for Wings developers and tutorials - micheus - 03-21-2015
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
RE: Coding Guidelines for Wings developers and tutorials - micheus - 10-25-2015
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
Quote:- 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.