tfaour/espresso_frame
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases 13 Wiki Activity

Let a tasks widget have a custom on-panel name
Build and push server image / test (push) Successful in 25s
Details
Build and push server image / build-and-push (push) Successful in 1m59s
Details
Build and push server image / deploy (push) Successful in 53s
Details

Browse Source 
Adds TaskWidgetConfig.name (migration 19, plain column add) shown at
the top of the widget on the actual panel instead of the hardcoded
"Tasks" header -- e.g. "Chores" or "Mom's list". The only widget type
with its own on-panel title at all, since it's the only one where
"which list is this" isn't already obvious from a calendar/photo/
whiteboard's own content.

Threaded through calendar_render's _draw_tasks/_build_tasks/
render_tasks/render_tasks_preview_png as a `title` param (default
"Tasks", truncated to fit -- a long custom name shouldn't be able to
overflow the widget's box), the config-save endpoint (tasks_name,
truncated server-side to a sane header length rather than rejected),
and a new "Settings" section in the tasks dialog.

Verified live in the browser: the name actually renders at the top of
the real composited panel (not just the dialog preview, which stays
gated on having a configured source), and persists correctly on both
desktop and mobile. Full suite (196 tests) passes.
This commit is contained in:
Thomas Faour
2026-07-25 04:05:36 +00:00
parent 14c47aa2a0
commit 4a2b1f3795
10 changed files with 120 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
server/app/static/widget_dialog_tasks.js
+6 -5
View File
@@ -1,10 +1,10 @@
// Tasks widget dialog: per-user included-task-list checkboxes + color
// pins (same shape as the calendar widget's "Included calendars"), the
// recently-completed toggle, and the rendered preview. Not a page-load
// script -- frame_layout.js fetches this widget's dialog HTML fragment,
// injects it into the shared <dialog>, points window.FRAME_API at this
// specific widget (/api/frames/{id}/widgets/{widget_id}), then calls
// initTasksDialog().
// name/recently-completed settings form, and the rendered preview. Not
// a page-load script -- frame_layout.js fetches this widget's dialog
// HTML fragment, injects it into the shared <dialog>, points
// window.FRAME_API at this specific widget
// (/api/frames/{id}/widgets/{widget_id}), then calls initTasksDialog().
function loadTasksPreview() {
document.getElementById('tasks-preview').src = `${window.FRAME_API}/preview/tasks?_=${Date.now()}`;
@@ -69,6 +69,7 @@ function initTasksDialog() {
document.getElementById('tasks-config-form').addEventListener('submit', async (e) => {
e.preventDefault();
const body = new URLSearchParams({
tasks_name: document.getElementById('tasks_name').value,
tasks_show_completed: String(document.getElementById('tasks_show_completed').checked),
});
try {