Talin

> @calvinf is not wrong. I could see extracting some of the Ladle's core functionality into library (story processing/parsing, configuration, vite setup...) so other frameworks can built the UI around...

> It should be pretty easy to work around those, also `vite.config.js` is fully accessible. Beyond my skill unfortunately. I spent about a day trying to solve this, and ran...

What I want to see is an ecosystem in which frameworks like Leafwing Input Manager (LWIM) and bevy_eventlistener (BEL) can coexist. We are already part of the way there in...

I just wanted to add that if clipping is holding up this PR, I would say go ahead and commit even if clipping is not there yet, and finish it...

Q: Are there any plans to support "inset" shadows? In CSS, I occasionally use this feature for things like text input fields, slider tracks, and other widgets that require a...

@ickshonpe Wanted to mention that `ZIndex` is the only ui component that doesn't implement `PartialEq`. This came up because I was writing unit tests for styling which needed to compare...

Q: Are there plans to support "font families", in other words, the ability to select the correct font asset based on style options? As opposed to what we have now:...

@TotalKrill I am in 100% agreement with that approach. Small bites. We can talk about font-families later. I think that it should be something that can be defined either in...

BTW, at first I thought that this might be difficult to fix because clipping happens earlier in the pipeline. However, if the UV coordinates are correct for background images, then...

I've been using the [palette](https://docs.rs/palette/0.7.4/palette/) crate as inspiration for what methods and traits to support - but only as a starting point, not as a rigid spec. Now, `palette` doesn't...