Olivier Goffart

@Be-ing Is what you want related to issue #251 ? I believe we still want to declare explicitly what are the public properties.

Not much progress. We are still wondering what to do with the globals: When you declare a `global` in slint, is the `global` global for the one component (this is...

Note that multi-window do work in Slint if you either - Use the same root component multiple times - Use a different `slint!` macro or compilation unit for each windows...

I think this will get solved by updating the cargo dependency. There are several PR that does that. Eg https://github.com/kbknapp/cargo-outdated/pull/329 I wonder if this repository is still maintained.

document-features already fallbacks to Cargo.toml.orig. I think the problem happens when the dependencies end up vendored. Not sure what tools their using that removes the Cargo.toml.orig. But I agree it...

Maybe Releates to #2911 ?

Local variables might make some sense. But i would be hesitant to implement `for` loop. Our strategy had been to keep the language intentionally simple because the actual logic should...

We would need to decide a syntax for it. I'd go with `let` as this is the same syntax as rust and typescript. ``` let foo : string = "123";...

Thanks for filling the issue. This kind of related to https://github.com/slint-ui/slint/issues/104 We should put the documentation in the .slint files so then the LSP could know the documentation. (For our...

I am referring to the keyboard shortcut (edited description)