You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! Thank you very much for the AnyMaps library. I am working on implementing it into my EVMap project (https://github.com/johan12345/EVMap).
In the process have done some improvements to AnyMaps in my fork, as seen in the list below.
Is this project still maintained? Would you be open to PRs for some or all of these changes?
If yes, how should we handle this - one small PR for each of the changes? In that case it may be necessary to have the PRs built on top of each other as not all changes are completely separable from each other. Or I can make one large PR with the features you would like to have.
Major changes
Add a MapFragment class (ev-map@830989e, ev-map@e172821), which handles lifecycle callbacks automatically and allows the user to directly set which map implementation should be used. This alleviates the need to import a specific MapView and MapsConfiguration implementation and can automatically select the best backend based on the anymap-... libraries that are available (e.g. if you have one Build flavor for Google Maps and one for OSM, you don't need any flavor-specific code to handle the creation of the map).
The text was updated successfully, but these errors were encountered:
johan12345
changed the title
Various changes on my fork, which would you like to include?
Various changes on my fork, which you might like to include?
Aug 8, 2020
Hi! Thank you very much for the AnyMaps library. I am working on implementing it into my EVMap project (https://github.com/johan12345/EVMap).
In the process have done some improvements to AnyMaps in my fork, as seen in the list below.
Is this project still maintained? Would you be open to PRs for some or all of these changes?
If yes, how should we handle this - one small PR for each of the changes? In that case it may be necessary to have the PRs built on top of each other as not all changes are completely separable from each other. Or I can make one large PR with the features you would like to have.
Major changes
MapFragment
class (ev-map@830989e, ev-map@e172821), which handles lifecycle callbacks automatically and allows the user to directly set which map implementation should be used. This alleviates the need to import a specificMapView
andMapsConfiguration
implementation and can automatically select the best backend based on theanymap-...
libraries that are available (e.g. if you have one Build flavor for Google Maps and one for OSM, you don't need any flavor-specific code to handle the creation of the map).anymaps-mapbox
module (ev-map@61c95e6, ev-map@ebc4582)Minor changes (relevant for all AnyMaps backends)
OnCameraChangeListener
withOnCameraIdleListener
(ev-map@1e04d7a, ev-map@7dc99ec) for consistency with current Google Maps APIsLatLngBounds.contains
(ev-map@9f3041e)Marker.setAnchor
for all backends (ev-map@75f7048)Minor changes (OSM)
Minor changes (Google Maps)
mapsv3
branch, I upgraded the Google Maps SDK vom V2 to the current V3.1 Beta version.The text was updated successfully, but these errors were encountered: