Repository navigation
AtomView 0.2.0
Personal colors and display settings (Stage 1 of the roadmap). No parser change; coordinates, atom IDs and cell handling are untouched. Blocks without a display key load exactly as before.
- New settings tab section "Colors": element palette (AtomView softened Jmol or Jmol), type palette (AtomView, Okabe-Ito, Tol bright, IBM), scalar palette (AtomView, Viridis, Magma, Cividis, Turbo, red-white-blue, greys) with optional reversal, below-/above-range colors, selected-atom color, per-element and per-type color overrides, and a live preview on the viewport and on a light background.
- New settings tab section "Display": sphere scale (0.2–3), viewport background, cell wireframe color and width, and a reset to built-in defaults.
- Settings are stored under
displayin the vault's plugindata.json; changing them redraws every open view immediately. Invalid stored values are dropped on load instead of failing the plugin. - Block schema 2: an optional
displaymapping with the same keys overrides the personal settings for that block only; schema 1 blocks load unchanged and copied blocks are written as schema 2. - Legend shows the active palette, marks a block override, and for fixed ranges lists how many atoms fall below and above the range together with the clip colors.
- Type colors index the type palette by type number and never imply an element; element colors apply only to atoms with a known element or an explicit
elementMapentry. - Release attachments remain main.js, manifest.json and styles.css only; license notices remain embedded in main.js.
Filesystem notices remain expected: registered external files are read-only and explicit. Clipboard access only writes the requested view block. Windows/macOS behavior is not verified by the maintainer.
AtomView 0.1.6
Housekeeping release; no parser, renderer, schema or settings change. The 0.1.5 tag was never published: its CI release run stopped at the npm audit --omit=dev gate on a newly published advisory for the transitive dependency body-parser (GHSA-27r3-jxmh-p828, reached through Mol* → express). body-parser is not part of the plugin bundle.
- Adjust UI wording (input placeholders, one aria-label, one status message) so the official Obsidian lint reports zero errors and zero warnings; scientific acronyms are kept as-is.
- Refresh README, VALIDATION, TEST_REPORT, KNOWN_ISSUES and ROADMAP: community-directory listing, verified in-app installation on Linux desktop Obsidian 1.14.5, and the reordered roadmap (personal color/display settings next).
- Update
package-lock.jsonso the production dependency audit is clean (body-parser 2.3.0 → 2.4.0;package.jsonunchanged; not bundled into main.js). - Release attachments remain main.js, manifest.json and styles.css only; license notices remain embedded in main.js.
Filesystem notices remain expected: registered external files are read-only and explicit. Clipboard access only writes the requested view block. Windows/macOS behavior is not verified by the maintainer.