https://bugs.documentfoundation.org/show_bug.cgi?id=153534
--- Comment #21 from Klim <[email protected]> --- (In reply to Eyal Rozenberg from comment #6) > I protest the non-serious discussion of this bug in the recent design > committee session. -X- I don't think certain things have to be hierarchical. they can be combined with composition. however, composition is not how style works. there is something to think about. a style can be selected from a list without overriding things that are not related to the style and the behavior of other styles at the same level. in fact, the page is a composition of its entities. the page style is a description of the properties of these entities. the page style hierarchy must depend on the hierarchy of these entities. based on falsifiability, I would prefer to consider cons, not pro. -XX- based on architectural principles, i would prefer to see from more specific things with flexible behavior to more general things with specific behavior (instability and abstraction relation). -XXX- It seems to me that it is necessary to separately and in detail describe the shortcomings associated with: - unexpected or counter-intuitive behavior, side effects, violation of the Least principles, violation of the DRY and KISS, violation of the open-closed principle. - destructive use cases, context violation, scope and lifetime violations. -XXXL- example of bad style design: https://shaunakelly.com/word/styles/custom-table-styles-2002-2003.html i.e. perhaps it would be a better solution to separate (9) and (10) into first page properties (added blanked page) and footer properties (for odd numbering). etc. Some of this has already been covered, but not in as much detail as i would like. -- You are receiving this mail because: You are the assignee for the bug.
