Text styles should be inheritable about bevy HOT 2 OPEN

I would much prefer other tools for composition: I have been endlessly frustrated by style-inheritance in the past due to how poorly organized and difficult to reason about it is. That said, we need to at least demonstrate patterns to show how to build and compose styles, both for text and other UI elements.

I really like the list of text properties though, and want to have first class primitives (components maybe?) for all of those so users can quickly modify one property independently.

from bevy.

@alice-i-cecile I suspect that for many users, the reason CSS inheritance is hard to understand has to do more with the rules of cascade priority (which we are not proposing to add here) than inheritance.

However, as a compromise, we could make this behavior opt-in at the entity level. That is, in order to get inheritable text styles, you would add a marker component (e.g. UseInheritedStyle) to your Text entity that indicates that it wants to participate in inherited styling. This marker component would be used just like any other style component.

This is still an improvement over the current situation, particularly for font families. Loading a font asset from the asset system involves a non-trivial amount of code. Since most games only use a single font family, ideally you should only have to do this once at the top level of your app. Yes, you could store the font handle in a resource and inject the resource every place you create a text span; but it would be even better not to have to do this at all. Except in the case of image assets, style properties ideally should be standalone and not require references to things other than the entity.

from bevy.