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
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
Hello, this feature request is inspired by tobrun whose efforts are going towards the flutter mapbox gl plugin, however he made an issue there flutter-mapbox-gl/maps#140 regarding exposing the native functionality interface and using dart:ffi directly jumping straight from Dart to C++ rather than Dart -> Android/IOS -> C++.
Are there any plans for this interface to be exposed, it would be of huge use for many people that want to go to the Dart/Flutter way, which is certainly amazing!
Much thanks!
The text was updated successfully, but these errors were encountered:
I suppose my meaning for posting is really bringing awareness that it's mature enough for them to document how you'd do this sort of thing, so the Dart team is clearly encouraging it.
What is the status here ? There is also an FFI generator that can be used to create the bridge, so it could do the heavy lifting.
As far as I understand this would allow the flutter wrapper to be thinner, which would bring confidence in using a public wrapper or even our own. For the time being we are moving to google maps.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, this feature request is inspired by tobrun whose efforts are going towards the flutter mapbox gl plugin, however he made an issue there flutter-mapbox-gl/maps#140 regarding exposing the native functionality interface and using dart:ffi directly jumping straight from Dart to C++ rather than Dart -> Android/IOS -> C++.
Are there any plans for this interface to be exposed, it would be of huge use for many people that want to go to the Dart/Flutter way, which is certainly amazing!
Much thanks!
The text was updated successfully, but these errors were encountered: