Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-22084

Full Asset Referencing

    XMLWordPrintable

Details

    • Epic
    • Resolution: Out of scope
    • P2: Important
    • None
    • None
    • Qt3D
    • None

    Description

      • In order to use QML 3D to effectively manage resources, improve performance, and correctly use 3D model files,
      • As a Qt application developer working with QML,
      • I want to directly create, modify, and render the 3D scenegraph and 3D models within it, from within my QML application code.

      Assumptions

      • Nodes and trees are generally interchangeable (A tree is just a collection of nodes connected by parent/child relationships)
        • Anywhere that we reference meshes or textures, we do not duplicate that data unless necessary (copy on write)
      • Syntax will have to be modified and framework level code written or modified to support this in the QML 3D

      Overall Requirements

      • Syntax changes and usage should follow as far as possible existing 2D QML
        • So, for example, the Item3D element may be written standalone (that is without an enclosing Viewport item)
      • Where possible short-hand syntax for common uses should be provided
        • Currently as well as specifying Translation2D? we can also just set the x or y property

      Developer Notes:

      Three key problems addressed by this epic/theme are:

      • Speed of rendering
      • Efficient use of storage (sharing objects, etc).
      • Usability (closing known gaps in the coverage of QML usage scenarios in 3D).

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              dpope Daniel Pope (closed Nokia identity) (Inactive)
              sarasmit Sarah Smith (closed Nokia identity) (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 4 weeks
                  4w
                  Remaining:
                  Remaining Estimate - 4 weeks
                  4w
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                  Gerrit Reviews

                    There are no open Gerrit changes