Fix doc snippets paths and parsing errors

qtqml.qdocconf and qtquick.qdocconf now refer to the correct
snippets and source directories.

Snippet paths in .qdoc and .cpp files have been updated to refer to
the new shortened path references, e.g. \snippet qml/file.cpp instead of
\snippet doc/src/snippets/qml/file.cpp.

This also deletes snippets from src/qml/doc/snippets that belonged under
src/quick/doc/snippets (and were already duplicated there anyway) and
restores some snippet files that shouldn't have been deleted.

Also fixes some inline snippets to use \code .. \endcode instead of
\qml .. \endqml as they contained javascript or partial QML
snippets that were causing parsing errors from qdoc.

There are still snippet errors arising from qmlintro.qdoc as the
qmlintro snippets directory that it refers to cannot be located.

There are also two references to a removed snippet identifier in
examples/qml/cppextensions/plugins/plugin.cpp that need to be fixed
in conjunction with the related docs in a later commit as the relevant
code has changed and the docs are now invalid.

Task-number: QTBUG-25721

Change-Id: I50c665245a74c140470c58a32546591d187dfe4b
Reviewed-by: Chris Adams <christopher.adams@nokia.com>

1 files changed, 8 insertions, 8 deletions

diff --git a/src/quick/items/qquickitemviewtransition.cpp b/src/quick/items/qquickitemviewtransition.cpp
index aec4de43b6..d51d79230a 100644
--- a/src/quick/items/qquickitemviewtransition.cpp
+++ b/src/quick/items/qquickitemviewtransition.cpp
@@ -642,7 +642,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     Here is a basic example of the use of view transitions. The view below specifies transitions for
     the \c add and \c displaced properties, which will be run when items are added to the view:
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-basic.qml 0
+    \snippet qml/viewtransitions/viewtransitions-basic.qml 0
 
     When the space key is pressed, adding an item to the model, the new item will fade in and
     increase in scale over 400 milliseconds as it is added to the view. Also, any item that is
@@ -728,7 +728,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     each displaced item based on the difference between its index (provided by ViewTransition.index)
     and the first removed index (provided by ViewTransition.targetIndexes):
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-delayedbyindex.qml 0
+    \snippet qml/viewtransitions/viewtransitions-delayedbyindex.qml 0
 
     Each displaced item delays its animation by an additional 100 milliseconds, producing a subtle
     ripple-type effect when items are displaced by the add, like this:
@@ -748,7 +748,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     animate to an intermediate position relative to its starting point for the transition, before
     animating to its final position in the view:
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-intermediatemove.qml 0
+    \snippet qml/viewtransitions/viewtransitions-intermediatemove.qml 0
 
     Now, a displaced item will first move to a position of (20, 50) relative to its starting
     position, and then to its final, correct position in the view:
@@ -764,7 +764,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     a curved path. For example, the \c add transition in the previous example could be augmented with
     a PathAnimation as follows: to animate newly added items along a path:
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-pathanim.qml 0
+    \snippet qml/viewtransitions/viewtransitions-pathanim.qml 0
 
     This animates newly added items along a path. Notice that each path is specified relative to
     each item's final destination point, so that items inserted at different indexes start their
@@ -787,7 +787,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     properties, this interruption may cause unwanted side effects. Consider the first example on this
     page, repeated below for convenience:
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-basic.qml 0
+    \snippet qml/viewtransitions/viewtransitions-basic.qml 0
 
     If multiple items are added in rapid succession, without waiting for a previous transition
     to finish, this is the result:
@@ -804,7 +804,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     set to the end values specified in the \c add transition, effectively resetting these values
     whenever an item is displaced. In this case, it means setting the item opacity and scale to 1.0:
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-interruptedgood.qml 0
+    \snippet qml/viewtransitions/viewtransitions-interruptedgood.qml 0
 
     Now, when an item's \c add transition is interrupted, its opacity and scale are animated to 1.0
     upon displacement, avoiding the erroneous visual effects from before:
@@ -829,7 +829,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     attached property, as it may not refer to the expected values at the time that the ScriptAction
     is actually invoked. Consider the following example:
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-scriptactionbad.qml 0
+    \snippet qml/viewtransitions/viewtransitions-scriptactionbad.qml 0
 
     When the space key is pressed, three items are moved from index 5 to index 1. For each moved
     item, the \c moveTransition sequence presumably animates the item's color to "yellow", then
@@ -847,7 +847,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent)
     In this instance, to avoid this issue, the view could set the property using a PropertyAction
     instead:
 
-    \snippet doc/snippets/qml/viewtransitions/viewtransitions-scriptactiongood.qml 0
+    \snippet qml/viewtransitions/viewtransitions-scriptactiongood.qml 0
 
     When the transition is initialized, the PropertyAction \c target will be set to the respective
     ViewTransition.item for the transition and will later run with the correct item target as