pinchord-18 Build Process
Pinchord · pinchord.git · Tickets · Changelog
A Pinchord Ticket (Triaged):
Ticket · History
- August 29, 2026 Created (title: build-process)
Changes
@@ -0,0 +1,8 @@+---+title: build-process+permalink: pinchord/build-process+---++*A [[pinchord-tickets|Pinchord Ticket]] (Open)*++- No documented build process :( - September 1, 2026 Edited
Changes
@@ -3,6 +3,14 @@ permalink: pinchord/build-process --- -*A [[pinchord-tickets|Pinchord Ticket]] (Open)*+*A [[pinchord-tickets|Pinchord Ticket]] (Open):* -- No documented build process :(+## Symptom++Pinchord has a long and arduous build process that is not documented anywhere. This causes a lot of friction in shipping out updates, and often leads to things being forgotten.++This build process is basically the same process any [[Pinchord Derivations|Pinchord derivations]] would have to do in order to be compatible with both Plover and Javelin. As [[pinchord-chords-format]] talks about, this has led to derivation authors picking one platform, rather than supporting both.++## Potential Solutions++- Have a unified build process that takes a set of input files, such as the existing `chords.edn`, and generates the Plover plugin and Javelin files - and later, firmware images. See [[pinchord-att-chords-format-implementation]] for more about what this might look like. - September 1, 2026 Edited (title: build-process → build process)
Changes
@@ -1,6 +1,6 @@ ----title: build-process-permalink: pinchord/build-process+title: build process+permalink: pinchord/build-process/ --- *A [[pinchord-tickets|Pinchord Ticket]] (Open):* - September 4, 2026 Edited
Changes
@@ -5,12 +5,20 @@ *A [[pinchord-tickets|Pinchord Ticket]] (Open):* -## Symptom+## Symptoms++### Pinchord Pinchord has a long and arduous build process that is not documented anywhere. This causes a lot of friction in shipping out updates, and often leads to things being forgotten. This build process is basically the same process any [[Pinchord Derivations|Pinchord derivations]] would have to do in order to be compatible with both Plover and Javelin. As [[pinchord-chords-format]] talks about, this has led to derivation authors picking one platform, rather than supporting both. +### Derivations++As talked about in [[pinchord-chords-format]], pinchord derivations are currently fragmented across Plover and Javelin. Pinchord sits on these 2 steno engines, but people almost exclusively use one or the other. It is unreasonable to expect a derivation author to go through the build process that I do for the engine that they don't use. ++This fragmentation of derivations harms adoption and leaves derivation authors with a poor choice of either wasting their own time, or making their system inaccessible to half of its potential users.+ ## Potential Solutions - Have a unified build process that takes a set of input files, such as the existing `chords.edn`, and generates the Plover plugin and Javelin files - and later, firmware images. See [[pinchord-att-chords-format-implementation]] for more about what this might look like. - September 4, 2026 Edited
Changes
@@ -9,9 +9,7 @@ ### Pinchord -Pinchord has a long and arduous build process that is not documented anywhere. This causes a lot of friction in shipping out updates, and often leads to things being forgotten.--This build process is basically the same process any [[Pinchord Derivations|Pinchord derivations]] would have to do in order to be compatible with both Plover and Javelin. As [[pinchord-chords-format]] talks about, this has led to derivation authors picking one platform, rather than supporting both.+Pinchord has a long and arduous build process that is not documented anywhere. This causes a lot of friction in shipping out updates, and often leads to things being forgotten and being patched on later. ### Derivations - September 4, 2026 Edited
Changes
@@ -19,4 +19,15 @@ ## Potential Solutions -- Have a unified build process that takes a set of input files, such as the existing `chords.edn`, and generates the Plover plugin and Javelin files - and later, firmware images. See [[pinchord-att-chords-format-implementation]] for more about what this might look like.+Have a unified build process that takes a set of input files, such as the existing `chords.edn`, and generates the Plover plugin and Javelin files - and later, firmware images. See [[pinchord-att-chords-format-implementation]] for more about what this might look like.++## Implementation++I think the best way to implement this would be to rewrite the existing `generate-dictionary.clj`, test for parity, and then start generating more files from `chords.edn`.++`generate-dictionary.clj` currently bundles a lot of assumptions about Pinchord, so it will need to be updated.++- Have `src/` `config/`?, and `javelin/` for javelin outputs++Sub-things:+- Move `generate-dictionary.clj` into a Clojure program - September 5, 2026 Edited
Changes
@@ -5,6 +5,8 @@ *A [[pinchord-tickets|Pinchord Ticket]] (Open):* +[[pinchord-git|Git]] branch: `build-process`+ ## Symptoms ### Pinchord@@ -30,4 +32,6 @@ - Have `src/` `config/`?, and `javelin/` for javelin outputs Sub-things:-- Move `generate-dictionary.clj` into a Clojure program+- [ ] Move `generate-dictionary.clj` into a Clojure program+- Generate Javelin files via the program+- Generate the Plover plugin via the program - September 5, 2026 Edited
Changes
@@ -32,6 +32,8 @@ - Have `src/` `config/`?, and `javelin/` for javelin outputs Sub-things:-- [ ] Move `generate-dictionary.clj` into a Clojure program-- Generate Javelin files via the program-- Generate the Plover plugin via the program+- [ ] Move `generate-dictionary.clj` into a Clojure program, keeping the coupling of Pinchord-specific things+- [ ] Move Pinchord-specific code in the program to `chords.edn`+- [ ] Add specs for `chords.edn`+- [ ] Generate Javelin files via the program+- [ ] Generate the Plover plugin via the program - September 5, 2026 Edited
Changes
@@ -7,6 +7,8 @@ [[pinchord-git|Git]] branch: `build-process` +Att: [[pinchord-att-build-process]]+ ## Symptoms ### Pinchord@@ -32,8 +34,12 @@ - Have `src/` `config/`?, and `javelin/` for javelin outputs Sub-things:-- [ ] Move `generate-dictionary.clj` into a Clojure program, keeping the coupling of Pinchord-specific things+- [x] Move `generate-dictionary.clj` into a Clojure program, keeping the coupling of Pinchord-specific things - [ ] Move Pinchord-specific code in the program to `chords.edn`+ - [ ] Maybe move to Clojure JVM for keys!+ - [x] Rename `fill-gaps-in-banks` to `with-gaps-filled`+ - [ ] I believe with `:avoidMask` being set, sorting the entries by length is no longer needed - [ ] Add specs for `chords.edn` - [ ] Generate Javelin files via the program - [ ] Generate the Plover plugin via the program+ - [ ] Make keys use their individual thing - September 11, 2026 Edited
Changes
@@ -35,6 +35,7 @@ Sub-things: - [x] Move `generate-dictionary.clj` into a Clojure program, keeping the coupling of Pinchord-specific things+- [ ] Rename `chords.edn` to `system.edn` as the formats are not compatible . - [ ] Move Pinchord-specific code in the program to `chords.edn` - [ ] Maybe move to Clojure JVM for keys! - [x] Rename `fill-gaps-in-banks` to `with-gaps-filled` - September 15, 2026 Edited (title: build process → Build Process)
Changes
@@ -1,5 +1,5 @@ ----title: build process+title: Build Process permalink: pinchord/build-process/ --- - September 21, 2026 Edited
Changes
@@ -21,6 +21,13 @@ This fragmentation of derivations harms adoption and leaves derivation authors with a poor choice of either wasting their own time, or making their system inaccessible to half of its potential users. +## Problem++- I do not know+- Building pinchord takes too long?+- Pinchord derivations are fragmented?+- I think problem is that Pinchord derivations are fragmented, and this build process is part of the reason _why_.+ ## Potential Solutions Have a unified build process that takes a set of input files, such as the existing `chords.edn`, and generates the Plover plugin and Javelin files - and later, firmware images. See [[pinchord-att-chords-format-implementation]] for more about what this might look like. - October 20, 2026 Change formatting
Changes
@@ -5,9 +5,9 @@ *A [[pinchord-tickets|Pinchord Ticket]] (Open):* -[[pinchord-git|Git]] branch: `build-process`+[[pinchord.git|Git]] branch: `build-process` -Att: [[pinchord-att-build-process]]+Att: [[pinchord-att-build-process|attachment: build process]] ## Symptoms @@ -17,7 +17,7 @@ ### Derivations -As talked about in [[pinchord-chords-format]], pinchord derivations are currently fragmented across Plover and Javelin. Pinchord sits on these 2 steno engines, but people almost exclusively use one or the other. It is unreasonable to expect a derivation author to go through the build process that I do for the engine that they don't use. +As talked about in [[pinchord-chords-format|chords format]], pinchord derivations are currently fragmented across Plover and Javelin. Pinchord sits on these 2 steno engines, but people almost exclusively use one or the other. It is unreasonable to expect a derivation author to go through the build process that I do for the engine that they don't use. This fragmentation of derivations harms adoption and leaves derivation authors with a poor choice of either wasting their own time, or making their system inaccessible to half of its potential users. @@ -30,7 +30,7 @@ ## Potential Solutions -Have a unified build process that takes a set of input files, such as the existing `chords.edn`, and generates the Plover plugin and Javelin files - and later, firmware images. See [[pinchord-att-chords-format-implementation]] for more about what this might look like.+Have a unified build process that takes a set of input files, such as the existing `chords.edn`, and generates the Plover plugin and Javelin files - and later, firmware images. See [[pinchord-att-chords-format-implementation|attachment: chords format implementation]] for more about what this might look like. ## Implementation - October 21, 2026 Update the rest of the ticket pages to use numbers (renamed from pinchord-build-process.md, status: none → open, category: none → triaged, type: none → addition)
Changes
@@ -1,10 +1,12 @@ --- title: Build Process-permalink: pinchord/build-process/+status: open+category: triaged+type: addition+redirect_from:+ - pinchord/build-process/ --- -*A [[pinchord-tickets|Pinchord Ticket]] (Open):*- [[pinchord.git|Git]] branch: `build-process` Att: [[pinchord-att-build-process|attachment: build process]]@@ -17,7 +19,7 @@ ### Derivations -As talked about in [[pinchord-chords-format|chords format]], pinchord derivations are currently fragmented across Plover and Javelin. Pinchord sits on these 2 steno engines, but people almost exclusively use one or the other. It is unreasonable to expect a derivation author to go through the build process that I do for the engine that they don't use. +As talked about in [[pinchord@14|chords format]], pinchord derivations are currently fragmented across Plover and Javelin. Pinchord sits on these 2 steno engines, but people almost exclusively use one or the other. It is unreasonable to expect a derivation author to go through the build process that I do for the engine that they don't use. This fragmentation of derivations harms adoption and leaves derivation authors with a poor choice of either wasting their own time, or making their system inaccessible to half of its potential users. - October 23, 2026 Remove trailing slashes
Changes
@@ -4,7 +4,7 @@ category: triaged type: addition redirect_from:- - pinchord/build-process/+ - pinchord/build-process --- [[pinchord.git|Git]] branch: `build-process` - October 24, 2026 Rename tickets to <project>-<number> <title> (renamed from pinchord@18.md, title: Build Process → none)
Changes
@@ -1,5 +1,4 @@ ----title: Build Process status: open category: triaged type: addition@@ -19,7 +18,7 @@ ### Derivations -As talked about in [[pinchord@14|chords format]], pinchord derivations are currently fragmented across Plover and Javelin. Pinchord sits on these 2 steno engines, but people almost exclusively use one or the other. It is unreasonable to expect a derivation author to go through the build process that I do for the engine that they don't use. +As talked about in [[pinchord-14 Chords Format]], pinchord derivations are currently fragmented across Plover and Javelin. Pinchord sits on these 2 steno engines, but people almost exclusively use one or the other. It is unreasonable to expect a derivation author to go through the build process that I do for the engine that they don't use. This fragmentation of derivations harms adoption and leaves derivation authors with a poor choice of either wasting their own time, or making their system inaccessible to half of its potential users. - October 24, 2026 Replace ticket status, category and resolution with ticket (status: open → none, category: triaged → none)
Changes
@@ -1,6 +1,5 @@ ----status: open-category: triaged+ticket: triaged type: addition redirect_from: - pinchord/build-process - October 24, 2026 Edited
Changes
@@ -9,6 +9,8 @@ Att: [[pinchord-att-build-process|attachment: build process]] +While this page is a lot about Javelin, which has been dropped, it is not strictly, so it should be kept and reworded.+ ## Symptoms ### Pinchord