From ad2aecf9e87158bad0e527e04368e92303f5a276 Mon Sep 17 00:00:00 2001 From: Thomas Walker Lynch Date: Sun, 2 Aug 2026 18:06:29 +0000 Subject: [PATCH] grid based semantic types working, manual updated --- .../Manuscript.copy/Document/manual.html | 178 ++++++++++++------ .../authored/Manuscript.copy/Element/TOC.js | 9 +- .../authored/Manuscript.copy/Element/grid.js | 51 +++-- .../Layout/article_tech_ref.js | 3 +- tester/authored/Grid/test_dictionary.html | 1 - tester/authored/Grid/test_grid.html | 1 - tester/authored/Grid/test_matrix.html | 9 +- tester/authored/Grid/test_relation.html | 6 +- 8 files changed, 161 insertions(+), 97 deletions(-) diff --git a/developer/authored/Manuscript.copy/Document/manual.html b/developer/authored/Manuscript.copy/Document/manual.html index d9bbc77..2080181 100644 --- a/developer/authored/Manuscript.copy/Document/manual.html +++ b/developer/authored/Manuscript.copy/Document/manual.html @@ -18,7 +18,7 @@ @@ -27,26 +27,24 @@

Leonardo·da·Vinci and other notes

- The middle dot used as a namespace separator is the middle dot of typography. On macOS: Option + Shift + 9. On Windows: Hold Alt and type 0183 on the numeric keypadLinux: Compose Key followed by . and -. It can be added to editor settings. If necessary, it can also be copied then pasted from the heading above. + The middle dot used as a namespace separator is the middle dot of typography. On macOS: Option + Shift + 9. On Windows: Hold Alt and type 0183 on the numeric keypad. Linux: Compose Key followed by . and -. It can be added to editor settings. If necessary, it can also be copied then pasted from the heading above.

- Content is found between the opening HTML tag and the closing HTML tag. E.g. <RT·noop>This is content.</RT·noop>. + Content is found between the opening HTML tag and the closing HTML tag. E.g. <RT·noop>This is content.</RT·noop>.

- An attribute is a name value pair found within an opening HTML tag. E.g. <RT·noop><RT·noop>. Here the attribute name is name and the attribute value is value. This examples shows a name attribute. + An attribute is a name-value pair found within an opening HTML tag. E.g. <RT·noop name="value">. Here the attribute name is name and the attribute value is value.

-

- All tags must be given in pairs, but not all have scoped content. + All tags must be provided in pairs, though not all enforce scoped content constraints.

-

Manuscript types

- These are the current top level semantic tag environments. They affect the formatting of scoped content. This includes the custom semantic tags, and can also include standard HTML tags. + Top-level semantic environments. These boundaries enforce the rendering constraints for all scoped content, encompassing both custom RT elements and standard HTML tags.

@@ -59,22 +57,22 @@ - + - + - +
<RT·article>A technical article.Standard technical document architecture.
<RT·memo>Strict print layout (6.5 inch width, serif typography, monochrome).Strict print layout constraint (6.5-inch width boundary, serif typography, monochrome execution).
<RT·book>Book layout. Does not yet exist, planned to be broken out of the article layout.Multi-chapter architecture. (Implementation pending; currently routes through the article layout).

Article manuscript

-

Here is an example header for an article

+

Structural header template for an article instance.

<!DOCTYPE html> @@ -111,20 +109,20 @@ <RT·term> - Standard technical term. Decorates first occurrence and establishes an anchor. Author should mark all occurrences of the term.
+ Semantic anchor for technical terminology. Formats the initial occurrence and registers the element ID for index generation. Authors must mark all occurrences of the term.
Attributes:
- id: (Default: Auto-generated from text content, e.g., "def-my-term") + id: (Default: Auto-generated slug, e.g., "def-my-term")
<RT·neologism> - Technical term coined in this document. Decorates first occurrence and establishes an anchor. Author should mark all occurrences of the term.
+ Semantic anchor for a novel term coined within the current document boundaries. Registers the ID for index generation.
Attributes:
- id: (Default: Auto-generated from text content, e.g., "def-my-term") + id: (Default: Auto-generated slug, e.g., "def-neo-my-term")
@@ -133,8 +131,8 @@

Layout environments

- This can be written inline with text, or as blocks. -

+ Context-aware formatting blocks. Valid inline or as distinct structural segments. +

@@ -145,19 +143,91 @@ - + - +
<RT·code>Code span or pre formatted code block with theme aware borders. Automatically dedents block content.Code span or pre-formatted code block. Automatically dedents structural alignment spaces and inherits theme boundaries.
<RT·math>Inline or block mathematics evaluated by MathJax.Injects mathematical layout evaluation via the MathJax rendering engine.
+

Grid environments

+

+ These structures map semantic data into an internal Cartesian grid state prior to CSS projection, isolating the markup from physical layout mechanics. +

+ + + + + + + + + + + + + + + + + + + + + + + + + +
TagDescription & Arguments
<RT·grid> + Base Cartesian coordinate grid. Projects child <RT·e> elements based on explicitly defined x and y index geometries.
+
+ Attributes:
+ model: Projection strategy. "html-grid-direct" or "html-grid-transpose". (Default: "html-grid-direct")
+ major: Carriage return trigger direction. "x" or "y". (Default: "x")
+
+ Child Element: <RT·e>
+ x: Target x-axis index or index range (e.g., "0-2", where 2 is the maximum index extent).
+ y: Target y-axis index or index range.
+ type: Decoration type. "data", "x-label", "y-label", or "name". (Default: "data") +
+
<RT·dictionary> + Two-column associative layout mapping explicitly declared keys to their scoped definitions.
+
+ Attributes:
+ key: Header text for the identifier column.
+ definition: Header text for the data payload column.
+
+ Child Element: <RT·entry>
+ key: The term being defined. The scoped HTML of the entry forms the definition value. +
+
<RT·relation> + Relational algebra layout formatter. Enforces multi-line text wrapping limits, calculates row distinction boundaries, and restricts column headers to the tuple scope.
+
+ Attributes:
+ layout-intention: "row-tuple" or "column-tuple". (Default: "row-tuple")
+
+ Child Elements:
+ <RT·tuple-meta>: Container for <RT·e> elements establishing the tuple field headers.
+ <RT·tuple>: Data tuple boundaries. Permits an <RT·name> identifier, followed by <RT·e> field values. +
+
<RT·matrix> + Linear algebraic matrix representation. Enforces rigid structural padding, brackets mathematical delimiters, and suppresses the exterior grid coordinate layout.
+
+ Attributes:
+ layout-intention: "row-vector" or "column-vector". (Default: "row-vector")
+
+ Child Elements:
+ <RT·vector-meta>: Container for <RT·label> elements defining the vector components/basis.
+ <RT·vector>: Vector boundary. Permits an <RT·name> identifier, followed by <RT·e> scalar values. +
+

Generators

-

The generators have no content between the opening and closing tags, rather generation is guided through attributes.

+

Data-injection nodes. These elements do not wrap content; execution is governed strictly by the attributes provided.

@@ -170,6 +240,7 @@ - +
<RT·title> + Constructs the primary document header block.
Attributes:
title: (Default: "Untitled Document")
@@ -182,16 +253,16 @@
<RT·TOC> - Compiles an automatic table of contents by scanning heading depths.
+ Compiles an automated Table of Contents by scanning the document's header hierarchy depth.
Attributes:
- level: Target heading level "N" or range "A-B". (Default: Context-aware. Looks backward for the nearest heading H(N) and targets H(N+1)). + level: Target heading index "N" or range "A-B". (Default: Context-aware. Scans backward for the nearest heading H(N) and evaluates targets at H(N+1)).
<RT·endnotes>Inserts a numbered list of the endnotes. Citations to the endnotes found in th text are replaced by their numbers in square brackets.Generates the numeric list of endnote payloads. Replaces all inline endnote citations with bracketed indices.
@@ -199,8 +270,7 @@

Counters

- A counter is made with the make tag. A distinct name attribute is required. - When a step occurs witin the content of another step, there will be a nested count. There is one internal representation for a count, but there are many styles of presentation available when the count is read. + Counters operate as explicit state machines. Initialization requires a unique identifier. Execution evaluates scope depth and increments the state. The layout engine maintains a single internal representation but maps it to multiple visual styles upon request.

@@ -213,15 +283,15 @@ @@ -230,32 +300,32 @@ <RT·Counter·step> @@ -264,7 +334,7 @@

Cross reference

- The Note tags provide a two pass mechanism for cross referencing content and page numbers throughout the document. + A two-pass structural mechanism bridging logical content with its physically paginated layout geometry.

<RT·Counter·make> - Initializes an empty named counter.
+ Initializes the named counter state machine.
Attributes:
- counter: Name of the counter.
- style: Either a single style, or a comma-separated list defining the formatting at each nesting level. The last format in the list applies to all yet higher nesting levels. Valid options: "NaturalNumber", "CountingNumber", "Roman", "roman", "Alpha", "alpha". The keyword "outline" maps to a standard mixed array. (Default: "NaturalNumber")
- on-first-step: The initial starting value, supplied in the format of the top-level style. (Default: "0")
- separator: The string joining depth sequence segments. (Default: ".")
+ counter: Required state identifier.
+ style: Single style string, or comma-separated hierarchy defining formats at each nesting depth. The terminal format applies to all deeper nestings. Valid arguments: "NaturalNumber", "CountingNumber", "Roman", "roman", "Alpha", "alpha". The "outline" flag translates to a standard mixed document array. (Default: "NaturalNumber")
+ on-first-step: The initial base value. (Default: "0")
+ separator: String appended between depth sequence levels. (Default: ".")
separator-placement: "embedded" or "embedded-after". (Default: "embedded")
- mode: "scoped" text between count scopes gets the count of the outer scope (like scope in code), or "milestone" between scopes continue with the prior scoped count (like sections of a document). + mode: "scoped" (content embedded between count boundaries receives the parent scope's value) or "milestone" (state carries forward sequentially irrespective of lexical depth).
- Count is available within scope. Th next scope will have one greater count. Any embedded steps will count at the next depth level.
+ Increments the counter block. Executing a step inside an existing step boundary pushes the state to the next depth index.
Attributes:
- counter: Required identifier. + counter: Required state identifier.
<RT·Counter·snapshot> - Clones count into a dictionary. Snapshots are processed by a separate document walk, so can can be referenced from anywhere.
+ Clones the active count variables into the lookup dictionary. Snapshot processing operates independently of the layout pass, allowing global retrieval regardless of physical placement.
Attributes:
- counter: Required identifier.
- snapshot: Required snapshot name. + counter: Required state identifier.
+ snapshot: Required dictionary assignment key.
<RT·Counter·read> - Accesses specified field from a snapshotted counter and renders it as innerHTML.
+ Retrieves the stored snapshot and projects it as innerHTML.
Attributes:
- snapshot: Required snapshot name.
- key: The state property to read. Dot-notation permits querying nested attributes (e.g., "count.status", "count.list"). Querying "count" outputs the style-mapped, separator-joined visual string. (Default: "count") + snapshot: Required dictionary assignment key.
+ key: Sub-state query property. Resolves dot-notation parameters (e.g., "count.status", "count.list"). Querying "count" triggers the style formatter and separator join parameters. (Default: "count")
@@ -277,21 +347,21 @@ @@ -311,13 +381,13 @@ - + - +
<RT·Note·write> - Records the scoped content and its resolved page number into the reference dictionary.
+ Registers the scoped content and its finalized layout page index into the reference dictionary.
Attributes:
- key: Required unique identifier for the note. + key: Required mapping identifier.
<RT·Note·read> - Retrieves data from a previously recorded note and injects it as innerHTML.
+ Queries the reference dictionary and injects the output.
Attributes:
- key: Required identifier matching a write tag.
- field: Selects the data to retrieve. Valid options are "content" (the original scoped HTML) or "page" (the computed page number). (Default: "content") + key: Target mapping identifier.
+ field: Data extraction parameter. Valid targets are "content" (the original HTML payload) or "page" (the evaluated layout page number). (Default: "content")
<RT·endnote> Scoped contents added to the list of endnotes.Marks the scoped content for extraction and placement in the endnotes block.
<RT·footnote> Scoped contents moved to the bottom of the page.Marks the scoped content for layout relocation to the active page's footer.
@@ -333,23 +403,23 @@ <RT·page> - Automatically generated boundary container. Do not author manually. + Physical document boundary generated dynamically by the paginator. Not for manual insertion. <RT·page-break> - Explicit directive forcing subsequent content to the next page container. + Explicit directive terminating the current <RT·page> evaluation and pushing subsequent data to the next boundary.

Memo environment

- The <RT·memo> container inherits all valid tags from the Article environment but overrides the global CSS to enforce a static, print ready monochrome aesthetic. Yeah, at one time this was working. + The <RT·memo> container inherits all layout functionality from the Article configuration but enforces a static, print-ready CSS environment.

Book environment

- The <RT·book> container is reserved for multi chapter compilations. It introduces tags designed exclusively for macro level document orchestration. (Does not currently exist, rather using the Article Tech Ref format.) + The <RT·book> container manages multi-chapter assemblies. It executes tags restricted to macro-level architectural transitions.

Book specific tags

@@ -363,7 +433,7 @@ <RT·chapter> - Chapter heading. Implies a page break, inherits standard H1 typography, and registers as a top level division in the TOC. Preserves existing class attributes. + Chapter delimiter. Triggers an immediate page break, escalates to H1 typography, and writes a top-level node to the TOC sequence. Retains any authored class attributes. @@ -379,7 +449,7 @@ <RT·theme-selector> - Floating interactive widget permitting real time swapping of visual themes. Retains preference in localStorage. + Injects a floating overlay permitting real-time CSS theme execution. Writes the selection to the browser's localStorage. diff --git a/developer/authored/Manuscript.copy/Element/TOC.js b/developer/authored/Manuscript.copy/Element/TOC.js index 78d7daa..227a090 100644 --- a/developer/authored/Manuscript.copy/Element/TOC.js +++ b/developer/authored/Manuscript.copy/Element/TOC.js @@ -118,6 +118,7 @@ Next heading 2 3 const topList = document.createElement('ul'); topList.style.listStyle = 'none'; topList.style.paddingLeft = '0'; + topList.style.marginBottom = '0'; container.appendChild(topList); // Stack of