3 ms·
Eh? X11 is probably Qt's best target, and it's one of the most popular toolkits for building X11 applications. What made you think it wasn't efficient?
by rossy 7y ago
Eh? X11 is probably Qt's best target, and it's one of the most popular toolkits for building X11 applications. What made you think it wasn't efficient?
- yakubin 7y agoLack of support for X forwarding in Qt5 perhaps? JPEGs are being sent over the network and so the experience when using e.g. X2GO with a recent Qt Creator on a server is crappy.
- Spivak 7y agoCheck out https://bugreports.qt.io/browse/QTBUG-50338 https://bugreports.qt.io/browse/QTBUG-50338 They made a choice that was good for local rendering but because it sends full bitmaps to the X server to display it uses a lot of bandwidth which killed performance when forwarding X applications over the network. I'm personally of the opinion that today's X is only accidentally network transparent and a bad remote desktop solution but I don't deny that it's part of a lot of peoples' workflows.
- rossy 7y agoRight, that makes sense. I didn't know they removed QT_GRAPHICSSYSTEM=native in Qt5. I'm of the same opinion as you, but I can see why it would be a problem for some. (For some reason we still had to use Solaris X terminals in my first year of university.)
- jcelerier 7y agoNative painting was reimplemented since 5.10. You need to configure Qt with with -xcb-native-painting though.