Find a file
2011-01-18 06:14:08 -05:00
bitmap Added a scad code to generate letters with a hole in them to make a necklace out of 2010-12-21 21:40:28 +02:00
__init__.py Add __init__.py to be able to import the python code also 2010-10-06 15:54:42 +03:00
bearing.scad API change! This actually makes the bearing code usable sice it works around a bug in openscad that prevented using the code easily 2010-10-07 17:33:07 +03:00
boxes.scad Added code from the openscad svn repo for easy use and improvement. 2010-08-26 17:25:29 +08:00
constants.scad Clarified the licenses in use in this library, has GPL2 and GPL3 which are incompatible 2010-07-25 19:39:52 +03:00
curves.scad Clarified the licenses in use in this library, has GPL2 and GPL3 which are incompatible 2010-07-25 19:39:52 +03:00
gears.scad Corrections spotted by tests 2010-08-26 17:25:28 +08:00
gridbeam.scad added functions and fixes to gridbeam.scad 2011-01-05 17:42:10 -05:00
hardware.scad first commit of whosawhatsis' hardware.scad 2011-01-18 06:14:08 -05:00
involute_gears.scad fixed tests 2010-10-06 15:51:19 +03:00
lgpl-2.1.txt Changed to LGPL, since all the code is now compatible 2010-07-26 13:24:12 +03:00
materials.scad Added testing infra using py.test. Catches parse errors already, but stl compiling tests fail 2010-07-26 21:03:44 +03:00
math.scad Clarified the licenses in use in this library, has GPL2 and GPL3 which are incompatible 2010-07-25 19:39:52 +03:00
metric_fastners.scad commit Giles' regular shapes and metric fasteners 2011-01-18 06:10:38 -05:00
motors.scad Typo fix submitted by Koen Kooi 2010-08-04 23:19:57 +03:00
nuts_and_bolts.scad fixed tests 2010-10-06 15:51:19 +03:00
openscad_testing.py Moved testing code to another file for easier using outside MCAD 2010-10-13 09:25:21 +03:00
openscad_utils.py Raised the default timeout for calling openscad to make tests not fail 2010-10-07 17:19:45 +03:00
README.markdown Maybe this is enough... 2011-01-12 14:35:18 +02:00
regular_shapes.scad commit Giles' regular shapes and metric fasteners 2011-01-18 06:10:38 -05:00
screw.scad Testing improvements and cleanup 2010-08-26 22:24:32 +08:00
servos.scad Testing improvements and cleanup 2010-08-26 22:24:32 +08:00
shapes.scad Added a general ngon and improved some api docs 2011-01-08 15:38:47 +02:00
stepper.scad Some adjustments to the new files 2010-07-26 09:10:01 +03:00
teardrop.scad Added info about developing MCAD and other improvements to README 2010-08-22 15:06:24 +03:00
test_docs.py Improved docs based on failures of test_docs.py 2010-10-30 12:57:26 +03:00
test_mcad.py Moved testing code to another file for easier using outside MCAD 2010-10-13 09:25:21 +03:00
TODO Added a to be integrated itme to TODO 2010-11-15 15:38:58 +02:00
triangles.scad Merged changes from a fork 2010-08-28 08:47:00 +03:00
units.scad Added a switch to generate bearing outlines for hole cutting etc. 2010-07-26 12:57:28 +03:00
utilities.scad Improved testing and fixed a warning thus found 2010-09-30 09:22:54 +03:00

OpenSCAD MCAD Library

This library contains components commonly used in designing and moching up mechanical designs. It is currently unfinished and you can expect some API changes, however many things are already working.

This library is licensed under the LGPL 2.1 See http://creativecommons.org/licenses/LGPL/2.1/ or the included file, lgpl-2.1.txt.

Usage

You can import these files in your scripts with use <MCAD/*.scad>, but some files include useful constants which will be available with include <MCAD/*.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.

Currently Provided Tools:

  • involute_gears.scad (http://www.thingiverse.com/thing:3575):

    • gear()
    • bevel_gear()
    • bevel_gear_pair()
  • gears.scad (Old version):

    • gear(number_of_teeth, circular_pitch OR diametrial_pitch, pressure_angle OPTIONAL, clearance OPTIONAL)
  • motors.scad:

    • stepper_motor_mount(nema_standard, slide_distance OPTIONAL, mochup OPTIONAL)

Other tools (alpha and beta quality):

  • nuts_and_bolts.scad: for creating metric and imperial bolt/nut holes
  • bearing.scad: standard/custom bearings
  • screw.scad: screws and augers
  • materials.scad: color definitions for different materials
  • stepper.scad: NEMA standard stepper outlines
  • servos.scad: servo outlines
  • boxes.scad: box with rounded corners
  • triangles.scad: simple triangles

Very generally useful functions and constants:

  • math.scad: general math functions
  • constants.scad: mathematical constants
  • curves.scad: mathematical functions defining curves
  • units.scad: easy metric units
  • utilities.scad: geometric funtions and misc. useful stuff
  • teardrop.scad (http://www.thingiverse.com/thing:3457): parametric teardrop module
  • shapes.scad: simple shapes by Catarina Mota

External utils that generate and and process openscad code:

  • openscad_testing.py: testing code, see below
  • openscad_utils.py: code for scraping function names etc.

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.