What's new in 2.1
The currently available ArcGIS API for Windows Phone version 2.1 is the initial release of the API. As such, all of it is new! However, for those developers working with our Beta 1, Beta 2, and release candidate (RC) versions, this topic provides information on the changes made through those versions.
This topic includes the changes from Beta 1 to Beta 2, as well as the changes between Beta 2 and the currently available release RC version of the API.
What's new at RC from Beta 2
The following changes were introduced between the Beta 2 and Release Candidate versions of the ArcGIS API for Windows Phone.
New Toolkit assembly
With the Release Candidate a new assembly, ESRI.ArcGIS.Client.Toolkit.dll, has been added to provide some additional controls that will make developing mapping application for Windows Phone easier. It contains two namespaces: ESRI.ArcGIS.Client.Toolkit and ESRI.ArcGIS.Client.Toolkit.Primitives. Some of the key controls provided include an InfoWindow, a ChildPage, and a Legend.
InfoWindow control
The Toolkit (ESRI.ArcGIS.Client.Toolkit) library includes an InfoWindow control which is basically a window that contains content with a tail that points to a location or feature of interest. Since the ArcGIS API for Windows Phone doesn't have built-in map tips on layers, this control can be used to create map tips. See (Using the InfoWindow to create map tips. The control can also be used to provide information on a map at any time, usually in response to a user action, such as a touch event. An InfoWindow can also remain visible and be anchored to a position relative to the map.
 |
ChildPage control
The Toolkit Primitives (ESRI.ArcGIS.Client.Toolkit assemly, in the ESRI.ArcGIS.Client.Toolkit.Primitives namespace) include a ChildPage control which is basically a window that contains content and slides in and out of view. One common usage scenario is to pair it with an InfoWindow to provide additional information. See (Using the InfoWindow to create map tips for a detailed example using this control.
Legend control
The Toolkit (ESRI.ArcGIS.Client.Toolkit) library includes a Legend control to display layer and symbol content in a map. See Adding a legend. The Legend control is templatable, thus other controls can be added to layer items, such as radio buttons, check boxes, and sliders to create an interactive table of contents). Symbol swatches for feature layers and ArcGIS dynamic map service layers can be retrieved and displayed within the legend. ArcGIS Server 10 SP1 map services provide a legend resource to return legend details. Map services prior to version 10 SP1 use a legend service on ArcGIS.com to generate swatches, but the original map service must be available publicly.
 |
New Edit and Draw magnifier
The Editor provides for an interactive editing experience using gestures, and Draw surfaces simplify drawing on the map. When moving a point or a vertice of a line or polygon using touch (e.g. dragging a vertice on the map) either when editing or drawing, a magnifier window will now be displayed to assist in the final placement of the point.
 |
What's new at Beta 2 from Beta 1
The following changes were introduced between the Beta 1 and Beta 2 versions of the ArcGIS API for Windows Phone:
- Support for WebMap documents: A new library, ESRI.ArcGIS.Client.WebMap.dll, was added to provide support for reading, processing, and utilizing WebMap documents created and hosted on ArcGIS.com. It uses the arcgis.com web map specification version 1.1.
- New KML layer: The Toolkit DataSources library (ESRI.ArcGIS.Client.Toolkit.DataSources.dll) includes a new KmlLayer to support KML data sources. The initial implementation targets a subset of the KML specification supported by Google Maps.
- Version and Capabilities properties added to ArcGIS service layer classes: These new properties allow developers to discover the version or capabilities of a service at runtime.
- ArcGISImageServiceLayer supports mime output for map images.
- ArcGISDynamicMapServiceLayer and ArcGISImageServiceLayer support large requests that require HTTP POST.