kas VS SIMple-Mechanics

Qt classic/widgets? I'm developing Kas to offer vaguely similar features (e.g. data models, theme abstraction, custom widgets with complex event handling), though said event handling and data models are quite different. It's still got a long way to go (so API is not stable), but in case you are interested, I should be dropping a new release tomorrow.

KAS GUI

kas-wgpu looks hopeful, but there's very little information about it and I'm not even sure it works on Android.

Changelog

The next release will support dynamic linking which approx. halves the recompile time in my quick tests. This is based on Bevy which also recommends using LLD (see here); I didn't have much success with this yet however.

If you want a "native-like" toolkit like Qt but Rust-native, then Druid, KAS and Iced are the most advanced in my opinion (though all are incomplete).

Yes. It was actually a mistake (using a nightly compiler and not realising the lock-in). But in this case (with KAS still in "earlyish development" and the workaround being less concise), I decided to leave it.

This is a little library I've been using recently (original version here).

Hello, I am github.com/dhardy, maintainer of rand, former dev of OpenMalaria epidemiology simulator, author of KAS GUI and Rust enthusiast since 2013. I may be interested in positions within Europe.

I'm a freshman in college at Purdue University and I'm looking for a Summer 2021 internship. My biggest project is SIMple Physics (https://github.com/mkhan45/SIMple-Mechanics), and I'm experienced with Rust, Python, and Java among others. I'm open to an unpaid internship if I think the experience will be truly educational but I would, of course, prefer to be paid.

A side effect of this feature is that the sim is practically a Lua scriptable game engine now, with the exception that you can't handle user input from Lua. I wrote flappy bird with an AI using it.