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
Jasonette is extremely interesting, thank you for the work so far, however I could not find any reference to using the devices' GPS, nor the examples make use of it. If Jasonette can't use GPS, please make it explicit somewhere in the documentation. Geofencing in particular is critical to an application I would like to use Jasonette to build. Thanks.
Giacecco
The text was updated successfully, but these errors were encountered:
If you are looking for something more sophisticated or custom, you can always write an extension, it's very easy to write one.
Please let me know if this wasn't what you were looking for, thanks!
p.s.
as for geofencing, short answer is No it's not supported yet. Here's the long answer: We do plan on implementing some sort of geofencing in the future, but this is completely different in nature to existing actions, since it has to sit in the background and constantly running. It wouldn't be hard to write an extension to do this (which is why i encourage writing an extension if you're adventurous), but incorporating it into the core project means we will have to go with the policy for a while (not just for geofencing but for any kind of daemon type actions) and that's why we're still thinking about different ideas, and it's not built into the framework yet. Check out some discussion threads on background actions: Jasonette/JASONETTE-iOS#57Jasonette/JASONETTE-iOS#63
Jasonette is extremely interesting, thank you for the work so far, however I could not find any reference to using the devices' GPS, nor the examples make use of it. If Jasonette can't use GPS, please make it explicit somewhere in the documentation. Geofencing in particular is critical to an application I would like to use Jasonette to build. Thanks.
Giacecco
The text was updated successfully, but these errors were encountered: