Closed shawngraham closed 6 years ago
As the person chiefly responsible for the JavaScript used, I suppose that I should probably tackle this.
Yes - here's the original thread - https://twinery.org/forum/discussion/2789/geolocation-as-trigger . Saying 'I worked out' is pretty not the case, isn't it. 'I asked a question' is a far more truthful and accurate representation.... thank you.
It wasn't my intention to castigate you for saying you "worked it out". You put in plenty of your own effort and your write up is entirely yours. I was merely saying that as the chief JavaScript monkey of your endeavor—and only that, don't sell your own work short—that I should probably be the one to tackle doing the geolocation examples for the cookbook. My apologies for any confusion about that.
Even that is kind of presumptuous of me. I should have said that, as someone who's written geolocation code before, I'd be willing to tackle the examples for it—rather than saying that I should do so, as if no one else could.
Oh no, I understand! All is good! It was more me slapping my forehead and thinking, darn I didn't really give credit where it is due. I really appreciate you doing all of this.
I considered this for the Version 1 milestone, but think this is one of a number of good examples that should be part of Version 2 and the move to more complex projects. As this has the potential to pull from a number of different and existing examples, I'm hopeful this can serve as a cross-referenced entry for people interested in this higher-concept example to learn about the techniques underlining what and how it does things.
@shawngraham I added you as a contributor to the Cookbook since I based the new "Geolocation" set of examples on ideas on your code. The examples have also been change away from solely supporting SugarCube and can now be safety inserted in any project.
I worked out a way to use geolocation to trigger passages; I'm not much good, so it'd be nice if someone could make it all more elegant. My write-up is here