Simon Hausmann

The proposed path forward would be at least three-fold: 1. Add the ability to include additional message catalogues in the bundled translations. This might require a new variant of the...

Agreed. I think this is the right signature. For SharedString: I agree. I think if we're willing to sacrifice a bit `SharedVectorHeader` this should be doable.

In a separate project, I tried to implementing this without Slint and it turns out to be quite possible, with the `tr` crate, `xtr` for extraction, implementing the `tr::Translator` trait,...

Yeah, I was thinking the same. I might just end up doing that. Will discuss with you later :)

That's an excellent point - thanks! We'll go with `slint/slint-nightly` then.

Yes, it can't have children at run-time. But I was solely thinking in terms of syntax (and I used the wrong term, oops :). What I mean is that I...

You're right, it's strange that `Path` doesn't allow `Image` and `Text` and the allowed "children" don't have the usual geometry but a `LineTo`'s `x` and `y` has a very different...

Currently the `width` and `height` of a `Path` is zero by default. We should consider revisiting this and applying perhaps `100%` like we do for Rectangle.

related cleanup: https://github.com/slint-ui/slint/pull/2087

The discussion at https://github.com/slint-ui/slint/issues/1742 also yields an aspect we should improve on: The properties in the path elements don't behave like properties, i.e. they can't be animated directly, only via...