issue 119 fit feature added back to angular-google-maps
AsyncProccessor bug caught by firefox. The setTimeout needs a function reference passed to it, not a function call. Chrome does not catch this. The AsyncProcessor now has adone callback.
asyncProcessor needs to call doneCallBack() when there are no array elements or an undefined array.
ie8,9 actually working clustering does not.. atleast well. Fixed AsyncProcessor bugs in WindowsParentModel
Example Fixes
- Clear MArkers button is now ClearMap and moved to the top right
- fixed improper html within the table element which was causing IE
  errors
Numerous bug fixes
- patched MarkerWithLabel 1.0.9
      - bug with onRemove with calling labelDiv_.parentNode and
        eventDiv_.parentNode as null
- polygon and LatLngSync fixes with not checking values fully for
  nulls
finishing polygon and LatLngArraySync null checks
evalModelHandle specs added to MarkerChildModel
finally got a jasmineServer endpoint working for visual.
more evalHandle specs for MarkerChildModel
more evalHandle specs for MarkerChildModel
maybeSetScopeValue specs started, found a bug where the function needs to use => not -> to reference @myScope.
window-child-model.spec.coffee almost .. started
WindowChildSpec working
more specs, ngGMapModule and base-object
trafficLayer directive changed to a generic layerDirective. This can load any layer in google maps along with additional gmap services.
pushed layer code to a LayerParentModel to make it ng-repeatable as well as easier to test
code coverage working.
lowering function threshold to 75%. Therefore our goal of specs will be 75% across the board.