FabLearn 2020 Demo
A collaborator and I had a short paper on programmatic fabrication accepted at FabLearn 2020, and we’re presenting that work in a demo session on Zoom next weekend. Herein I walk through some of the example programs that we plan to work through with our visitors.
Let’s start with a practical example—one inspired by a real-life incident. Suppose you have a pair of pants whose button has popped off somewhere in the antics of your day. You look around home for a spare, but none can be found. You do, however, have fabrication tools, and you decide to make your own button.
Probably you open up Illustrator or Inkscape or GravitPro. These tools help create a design file quickly, but you are intellectually dissatisfied because the design is brittle. If you tweak a size or a position of one of the holes, you must repeat your work for the three other holes.
You would benefit from an editor that supports parametric design—like Twoville, the one we are presenting today. Twoville lets you create SVG design files using code. Our first draft of a Twoville program to make our button might look something like this:
This is code, yeah, but it’s just as brittle as a non-parametric design file. And it’s very verbose. We can improve upon it with a little abstraction. Let’s turn the circle drawing code into a reusable routine named
The verbosity is gone, but the design is still brittle because the parametric relationship of the holes is not established. Let’s establish some parameters and relate them with some arithmetic:
smallRadius to alter all four button holes at once. The buttons always stay centered. You are satisfied. You export the SVG, load it up in your laser cutter, extract the cut button, and find some needle and thread. But what if you can’t find those?
For our next example, let’s make a crescent moon. The best learning starts, in my opinion, with graph paper. If I were working with students on this exercise, I’d ask them to plot a few different moons and identify some properties of the ones they like liked best. These properties include:
- What are the coordinates of the two points?
- How many degrees are in the small circle?
- How many degrees are in the big circle?
With rough values worked out for these properties, we can use the
path command to trace out the perimeter of the crescent moon:
The previous examples demonstrate abstraction and parametricity. Coding also facilitates repetition through looping. Let’s use a loop to plot a star. In an educational setting, I would ask my students to draw a star on some polar graph paper and then to identify the angles and radii of each of the ten points.
Based on their answers, we would write a loop that iterates 5 times, plotting an external and an internal point on each iteration. Between iterations it jumps 72 degrees. The loop might look something like this:
We use this loop to produce the vertices of a polygon, turning the polar coordinates into Cartesian.
An ungon is a polygon that has been rounded off.
Code brings certain advantages, but the design process is not always so algorithmic. Ideally, our editors should support both parametric and aesthetic design. We are working on that in Twoville. Let’s demonstrate its hybridity as we model a raindrop.
Again, I would start by sketching on graph paper and getting a rough feel for the coordinates of the points. The drop is symmetric, and we can save ourselves some work by only thinking about one half and letting Twoville mirror the rest. Really we just have two salient points: the one at the top of the drop and one on the bulb.
There aren’t any straight lines connecting these points. Rather, we will need a Bezier curve, with two control points shaping the path between the points.
Putting all these ideas together, we end up with something like this: