josephhenryblack wrote: > André Pouliot wrote: > >> Also if there is multiple person who work on the code we better use some >> guideline on signal denomination and file name convention. Also the >> structure of directory used. It's some boring consideration to do right >> now but if we don't in a few month we are going to wish we did. > > This is where the wiki can help. Especially if we add it as we go. If > someone wants a small task - add the info that has already been said > about software. We can always fix the formatting in the wiki later, > but getting in on the page is the important part. I will have a look > late today so if you want to start to help out it would be great. The > beauty of documentation, is that by working together writing it up, > you are teaching yourself how to do it. The wiki has no restriction on > editing and is easy to get a log in.. we only ask that you validate > you new account using email - to limit spamming, and we will > eventually want put on your 'page' a note if you agree that Traversal > can use the any documentation. > I have made a rough start here: > http://wiki.duskglow.com/tiki-index.php?page=Contributing+Code > feel free to join in ;-) > jb
I did modify the page to write some form of naming convention, and also a standard header for the code file to explain it's use and also indicate if some external connection are required. It a first rough draft but it's better than nothing. If someone want to add of modify what I wrote feel free to do so. :) http://wiki.duskglow.com/tiki-index.php?page=Contributing+Code André _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
