I love the concepts underlying the "styling paradigm" introduced in the old Omikhleia classes (so call that a "version 1"). Abstracting styling decisions in a consistent way (with "style specifications", style inheritance, etc.), outside the main code logic, is one of the key concepts I want to keep in the "refactored" Resilient classes.
From the inception, it was highly experimental, with decisions made on-the-go as I needed them for styling an actual book and being able to quickly change some styles and see the effects.[^1] To some extent, it worked well, but under time pressure[^2], some decisions were quick and not that general.
So big breaking changes were considered, and some work even started privately in that direction.
Without committing on a deadline, I'll open a PR referring to this issue, and push there the design documents, (part of) the current code changes (some were made in a private repository for my next book -- I'll check how to cherry-pick them, or just copy the relevant code if it's too entangled).
These changes encompass a lot of breaking changes regarding the styling API inherited from the old Omikhleia classes. (Die, \style:define and SIL-like friends, die!). When it's there, follow the PR and don't hesitate commenting it ;-)
[^1]: For the mere record, it's that book.
[^2]: With all the ongoing development of the support packages at the same time (tables, cross-refs, captioned figures, poetry...), it left little time to make sound decisions regarding the internals of the styling stuff. Then came some major work on the Markdown package collection, the switch to SILE 0.14... And a new book project....
This got mentioned in #11 and https://github.com/Omikhleia/markdown.sile/discussions/34#discussioncomment-4246305, and it is one of the major uncompleted task from the old repository https://github.com/Omikhleia/omikhleia-sile-packages/issues/13 (first bullet), it might be the good time for moving on, regarding the "version 2" Style Paradigm topic.
To summarize the things at stakes
So big breaking changes were considered, and some work even started privately in that direction. Without committing on a deadline, I'll open a PR referring to this issue, and push there the design documents, (part of) the current code changes (some were made in a private repository for my next book -- I'll check how to cherry-pick them, or just copy the relevant code if it's too entangled).
These changes encompass a lot of breaking changes regarding the styling API inherited from the old Omikhleia classes. (Die,
\style:defineand SIL-like friends, die!). When it's there, follow the PR and don't hesitate commenting it ;-)[^1]: For the mere record, it's that book. [^2]: With all the ongoing development of the support packages at the same time (tables, cross-refs, captioned figures, poetry...), it left little time to make sound decisions regarding the internals of the styling stuff. Then came some major work on the Markdown package collection, the switch to SILE 0.14... And a new book project....