/****************************************************************************
**
** Copyright (C) 2022 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 qtlocation-changes-qt6.html
    \title Changes to Qt Location
    \ingroup changes-qt-5-to-6
    \brief Migrate Qt Location 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 Location, and provide
    guidance to handle them.

    \section1 Breaking public API changes

    \section2 Maps

    \list
        \li The \c {MapRectangle::backend}, \c {MapCircle::backend},
            \c {MapPolyline::backend}, and \c {MapPolygon::backend} properties
            have been removed.
        \li The former Routing-related QML element types \c Route, \c RouteSegment,
            and \c RouteManeuver are now value types \l route, \l routeSegment, and
            \l routeManeuver. They can no longer be instantiated as items in QML,
            and their properties can not be bound to.
        \li The former Mapping-related QML element types \c MapType and
            \c CameraCapabilities are now value types \l mapType and
            \l cameraCapabilities. They can no longer be instantiated as items in
            QML, and their properties can not be bound to.
        \li The \c QGeoRouteLeg class and the QML equivalent, \c RouteLeg, have
            been merged into \l QGeoRoute (and the \l route type). A route can
            be an aggregate of several routes.
    \endlist

    \section2 Places

    \list
        \li The \c {QPlaceImage}, {QPlaceEditorial}, and {QPlaceReview} classes
            have been folded into \l QPlaceContent.
        \li The \l QPlaceContent API has been changed to give access to a list of
            QVariant values.
    \endlist

    \list
        \li The former QML element types \c PlaceUser, \c PlaceRatings,
            \c PlaceAttribute, \c PlaceIcon, \c PlaceSupplier, and
            \c PlaceContactDetail are now value types \l user,
            \l ratings, \l placeAttribute, \l icon,
            \l supplier, and \l contactDetail.
            They can no longer be instantiated as items from QML, and
            their properties can not be bound to.
    \endlist

    \section2 Experimental APIs

    Functionality that had "labs" status has been removed. This includes the
    experimental framework for turn-by-turn navigation, as well as the
    MapObjects abstraction.

    \section2 Backend Provider API

    The backend provider API is no longer subject to binary and source
    compatibility guarantees.

    \section1 Other API changes

    This section contains API improvements that do not break source
    compatibility. However they might have an impact on the application logic,
    so it is still useful to know about them.
*/