-
Notifications
You must be signed in to change notification settings - Fork 379
Rewrite Text migration guide for 0.15 #1814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
||
__Accessing text spans by index__ | ||
- `ab_glyph` has been replaced with `cosmic-text`. These changes are mostly internal and the majority of users will not interact with either text backend directly. | ||
- each text section is now stored as a distinct entity within the standard hierarchy, rather than as a `Vec<TextSection>` on the `Text` component. Children of `Text`/`Text2d` entities with `Text` `Text2d` components will act as additional text sections. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps not a migration issue, but somewhere I think it useful to mention that since text sections are entities, you can now insert components on them, which is useful for things like:
- Dynamically-computed text
- Picking behavior
- Animated text styles.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this belongs in the release notes, not the migration guide.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Much improved. Couple notes:
There are so many changes to text that I think we could use a few quick before/afters:
- Spawning some text
- Spawning some text with multiple sections
The guide for 15368 also needs adjustment after 15857. It's content would also be better communicated with a diff, I think.
I wonder if we should be linking off to the required components blog post section for context in related migration guides.
Fixes #1782.
This PR leans heavily on the migration guide provide by @MiniaczQ in bevyengine/bevy#15887 <3