Usage

You can import these files in your scripts with use <MCAD/filename.scad>,
where 'filename' is one of the files listed below like 'motors' or
'servos'. Some files include useful constants which will be available
with include <MCAD/filename.scad>, which should be safe to use on all
included files (ie. no top level code should create geometry). (There is
a bug/feature that prevents including constants from files that
"include" other files - see the openscad mailing list archives for more
details. Since the maintainers aren't very responsive, may have to work
around this somehow)

If you host your project in git, you can do git submodule add URL PATH in your
repo to import this library as a git submodule for easy usage. Then you need to do
a git submodule update --init after cloning. When you want to update the submodule,
do cd PATH; git checkout master; git pull. See git help submodule for more info.

Development

You are welcome to fork this project in github and request pulls. I will try to
accomodate the community as much as possible in this. If for some reason you
want collaborator access, just ask.

Github is fun (and easy), but I can include code submissions and other
improvements directly, and have already included code from various sources
(thingiverse is great :)

Code style

I'd prefer to have all included code nicely indented, at least at the block
level, and no extraneous whitespace. I'm used to indent with four spaces as
opposed to tabs or other mixes of whitespace, but at least try to choose a style
and stick to it.

Testing

I've started a minimal testing infrastucture for OpenSCAD code. It's written in
python and uses py.test (might be compatible with Nose also). Just type py.test
inside the lib dir in a terminal and you should see a part of the tests passing
and tracebacks for failing tests. It's very simplistic still, but it should test
that no syntax errors occur at least.

The code is included in openscad_testing.py, and can be imported to be
used in other codebases.