2026/10/30
< 2026
|
Friday, October 30, 2026 (#303)
|
|
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"
- ⇒ new rich-text output system
- ⇒ improving logging output so I can figure out what's going on
- ⇒ problem: dumping each schema using the previous schema's filename
A tentative solution to yesterday's conundrum:
- Each Venue class is configured with a set of Shape objects.
- Each Shape object is configured with a set of Style objects.
- A Shape is no longer an Attribute.
- A Role is still an Attribute (currently the only kind, but I expect there to be more).
- Every Shape-object has a list of (zero or more) Attributes.
- Each text-blob object now takes a Shape object instead of an Attribute list (array).
...and I think the rules for the new Style system (to replace the old one in \Config) will be:
- Each Venue has a Styles object which lists all the available Style objects.
- Each Styles object has a Screen object, at least for now, to handle certain kinds of rendering. (The Screen clade is a bit awkward, and should be revisited later.)
- Maybe this property should be protected, because I don't think we want other code depending on it.
- There still needs to be a global Screen object representing the default output device/Venue/whatever -- and since some code will be using that to format its output, a Screen object will need to have a Venue object.