Index: trunk/doc-rnd/TODO =================================================================== --- trunk/doc-rnd/TODO (revision 2157) +++ trunk/doc-rnd/TODO (revision 2158) @@ -10,8 +10,9 @@ - replace settings with lihata (conf_*) - project files: - - load project conf (replacing the original) after loading a .pcb - - save project conf properly + - save only if changed + - save project conf properly (needs lihata smart save long term, test with plain save now) + - implement binary->lht setter and use it in config_any_replace() if the source role sais so - revise gsch2pcb-rnd warnings - gtk hid: clean up the #warnings Index: trunk/doc-rnd/c89.html =================================================================== --- trunk/doc-rnd/c89.html (nonexistent) +++ trunk/doc-rnd/c89.html (revision 2158) @@ -0,0 +1,14 @@ + + +

pcb-rnd - C89

+ +The code is written in C, namely C89 for most parts with a few exceptions +written in C99. It's not yet decided whether the code will be C89 or C99 +long term. If it'll be C89, the C99 parts will be rewritten. If it'll be +C99, new code can use C99 features freely. Until the decision, keep +new code C89. Especlially watch out for these: +

commengt: always use /* */, never // +
don't mix variable declaration with code - open a new {} block, which will also scope your new variables, or better yet, split up the function into smaller, static functions, the compiler will inline them anyway +
try to avoid vararg macros, use vararg functions instead +

Index: trunk/doc-rnd/contrib.html =================================================================== --- trunk/doc-rnd/contrib.html (nonexistent) +++ trunk/doc-rnd/contrib.html (revision 2158) @@ -0,0 +1,48 @@ + + +

pcb-rnd - contribution

+ +If you are interested to help out, please contact me using + the live chat (CET daytime) or mail to: +pcb-rnd (at) igor2.repo.hu. + +

Contributing as a user

+Using pcb-rnd in production and just reporting bugs is already a huge contribution. +

+More dedicated users can join in scheduled, systematic testing. Such testing +is split up into independent chunks that each can be done in an hour. +

+Even more dedicated users can join developing the documentation. +

+None of the above requires or assumes any programming skill. + +

Contributing as a programmer

+ +The project is lead in an autocratic way by Igor2. + +Developer freedom taken away: +

the basic concept of pcb-rnd is set and won't change +
the toolchain is chosen, and won't change; the usual hot topics: svn, scconfig, C. +
don't add code that restricts usability for others; add code that increases usability for some; thus prefer to add code in plugins! +

+Developer freedom promptly granted: +

svn commit access from day 0 +
work together in trunk/, not alone in a branch +
pcb-rnd has a strong plugin support; want to implement a strange/contrversial feature? In a plugin, almost anything goes +
especially in plugins, work on whatever you want, even if noone else needs that feature +

+Coding style/indentation: there's an unified style +in core and core plugins. If you work on those parts, try to stick to it. If you +are working on a new plugin, it's still the preferred style but you can use +a different style. However, the rule is that if someone else starts hacking +that part too, he is allowed to convert the code to the unified format; but +unified format can not be converted to anything else. So it's a one way +process which long term grants unified style while not demotivates a plugin +developer by forcing a syle on him in the early, "when the bulk of the code +is written" phase. + + Index: trunk/doc-rnd/index.html =================================================================== --- trunk/doc-rnd/index.html (revision 2157) +++ trunk/doc-rnd/index.html (revision 2158) @@ -16,6 +16,7 @@

debian packages

comments, feedback, patches: live chat with the developer or mail to: pcb-rnd (at) igor2.repo.hu

Scripting PCB? Check the rosetta stone of pcb-rnd example scripts and the scripting documentation +

the project is open for contribution