Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. General talk
  3. The Lounge
  4. Finally from Nokia to Digia.
Forum Updated to NodeBB v4.3 + New Features

Finally from Nokia to Digia.

Scheduled Pinned Locked Moved The Lounge
16 Posts 8 Posters 6.3k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jaak
    wrote on last edited by
    #7

    Digia is aiming Qt 5.0 support for ios / Android. It would have been good if Digia somehow made the existing Qt 4.8 ports officially available. They have been in talks with both Bogdan and Mediator software.

    1 Reply Last reply
    0
    • U Offline
      U Offline
      utcenter
      wrote on last edited by
      #8

      The one big advantage Qt4 has over Qt5 is it doesn't require OpenGL hardware to run. Both Android and iOS devices all have openGL support, so it doesn't really make sense to waste more efforts on porting both Qt4 and Qt5 to those platforms, especially considering porting Qt4 will likely be more challenging.

      1 Reply Last reply
      0
      • sierdzioS Offline
        sierdzioS Offline
        sierdzio
        Moderators
        wrote on last edited by
        #9

        Strange of you to say that. Qt4 ports for both OSes already do exist. And Qt5 does not require OpenGL as long as you don't use QtQuick 2/ Qt3D.

        (Z(:^

        1 Reply Last reply
        0
        • S Offline
          S Offline
          Sam
          wrote on last edited by
          #10

          [quote author="Katherine " date="1348079625"]Aloha! Apologies for the radio silence from Digia's side. We were finalizing the last bits and pieces of the acquisition of Qt from Nokia. The deal is now closed - YAY! Our goal is to advance Qt and make it the best framework out there. We can't do this alone and look forward to working with the Qt ecosystem. Let's do this together!

          As the craziness of the transition settles and we finish combing through the hundreds of open items on our to-do lists, we are planning the next step forth for the future of Qt.

          We want to continue the conversation with you, so please continue engaging via the forums on this site.

          First order of the day: Let's get Qt 5 out the door successfully. Let's do it together!

          As we gather our forces, we will be communicating and engaging more and more on this site. Bear with us as we regroup!

          Smiles from the Digia Qt team[/quote]

          Well this was the response from Digia team on "this thread":http://qt-project.org/forums/viewthread/19443/P45/ , So we need to wait :)

          1 Reply Last reply
          0
          • S Offline
            S Offline
            stereomatching
            wrote on last edited by
            #11

            very nice to Qt + 1.

            1 Reply Last reply
            0
            • U Offline
              U Offline
              utcenter
              wrote on last edited by
              #12

              @sierdzio - IIRC widgets/QtGui in Qt5 is implemented on top of the scenegrapgh, which does require OpenGL. Not 100% sure thou.

              I remember people voicing concerns that Qt5 in practice is incompatible with embedded Linux, because unlike handheld devices, OpenGL is not granted. This is no big deal since a Qt4 port for embedded Linux already exists.

              Also I suspect as a new release, Qt5 is far more modular and flexible, with the very base infrastructure being designed to make porting easy, in contrast, Qt4 dates back to times long before those platforms existed, let alone considerations of porting to them.

              Matter of fact is Digia have pretty much confirmed they will be porting Qt5 and not Qt4. As for the maturity of existing ports, I haven't used the iOS port, but Necessitas lacks many features, such as multimedia, that are crucial to applications, oriented at those platforms. It shouldn't be that hard for Digia to implement ports from scratch, I was surprised to see JUCE, which has a single maintainer, providing fairly good support for both Android and iOS, and if a single guy can do it while maintaining and developing an entire framework, how hard could it be for Digia, especially now when they have taken in dozens of Qt developers.

              1 Reply Last reply
              0
              • sierdzioS Offline
                sierdzioS Offline
                sierdzio
                Moderators
                wrote on last edited by
                #13

                No, QtWidgets is independent of scenegraph.

                (Z(:^

                1 Reply Last reply
                0
                • L Offline
                  L Offline
                  lgeyer
                  wrote on last edited by
                  #14

                  As sierdzio already mentioned QtWidgets (as well as QtGui) is independent of the scenegraph. It is still based on QPainter, offering the raster and opengl backends.

                  The scenegraph requires OpenGL ES, not a OpenGL-capable GPU. Qt 5 can be used with any OpenGL software rasterizer, for example llvmpipe, where QtQuick2 still performs better than QtQuick1 based on QGV.

                  1 Reply Last reply
                  0
                  • U Offline
                    U Offline
                    utcenter
                    wrote on last edited by
                    #15

                    Good to know, but this still doesn't answer the question why Digia chose to port Qt5 instead of take advantage of the efforts, already spent on Qt4 by Bogdan and co.

                    1 Reply Last reply
                    0
                    • sierdzioS Offline
                      sierdzioS Offline
                      sierdzio
                      Moderators
                      wrote on last edited by
                      #16

                      Ask them, not us. Bogdan is working on Qt5 port, too. I really can't see an issue here. Qt5 is the way to go, and while Qt4 will be maintained, the real development effort goes in to v. 5.

                      (Z(:^

                      1 Reply Last reply
                      0

                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups
                      • Search
                      • Get Qt Extensions
                      • Unsolved