-
Notifications
You must be signed in to change notification settings - Fork 5
Bump masonry, vello, and parley deps. #13
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
base: main
Are you sure you want to change the base?
Conversation
92d8dd5 to
fb3e7d8
Compare
|
I've gone ahead and run this, the primary view demo works well but I'm not 100% sure of the Masonry demo. It seems to let me focus in and type but I'd like a second set of eyes on it. |
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.
LGTM, aside from the layer handling.
| .with_child(NewWidget::new_with_props( | ||
| Flex::row() | ||
| .with_flex_child(TextInput::new("").with_auto_id(), 1.0) | ||
| .with_child(Button::new("Add task").with_auto_id()), |
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.
You can make this code slightly more readable with Button::with_text.
|
|
||
| [dependencies] | ||
| android-view = { path = ".." } | ||
| masonry = { git = "https://github.com/linebender/xilem" } |
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 think you could use the crates.io release instead?
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.
It didn't exist at that point 😉
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.
Oh and also that has to go in the ui-events 0.2.0 PR, because that's a separate set of changes.
| RenderRootSignal::NewLayer(..) => { | ||
| // TODO | ||
| } | ||
| RenderRootSignal::RepositionLayer(..) => { | ||
| // TODO | ||
| } | ||
| RenderRootSignal::RemoveLayer(..) => { | ||
| // TODO | ||
| } |
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.
If you don't know how to handle those, you should replicate the version in masonry_winit which calls RenderRoot::add_layer and the like. We should probably document this in Masonry.
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.
Will do, thanks.
No description provided.