A name, creator or description stored in the patch #10

New issue

Closed

opened 2026-08-18 01:34:39 +00:00 by bcox · 0 comments

bcox commented

2026-08-18 01:34:39 +00:00

Owner

Status: excluded by design during the preset-transport spec. Filed for the
record.

A preset's display name comes from its filename. Nothing stores a name,
creator or description inside the patch. From the spec:

A name, creator, or description stored in the patch. The filename is the
name. The rest is metadata nobody has asked to author and no UI would show.

The argument against a stored name specifically is stronger than "nobody
asked": a second copy inside the file creates a way for the two to disagree
after a rename. The discovery provider derives the browser's name from the
path, and playground::PresetName is now the single derivation shared by the
provider, the editor's listing and its Save As field.

Note this is not the same question as macro names, which are stored in
the patch (the MNAM chunk, format minor 5). Those have no other source of
truth — nothing but the patch knows what macro 3 does — whereas a preset's
name is already on disk as the filename. That distinction is the whole test
for whether something belongs in the file.

Reopen if a browser ever wants to show authorship or a description, which
would need a UI to author them first.

**Status: excluded by design during the preset-transport spec. Filed for the record.** A preset's display name comes from its filename. Nothing stores a name, creator or description inside the patch. From the spec: > **A name, creator, or description stored in the patch.** The filename is the > name. The rest is metadata nobody has asked to author and no UI would show. The argument against a stored *name* specifically is stronger than "nobody asked": a second copy inside the file creates a way for the two to disagree after a rename. The discovery provider derives the browser's name from the path, and `playground::PresetName` is now the single derivation shared by the provider, the editor's listing and its Save As field. Note this is **not** the same question as macro names, which *are* stored in the patch (the `MNAM` chunk, format minor 5). Those have no other source of truth — nothing but the patch knows what macro 3 does — whereas a preset's name is already on disk as the filename. That distinction is the whole test for whether something belongs in the file. Reopen if a browser ever wants to show authorship or a description, which would need a UI to author them first.