News for hackers. Stuff that matters.
Re:KDE makes Qt by exDM69 on Monday October 27, 2014 @07:52AM (#8514946)
In my opinion, it might be related to Qt being a huge framework and ecosystem where GTK is "just" a GUI toolkit.

I don't know if things have changed recently but at Qt at least used to require custom C++ extensions. This requires you to use custom toolchains or the recommended way of using the Qt Creator IDE. This isn't necessarily bad (I've only quickly tried it out, I don't really know) but it certainly makes me look at other alternatives first.

This isn't perhaps a big problem if you use other languages than C++ and there are decent wrappers available. But having to use a custom compiler/preprocessor just to get a GUI up isn't what I really want.

Qt is a pretty intrusive framework and ecosystem, where you have QStrings and QSockets and QEverything. GTK is perhaps a bit more lean and mean library than a full ecosystem.

I've also noticed that Qt applications do not work very well over remote X connection over slow networks. Apps built with other GUI toolkits work much more fluently. (I understand that this is not very common these days but I still do work on remote X on a daily basis).

I am sure that the Qt frameworks solve practical problems in cross platform development, but I'd rather not get involved in a whole ecosystem when all I need is a GUI toolkit.

Re:KDE makes Qt by nknighthb on Monday October 27, 2014 @08:17AM (#8515030)
"Custom toolchains" is massively overstating things. The only mandatory thing is the MOC, which is just a preprocessor that spits out some more C++ code for your regular compiler to build, and it's easily integrated with ordinary Makefiles (or whatever other half-sane build process you want). qmake is optional.

http://qt-project.org/doc/qt-4.8/moc.html

http://stackoverflow.com/questions/3632038/can-i-use-qt-with...

(And I don't know what to make of your comment about remote X. Years ago I sometimes ran entire remote KDE sessions in Xnest and didn't really have any problems, so this would seem like either something new, or a problem with your environment.)

Re:KDE makes Qt by scarygliders on Monday October 27, 2014 @08:06AM (#8514999)
As another poster replied, remote desktop users are a lot more common than you might realise :)

I haven't found this problem with Qt and remote connections. Then again I usually use Xrdp with the X11rdp back-end. If you haven't already done so, perhaps you should try it, it works beautifully, and if you run a Debian-based distro, I've even written a utility which compiles X11rdp/xrdp and packages it for your convenience ;)

Re:KDE makes Qt by dded on Monday October 27, 2014 @07:58AM (#8514964)
> (I understand that this is not very common these days but I still do work on remote X on a daily basis)

It's probably more common than you think. We also use it.

Re:KDE makes Qt by mkesper on Monday October 27, 2014 @08:41AM (#8515102)
Some people seem to profit of that, namely LXDE: http://blog.lxde.org/?p=1013