Useful code for sharing

Travis' comment in my GPS functionality thread got me thinking about a Git repo of code snippets and samples again and I'm wondering if anyone else is interested. If I set up a git repo on Github, I was thinking that a few of us here could be what Github calls a "Collaborator" with permission to do whatever on the repo and anyone else that wants to contribute would fork the repo and make a pull request. I had originally contributed some stuff to Garmin's repo but it looks like they are keeping that as an "official" repo for use with examples in books and blog posts.

If there is indeed interest, does anyone have thoughts on how it should be organized? The fully working samples obviously would go in their own directories but I'm not sure how best to organize the snippet stuff since it may or may not span multiple files.

If you're interest, please post any thoughts on how to organize this along with your github name and I'll set it up today.

UPDATE: The repo has been created here: https://github.com/douglasr/connectiq-samples

Cheers,
Douglas
  • Thanks for setting this up dbrobert. We have an "official" and sadly under-utilized repo here https://github.com/garmin/connectiq-apps, but there's a certain kind of freedom that's afforded developers when it's not a Garmin-moderated resource. If I'm able to do some of the things I'd like with our developer site later this year, I'll see about linking to this as our "official-unofficial" repo. :)


    Yes, I had a pull request in that repo that lingered long enough that I decided "unofficial" was the way to go. But thanks for the reminder; I've added a link to the official repo in the README in my unofficial repo.

    Cheers,
    Douglas
  • I finally got around to extracting my TextPicker code from my amazing METAR/TAF widget and then adding the library to the github repo. If you want a bit more control over any text input from the user, this might be a good start. It's under the MIT license so you can basically do what you want with it, though updates back to the repo are appreciated, especially since this is some of the first MonkeyC I ever wrote so it may not be using all (or any) best practices. ;)



    Enjoy!

    Cheers,
    Douglas