Developer Guide

developer_en.html

This document describes how developers should understand, extend, and maintain the MyAnythingList system.

1. Development Philosophy

• Preserve simplicity.
• Preserve human-readable text.
• Prefer transparent behavior over hidden logic.
• Document decisions clearly.

2. Core System Components

Playlist text
   ↓
URL discovery
   ↓
Command parsing
   ↓
Tile model creation
   ↓
Thumbnail / QR resolution
   ↓
Grid rendering

3. Playlist Parser

The parser extracts valid URLs from any UTF-8 text.

Rules:

• URLs may appear anywhere in text.
• Lines beginning with # are comments.
• Commands use the syntax #_Command().

Example:

My research notes:

https://example.com/article

#_ReplaceThumbnailWithImage("cover.jpg")

4. Command System

Commands extend playlist behavior.

Examples:

#_ReplaceThumbnailWithImage("image.jpg")
#_LoadImage("panel.png")
#_LoadImageHideLinks("poster.png")

Commands apply to the most recent URL unless otherwise defined.

The command system currently treats two image-related commands as first-class supported behavior:

#_ReplaceThumbnailWithImage("https://example.com/image.jpg")
#_LoadLinkedImage("https://example.com/image.jpg")

• ReplaceThumbnailWithImage applies to the most recent URL above it and preserves the original destination URL and QR target.
• LoadLinkedImage creates a standalone image tile whose image, destination, and QR all point to the image URL itself.
• The public default playlist may use embedded SVG data URLs with ReplaceThumbnailWithImage so custom thumbnails can ship without additional hosted assets.

5. UI State Architecture

Runtime state is controlled by configuration variables.

Examples:

• ShowControls
• ShowGear
• AutoHideGear
• ShowQR
• ShowTypes
• ShowURLs

These values may be set through:

• startup configuration
• URL parameters
• UI interaction

6. Thumbnail System

Thumbnail sources are prioritized:

Command thumbnail
→ Uploaded thumbnail
→ Platform thumbnail
→ Fallback image

Rules:

• QR images must never replace thumbnails.
• Uploaded images must affect only the intended tile.

7. Contribution Guidelines

• Preserve existing behavior unless explicitly redesigned.
• Update documentation when behavior changes.
• Favor readability over cleverness.

8. Long-Term Goal