Details
-
Suggestion
-
Resolution: Done
-
Not Evaluated
-
5.11
-
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
- is duplicated by
-
AUTOSUITE-678 Doc update: mark where classes can be used
-
- Closed
-
Gerrit Reviews
| 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 |