Add hasFeature() to MXN Core

[vicchi]

Not all map providers support all the MXN core features. It's currently left to the caller to look at a given provider's implementation to determine what is and what isn't supported.

We should add a hasFeature() call to the MXN core to allow the caller to determine whether a feature is supported or not at run-time.

For example, OpenLayers only supports the OSM map style out of the box. So a call to mxn.hasFeature(mxn.Mapstraction.PHYSICAL) when using OpenLayers would return false, whereas the same call when using Google v3 would return true.

[gilesc50]

What an excellent idea – this would help with the removeAllMarkers where I want to allow each provided to offer an optimised implementation, but fall back to the one in the core if it isn’t provided.

From: Gary Gale [mailto:notifications@github.com]
Sent: Thursday, November 29, 2012 2:57 PM
To: mapstraction/mxn
Subject: [mxn] Add hasFeature() to MXN Core (#182)

Not all map providers support all the MXN core features. It's currently left to the caller to look at a given provider's implementation to determine what is and what isn't supported.

We should add a hasFeature() call to the MXN core to allow the caller to determine whether a feature is supported or not at run-time.

For example, OpenLayers only supports the OSM map style out of the box. So a call to mxn.hasFeature(mxn.Mapstraction.PHYSICAL) when using OpenLayers would return false, whereas the same call when using Google v3 would return true.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/182.