Adom Library

@@ -10,7 +10,7 @@ checksum = "320119579fcad9c21884f5c4861d16174d0e06250625266f50fe6898340abefa"  [[package]] name = "adom-lbr"-version = "2.22.2"+version = "2.22.3" dependencies = [  "altium-codec",  "anyhow",

@@ -1,6 +1,6 @@ [package] name = "adom-lbr"-version = "2.22.2"+version = "2.22.3" edition = "2021" description = "adom-lbr generator / EDA translator: the canonical adom-lbr JSON is the hub, with native converters to Altium (.SchLib/.PcbLib/.IntLib), EAGLE/Fusion (.lbr), and KiCad. Altium output is written natively — no Altium needed at conversion time." 

@@ -175,16 +175,27 @@ ADD dialog searches the deviceset's text. adom-lbr fills all three: - Catalogue boilerplate ("Datasheet-verified pinout", "KiCad symbol/footprint/3D") is   stripped from a page brief before it becomes a description. It is page prose. -For a VARIANT SET, give each `generate` its own `--description` saying which look it is.-Ten devicesets carrying one identical sentence tell a reader nothing about which to pick:+**LEAD WITH WHAT DIFFERS.** Fusion's Content Manager shows about **20 characters** of the+Description column before it truncates with an ellipsis; the full text appears only on+hover. Measured in Fusion on a ten-deviceset CH340G library: every row described as+"USB serial converter, UART, SOIC-16. Square 4-side symbol, ..." rendered as+`USB serial conv...` on all ten rows, so the column was identical for every variant and the+one word a reader needed was past the cut. The part description is the SAME for every+variant, which is exactly why it cannot go first.++So for a VARIANT SET, put the look first and the part after it:  ``` adom-lbr generate --sym CH340G-SQ.kicad_sym --fp CH340G.kicad_mod --part-metadata page.json \   --name CH340G-SQ \-  --description "CH340G: USB to serial converter, UART. Square 4-side symbol, pins grouped by function" \+  --description "Square, grouped, chip outline. CH340G USB to serial converter, UART" \   -o CH340G-SQ.lbr ``` +The same rule is why the PACKAGE line leads with geometry rather than with a manufacturer:+`Walsin Technology Co...` identifies nothing at 20 characters, while+`2 pads, 2.5 x 1.0 mm...` identifies the package and leaves the prose for the hover.+ Duplicate PAD names (KiCad same-net arrays: thermal vias, ground paddles, shield tabs) are resolved to the EAGLE `@`-suffix convention (`17`, `17@2`, `17@3`, ...) with one space-separated multi-pad `<connect>` binding the whole

@@ -1 +1 @@-2.22.2+2.22.3

⋯ 1 unchanged line ⋯

@@ -1,6 +1,6 @@ {   "slug": "adom-lbr",-  "version": "2.22.2",+  "version": "2.22.3",   "type": "app",   "description": "adom-lbr \u2014 the EDA library translator. Bring a component in from any supported EDA tool and convert it to any other (KiCad \u21c4 Altium \u21c4 EAGLE/Fusion) through one canonical adom-lbr JSON \u2014 symbol + footprint + 3D + pin\u2194pad map. Altium is written natively (no Altium needed). Includes the adom-lbr Manager: browse wiki components and view symbol/footprint/3D + the per-EDA layer stackup.",   "dependencies": {},

@@ -1,6 +1,6 @@ {   "slug": "adom-lbr",-  "version": "2.22.2",+  "version": "2.22.3",   "type": "app",   "description": "adom-lbr — the EDA library translator. Bring a component in from any supported EDA tool and convert it to any other (KiCad ⇄ Altium ⇄ EAGLE/Fusion) through one canonical adom-lbr JSON — symbol + footprint + 3D + pin↔pad map. Altium is written natively (no Altium needed). Includes the adom-lbr Manager: browse wiki components and view symbol/footprint/3D + the per-EDA layer stackup.",   "dependencies": {},@@ -88,4 +88,4 @@       "label": "Browse parts"     }   ]-}\ No newline at end of file+}