Remove parameterization functionality

The abstraction of plugin-specific parameters makes little sense if
we don't want to provide a cross-backend API. So remove this for
now.

If in the future we want to attach meta-data or backend-specific
properties to values or element types, then we might be able to use
existing QVariantMap type properties (like QGeoRouteRequest's
extraParameters, via QDeclarativeGeoRouteQuery::extraParameters),
or register backend specific QML types that applications can opt in
to use.

This requires a bit of research and experimenting based on specific
use cases. If we can't come up with anything better, then bringing
back a, perhaps simplified, version of the infrastructure removed
here will still be an option.

Change-Id: If590a35f2ffb80b0c918d866e88913a9caf75d2b
Reviewed-by: Alex Blasche <alexander.blasche@qt.io>

1 files changed, 0 insertions, 5 deletions

diff --git a/src/location/maps/qgeomap_p.h b/src/location/maps/qgeomap_p.h
index e51c4900..0a7b76b1 100644
--- a/src/location/maps/qgeomap_p.h
+++ b/src/location/maps/qgeomap_p.h
@@ -68,7 +68,6 @@ class QGeoShape;
 class QGeoRectangle;
 class QSGNode;
 class QQuickWindow;
-class QGeoMapParameter;
 class QDeclarativeGeoMapItemBase;
 class QDeclarativeGeoMap;
 
@@ -133,10 +132,6 @@ public:
     virtual void prefetchData();
     virtual void clearData();
 
-    void addParameter(QGeoMapParameter *param);
-    void removeParameter(QGeoMapParameter *param);
-    void clearParameters();
-
     ItemTypes supportedMapItemTypes() const;
 
     void addMapItem(QDeclarativeGeoMapItemBase *item);