https://bugs.documentfoundation.org/show_bug.cgi?id=153534
Eyal Rozenberg <eyalr...@gmx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.documentfounda
| |tion.org/show_bug.cgi?id=14
| |9271
--- Comment #24 from Eyal Rozenberg <eyalr...@gmx.com> ---
(In reply to Klim from comment #21)
> -X- I don't think certain things have to be hierarchical. they can be
> combined with composition.
Yes, you're right, in the sense that if we had composition but not inheritance,
we could have a "landscape layout mixin", a "red background" mixin the user
might create, etc. - and those would not need to inherit the default page
style.
> however, composition is not how style works.
Well, it is how style (should) work, and how it works in CSS for example (and
remember ODS is an XML-based document format); it's just that we haven't gotten
around to implementing composition yet: bug 149271.
In the mean time, style inheritance is implemented in general, so it makes
sense to enable it for page (sequence) styles as well. OTOH, I wouldn't mind if
the styles which need either composition or inheritance to be "legitimate"
would be removed until either of the two bugs is fixed.
> 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.
I... am not sure I follow what you wrote, I'm sorry. I _think_ I agree with a
lot of it? Perhaps we could ask Heiko to hold a design meeting discussing this
issue and you could present your view?
>
> -XXXL- example of bad style design:
> https://shaunakelly.com/word/styles/custom-table-styles-2002-2003.html
>
Actually, we have rather similar problems with LO table "styles": See bug
152711 for Writer and bug 151264 for Impress.
> 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.
(9.) and (10.) are Left Page and Right Page. I'm not sure what you mean by
making them into "first page properties".
--
You are receiving this mail because:
You are the assignee for the bug.
