6 ms·
With regards to QML, I believe KDE could benefit from offering a React/JSX-based API (similarly to what ReactNative does). This could potentially boost the KDE
by denysonique 2y ago
With regards to QML, I believe KDE could benefit from offering a React/JSX-based API (similarly to what ReactNative does).
This could potentially boost the KDE extension ecosystem by lowering the entry barrier for existing React devs familiar with the JSX syntax.
- guappa 2y agoQML already uses js? If you want to use the same API of an existing web framework, I'm sure that wouldn't work, since QML is exposing C++ objects to js code, so the API is set.
- Double_a_92 2y agoBut it's still an extra overhead that you need to first understand, instead of just writing a JS file with your code and then loading it.
- guappa 2y ago> instead of just writing a JS file with your code and then loading it If your js does no I/O at all, you can write pure js. But if you want to show some results, there is no way that you can do it without learning the relevant API to do that.
- noahadavis 2y agoEvery library is overhead that you need to first understand. There's no "just writing a JS file" or just writing a C++/C#/Java/Python/etc. file.
- cocoa19 2y agoMaybe not implement React, but Qt would benefit from using something like Facebook’s Flux architecture, where state flows down from parent objects to children. With Qt Widgets, it is annoying to create models (QAbstractItemModel), they are more difficult to implement than what it should and prone to errors. I haven’t done much QML beyond simple sample apps, but it seemed you still have to create Qt models for a lot of use cases.