![]() * Added intersect aggregator * Addressed stylistic PR feedback * Set the rotation of the intersected point to the second point’s rotation * Revert "Set the rotation of the intersected point to the second point’s rotation" This reverts commit d210a98f79a8866519fc9695487a9ea235167b8b. * Adjusted aggregate function to not need axis1 and axis2 parameters * Add assert to check for exactly 2 parts * Add unit tests for the aggregate intersect method * Change the assert string to use ${name.length} * Change test group name to align with style guide * Update intersect logic to consider negative Y axis --------- Co-authored-by: Marco Massarelli <60667061+ceoloide@users.noreply.github.com> |
||
---|---|---|
.github | ||
meta | ||
src | ||
test | ||
.gitignore | ||
.npmrc | ||
changelog.md | ||
LICENSE | ||
package-lock.json | ||
package.json | ||
README.md | ||
roadmap.md | ||
rollup.config.mjs | ||
showcase.png |
Ergogen
Ergonomic Keyboard Generator
The project aims to provide a common configuration format to describe ergonomic 2D layouts and generate automatic plates, cases, as well as un-routed PCBs for them. The project grew out of (and is an integral part of) the Absolem keyboard, and shares its Discord server as well.
Getting Started
Until there's a proper "Getting started" guide, try getting acquainted with Ergogen by following these steps in order:
-
Read the Documentation.
D'uuh. They're not complete by any measure, but should give you a fairly good idea what you're dealing with here.
-
Try one of the web-based deployments.
The unofficial deployment is probably better, tbh, and will soon be replacing the official one. Choose either one, then click things, look at outputs and see if things start to make sense.
There is no need for you to download the CLI unless you want to do one of the following:
- Preview in-development features
- Use custom modifications
- Contribute code
-
Search the
ergogen
topic on GitHub.There, you can look at (and reverse engineer) a variety of real life configs using Ergogen. Pop them into the web UI to see what they do, tinker with them and things should start to make more sense.
-
If a question persists after all of the above, feel free to ask it over on Discord and we'll do our best to help you out.
Contributions
Feature ideas, documentation improvements, examples, tests, or pull requests welcome! Get in touch on our Discord, and we can definitely find something you can help with, if you'd like to.
Sponsors
Huge thanks go to everyone who chooses to support my work! But even huger thanks are due to the following, distinguished sponsors: