Flutter-geolocator: Is there a reason for witch the plugin is written using Swift?

Created on 5 Feb 2019  ·  4Comments  ·  Source: Baseflow/flutter-geolocator

Most helpful comment

Perfect, let’s start there.

On Wed, 13 Feb 2019 at 16:34, Maurits van Beusekom notifications@github.com
wrote:

Yes we definitely do, if you would also be willing to take the
permission_handler
https://github.com/BaseflowIT/flutter-permission-handler into account.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BaseflowIT/flutter-geolocator/issues/178#issuecomment-463221301,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI2nVhnFAhS7E8rktDysjOguYkPnuIbRks5vNCKAgaJpZM4ajh2m
.

All 4 comments

The main reason is that we don't (want to) understand Objective-C and because it is the recommended language by Apple (quoted from here):

Swift is a successor to both the C and Objective-C languages. It includes low-level primitives such as types, flow control, and operators. It also provides object-oriented features such as classes, protocols, and generics, giving Cocoa and Cocoa Touch developers the performance and power they demand.

Unfortunately when we started developing we didn't realize (like so many of us) that using Swift and Flutter would have such a big penalty in the final app size. Now we are so far in that we don't have the knowledge or time to translate the plugins (see also permission_handler) back to Objective-C.

Are welcoming pull requests on this?

On Wed, 13 Feb 2019 at 16:30, Maurits van Beusekom notifications@github.com
wrote:

Closed #178 https://github.com/BaseflowIT/flutter-geolocator/issues/178.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BaseflowIT/flutter-geolocator/issues/178#event-2136871060,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI2nVmJ4ZfhtQBCYeybOjVh6QiJJ02Iyks5vNCFwgaJpZM4ajh2m
.

Yes we definitely do, if you would also be willing to take the permission_handler into account.

Perfect, let’s start there.

On Wed, 13 Feb 2019 at 16:34, Maurits van Beusekom notifications@github.com
wrote:

Yes we definitely do, if you would also be willing to take the
permission_handler
https://github.com/BaseflowIT/flutter-permission-handler into account.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/BaseflowIT/flutter-geolocator/issues/178#issuecomment-463221301,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AI2nVhnFAhS7E8rktDysjOguYkPnuIbRks5vNCKAgaJpZM4ajh2m
.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

deisold picture deisold  ·  3Comments

joesnarky picture joesnarky  ·  3Comments

dark-chocolate picture dark-chocolate  ·  3Comments

devalp-pro picture devalp-pro  ·  3Comments

CNogueira92 picture CNogueira92  ·  3Comments