Qt5's Linux Requirements Cause Problems

[phoronix]

Phoronix: Qt5's Linux Requirements Cause Problems

With XCB being a requirement for the Linux version of Qt 5.0, and Xlib not being supported, it's causing problems for some wishing to adopt this forthcoming tool-kit...

http://www.phoronix.com/vr.php?view=MTE4NTk

[RealNC]

Qt 5 is using the raster engine, so no GUI operation is actually hardware accelerated (that model of accelerating "lines" and "triangles" on 2D GUIs has been outdated for years now on most modern operating systems.) So using XCB is fine.

[dolo]

Qt 5 is using the raster engine, so no GUI operation is actually hardware accelerated (that model of accelerating "lines" and "triangles" on 2D GUIs has been outdated for years now on most modern operating systems.) So using XCB is fine.

Yeah, fine. Why? Why do we need yet another useless dependency on mono stuff? What was the reasoning for this change?

I haven't heard any good reasons yet. It looks like Qt is going down the shitter and then I'll have to stop using KDE unless they fix it with a fork.

[chuckula]

Somebody made a post saying that using XCB means you are relying on Mono... that is a completely factually wrong statement and I'm a little confused as to how anyone could even come up with something that weird.

A little more seriously, could the original writer of the rant look into using EGL instead of GLX? Apparently GLX is quickly on its way to deprecation anyway, so EGL could be the right way to go. I'm not sure what sort of functionality he needs, but I hope that the XCB bindings (or another API interface) would give it to him. If he is just writing a window manager then I'm not sure why he needs low-level access to the guts of OpenGL anyway...

[lethal]

Qt5 is OpenGL based right

Can you show us where you fetching this information from? Sounds completely wrong.

[Shnatsel]

The reason I am soooo pissed is because I have been writing a new Qt Desktop Environment for the last 1-1/2 years and Qt devs broke it by removing the QX11 API's. And my new desktop is blazzzzzzing rubber melting FAST!!!!

Mind revealing the mysterious DE? "Steven Starr" isn't listed as an author at neither http://razor-qt.org/ nor http://www.maui-project.org/, and those are the only two emerging Qt DEs I'm aware of.

[RealNC]

Can you show us where you fetching this information from? Sounds completely wrong.

Qt 5 QML is OpenGL based (even on MS Windows):

http://doc-snapshot.qt-project.org/5...rting-qt5.html

"In Qt 5, all QML applications are rendered with an OpenGL scenegraph architecture rather than the Graphics View framework used in Qt 4."

Qt 5 widgets, however, are not using GL.

[jrdls]

Somebody made a post saying that using XCB means you are relying on Mono... that is a completely factually wrong statement and I'm a little confused as to how anyone could even come up with something that weird.

A little more seriously, could the original writer of the rant look into using EGL instead of GLX? Apparently GLX is quickly on its way to deprecation anyway, so EGL could be the right way to go. I'm not sure what sort of functionality he needs, but I hope that the XCB bindings (or another API interface) would give it to him. If he is just writing a window manager then I'm not sure why he needs low-level access to the guts of OpenGL anyway...

Completely agree. MESA developers discourage the use of GLX. EGL is usable and is a Khronos standard. And since Qt is all about portability, his code should run on more platforms, EGL being platform agnostic.

[curaga]

Completely agree. MESA developers discourage the use of GLX. EGL is usable and is a Khronos standard. And since Qt is all about portability, his code should run on more platforms, EGL being platform agnostic.

EGL hardly has an installed base right now. Maybe in five years you can rely only on it.

By my count, EGL is available on mobiles, mesa git, recent blobs. Not on much of the linux systems, nor Windows or Macs. (not 100% sure on the EGL situation on Macs)

[RealNC]

Yeah, fine. Why? Why do we need yet another useless dependency on mono stuff? What was the reasoning for this change?

I haven't heard any good reasons yet. It looks like Qt is going down the shitter and then I'll have to stop using KDE unless they fix it with a fork.

I think you're confusing something here. XCB has nothing to do with Mono. This is XCB:

http://xcb.freedesktop.org

It has been around for a long time and is a better way to get to X11 compared to using Xlib.