-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
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
Flutter support #182
Comments
One of the many downsides of 3rd party map rendering frameworks is the ability to include platform views into the map. If we add support for adding native views as map elements, then we might be able to support flutter widgets as well because we should be able to render specific widgets into an android surface or texture view. I would love to get your feedback and thoughts on this @maxammann |
yes, absolutely. The differenciation between, SDK views (UIView, DOM element) is a tough topic. You definitely want to use SDK views where ever possible actually. But that comes with a high development cost, because you then need to develop the feature X times (web, android, iOS, desktop). But like you said: If we support flutter, then we might be able to render close-to-native views on top of the map easily. |
Shouldn't it be "easy" to avoid the dependency to flutter (or any other framework) in maplibre-rs? Afaik maplibre-rs needs a surface to paint to and this will be provided by the platform view in all cases, right? For a marker we can do the same thing. Give maplibre-rs a surface for a marker and additionally render the platform view in the marker surface as well? |
I think we need to concertize what we want to achieve. I'm a little bit lost on what we want to achieve. The maplibre could already provide callbacks which then trigger e.g. the movement of a native android.Button. |
🤔 Expected Behavior
😯 Current Behavior
💁 Possible Solution
🔦 Context
💻 Examples
The text was updated successfully, but these errors were encountered: