diff options
author | Robert Griebl <robert.griebl@qt.io> | 2020-07-14 14:59:08 +0200 |
---|---|---|
committer | Robert Griebl <robert.griebl@qt.io> | 2020-07-17 01:39:18 +0200 |
commit | 8ba183a4ebaf550672ce5df506e87468f2baaed9 (patch) | |
tree | 4b03876dcd14f6699c8189340740a09043239ccf /src/plugin-interfaces/startupinterface.cpp | |
parent | 877ec0c6c206e40c24ccdcc6ec595af500029d00 (diff) |
Spelling fixes all over the place
Change-Id: Ic0018eddb8fcfbd22136fbf62d3e15e0e1c4c0b3
Reviewed-by: Bernd Weimer <bernd.weimer@pelagicore.com>
Diffstat (limited to 'src/plugin-interfaces/startupinterface.cpp')
-rw-r--r-- | src/plugin-interfaces/startupinterface.cpp | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/src/plugin-interfaces/startupinterface.cpp b/src/plugin-interfaces/startupinterface.cpp index 73db5db3..8b464ff7 100644 --- a/src/plugin-interfaces/startupinterface.cpp +++ b/src/plugin-interfaces/startupinterface.cpp @@ -49,19 +49,19 @@ StartupInterface::~StartupInterface() { } \inmodule QtApplicationManager \brief An interface that allows to implement custom startup activities. - This interface provides hooks that are called during the startup of application-manager + This interface provides hooks that are called during the startup of application manager processes. Hence, implementers of the interface can run their custom code at certain points during the startup phase. A plugin has to implemet the pure virtual functions of the StartupInterface. The interface is - the same for the System-UI (appman), as well as for QML applications (appman-launcher-qml). The + the same for the System UI (appman), as well as for QML applications (appman-launcher-qml). The plugins that should be loaded have to be specified in the (am-config.yaml) configuration file. - The following snippet shows how the application-manager can be configured to load and execute - the \c libappmanplugin.so in both the System-UI and applications and additionally the - \c libextplugin.so in the System-UI only: + The following snippet shows how the application manager can be configured to load and execute + the \c libappmanplugin.so in both the System UI and applications and additionally the + \c libextplugin.so in the System UI only: \badcode - # System-UI + # System UI plugins: startup: [ "path/to/libappmanplugin.so", "path/to/libextplugin.so" ] @@ -90,7 +90,7 @@ StartupInterface::~StartupInterface() { } /*! \fn void StartupInterface::afterRuntimeRegistration() This method is called, right after the runtime has been registered. - \note It will only be called in the System-UI process. + \note It will only be called in the System UI process. */ /*! \fn void StartupInterface::beforeQmlEngineLoad(QQmlEngine *engine) |