Uploaded image for project: 'Qt Automotive Suite'
  1. Qt Automotive Suite
  2. AUTOSUITE-671

Should we split the import QtApplicationManager 1.0 namespace?

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • Icon: Not Evaluated Not Evaluated
    • 5.12.0
    • 5.11
    • Qt Application Manager
    • None

      Right now, all exported C++ classes end up in the QtApplicationManager import, regardless even if they are for the appman or app side.

      Should we split that kitchensink namespace into something along those lines?

      • QtApplicationManager.(Server|Client) to separate between server and client APIs? or even
      • split of non-core features like intents and notifications into separate imports?

        1.
        		 Doc update: mark where classes can be used Sub-task Closed Robert Griebl
        For Gerrit Dashboard: AUTOSUITE-671
        # Subject Branch Project Status CR V
        244028,7 Split the QtApplicationManager qml module dev qt/qtapplicationmanager Status: MERGED +2 0

            dandrader Daniel d'Andrada
            rgriebl Robert Griebl
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes