Announcement

Collapse
No announcement yet.

Qt5's Linux Requirements Cause Problems

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Btw, the performance difference was reported upstream back in May, but no Qt developer seems to be interested:

    Comment


    • #62
      It is possible that Microsoft paid Nokia to screw up Linux support in Qt library.

      Comment


      • #63
        Originally posted by JS987 View Post
        It is possible that Microsoft paid Nokia to screw up Linux support in Qt library.
        Linux support in Qt hasn't been "screwed up", so no that did not happen. Too much FUD posted on this site :/

        Comment


        • #64
          Originally posted by JS987 View Post
          It is possible that Microsoft paid Nokia to screw up Linux support in Qt library.
          Yeah, just what this forum needs is more conspiracy theorists. Qt is developed in the open as open source software by various different parties and you somehow imagine that Nokia could intentionally ruin Qt to please some other company in less than a year without anyone noticing or leaking the information? Zester doesn't sound too smart either... a guy that would rather fork an entire toolkit than create an alternate QPA backend.
          Last edited by Teho; 16 September 2012, 01:25 PM.

          Comment


          • #65
            Originally posted by bwat47 View Post
            Linux support in Qt hasn't been "screwed up", so no that did not happen. Too much FUD posted on this site :/
            Qt5 is screwed up on Linux because it doesn't support native graphics system like Qt4 AFAIK, which will mean 6 times worse performance on my PC.

            Comment


            • #66
              Originally posted by JS987 View Post
              Qt5 is screwed up on Linux because it doesn't support native graphics system like Qt4 AFAIK, which will mean 6 times worse performance on my PC.
              I think the native renderer is still there. However, raster was introduced because it was supposed to be faster, even if it's purely software. So this looks more like a bug.

              Comment


              • #67
                Originally posted by RealNC View Post
                I think the native renderer is still there. However, raster was introduced because it was supposed to be faster, even if it's purely software. So this looks more like a bug.

                It seems Qt5 won't support -graphicssystem

                Comment


                • #68
                  Originally posted by JS987 View Post
                  https://bugreports.qt-project.org/browse/QTBUG-23022
                  It seems Qt5 won't support -graphicssystem
                  Those patches seem to be about the build option. If Qt5 allows switching gfx systems during runtime, then good riddance to build switches.

                  Comment


                  • #69
                    Originally posted by rohcQaH View Post
                    Those patches seem to be about the build option. If Qt5 allows switching gfx systems during runtime, then good riddance to build switches.

                    The QWidget based stack continues to work as in Qt 4.x, based on QPainter. QPainter does however support less backends than it used to. It is now limited to SW rasterization (Raster backend) for drawing to the screen, pixmaps and images, an OpenGL backend for GL surfaces and a backend for PDF generation and printing. The platform dependent backends using X11 or CoreGraphics are gone.
                    It seems only raster is supported.

                    Comment


                    • #70
                      Originally posted by JS987 View Post
                      http://labs.qt.nokia.com/2012/04/03/qt-5-alpha/

                      It seems only raster is supported.
                      It does say the opengl backend is still there though. Once the opengl backend matures it should be superior to both raster and x11. On my intel machine there's barely any difference between raster and x11 speed-wise, and for many raster is actually faster, if you see a big difference you should probably report a bug.

                      Comment

                      Working...
                      X