fold icon indicating copy to clipboard operation
fold copied to clipboard

FOLD file format for origami models, crease patterns, etc.

Results 35 fold issues
Sort by recently updated
recently updated
newest added

I think GitHub Pages and NPM are enough places to put the compiled JavaScript; the .js code doesn't need to be in the main repo. However, GitHub Pages is currently...

This needs testing but may fix https://github.com/edemaine/cp-editor/issues/8 and (via re-export?) #37.

From the spec: `faces_vertices` and `faces_edges` should align in start so that `faces_edges[f][i]` is the edge connecting `faces_vertices[f][i]` and `faces_vertices[f][(i+1)%d]` where `d` is the degree of face `f`. The [diagonal-cp](https://github.com/edemaine/fold/blob/main/examples/diagonal-cp.fold)...

* Add join edge (`"J"`) option to `edges_assignment` (fix #26). * Add cut/slit edge (`"C"`) option to `edges_assignment` (fix #24). * Define `vertices_edges` and `faces_faces` (mostly fix #27 -- `edges_edges`...

spec

Type definitions for the FOLD library would allow for static type checking as well as intellisense in code editors. This could be accomplished either by providing a `.d.ts` type definition...

library

I created a FOLD viewer () using TypeScript and Three.js. I created it because I wanted an easy-to-use viewer and maintainable reference implementation of the FOLD specification that can easily...

Here is the plan for adding curved crease support to FOLD (probably version 2) via [NURBS](https://en.wikipedia.org/wiki/Non-uniform_rational_B-spline), based on discussions with Jason, Amanda, Klara: * A curved crease is a type...

spec
spec-v2

@estollnitz suggests removing redundancy from the various data structures in the spec. @origamimagiro's proposal is to split the spec into two parts: 1. **Storage spec** minimal nonredundant options, ideally classified...

spec
spec-v2

@origamimagiro suggests organizing the classes into a hierarchy, where any child implies all descendants. * `orientable` should be a child of `manifold`, so `orientable` automatically implies `manifold` * `2D` and...

spec

@robbykraft points out that the following natural pairings of `vertices`, `edges`, and `faces` are currently not in the spec: * `vertices_edges` * `edges_edges` * `faces_faces` We should explicitly mention that...

spec