Getting sources from Github

Sparki
#1

hi,

Can anyone post instructions on how to get latest sources from Github and integrate them into the Sparkduino environment?

I noticed that there where a bunch of commits during the last couple of weeks and I would really like to integrate them into my version.

btw - how do I check what is my exact version?

also - is there a mailing list to get notifications when new bundles of the code are being made publicly available?

thanks!

bitboy.

#2

[quote=“bitboy”]Can anyone post instructions on how to get latest sources from Github and integrate them into the Sparkduino environment?..

btw - how do I check what is my exact version?

also - is there a mailing list to get notifications when new bundles of the code are being made publicly available?
[/quote]
If you used the ArcBotics Installer for the initial install, I would suggest that you wait for the new version of the Installer from ArcBotics (due later this week?) which should include all the software revisions to-date.

If you did a manual install using the zip file, you can use the Github source to download all the current software components as a new zip file. The Arduino library files that you want to look for are Sparki.cpp (function library) and Sparki.h (function attributes). You can also replace individual updated sketches (".ino" files) from Github.

None of these updated files show a version as such, which is why I use the file date/time as a reference (see my signature below).

Lastly, there is a notification function in Github to monitor repositories that you are “watching”, but this does not appear to give timely results. I use a free Web service (followthatpage.com) to watch for changes to the Sparki pages. When you watch a Github page, if you use the option to ignore numeric changes, you will get an email when software components are changed.

#3

@roboalchemist: Is it possible for you to start writing a rev number into the comments on the top of each sketch or other file as you update please? Thanks.

#4

thanks guys!

#5

Any thoughts on this yet?

Would be a lot better in my opinion if the date &/or rev # was at the top of sketches, .cpp & .h files as you upload to the GitHub.

Thanks.

#6

Sorry, git doesn’t really work like ‘rev numbers’. I will post in the file the last time it was updated, though.

#7

Perfect. Sorry, that’s what I meant. Just a text line at the top of the code with date and rev. Thanks a lot.