2026/11/06

From WoozleCodes
Jump to navigation Jump to search
Friday, November 6, 2026 (#310)
Thursday Friday Saturday

References

Main Work

  • DBA
    • ⇒ problem: dumping each schema using the previous schema's filename
      • ⇒ improving logging output so I can figure out what's going on
        • ⇒ new rich-text output system
          • ⇒ "attributes"
            • ⇒ encapsulating the rendering of sub-items (starting with bullet-lists)

Let's say each Shape has a default shape for sub-elements. Then the blob-object can have a NewTwig() method which creates a new twig with the appropriate shape for the parent's context.

...but that still doesn't let me assign a default Style (e.g. List / ListItem)...

I'm wondering if maybe some of what is currently done in Style (or Rich?) belongs in Shape instead; as it is, Shape is almost useless except as a collection of Styles. The individual classes do nothing beyond being xenums, and I don't see any evidence that this information (i.e. which shape-type we're looking at) is ever used.

Tentative reworking:

  • Get rid of Shape.
    • (...or turn it back into a regular attribute-type? why do I keep thinking I will need it?)
  • Move Shape's attribute-value-objects list ($OAtVals) back into Rich.
  • Rich blobject construction now takes an optional list of Attribute-value objects, as it once did (a few days ago).
  • [insert more thinking here, because this thought isn't complete yet]

Clarity on the purpose of this class-structure:

  • The Rich clade and its helper-clade-families represent formatted text in the abstract: each piece can be assigned meaning or significance (both words trying to describe the same thing).
  • The Venue and Style clade-families (and helpers) represent how that meaning is presented.
  • The Venue object determines how meaning (Attributes) are mapped to presentation (Styles).
  • Each Style-class is Venue-specific, and can specify details of presentation that may only apply within its particular Venue (though it can also specify presentation-details that are largely portable or abstract, just at a lower/more-specific level -- e.g. color).

...so the idea of a Shape (or Rich blob) having a default Style is muddling the boundary between meaning and presentation; what I would want is default Attributes.

Revised plan:

  • Relegate Shape back to being another attribute.
  • Comment out all the places where I tried to use Shape-objects, and see if that causes a problem. If it does end up being needed, it should be relatively easy to update these.
  • Move Shape's attribute-value-objects list ($OAtVals) back into Rich.
  • Since there is already an object-class (AtVals) for representing a list of Attribute-objects, why not modify Rich blobject construction so it can take one of these (instead of a raw array).

Would it make sense to have AtVals provide default AtVal lists? That seems sensible... but instead of individual classes, they can be provisioned at need... somewhere, TBD...

Okay, the only thing that makes sense (to me and my tiny brain, as of yet) is that we can pull it from the Role attribute-value-object. Seems a little nuts, somehow, but maybe it will work?