xamarin.android - How to use Google Maps v2 API with MVVMCross -
i'm trying google maps v2 api working mvvmcross v2 (vnext) , have run problems.
the example have using google maps mvvmcross has view inherits mvxbindingmapactivityview. trouble uses mapview google maps v1 api, api deprecated , google no longer issuing license keys.
i have code adapted xamarin google maps v2 example works great:
https://github.com/xamarin/monodroid-samples/tree/master/mapsandlocationdemo_v2
but don't understand how working mvvmcross v2. uses fragments, , i'm not sure whether supported current version of mvvmcross?
i can google maps v2 activity working fine outside of mvvmcross framework firing off intent mvvmcross view, , option, wondering if there support inside mvvmcross google maps v2 or whether hackery involved more trouble it's worth.
thanks!
matthew
the maps code in v1 (master
) , v2 (vnext
) mvvmcross both relied on google maps v1 api - no longer option new apps.
meanwhile, master
, vnext
firmly rooted in android v1 , v2 - don't contain fragment support.
so analysis of situation right.
some options developing google maps v2 are:
add non-mvvm activity within app page/tab needs new style map.
try implement
exfragmentactivity
- or without data-binding support.to first need inherit android's
fragmentactivity
class , need provide additional methods , properties. more on in insert monogame view inside mvvmcross monodroid activity.there's lot of cut , paste in doing this, think should trivial
exfragmentactivity
working non data-binding level.to go further - data-binding working - may find need adjust binding/inflation code - code around
layoutinflater
. way fragmentmanager hooks parent fragmentactivity may need adjusted. sorry don't have more details on how - thinkhackery
, experimentation might involved.v3 have full fragment support - switching v3 (when ships) , using fragments 1 option future support. however, changes older versions v3 quite large - doing may not option right - depends in project.
Comments
Post a Comment