diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-13 15:48:59 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-13 15:48:59 -0500 |
| commit | c74c60dcb6df932c6002668f79c363a07cd60238 (patch) | |
| tree | 32c141bcbb9263382b4981fcfce239ecf6f95772 /todo.org | |
| parent | 1230868b8e271519530527e1d58be7cdd0f5647c (diff) | |
| download | dotemacs-c74c60dcb6df932c6002668f79c363a07cd60238.tar.gz dotemacs-c74c60dcb6df932c6002668f79c363a07cd60238.zip | |
Treat legacy color names as base columns
Diffstat (limited to 'todo.org')
| -rw-r--r-- | todo.org | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -174,6 +174,17 @@ Fixed 2026-06-13: org heading three now has an =org-todo= keyword before =org-he :END: Package faces model =inherit= explicitly, but UI faces currently expose only fg/bg/style fields in the table and generated theme output. Before implementing UI-face inheritance, write and review a small spec that defines: which UI faces get an inherit selector, how own defaults from =emacs-default-faces.json= appear versus effective inherited values, how export/import stores cleared vs inherited vs explicit values, how preview resolution follows UI inherit chains, and what browser gates prove the behavior. This touches the UI model, generated defaults, export format, preview rendering, and reset semantics, so it should not be slipped in as a refactor. +** TODO [#B] theme-studio import organization workflow needs a spec :feature: +:PROPERTIES: +:LAST_REVIEWED: 2026-06-13 +:END: +Design import handling for unstructured color sources such as Emacs themes, CSS palettes, screenshots, and generic palette files. Principles from the 2026-06-13 Theme Studio discussion: +- Preserve declared structure whenever an imported entry has a =columnId=. +- For unstructured legacy imports with no =columnId=, avoid silent hue clustering and avoid treating arbitrary =color-N= names as one long ramp; each =color-N= should become its own base column. +- Keep meaningful generated ramp-name inference for names like =blue-1= / =blue= / =blue+1=. +- Add explicit organization tools rather than hidden inference: group selected colors into a column, suggest hue groups as a preview/action, sort imported colors for inspection, and promote a color from an import bucket into a normal column. +- Consider a compact imported/captured bucket UI for large unstructured imports while preserving per-color column ids internally. + ** TODO [#B] Split window opens the dashboard in the other window :feature:quick:solo: :PROPERTIES: :LAST_REVIEWED: 2026-06-10 |