Details
-
User Story
-
Resolution: Unresolved
-
P1: Critical
-
None
-
Qt Installer Sprint 68, Qt Installer Sprint 69, Qt Installer Sprint 70, Qt Installer Sprint 71, Qt Installer Sprint 72, Qt Installer Sprint 73, Qt Installer Sprint 74, Qt Installer Sprint 75, Qt Installer Sprint 76, Qt Installer Sprint 77, Qt Installer Sprint 78, Qt Installer Sprint 79, Qt Installer Sprint 80, Qt Installer Sprint 81, Qt Installer Sprint 82, Qt Installer Sprint 83, Qt Installer Sprint 84, Qt Installer Sprint 85, Qt Installer Sprint 86, Qt Installer Sprint 87, Qt Installer Sprint 88, Qt Installer Sprint 89, Qt Installer Sprint 90, Qt Installer Sprint 91, Qt Installer Sprint 92, Qt Installer Sprint 93, Qt Installer Sprint 94, Qt Installer Sprint 95, Qt Installer Sprint 96, Qt Installer Sprint 97, Qt Installer Sprint 98, Qt Installer Sprint 99, Qt Installer Sprint 100
Description
After deciding to ramp down Qt Conan, we should concentrate on improving the installer CLI experience.
For example, the CLI documentation is in Qt Installer Framework documentation, where it is difficult to find it. We should link it at least for "Get and Install Qt", which currently documents only the GUI installer use.
The CLI has been reported to be a little bit challenging to use because of complicated component names. We should study, if we can provide easy to use alias names like install qt-virtualkeyboard.
We should also study, if the default installation could be used in the command line, such as install QtDesignStudio. The component names should not be case-sensitive.