4 ms·
> I would much prefer a multiplatform native toolkit as a first class citizen in Rust It's extremely hard to make a proper cross-platform kit. Because every p
by troupo 3y ago
> I would much prefer a multiplatform native toolkit as a first class citizen in Rust
It's extremely hard to make a proper cross-platform kit. Because every platform has a gazillion little (and not-so-little) conventions about what's expected, behaviours, and even control placements. Even Qt struggles there and they have been doing it for over 30 years.
- zozbot234 3y agoWxWidgets does just that, but it exposes clunky, MFC-style C++ for its API. Bindings to other languages do exist though, so a Rust native binding should be possible too.
- troupo 3y agoWxWidgets has all the same issues: it's almost but not exactly native-looking and native-behaving on all platforms. Though I'll admit I haven't seen many wxWidgets app in the wild lately.
- hannofcart 3y ago> Even Qt struggles there and they have been doing it for over 30 years Furthermore, even they seem to have thrown in the towel and made the QtQuick (GPU rendered, non native looking widgets) as an alternative to the traditional QtWidgets.
- ahartmetz 3y agoSort of. Qt Quick is touch focused and native styling is (slowly...) in the works.