Conversation

Replying to
I understand why someone would make an app that runs in a browser; that has certain benefits. but you had a choice and you *still* used a browser? that's just irresponsible.
4
45
the only sort of valid reason I have heard so far is "I have ideological hatred of all native UI toolkits", everything else is just not knowing what e.g. Qt 5 can do
11
36
look, if you absolutely *insist* on using JavaScript, you can use that to write apps with Qt 5. I wouldn't say you should, but you can, and it's less horrible than the "web platform"
5
20
Replying to
depending on what part of Qt5 you use, the JS support is years behind browsers though (writing QML JS feels like 2010 again, without the cross-browser issues though)
1
Replying to and
you can embed a WebView but iirc that's a WebKit so uhhh what exactly did I save again maybe there's a way of writing nice JS for Qt that isn't also pointless but I've not found it yet
1
1
Replying to
ok so QML (which allows you to write interfaces in JS and has nice things like actual Signals) uses its own JS engine called V4, at least it did the last time I evaluated the topic which was Qt 5.4 times iirc
1
Replying to and
that stuff is native but it's not my department at work so take it with a grain of salt meanwhile Qt WebView allows you to render HTML+CSS+JS but is a full webkit, so basically a browser (unless they switched to V4? which I doubt)
1
1
Replying to and
the way our codebase currently looks, this may be useful in one or two places, but I don't know if I'll be able to get a green light for it (there are so many lower-hanging fruits and nobody but me has web background)
1