Add the Qt 6 porting guide

With the known differences so far

Task-number: QTBUG-90848
Change-Id: I18bfc6e32b7dc6a5ff56b431f5a65ceea6c19a43
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Sona Kurazyan <sona.kurazyan@qt.io>

1 files changed, 54 insertions, 0 deletions

diff --git a/src/remoteobjects/doc/src/qt6-changes.qdoc b/src/remoteobjects/doc/src/qt6-changes.qdoc
new file mode 100644
index 0000000..8cd70f1
--- /dev/null
+++ b/src/remoteobjects/doc/src/qt6-changes.qdoc
@@ -0,0 +1,54 @@
+/****************************************************************************
+**
+** 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 remoteobjects-changes-qt6.html
+    \title Porting to Qt 6 - Qt Remote Objects
+    \ingroup porting-guides-5-to-6
+    \brief Migrate Qt Remote Objects to Qt 6.
+
+    Qt 6 is a result of the conscious effort to make the framework more
+    efficient and easy to use.
+
+    We try to maintain binary and source compatibility for all the public
+    APIs in each release. But some changes were inevitable in an effort to
+    make Qt a better framework.
+
+    In this topic we summarize those changes in Qt Remote Objects, and provide
+    guidance to handle them.
+
+    \section1 API changes
+
+    \section2 Functions taking const-ref QString changing to QStringView
+
+    QRemoteObjectHostBase::proxy, QRemoteObjectHostBase::reverseProxy and
+    QRemoteObjectNode::instances now accept a QStringView instead
+    of \c{const QString &}. The largest difference caused by this is that it
+    no longer accepts implicit conversion from string literals
+    (i.e. \c{node.instances("abc");}). Instead, you could use a UTF-16
+    string literal (\c{node.instances(u"abc")}).
+*/