docs: Remove old ApplicationInstaller references

Change-Id: I0dbb4197a669df2434f1d2ba07ac6e8fa2bd6877
Reviewed-by: Bernd Weimer <bernd.weimer@qt.io>

8 files changed, 21 insertions, 21 deletions

diff --git a/doc/configuration.qdoc b/doc/configuration.qdoc
index d46b958b..770b1c56 100644
--- a/doc/configuration.qdoc
+++ b/doc/configuration.qdoc
@@ -190,7 +190,7 @@ ui:
     \row
         \li \b --dbus
         \li string
-        \li Registers the ApplicationManager, ApplicationInstaller, NotificationManager, and
+        \li Registers the ApplicationManager, PackageManager, NotificationManager, and
             WindowManager on the specified D-Bus. This can be a full D-Bus bus specification string,
             \c session, \c system, \c auto (default), or \c none (for no registration at all).
 
@@ -210,7 +210,7 @@ ui:
         \li Allows for more fine-grained control over D-Bus registrations and function call
             policies. Every key (with one exception - see next) in this map corresponds to the
             D-Bus interface name you want to configure (\c io.qt.ApplicationManager,
-            \c io.qt.ApplicationInstaller, \c io.qt.WindowManager, and \c org.freedesktop.Notifications).
+            \c io.qt.PackageManager, \c io.qt.WindowManager, and \c org.freedesktop.Notifications).
             If such a key is present, it takes precedence over the \c dbus command line option.
             Each key's value is a \l{D-Bus specification} object.
     \row
@@ -555,7 +555,7 @@ function, while preventing anyone to remotely call \c acknowledgePackageInstalla
 \badcode
 ...
 dbus:
-  io.qt.ApplicationInstaller:
+  io.qt.PackageManager:
     register: 'session'
     policy:
       startPackageInstallation:
@@ -575,8 +575,8 @@ of these available interfaces are as follows:
         \li \c io.qt.ApplicationManager
         \li ApplicationManager
     \row
-        \li \c io.qt.ApplicationInstaller
-        \li ApplicationInstaller
+        \li \c io.qt.PackageManager
+        \li PackageManager
     \row
         \li \c io.qt.WindowManager
         \li WindowManager
diff --git a/doc/manifest-old.qdoc b/doc/manifest-old.qdoc
index bcd2e00c..54f377ff 100644
--- a/doc/manifest-old.qdoc
+++ b/doc/manifest-old.qdoc
@@ -96,7 +96,7 @@ The fields within the \c info.yaml manifest data (second YAML document) are as f
         \c{!#$%&'`^~_+-=.,;()[]{}}. If you are building a larger system with third party
         applications, it is good practice to use reverse DNS notation for the application IDs to
         help keep track of your IDs in the long run. The helper function
-        \l{ApplicationInstaller::validateDnsName} can help you to enforce this policy from the
+        \l{PackageManager::validateDnsName} can help you to enforce this policy from the
         System UI.
 \row
     \li \c icon
diff --git a/doc/manifest.qdoc b/doc/manifest.qdoc
index 610df4d2..7ef25345 100644
--- a/doc/manifest.qdoc
+++ b/doc/manifest.qdoc
@@ -157,7 +157,7 @@ The fields used for each item within the \c applications list are as follows:
         \c{!#$%&'`^~_+-=.,;()[]{}}. If you are building a larger system with third party
         applications, it is good practice to use reverse DNS notation for the application IDs to
         help keep track of your IDs in the long run. The helper function
-        \l{ApplicationInstaller::validateDnsName} can help you to enforce this policy from the
+        \l{PackageManager::validateDnsName} can help you to enforce this policy from the
         System UI.
 \row
     \li \c code
diff --git a/doc/packager.qdoc b/doc/packager.qdoc
index ecdcac76..3a31e4d0 100644
--- a/doc/packager.qdoc
+++ b/doc/packager.qdoc
@@ -46,16 +46,16 @@ package installations.
         \c{--json}: Output in JSON format instead of YAML.
 
         \c{--extra-metadata} or \c{-m}: Add the given YAML snippet on the command line to the
-            packages's \c extra meta-data (see also ApplicationInstaller::taskRequestingInstallationAcknowledge).
+            packages's \c extra meta-data (see also PackageManager::taskRequestingInstallationAcknowledge).
 
         \c{--extra-metadata-file} or \c{-M}: Add the given YAML file to the
-            packages's \c extra meta-data (see also ApplicationInstaller::taskRequestingInstallationAcknowledge)
+            packages's \c extra meta-data (see also PackageManager::taskRequestingInstallationAcknowledge)
 
         \c{--extra-signed-metadata} or \c{-s}: Add the given YAML snippet on the command line to the
-            packages's \c extraSigned meta-data (see also ApplicationInstaller::taskRequestingInstallationAcknowledge)
+            packages's \c extraSigned meta-data (see also PackageManager::taskRequestingInstallationAcknowledge)
 
         \c{--extra-signed-metadata-file} or \c{-S}: Add the given YAML file to the
-            packages's \c extra meta-data (see also ApplicationInstaller::taskRequestingInstallationAcknowledge)
+            packages's \c extra meta-data (see also PackageManager::taskRequestingInstallationAcknowledge)
 
         All of the extra-meta-data options are merged together, so all options can be used together
         and each option can also be given multiple times. The signed fields are added to the
diff --git a/doc/systemui.qdoc b/doc/systemui.qdoc
index 6ab5ffd7..e3e74eca 100644
--- a/doc/systemui.qdoc
+++ b/doc/systemui.qdoc
@@ -133,23 +133,23 @@ sources at intervals and store a history of these values. You can use this data
 purposes, such as to plot its previous values over time. For more information, see the
 \l{Display Information about Application Processes Example}.
 
-\section2 Application Installer
+\section2 Package Manager
 
 The \l{ApplicationManager} provides a list of all available applications in the
 \l{ApplicationModel}. In addition to applications bundled with the System UI,
 \e{system applications}, the ApplicationManager also provides a way to install new applications
-at runtime. These applications are maintained by the \l{ApplicationInstaller} singleton.
+at runtime. These applications are maintained by the \l{PackageManager} singleton.
 
-To start an installation, use \l{ApplicationInstaller::startPackageInstallation}. Once all
+To start an installation, use \l{PackageManager::startPackageInstallation}. Once all
 metadata from the application's package is extracted, the
-\l{ApplicationInstaller::taskRequestingInstallationAcknowledge} signal is emitted. This signal
+\l{PackageManager::taskRequestingInstallationAcknowledge} signal is emitted. This signal
 can be used to give you more information about the package, such as the name, size, or
 permissions. This installation needs to be confirmed using
-\l{ApplicationInstaller::acknowledgePackageInstallation}. After the installation is complete,
+\l{PackageManager::acknowledgePackageInstallation}. After the installation is complete,
 you can start the new application, as described in the \l{Life-Cycle}. To remove applications
-that have been installed, use \l{ApplicationInstaller::removePackage}.
+that have been installed, use \l{PackageManager::removePackage}.
 
-For more information, see \l{Application Installer}.
+For more information, see \l{Package Installation}.
 
 \section1 Best Practices When You Write a System UI
 
diff --git a/doc/write-applications.qdoc b/doc/write-applications.qdoc
index bd02fc83..61ecdeaf 100644
--- a/doc/write-applications.qdoc
+++ b/doc/write-applications.qdoc
@@ -52,7 +52,7 @@ about changes to an \c info.yaml file, you have to force a rebuild of this datab
 \c{appman --recreate-database}.
 
 \note Dynamically adding, updating, or removing individual applications is supported via the
-ApplicationInstaller interface.
+PackageManager interface.
 
 \section2 qmake Integration
 
diff --git a/examples/applicationmanager/hello-world/doc/src/hello-world.qdoc b/examples/applicationmanager/hello-world/doc/src/hello-world.qdoc
index 6d42ad32..de7dbaa0 100644
--- a/examples/applicationmanager/hello-world/doc/src/hello-world.qdoc
+++ b/examples/applicationmanager/hello-world/doc/src/hello-world.qdoc
@@ -71,7 +71,7 @@ examples/applicationmanager/hello-world$ appman --builtin-apps-manifest-dir ./ap
 
 The \c --builtin-apps-manifest-dir command line parameter tells \c appman where to find bult-in
 applications, in this case the \c apps subdirectory. Built-in applications are those that come
-pre-installed and cannot be removed via the ApplicationInstaller APIs. The next parameter is the
+pre-installed and cannot be removed via the PackageManager APIs. The next parameter is the
 System UI's \c main.qml filename, \c system-ui.qml.
 
 The screenshot below is what you should see:
diff --git a/src/shared-main-lib/startuptimer.cpp b/src/shared-main-lib/startuptimer.cpp
index 130a5be3..84f8becb 100644
--- a/src/shared-main-lib/startuptimer.cpp
+++ b/src/shared-main-lib/startuptimer.cpp
@@ -79,7 +79,7 @@
 <span id="color-green">0'158.477</span> after NotificationManager instantiation     <span id="color-blue">     </span>
 <span id="color-green">0'158.534</span> after SystemMonitor instantiation           <span id="color-blue">     </span>
 <span id="color-green">0'158.572</span> after quick-launcher setup                  <span id="color-blue">     </span>
-<span id="color-green">0'159.130</span> after ApplicationInstaller instantiation    <span id="color-blue">     </span>
+<span id="color-green">0'159.130</span> after PackageManager instantiation          <span id="color-blue">     </span>
 <span id="color-green">0'159.192</span> after QML registrations                     <span id="color-blue">     </span>
 <span id="color-green">0'164.888</span> after QML engine instantiation              <span id="color-blue">     </span>
 <span id="color-green">0'189.619</span> after D-Bus registrations                   <span id="color-blue">     </span>