diff options
Diffstat (limited to 'doc')
-rw-r--r-- | doc/index.qdoc | 1 | ||||
-rw-r--r-- | doc/migration-guide-6.2.qdoc | 38 | ||||
-rw-r--r-- | doc/singlevsmultiprocess.qdoc | 11 | ||||
-rw-r--r-- | doc/systemui.qdoc | 3 |
4 files changed, 43 insertions, 10 deletions
diff --git a/doc/index.qdoc b/doc/index.qdoc index 440b7e92..a6d70c83 100644 --- a/doc/index.qdoc +++ b/doc/index.qdoc @@ -56,6 +56,7 @@ For a high-level overview, see \l{The Qt Application Manager}{Introduction to th \li \l{Single-Process vs. Multi-Process Mode} \li \l{Migrating code from 5.11 to 5.12} \li \l{Migrating code from 5.13 to 5.14} + \li \l{Migrating code from 5.15 to 6.2} \endlist \section1 Tools diff --git a/doc/migration-guide-6.2.qdoc b/doc/migration-guide-6.2.qdoc new file mode 100644 index 00000000..67eb9e74 --- /dev/null +++ b/doc/migration-guide-6.2.qdoc @@ -0,0 +1,38 @@ +/**************************************************************************** +** +** Copyright (C) 2021 The Qt Company Ltd. +** Contact: https://www.qt.io/licensing/ +** +** This file is part of the documentation of the Qt Toolkit. +** +** $QT_BEGIN_LICENSE:FDL$ +** Commercial License Usage +** Licensees holding valid commercial Qt licenses may use this file in +** accordance with the commercial license agreement provided with the +** Software or, alternatively, in accordance with the terms contained in +** a written agreement between you and The Qt Company. For licensing terms +** and conditions see https://www.qt.io/terms-conditions. For further +** information use the contact form at https://www.qt.io/contact-us. +** +** GNU Free Documentation License Usage +** Alternatively, this file may be used under the terms of the GNU Free +** Documentation License version 1.3 as published by the Free Software +** Foundation and appearing in the file included in the packaging of +** this file. Please review the following information to ensure +** the GNU Free Documentation License version 1.3 requirements +** will be met: https://www.gnu.org/licenses/fdl-1.3.html. +** $QT_END_LICENSE$ +** +****************************************************************************/ + +/*! + +\page migration-guide-6.2.html +\title Migrating code from 5.15 to 6.2 + +Qt Application Manager 6.2 added no new APIs, but switched the build system from qmake to cmake and +finally removed the deprecated legacy \c ApplicationInterfaceExtension IPC mechanism. +A direct replacement for the old IPC had been added in 5.14 already in form of the new \l{Intents} +mechanism. + +*/ diff --git a/doc/singlevsmultiprocess.qdoc b/doc/singlevsmultiprocess.qdoc index da8b5fef..027fa58e 100644 --- a/doc/singlevsmultiprocess.qdoc +++ b/doc/singlevsmultiprocess.qdoc @@ -211,13 +211,8 @@ stopped. The QML engine doesn't allow you to unload parts of the object hierarch If your application needs to support both, single-process mode and multi-process mode, you must define a set of Inter-Process Communication (IPC) interfaces between the application and System UI, and always stick to them. Consider making these interfaces part of your review policy. While you -can use any IPC mechanism that suits your use case, the application manager includes an IPC -mechanism that fully abstracts the single-process vs. multi-process difference. This mechanism -also makes it easy to create new interfaces for QML developers. - -Be aware that the application manager's IPC is not suitable to interface your entire middleware. -Its sole purpose is to avoid a situation where there is a large number of one-off daemons that need -to be kept track of, involving various pieces of state information that need to be shared between -the System UI and some or all applications. +can use any IPC mechanism that suits your use case, the application manager includes an \l{Intents} +based IPC mechanism that fully abstracts the single-process vs. multi-process difference. This +mechanism also makes it easy to create new interfaces for QML developers. */ diff --git a/doc/systemui.qdoc b/doc/systemui.qdoc index 91da364b..f0698618 100644 --- a/doc/systemui.qdoc +++ b/doc/systemui.qdoc @@ -143,8 +143,7 @@ side. The application should do all the necessary clean-ups and then confirm tha terminates with \l{ApplicationInterface::acknowledgeQuit()}. You can implement other life-cycle management features that are tailored to the specific -requirements of IPC mechanisms like window properties, \l{ApplicationInterfaceExtension}, -or proprietary IPCs. +requirements of IPC mechanisms like window properties, \l{Intents}, or proprietary IPCs. For more information, see the \l{Desktop System UI Example}. |