Files
ekklesiaandClaude Opus 5.5 fd4330a649 docs: temporary workspace restore, the admin link bubble, and Sunday's checks
wonder-ink.md: where WonderInk keeps its sign-in (Basic auth in a cookie)
and why only tabs are restored; what comes back and what never does; what
counts as use; when it is not restored; the test-only override. And the
link bubble teachers saw: WonderInk's CKEditor 5 for Admin accounts,
where a plain click on a link is an editing click by design; Viewers get
one-click links, measured on the real Saul lesson, and Wonder Ink does
not override the editor.

The manual says closing still signs you out and recent tabs come back
for two hours. testing.md has the Little Waders checklist.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-26 21:12:17 -05:00

5.3 KiB
Raw Permalink Blame History

Backlog — 0.3.0 and later

Recorded after hands-on testing of 0.2.6.1 in September 2026. None of this is in 0.2.6.2 to 0.2.6.4: 0.2.6.2 is limited to picture printing, the Presentations memory failure and the settings lockdown, 0.2.6.3 to the black-and-white preview and Print image, and 0.2.6.4 to temporary workspace restore (the two items that were here about links and sign-in retention are answered in wonder-ink.md). Each item says what was observed, so whoever picks it up starts from the evidence.

Wonder Ink

  • An interface like Chrome's, visibly the classroom's. Familiar tabs and back/forward/reload, without an address bar, new-tab button or anything that takes a teacher somewhere the lesson did not. The 0.2.6.1 tab strip is a step towards it, not the design.
  • The PDF viewer's own Download button. It saves a copy, which the download handler then opens as another worksheet tab. Remove it, or intercept the download from a worksheet tab so it does nothing visible. (0.2.2 already skips re-opening a save from a worksheet tab — see from_worksheet in on_download — so check first which route it now takes.)
  • One Print, not two. A worksheet tab has the viewer's printer icon and Wonder Ink's Print; both now open the same preview, but a teacher sees two buttons. One teacher-facing workflow.
  • Readable worksheet names. Tabs show the downloaded file's name, which for many worksheets is a long generated prefix. Strip it, or take the name from the PDF's own title.
  • Print image and CSS background pictures (from 0.2.6.3). The engine's hit test does not call a CSS background a picture, so right-click there offers only Print page. Only worth doing if Sunday's testing finds Wonder Ink's site draws artwork that way; the lab has no account to tell. See wonder-ink.md, Print image.
  • The clipboard after Print image (from 0.2.6.3). It is put back, but owned by Wonder Ink afterwards, so text copied elsewhere before is gone once Wonder Ink closes — there is no clipboard manager in the session. Measured, and judged smaller than leaving the picture there.
  • A speaker on the tab that is playing sound (QWebEnginePage.recentlyAudible).
  • A picture in its own tab, in a room above 100% (seen testing 0.2.6.4). Page zoom is the room's UI_SCALE, and the engine's picture viewer takes it too, so at 200% a slide opened from a lesson is shown twice its size with scrollbars rather than fitted to the window, as Chrome shows it. Printing is unaffected.
  • Staying signed in, if WonderInk ever issues a real session token. Today its sign-in is the teacher's email and password in a Basic-auth cookie (measured, 0.2.6.4), so keeping it would mean keeping a password; Wonder Ink does not. Worth asking WonderInk for a server-issued token that can be revoked; until then, closing Wonder Ink signs the teacher out, and only the recent tabs come back.
  • Workspace time as a room setting, if two hours turns out wrong for some room: IDLE_LIMIT_SECONDS in classroom_wonderink_workspace.py is the one place, and a device.conf key would be a small change.
  • The site's sluggishness, where it is ours. Measured in 0.2.6.1: Wonder Ink and Chrome take the same time (about 2.9 s cold) and the site is the weight — 119 – 160 requests, 3.2 MB, the Google Maps API loaded twice. Ours to look at: whether a classroom's QtWebEngine has its GPU (classroom-wonderink --diagnose on the machines), and the page shell being revalidated on every warm load (62 – 87 ms).
  • The browser is scaled twice under Plasma (dpr 2.25 at 150%): classroom-browser forces UI_SCALE on a Chrome that already follows the compositor. Deliberately left in 0.2.6.x because teachers know that size, and Wonder Ink was matched to it. Decide once, for both.

Presentations

  • A normal, maximisable application instead of the small floating library window.
  • Consistently sized tiles in a responsive grid.
  • No unnecessary internal scrollbars or stretched layouts. 0.2.6.2 had to give a row extra height by hand when a card carries the memory-failure message; the layout should size to its cards.
  • Keep the window's size and position when importing a presentation or changing a cover.
  • Click the slide to advance.
  • Hide the pointer after a moment of stillness while presenting, and bring it back on movement.
  • Keep the keyboard controls, and never advance when a playback control itself is clicked.
  • Remote control of a presentation — later than 0.3.0.

The launcher and Parent Call

  • Remove the subtitles under DVD and Presentations on the launcher.
  • Parent Call appears among the ordinary applications for a moment and then disappears, which looks like a crash. Keep it reachable through its background or notification route without it flashing up as a window.

The settings lockdown

  • A notification's Configure button still shows, and opens a small "module disabled" window (0.2.6.2). Hiding it needs a change to Plasma's notification applet, not configuration — revisit if Plasma gains a Kiosk key for it.
  • The settings-module list is per Plasma release. tools/lab/converged-check fails when a new one appears; the list in config/plasma/xdg/kdeglobals then needs the new name.