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

Should we split the import QtApplicationManager 1.0 namespace?

    XMLWordPrintable

Details

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

    Description

      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?

      Attachments

        Issue Links

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes