5 ms·
This (and WebEngine) is why we switched to Gtk. I'm sure it's a nice book, though.
by DiseasedBadger 8y ago
This (and WebEngine) is why we switched to Gtk.
I'm sure it's a nice book, though.
- MarvelousWololo 8y agoCould you elaborate here please? I'm trying to learn qt at the moment.
- toyg 8y agoI believe he means that he switched to GTK because Qt is moving away from traditional desktop widgets (in favour of QML / QtQuick) and he didn’t want to go that way.
- MarvelousWololo 8y agoHm that's a bummer. It sounds like it's taking the Electron path then? Because that's exactly what I was trying to avoid.
- marcoms 8y agoThe code is also compiled to native code, but it's written declaratively. It's not for everyone, but it's not the same as Electron. Even still you have the option to use the traditional imperative API.
- fernly 8y agoI'm sure one cause is that QtWebEngine is a steaming garbage fire, with a far more limited API than the old WebKit based system, and many more bugs (not that the Qt4 WebKit support was a shining example) -- especially if you attempt to "deploy" (package) an app using it on MacOS.
- flukus 8y agoGtk is also increasingly focusing on horrible xml UI's and treating the code API as a second class citizen, at least in documentation.
- 0815test 8y agoIt's nothing new, GLADE has been a thing since the late 1990s.