IceSentry

> If they're different units it becomes undefined I don't know if I like that idea. It seems _very_ prone to cause hard to find bugs. I'd much prefer _at...

> But before making things crash I'd prefer to not have these math traits implemented at all for Val and force users to take out the values from Px or...

My issue is that `Val` shouldn't just coerce to `undefined` whenever it can't compute something because it will spread everywhere and will be extremely hard to debug. Operating on a...

@maccesch just to clarify a bit, when I say that number 4 is unacceptable. Your PR was completely fine based on the issue description and I don't want you to...

That could work, but this new api encourages people to just use `"path/to/font.ttf".into()` everywhere which would mean it's very possible a font won't be loaded by the time it reaches...

I don't mind doing it as a fallback, but personally I'd rather get an error if it's not set. Eventually, once we ship an editor we'll be able to ship...

I like the last version, but how would it work if we ever want to add more metadata to a scene that isn't just another entity?

> Top level sections? I kinda assumed the scene format would support nested scene or even multiple scene in a file. Assuming it's only one per file it makes sense...

The main reason I only used `with_style` and `with_color` is that, honestly, nobody should even be touching the other components 99% of the time. They are pretty much just implementation...

I renamed new to styled and added a with_focus_policy for the rare cases where you would want a styled node with pass-through.