Changelog

What's new, doc?

Compatibility

$('#example').simplicityGoogleMapResults({
    markerCallback; $.simplicityGoogleMarker.resultsCallback
});

Improvements

Compatibility

<fieldset id="example">
  <input name="a">
  <input name="b">
  <input name="c">
  <button>Change</button>
</fieldset>
1 $('#example').simplicityInputs();
2 $('#example button').change(function () {
3   $('#example').change();
4 });

To maintain previous functionality, you’d change line 1 to read:

$('#example').simplicityInputs({
  handleChildChange: false
});

Improvements

Compatibility

Improvements

Improvements

Compatibility

Improvements

Compatibility

Improvements

Improvements

Improvements

Improvements

Compatibility

Improvements

Improvements

Compatibility

You will need to instantiate a different set of simplicity mapping widgets, configure them slightly differently, and update any jQuery event handlers related to the map events. The event names are slightly different due to the namespacing offered by jQuery’s _trigger() method. The semantics of some events were modified to better support the new feature set. The bottom line is that if you are using jQuery to bind to simplicity{vendor}map{event} events, you will need to adjust the names of the events to match the new widget names and double check that your event handler still works with the updated API.

We strongly suggest that you review the generated JavaScript documentation for full details, and that you explore the tutorial pages to see the new mapping widgets in action.

Here is a simple example of the simplicityGoogleMap widget being migrated from release 2.2 to release 2.3. Note that all the options are optional. Here’s an example just using the widget defaults.

Old:

$('#map').simplicityGoogleMap();

New:

$('#map')
  .simplicityGoogleMap()
  .simplicityGoogleMapBoundsCoordinator()
  .simplicityGoogleMapResults();

Here is an example with all the defaults shown.

Old:

$('#map')
  .simplicityGoogleMap({
     searchElement: 'body',
     latitudeField: 'latitude',
     longitudeField: 'longitude',
     fitOnResultSet: true,
     mapOptions: {},
     mapMoveEvents: 'idle'
  });

New:

$('#map')
  .simplicityGoogleMap({
       mapOptions: {}
  })
  .simplicityGoogleMapBoundsCoordinator({
       searchElement: 'body'
  })
  .simplicityGoogleMapResults({
       searchElement: 'body',
       latitudeField: 'latitude',
       longitudeField: 'longitude',
       updateBounds: true
  });

With the new smaller widgets, you can see that you can easily choose which behaviors and features to add to your simplicity map.

Note that the new widget simplicity{vendor}BoundsTracker will update the search based upon the maps current bounds. As a user pans and zooms, the search criteria are updated.

The simplicity{vendor}MapBoundsCoordinator widget allows the results and criteria mapping widgets to update the map bounds in a coordinated manner.

Here is an overview showing the mapping of the 2.2 event names to the 2.3 event names. We recommend that you refer to the JavaScript documentation or source code to fully understand the event contracts.

old new
simplicitygooglemapcreate simplicitygooglemapcreate
simplicitygooglemapmarker simplicitygooglemapresultsmarker
simplicitygooglemapbounds simplicitygooglemapboundcoordinatorcalculatebounds
simplicitygooglemapboundstrackerbounds
simplicitygooglemapboundsshapes simplicitygooglemapboundstrackerboundsshapes
simplicitygooglemapcriteriaplacemark

Improvements

Compatibility

Improvements

Compatibility

Improvements

Initial release.