-
Notifications
You must be signed in to change notification settings - Fork 9
This Month in Linebender, December 2025 #134
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
| - [xilem#1484][]: Split Android examples into separate files. | ||
| - [xilem#1488][]: Renamed `map_message` to `map_message_result`. | ||
| - [xilem#1500][]: Removed `ViewCtx::state_changed`. | ||
| - [xilem#1503][]: Split some Xilem code into new a new `xilem_masonry` package. | ||
| - [xilem#1504][]: Fixed `TextInput` placeholder alignment. | ||
| - [xilem#1507][]: Wrote guidelines for writing Xilem doc examples. | ||
| - [xilem#1510][]: Added a new `CollectionWidget` trait to unify collection widget method naming. | ||
| - [xilem#1513][]: Added `WidgetMut::id`. | ||
| - [xilem#1519][]: Added `Canvas` widget. | ||
| - [xilem#1520][]: Fixed `Portal` view. | ||
| - [xilem#1526][]: Implemented `Into<BrushRef>` for `BorderColor`. | ||
| - [xilem#1527][]: Added `Gap` property to `Flex` and `Grid`. | ||
| - [xilem#1528][]: Added alternative text to `Image` widget. | ||
| - [xilem#1529][]: Added `WidgetTag::unique`. | ||
| - [xilem#1533][]: Renamed `Grid` attributes from `width` / `height` to `row_count`, `column_count`. | ||
| - [xilem#1534][]: Migrated to Kurbo's `Axis`. | ||
| - [xilem#1537][]: Fixed `ScrollBar` behavior with large content sizes. | ||
| - [xilem#1540][]: Improved `Flex` child constraint accuracy. | ||
| - [xilem#1544][]: Documented node non-persistence in accessibility method. | ||
| - [xilem#1545][]: Now using third person more consistently in docs. |
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.
A PR list isn't the most interesting for people. It may be better if we split off new features and major improvements from bug fixes and code formatting PRs so that the things that people outside of the project may care about are more up front.
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.
There shouldn't be any code formatting PRs at all. These PR lists are somewhat curated, I omitted most internal housekeeping type stuff.
However, yes, they are currently in order of PR creation date, but a likely-interest based ordering would be better. I reordered them like a changelog, with new stuff in the beginning etc.
DJMcNab
left a comment
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.
I've not actually re-read this since I made my changes, so this is a fairly rubber-stampy review.
I see that you've set a target date of tomorrow, and would recommend waiting to see if we get any more review before then. Maybe bring it up on Zulip? But if not, then we can just land this.
| If you wish to discuss the Linebender project individually, Daniel is offering ["office hours" appointments](https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ32eQYJ9DtZ_wJaYNtT36YioETiloZDIdImFpBFRo5-XsqGzpikgkg47LPsiHhpiwiQ1orOwwW2), which are free to book. | ||
| It really helps us to learn what aspects our users care about the most. |
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.
Let's remove this for this month, since I'll be away from the end of January.
This should cover everything notable, but of course additions are welcome.