Hey, as long as it works...
Mr_Waffle wrote:I made your change to the warranty detection.
Great, should be future proof now.
By the way, Bioshox wanted us to make a pull request on the official repo, but I think we should first finish a few things before doing that
I have no problem with that but not sure he will want to go the way I (and I believe you agree with it since I laid it out in a previous post) have planned.
Last I heard, about 2 months ago he was doing a lot of changes to the current code and what I'm planning (when it's done) is basically throw away all his code and rewrite raspcontrol using a decent framework and a module based display template.
But anyway, as soon as I update my version with your changes I can do a pull to his repo (or you can do it, doesn't matter).
Since I am adding a version update check at startup that pulls the latest info from the github.com repo directly, what will most likely happen is that his version will be the "stable" or "legacy" release and mine (or yours) will be the "nightly" or "cutting edge" and people can update to whichever they want.
Mr_Waffle wrote:One thing I want to know is how the whole revision numbering works...
Sorry, didn't understand what you mean. what revision numbering? github's ?
Or the fact that raspcontrol should have a release and build number by now?
Again, that will be solved with the github update check.
BTW, next update on my part is enumerating all the hardware connected to the Pi, too bad that some of the hardware lies when asked on how much power it uses (ex: I get a return value for my keyboard of a maximum of 100mA but one 2.5" USB HDD that I have says 0mA) otherwise I could calculate the total minimum power needed for the Pi's PSU. This is part of my conversion to a PHP class.