Ink2Task v1.0.7
The on-page SYNC button now shows what it's doing.
New: sync progress
Until now the device just looked frozen while it ran a sync — no spinner, no message, nothing. Tapping the on-page SYNC button now brings up a small status bubble at the bottom of the screen that tracks the work as it goes: Reading the page… → Reading your handwriting… → Fetching and redrawing… → Saving…
It's deliberately non-interactive — you can keep writing straight through it, and it disappears on its own when the sync finishes.
This needed a small piece of custom Android code. The plugin SDK can't do it: its only way to show anything is to open the plugin full-screen, which is far more disruptive than the wait it would be covering. The bubble is drawn as a system overlay instead, so it can float over your note while the plugin itself stays closed.
Fixed
- A memory leak on every sync. Page elements are backed by native memory that has to be handed back explicitly, and the plugin never did — each sync allocated dozens of elements and read every element on the page several times over, none of it released. On a device where the plugin process stays alive for a long time, that accumulates. This doesn't make a single sync faster; it stops the plugin getting heavier the longer you use it.
For developers
The repo now carries a supernote-plugin-dev skill under .claude/skills/, so future Claude Code sessions start with the SDK's API surface and constraints already to hand. It's vendored from AgP42/supernote-dashboard (MIT) with a corrections block for the places its advice is wrong for this codebase.
The README also gains a Credits section — most importantly to SuperTask by @apclark31, the plugin that inspired Ink2Task and the reference for how a Supernote plugin is built and packaged.
Install
- Download
Ink2Task.snplgbelow. - Copy it to your Supernote's
MyStyle/folder (USB, or Settings → Browse and Access). - On the device: Settings > Apps > Plugins → remove the old Ink2Task → Install.
Your settings, list bindings, and checklist pages survive the reinstall.
New here? See the README for setup and backend options.