Make Open Street Maps the default plugin used in Qt Location examples.

The Nokia plugin requires application authentication codes before it
can be used. The OSM plugin does not. Use the OSM plugin by default so
that the examples work out of the box.

Change-Id: I4c965dc35b0ae6b643ee14f64c0758fee2bb958d
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>

5 files changed, 6 insertions, 6 deletions

diff --git a/src/imports/location/qdeclarativegeoroutemodel.cpp b/src/imports/location/qdeclarativegeoroutemodel.cpp
index b47d3313..90d07f03 100644
--- a/src/imports/location/qdeclarativegeoroutemodel.cpp
+++ b/src/imports/location/qdeclarativegeoroutemodel.cpp
@@ -86,7 +86,7 @@ QT_BEGIN_NAMESPACE
     \code
     Plugin {
         id: aPlugin
-        name: "nokia"
+        name: "osm"
     }
 
     RouteQuery {
diff --git a/src/imports/location/qdeclarativegeoserviceprovider.cpp b/src/imports/location/qdeclarativegeoserviceprovider.cpp
index 8bdac880..082464ea 100644
--- a/src/imports/location/qdeclarativegeoserviceprovider.cpp
+++ b/src/imports/location/qdeclarativegeoserviceprovider.cpp
@@ -68,12 +68,12 @@ QT_BEGIN_NAMESPACE
     The following snippet shows a Plugin object being created with the
     \l required and \l preferred properties set. This Plugin will attach to the
     first plugin found plugin that supports both mapping and geocoding, and will
-    prefer plugins named "nokia" or "foo" to any others.
+    prefer plugins named "nokia" or "osm" to any others.
 
     \code
     Plugin {
         id: plugin
-        preferred: ["nokia", "foo"]
+        preferred: ["nokia", "osm"]
         required: Plugin.AnyMappingFeatures | Plugin.AnyGeocodingFeatures
     }
     \endcode
diff --git a/src/location/doc/snippets/declarative/places_loader.qml b/src/location/doc/snippets/declarative/places_loader.qml
index d14223fd..6eea0194 100644
--- a/src/location/doc/snippets/declarative/places_loader.qml
+++ b/src/location/doc/snippets/declarative/places_loader.qml
@@ -48,7 +48,7 @@ Rectangle {
 
     Plugin {
         id: myPlugin
-        name: "nokia"
+        name: "osm"
         //specify plugin parameters if necessary
         //PluginParameter {...}
         //PluginParameter {...}
diff --git a/src/location/doc/src/places.qdoc b/src/location/doc/src/places.qdoc
index 2a853a20..edbd20f4 100644
--- a/src/location/doc/src/places.qdoc
+++ b/src/location/doc/src/places.qdoc
@@ -42,7 +42,7 @@
     \section2 Plugin
     A \l Plugin is an abstraction for a backend. One \l Plugin might access places from a
     REST server while another may access places from a local database. The following
-    instantiates a \l Plugin object by providing a name of "nokia". The \l Plugin name
+    instantiates a \l Plugin object by providing a name of "osm". The \l Plugin name
     identifies which backend to choose from. Plugins may also be provided with a set of
     \l {PluginParameter} {parameters}, which essentially takes the form of a set of
     key-value pairs. The \l {PluginParameter} {parameters} that can be specified vary
diff --git a/src/location/doc/src/qtlocation-qml.qdoc b/src/location/doc/src/qtlocation-qml.qdoc
index a2ef8058..68b82d30 100644
--- a/src/location/doc/src/qtlocation-qml.qdoc
+++ b/src/location/doc/src/qtlocation-qml.qdoc
@@ -68,7 +68,7 @@ geocoding and routing information, which can be consumed by the application.
 There may be various GeoServices plugins for various tasks with some plugins
 providing more than one service. One QML \l Plugin must be created for each
 required GeoService plugin. Plugins are required for maps, routing and geocoding,
-however the default plugin handles all three of these services. A plugin may
+and places, however the default plugin handles all four of these services. A plugin may
 require online access or may support on-board maps and data.
 
 \note Plugins may not provide features such as paging or relevance hints.