developer_en.html
This document describes how developers should understand, extend, and maintain the MyAnythingList system.
Future developers should not need historical chat logs to understand how the system works.
Playlist text ↓ URL discovery ↓ Command parsing ↓ Tile model creation ↓ Thumbnail / QR resolution ↓ Grid rendering
The parser extracts valid URLs from any UTF-8 text.
Rules:# are comments.#_Command().
My research notes:
https://example.com/article
#_ReplaceThumbnailWithImage("cover.jpg")
If a behavior can be driven by controls or code, it belongs in the scripting documentation. Developers must keep the commands-and-functions and scripting-interface documents synchronized with implementation reality, including command names, arguments, result expectations, defaults, sequencing rules, and failure conditions.
Arguments that materially change output must be explicit and stable. Avoid ambiguous values whose real effect is undocumented. Use command keys and enumerated behaviors that can be reproduced reliably across sessions and implementations.
Commands extend playlist behavior.
Examples:
#_ReplaceThumbnailWithImage("image.jpg")
#_LoadImage("panel.png")
#_LoadImageHideLinks("poster.png")
Commands apply to the most recent URL unless otherwise defined.
All controls and labels must be modeled as localizable UI strings rather than hardcoded English-only literals. Layout logic must tolerate longer strings, non-Latin scripts, and right-to-left direction without breaking composition or hiding controls.
Runtime state is controlled by configuration variables.
Examples:Do not implement export as a separate, manual tile reconstruction routine when the result can drift from the live tile. Developers should centralize composition so that live render and export are two targets of one rendering model.
Text-only URL-art thumbnails, QR overlays, type pills, and footer text must remain crisp at 4K and 8K. Never solve export issues by flattening the screen view and upscaling it.
Command thumbnail → Uploaded thumbnail → Platform thumbnail → Fallback imageRules:
Contributor patches to the docs must preserve prior content and integrate additions in the most logical section. Developers must not “clean up” the package by removing examples, edge cases, duplicated clarifications, or implementation warnings that still carry meaning.
The project aims to remain understandable to future developers and AI systems for decades.
Future sessions should not reread the full corpus every turn. Keep a high-level routing map of which document owns each type of rule and update only the affected docs. For the build, ViewScaleMode and SafeAreaProfile are first-class runtime settings that belong in window.MyAnythingListConfig and should also be GET-addressable. Exported thumbnails must capture the final composited tile canvas and use informative filenames such as MyAnythingThumbnail_2026-03-12_041552PM_3840x2160.png.
Updated: 2026-03-12 v09
Always build from the latest version. A new iteration may not start from an older build when a newer build already contains fixes or clarified runtime behavior. This rule prevents regressions such as the return of previously corrected QR startup behavior.
Canonical docs folders are meant to copy directly into 8k.art/_docs/en without stowaway files. Progress logs belong at the root of the iteration package beside the app build and handoff file, not inside the canonical docs folder.
All documentation pages must share the standard navigation header/footer and the same high-visibility freshness timestamp treatment at the top and bottom so anyone opening any page immediately knows how current it is.
MyAnythingList is a public educational system intended to help ethical, curious, and globally diverse people learn how information can be structured, inspected, rendered, and shared. The project should favor transparency, inspectability, multilingual access, and source-aware communication over black-box presentation.
Updated: 2026-03-12 v14