5 ms·
I'm the author. The QtSharp project used technology that couldn't really address the problem (MonoCppSharp). QML.Net is different. It is purely a QML integrat
by pknopf 7y ago
I'm the author.
The QtSharp project used technology that couldn't really address the problem (MonoCppSharp).
QML.Net is different. It is purely a QML integration (no c++ wrapper), using a C interop.
There is extensive unit tests for QML.Net, including garbage collection tests.
I consider it segfault-proof.
It's currently used in production on embedded medical devices: https://medxchange.com/4klear-all-in-one-camera-recorder/ https://medxchange.com/4klear-all-in-one-camera-recorder/
- simion314 7y agoSounds like a nice project, I did not want to insinuate that the quality is not good, I did not used Qt in a few years(since Qt4 days) so I am not sure about QML, without doing any research I think I am inclined to use the classic QtWidgedts for a desktop applications, SQML seems to me more mobile or designer first toolkit. I strongly believe that Microsoft made a huge mistake not making .Net WPF and Silverlight cross platform and open source it. they would have made money by selling the Visual Studio IDE,
- mlevental 7y agodoes it work with .net core? i.e. linux?