3 ms·

This reminds me of the project I am currently working on. .NET/QML https://github.com/pauldotknopf/net-core-qml https://github.com/pauldotknopf/net-core-qml N

by pknopf 9y ago

This reminds me of the project I am currently working on. .NET/QML https://github.com/pauldotknopf/net-core-qml https://github.com/pauldotknopf/net-core-qml Not quite production yet, but it will be soon. I'd love to here some input. You can check the unit tests for how things are working currently. At a certain point, I will also implement a Qml debugger in visual studio code.

jcelerier 9y ago
that's great! you should consider sharing this on the Qt mailing list.
dodyg 9y ago
Awesome. Starred!
_pmf_ 9y ago
Very nice. I have used both WPF/XAML and QML and definitely find QML's model much more intuitive (anchors make things so much easier). Looking forward to trying it out!
LemurMadness 9y ago
I really like this approach, particularly since it allows a clean separation between the responsibilities of designing the UI and writing the back-end code. The UI designer can still wire up events and design them in Qt Creator (maybe using placeholder events?) but then the .NET dev can write the back-end stuff for it.
- pknopf 9y ago
  Exactly. The tech-stack perfectly slices responsibilities. That is what really motivated me to do it. Seemed like peanut butter and jelly. Also, performance. Anything beats electron.