1 files changed, 0 insertions, 88 deletions
diff --git a/doc/qtcreator/src/qtquick/qtquick-properties.qdoc b/doc/qtcreator/src/qtquick/qtquick-properties.qdoc
index b356ac9633..be23396b5b 100644
--- a/doc/qtcreator/src/qtquick/qtquick-properties.qdoc
+++ b/doc/qtcreator/src/qtquick/qtquick-properties.qdoc
@@ -203,94 +203,6 @@
     You can add other languages later by editing the project file.
     \endif
 
-    \section1 Loading Placeholder Data
-
-    The Design mode supports views, models, and delegates, so that when you add
-    a Grid View, List View, or Path View item, the ListModel and the delegate
-    item are added automatically.
-
-    However, the missing context of the application presents a challenge.
-    Specific models defined in C++ are the most obvious case. Often,
-    the context is missing simple properties, which are either defined in C++,
-    or in other QML files. A typical example is an item that uses the
-    properties of its parent, such as \c parent.width.
-
-    \section2 Using Dummy Models
-
-    If you open a file in the Design mode that references a C++ model, you see
-    nothing on
-    the canvas. If the data in the model is fetched from the internet, you have
-    no control over it. To get reliable data, \e {dummy data} was introduced.
-
-    For example, the following code snippet describes the file example.qml that
-    contains a ListView that in turn specifies a C++ model:
-
-    \qml
-        ListView {
-            model: dataModel
-            delegate: ContactDelegate {
-                name: name
-            }
-        }
-    \endqml
-
-    Create a directory named \e dummydata in the root directory of the project,
-    so that it is not deployed to the device. In the \c dummydata directory,
-    create a QML file that has the same name as the value of \c model:
-
-    \code
-        qml/exampleapp/example.qml
-        dummydata/dataModel.qml
-    \endcode
-
-    Then create the dataModel.qml file that contains the dummy data:
-
-    \qml
-        import QtQuick 2.0
-
-        ListModel {
-             ListElement {
-                 name: "Ariane"
-             }
-             ListElement {
-                 name: "Bella"
-             }
-             ListElement {
-                 name: "Corinna"
-             }
-        }
-    \endqml
-
-    \section2 Creating Dummy Context
-
-    The following example presents a common pattern in QML:
-
-    \qml
-        Item {
-            width: parent.width
-            height: parent.height
-        }
-    \endqml
-
-    This works nicely for applications but the Design mode displays a zero-sized
-    item. A parent for the opened file does not exist, because the context is
-    missing. To get around the missing context, the idea of a \e {dummy
-    context} is introduced. If you place a file with the same name as the
-    application (here, example.qml) in the \c {dummydata/context} directory,
-    you can fake a parent context:
-
-    \qml
-        import QtQuick 2.0
-        import QmlDesigner 1.0
-
-        DummyContextObject {
-            parent: Item {
-                width: 640
-                height: 300
-            }
-        }
-    \endqml
-
     \section1 Building Transformations on Items
 
     The \uicontrol Advanced tab allows you to configure advanced