We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maplibre Compose Playground uses the MapLibre composable sourced from Ramani Maps.
MapLibre
In response to this Rallista/maplibre-compose-playground#59, it seems like a good start to evaluate the standard Jetpack Compose method for wrapping an Android View (see: https://developer.android.com/develop/ui/compose/migrate/interoperability-apis/views-in-compose).
We should closely reference https://googlemaps.github.io/android-maps-compose/maps-compose/com.google.maps.android.compose/-google-map.html to try to understand the best practices for a composable map view init.
Expectations are this view will end up being quite complicated, but it's worth investigating.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Maplibre Compose Playground uses the
MapLibre
composable sourced from Ramani Maps.In response to this Rallista/maplibre-compose-playground#59, it seems like a good start to evaluate the standard Jetpack Compose method for wrapping an Android View (see: https://developer.android.com/develop/ui/compose/migrate/interoperability-apis/views-in-compose).
We should closely reference https://googlemaps.github.io/android-maps-compose/maps-compose/com.google.maps.android.compose/-google-map.html to try to understand the best practices for a composable map view init.
Expectations are this view will end up being quite complicated, but it's worth investigating.
The text was updated successfully, but these errors were encountered: