You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every instruction needs to be unambiguous. The direction of a fold has to be known at all times. Either we make it so the syntax makes ambiguous instructions impossible, or any ambiguous instruction (if it can be easily determined) throws a compile error. In that case there needs to be a syntax to resolve these ambiguities.
Special folds
For a lot of intermediate and advanced origami you have to put a layer in between two other layers. Origami doesn't currently have a notion of layers and layer order, so it is impossible to specify these.
Things go 3D
Potentially the biggest difficulty. Origami figures aren't just creases on a 2D plane. At some point, after having made all necessary creases, they are put together into 3D objects. Sometimes that involves curling some edges or the like. What is a good way to specify that? Is it even easily specifiable?
Implementation
Lexing
ANTLR?
Parsing
?
Usage
Generating origami images
Initial state: Array of vertices for each corner of the original piece of paper
Fold: Folding generates new vertices along all faces that are to be folded. The crease is a line between these vertices. The to-be-folded vertices are then rotated around this line.
To make transitions smooth, additional temporary vertices should be created along the side of the to-be-folded part of the shape in order to allow the shape to become curly.
--> When pockets are created and corners put into those pockets a fold doesn't just move one rigid part of paper, instead the paper might need to be curled and tucked into the pocket. Could be resolved with the above mentioned temporary vertices.
--> Pinching: For demonstration purposes we might want to pinch something along a line, which should force additional paper outside, e.g. to open a pocket.
The text was updated successfully, but these errors were encountered:
Language specification
Avoiding ambiguity
Every instruction needs to be unambiguous. The direction of a fold has to be known at all times. Either we make it so the syntax makes ambiguous instructions impossible, or any ambiguous instruction (if it can be easily determined) throws a compile error. In that case there needs to be a syntax to resolve these ambiguities.
Special folds
For a lot of intermediate and advanced origami you have to put a layer in between two other layers. Origami doesn't currently have a notion of layers and layer order, so it is impossible to specify these.
Things go 3D
Potentially the biggest difficulty. Origami figures aren't just creases on a 2D plane. At some point, after having made all necessary creases, they are put together into 3D objects. Sometimes that involves curling some edges or the like. What is a good way to specify that? Is it even easily specifiable?
Implementation
Lexing
ANTLR?
Parsing
?
Usage
Generating origami images
Initial state: Array of vertices for each corner of the original piece of paper
Fold: Folding generates new vertices along all faces that are to be folded. The crease is a line between these vertices. The to-be-folded vertices are then rotated around this line.
To make transitions smooth, additional temporary vertices should be created along the side of the to-be-folded part of the shape in order to allow the shape to become curly.
--> When pockets are created and corners put into those pockets a fold doesn't just move one rigid part of paper, instead the paper might need to be curled and tucked into the pocket. Could be resolved with the above mentioned temporary vertices.
--> Pinching: For demonstration purposes we might want to pinch something along a line, which should force additional paper outside, e.g. to open a pocket.
The text was updated successfully, but these errors were encountered: