Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Future of QGraphicsView and QGraphicsScene
Forum Updated to NodeBB v4.3 + New Features

Future of QGraphicsView and QGraphicsScene

Scheduled Pinned Locked Moved Unsolved General and Desktop
qgraphicsviewqgraphicsscene
8 Posts 4 Posters 1.2k Views 3 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.
  • B Offline
    B Offline
    bewi
    wrote on last edited by
    #1

    Some years ago, there was a QT blog post essentially stating that one should avoid QGraphicsView for new implementations.
    How up-to-date is this warning today? What are the middle- to long-term plans for QGraphicsView?

    I'm maintaining a widget-based software module visualizing industrial data in custom diagrams. It's very customizable, interactive, may display thousands of objects at once and is highly performance-critical. It originiates from QT3 times, and uses a custom paint framework around QPainter. I'd love to migrate to QGrahicsview/-scene which covers most of our needs out of the box, but am hestitant to switch to something which will be deprecated in a while. However, I don't see that QML is up to the task for a long while.

    jeremy_kJ 1 Reply Last reply
    0
    • sierdzioS Online
      sierdzioS Online
      sierdzio
      Moderators
      wrote on last edited by
      #2

      QtGraphiscView is not deprecated and is not going away. It's also mature and feature-rich. You can safely port to it, in my opinion.

      If you want concrete plans from Qt project though (if there are any), ask on Qt Development Mailing List.

      (Z(:^

      1 Reply Last reply
      1
      • A Offline
        A Offline
        Asperamanca
        wrote on last edited by
        #3

        To my knowledge (and I dug hard and long), there is no adequate replacement for GraphicsView either existing or planned. It covers use-cases neither covered by QML nor Widgets nor Qt3D

        1 Reply Last reply
        1
        • B bewi

          Some years ago, there was a QT blog post essentially stating that one should avoid QGraphicsView for new implementations.
          How up-to-date is this warning today? What are the middle- to long-term plans for QGraphicsView?

          I'm maintaining a widget-based software module visualizing industrial data in custom diagrams. It's very customizable, interactive, may display thousands of objects at once and is highly performance-critical. It originiates from QT3 times, and uses a custom paint framework around QPainter. I'd love to migrate to QGrahicsview/-scene which covers most of our needs out of the box, but am hestitant to switch to something which will be deprecated in a while. However, I don't see that QML is up to the task for a long while.

          jeremy_kJ Online
          jeremy_kJ Online
          jeremy_k
          wrote on last edited by
          #4

          @bewi said in Future of QGraphicsView and QGraphicsScene:

          However, I don't see that QML is up to the task for a long while.

          QML (Quick), graphics view, and widgets don't need to be mutually exclusive. QQuickWidget plugs into an application in similar fashion to QGraphicsView.

          Asking a question about code? http://eel.is/iso-c++/testcase/

          A 1 Reply Last reply
          0
          • jeremy_kJ jeremy_k

            @bewi said in Future of QGraphicsView and QGraphicsScene:

            However, I don't see that QML is up to the task for a long while.

            QML (Quick), graphics view, and widgets don't need to be mutually exclusive. QQuickWidget plugs into an application in similar fashion to QGraphicsView.

            A Offline
            A Offline
            Asperamanca
            wrote on last edited by
            #5

            @jeremy_k said in Future of QGraphicsView and QGraphicsScene:

            @bewi said in Future of QGraphicsView and QGraphicsScene:

            However, I don't see that QML is up to the task for a long while.

            QML (Quick), graphics view, and widgets don't need to be mutually exclusive. QQuickWidget plugs into an application in similar fashion to QGraphicsView.

            Try to write a powerpoint-like editor in QML. GraphicsView is perfectly suited for this job.

            jeremy_kJ 1 Reply Last reply
            0
            • A Asperamanca

              @jeremy_k said in Future of QGraphicsView and QGraphicsScene:

              @bewi said in Future of QGraphicsView and QGraphicsScene:

              However, I don't see that QML is up to the task for a long while.

              QML (Quick), graphics view, and widgets don't need to be mutually exclusive. QQuickWidget plugs into an application in similar fashion to QGraphicsView.

              Try to write a powerpoint-like editor in QML. GraphicsView is perfectly suited for this job.

              jeremy_kJ Online
              jeremy_kJ Online
              jeremy_k
              wrote on last edited by
              #6

              @Asperamanca I think my point was missed. There's no need to choose Quick|Graphics View|Widgets for the entire application. Use each where they make sense and use the underlying Qt core functionality to communicate.

              Asking a question about code? http://eel.is/iso-c++/testcase/

              A 1 Reply Last reply
              0
              • jeremy_kJ jeremy_k

                @Asperamanca I think my point was missed. There's no need to choose Quick|Graphics View|Widgets for the entire application. Use each where they make sense and use the underlying Qt core functionality to communicate.

                A Offline
                A Offline
                Asperamanca
                wrote on last edited by
                #7

                @jeremy_k said in Future of QGraphicsView and QGraphicsScene:

                @Asperamanca I think my point was missed. There's no need to choose Quick|Graphics View|Widgets for the entire application. Use each where they make sense and use the underlying Qt core functionality to communicate.

                Yes, I missed your point. But maybe you missed mine: There is currently no better technology (in Qt) for some use cases than GraphicsView. Of course I can mix and match, depending on what I need. I took that as given :-)

                jeremy_kJ 1 Reply Last reply
                0
                • A Asperamanca

                  @jeremy_k said in Future of QGraphicsView and QGraphicsScene:

                  @Asperamanca I think my point was missed. There's no need to choose Quick|Graphics View|Widgets for the entire application. Use each where they make sense and use the underlying Qt core functionality to communicate.

                  Yes, I missed your point. But maybe you missed mine: There is currently no better technology (in Qt) for some use cases than GraphicsView. Of course I can mix and match, depending on what I need. I took that as given :-)

                  jeremy_kJ Online
                  jeremy_kJ Online
                  jeremy_k
                  wrote on last edited by
                  #8

                  @Asperamanca said in Future of QGraphicsView and QGraphicsScene:

                  @jeremy_k said in Future of QGraphicsView and QGraphicsScene:

                  @Asperamanca I think my point was missed. There's no need to choose Quick|Graphics View|Widgets for the entire application. Use each where they make sense and use the underlying Qt core functionality to communicate.

                  Yes, I missed your point. But maybe you missed mine: There is currently no better technology (in Qt) for some use cases than GraphicsView. Of course I can mix and match, depending on what I need.

                  No, I didn't.
                  We're in agreement there. It's easy to look at the graphics silos and forget that they can cooperate.

                  Asking a question about code? http://eel.is/iso-c++/testcase/

                  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