Announcement

Collapse
No announcement yet.

Qt3D Will Likely Only Be A Tech Preview In Qt 5.5

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

  • Qt3D Will Likely Only Be A Tech Preview In Qt 5.5

    Phoronix: Qt3D Will Likely Only Be A Tech Preview In Qt 5.5

    While Qt3D is making great progress in recent months, for the upcoming release of Qt 5.5 it will most likely only ship as a "tech preview" feature...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    so they replace a already working and used api with a new one cause the can't lock it? lol

    Comment


    • #3
      Originally posted by Thaodan View Post
      so they replace a already working and used api with a new one cause the can't lock it? lol
      Huh? Where did you read that? The only "allow for closed source projects"-reference I could find is ThreadWaver. It's a (quite) old lib developed by KDE to ease development of multithreaded applications. ThreadWaver is LGPL-only so no chance to use/bundle it with Qt (from the perspective of the user of the Qt commercial license).

      Comment


      • #4
        Originally posted by schmalzler View Post
        Huh? Where did you read that? The only "allow for closed source projects"-reference I could find is ThreadWaver. It's a (quite) old lib developed by KDE to ease development of multithreaded applications. ThreadWaver is LGPL-only so no chance to use/bundle it with Qt (from the perspective of the user of the Qt commercial license).
        Threadweaver old? Its updated to Qt5 and activly used by KDE. The only problem by it is the missing static linking exception for commerical apps.
        Last edited by Thaodan; 10 February 2015, 04:33 AM.

        Comment


        • #5
          Originally posted by Thaodan View Post
          Threadweaver old? Its updated to Qt5 and activly used by KDE. The only problem by it is the missing static linking exception for commerical apps.
          Could have gotten wrong impression from Wikipedia but looked like ThreadWeaver is part of KDE, not Qt. It doesn't really make much sense Qt would have KDE dependencies

          Comment


          • #6
            Originally posted by nanonyme View Post
            Could have gotten wrong impression from Wikipedia but looked like ThreadWeaver is part of KDE, not Qt. It doesn't really make much sense Qt would have KDE dependencies
            I has no KDE deps it's just plain Qt.

            Comment


            • #7
              Originally posted by Thaodan View Post
              I has no KDE deps it's just plain Qt.
              Your answer was unclear: Is it part of Qt project or KDE project?

              Comment


              • #8
                Originally posted by nanonyme View Post
                Your answer was unclear: Is it part of Qt project or KDE project?
                No but it could be merged instead of write a complete new module.

                Comment


                • #9
                  Originally posted by Thaodan View Post
                  No but it could be merged instead of write a complete new module.
                  Did you mean forked?

                  Comment


                  • #10
                    Originally posted by nanonyme View Post
                    Did you mean forked?
                    no just merged from KDE to Qt,

                    Comment

                    Working...
                    X