Live data from Hacker News

Technical Vision for Qt 6

blog.qt.io

141–150 of 184 posts

Re: Technical Vision for Qt 6

#141
post #129

I have given up on Qt since it doesn't work efficiently with X11. GTK works OK though.

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?

Lack 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.

Re: Technical Vision for Qt 6

#143
post #126
post #121

These changes are very welcome, but in my opinion are too little too late. Qt has missed the boat with the current developer mindset. While I want Qt to 'win', as the end result is superior to say an electron app, most developers are willing to sacrifice usability and add bloat by using electron. Or simply paint them selves into a corner with a native SDK. Qt has a massive uphill battle to try and stay relevant. Like…

I respect your comment, but I think it's a narrow look at what Qt is and what it's used for. You mentioned "native UI SDKs" having become preferrable, but keep in mind that in many scenarios, Qt is the native UI. On desktop Linux there isn't a lower level toolkit Qt is translating to, but also in the many embedded products Qt is used on: Car and aviation infotainment (a prominent example is Mercedes-Benz' MBUX OS, bu…

Another big user of Qt for their desktop products is Tableau, since it provides the same experience across Windows and OS X.

Re: Technical Vision for Qt 6

#144
post #97
post #34

I hope they fix QtDesigner to not be hot garbage. Elementary operations such as trying to move some controls to a container that has zero size is totally unintuitive (you need to alt+drag to the container in the widget tree view - note that nothing else needs that) and not always possible (the widget tree view doesn't scroll so if the container is out of view you can't move stuff there - the fact that selecting somet…

I prefer writing UI by hand, rather than using Qt Designer. In C++, I figured out a few simple macros to automatically redefine `auto w` and `auto l` to refer to the parent widget and layout. Is there a reason Qt Designer generates .cpp files which append a child to the parent after the child is fully fleshed out, rather than when the child is first constructed? Does the latter approach create too many relayouts, or…

I doubt order matters much. Typically you call setupUI() and then show(), so the widget is hidden during initialization. I don't think any layout work actually occurs until the widget becomes visible.

Re: Technical Vision for Qt 6

#146
I hoped there would be more focus on how their web assembly support will be improved (specifically, how they intend to handle the narrow viewports of mobile devices).

Web Assembly QT enables a really nice way for customers to mess with an app without installing anything on their systems. It works with Q5\, but a still has much to be improved.

\ with a bit of modification to QT's output.

Re: Technical Vision for Qt 6

#147
post #129

I have given up on Qt since it doesn't work efficiently with X11. GTK works OK though.

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?

Check out 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.

Re: Technical Vision for Qt 6

#148
post #147
post #129

Earlier quoted context omitted.

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?

Check out 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…

Right, 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.)

Re: Technical Vision for Qt 6

#150
post #61

Earlier quoted context omitted.

I keep coming back to the differences between OPENSTEP and Taligent and believe C++ isn't the best choice.

What were some of the differences? (Other than Taligent dying and OPENSTEP surviving via Mac OS X, which is all I know about the topic.)

There's a reason Qt had to invent the MOC.
Post reply on HN