Repository navigation
fix child layout - #2
Conversation
0eb87ae to
7572363
Compare
|
Looks better, awesome! I plan to add text sizing too, and maybe try to integrate some more advanced text rendering techniques. I'd love to review the native-core crate at some point. I saw you ran into some issues with GATs so it seems pretty advanced. I'm personally interested in writing custom elements using shaders as extensions for https://github.com/jkelleyrtp/sciviz and I haven't dug too deeply on how we would architect blitz to be extendable with custom elements. Additionally I'd like to see if we could get some input widgets working. Druid has the macos native text editing interface figured out and I think it'd be really slick if we could start to bring over some Druid widgets into piet-wgpu land. Ideally we could use Druid as inspiration for native widgets and use the VDOM patch API to drive them. I think Piet would be a natural extension for a canvas, but I'm particularly interested in a raw surface to pipe raw wgpu into. |
The only use I have for GATs is associating (A, B, C,..) with (&A, &B, &C,..) so it's not that bad. I feel like there should be a way to do that but I can't find one. I think the new version is quite a bit easier to read as well. I think text sizing should be possible, but text wrapping is requires the new version of native-core.
I looked for this earlier, it looks like they just mimic the native interface instead of embedding it. We can port most of the logic from the tui widgets for the cursor and textarea, it is missing some things (insert mode etc.) and does not have any platform specific behavior yet, but most basic functionality is done.
Yes, I need to learn more about how wgpu works, but it would be needed for things like video playback for internal widgets, so it makes sense to expose it. |
Update dependencies and implement linear-gradient
Add pitch to readme
Taffy outputs layout relative to the parent. Accumulate the offsets to calculate the current position.