# Working on ZiroEDA ZiroEDA is a port of KiCad 10.0.6 to the browser. The reference source is pinned at `/home/akshay/kicad-reference` (checked out at tag `10.0.6`) — read that, never KiCad master, because the parity target is the installed build. When Ubuntu updates the `kicad` package, move the reference tag with it: `kicad-cli version` and `git -C /home/akshay/kicad-reference describe --tags` must agree, or every kicad-cli oracle is checking against a different version than the source we port. **The manual is on disk too**, at the same version, and it is the second half of the answer whenever the source is ambiguous about *intent*: | | | |---|---| | `/home/akshay/kicad-docs` | the installed `kicad-doc-en` HTML (a symlink, so it tracks the package), images included | | `/home/akshay/kicad-docs-text` | the same, tags stripped, for `grep` | `eeschema.txt` and `pcbnew.txt` are ~500 kB and ~660 kB of prose. Reach for them when a reading of the C++ could go two ways — what a control is *for*, which of two behaviours is the documented one, what a warning actually means. Several things have been implemented backwards here from a defensible but wrong reading of the source; the manual usually settles those in one grep. The goal is that a user cannot tell whether they are in KiCad or in ours. ## The central-value rule **Wherever KiCad gets a value from a shared place, we must get it from ours. Never a local literal.** | KiCad asks | we ask | |---|---| | the GTK theme (`wxSYS_*`, `gtk-font-name`, the Yaru stylesheet) | the tokens in `common/widgets/shell.css` | | `common/` — `EDA_TEXT`, `SEG`, `StrNumCmp`, `COLOR4D`, `PLOTTER` statics | `common/**` | | a base class every subclass inherits | one shared module, never a per-editor copy | | its own data table — resistor bands, layer palette | mirror *that data*; do not invent | **This is not only fonts.** It covers colours, sizes, spacing, row pitch, control metrics, pen widths, strings, and the widgets themselves. ### Chrome versus data - **Chrome** is anything the theme decides: a face colour, a border, a font, a control height, padding. A literal here means we have drifted, because KiCad never wrote one — it asked GTK, and that single answer is why all of KiCad's launchers look like each other. - **Data** is a value KiCad itself hardcodes: the resistor colour-code bands, the galvanic series, the built-in colour themes. These stay local, but must mirror KiCad's own table rather than our invention. A surviving literal should carry a comment saying which of the two it is. ### Why this keeps happening 1. `.ze-app`, the root every launcher inherits from, hardcoded `13px` and a `"Segoe UI"` stack while `--ui-font-size` and `--ui-font-family` sat unused in the same file. 2. The drawing sheet wrote every metric as a literal — label font 11px against KiCad's 14.67, row pitch 26 against 37 — and its notebook tabs rendered in **Arial**, because a bare `