You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Optional softer look for marks (neat-annotations style)? #3
We made a softer look for marks, based on neat-annotations: soft colors, handwritten labels, thin arrows and see-through outlines. Would you want AInotate to support it?
Current look
Neat look: same marks, but the UI underneath stays the main thing.
Current look
Neat look
Two ways to do it, your call:
A small hook, the look lives outside. AInotate gets an entry point (ainotate.looks) so a package can add a look. Your look stays the only one built in, and we publish and maintain the neat one as a separate package. The core change is 142 lines plus tests, with no font and no neat code. The default renders pixel-identical. Branch ready: testy-cool:look-hook
Built in. About 770 lines plus a font file (Shantell Sans, SIL OFL), and every new mark type would need a neat version too.
We'd suggest 1. Either way, your current look stays the default. Happy to drop it if it's not something you want in AInotate.
Thanks, the neat look is lovely, and option 1 is the right call: a small ainotate.looks entry point in the core, with the neat look published and maintained as its own package.
Please open the look-hook branch as a PR. What we will check:
the default look stays pixel-identical (the golden tests should pass untouched);
a look that fails to load falls back to the default with a warning instead of breaking a render;
spec.md and the MCP tool docs say how to pick a look, so agents can use it;
every file stays under 500 lines.
Once it is in, we are happy to link the neat look package from the README.
Done in #4: your look-hook commit (rebased, authorship kept) plus a fallback so a look that fails to load renders with the default look and a warning. CI is green on macOS and Ubuntu. This issue closes when #4 is merged. Ping us when the neat look package is published and we will link it from the README.
Activity
visul commentedon Oct 10, 2026
Thanks, the neat look is lovely, and option 1 is the right call: a small
ainotate.looksentry point in the core, with the neat look published and maintained as its own package.Please open the look-hook branch as a PR. What we will check:
Once it is in, we are happy to link the neat look package from the README.
docs(changelog): pluggable looks (#3)
visul commentedon Oct 10, 2026
Done in #4: your look-hook commit (rebased, authorship kept) plus a fallback so a look that fails to load renders with the default look and a warning. CI is green on macOS and Ubuntu. This issue closes when #4 is merged. Ping us when the neat look package is published and we will link it from the README.
docs(changelog): pluggable looks (#3)