Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi George.
This PR adds possibility to use marker-animate-unobtrusive to perform marker animations. The process is explained here.
It includes non-functional and functional changes.
Non-functional changes are:
Functional changes are calls to ghostPosition instead of position everywhere.
What marker-animate-unobtrusive provide is MarkerWithGhost class that one can use instead of google.maps.Marker. It makes marker animate between setPosition calls, and in addition it provides "ghost mode", in which marker moves without notifying its position changes to user code. You enter "ghost mode" by calling setGhostPosition, and position changes are traced with ghostposition_changed events. It makes spiderfying completely transparent to user code.
My knowledge of coffeescript is close to zero, so I hope you can fix changes I made in oms.coffee.
What I did not implement is, of course, feature detection. It should check for existence of setGhostPosition method on marker, and if not found, call plain setPosition, as usual. Same with ghostposition_changed event and ghostPosition field.
Hope you will find this functionality useful.