Piface rubygem 0.4
Closed this issue · 9 comments
I've updated the Piface ruby gem to v0.4.
It has a few changes that should help to make installation more simple. There shouldn't be any breaking changes, but you may have to call Piface.init(true).
Depending how you track input/output state, since the Piface.init method no longer resets the pins when requiring the piface library, if you use assumed starting states you may need to make minor changes. (Quickly looking at your code, it shouldn't be a problem since you read directly from your door opener)
https://github.com/blakejakopovic/piface/blob/master/CHANGELOG.md
https://github.com/blakejakopovic/piface
Let me know if you have any issues. Cheers, Blake
Blake,
Thanks for the heads up. I will take a look.
Elvis
On Apr 13, 2013, at 7:24, Blake Jakopovic notifications@github.com wrote:
I've updated the Piface ruby gem to v0.4.
It has a few changes that should help to make installation more simple. There shouldn't be any breaking changes, but you may have to call Piface.init(true).
Depending how you track input/output state, since the Piface.init method no longer resets the pins when requiring the piface library, if you use assumed starting states you may need to make minor changes. (Quickly looking at your code, it shouldn't be a problem since you read directly from your door opener)
https://github.com/blakejakopovic/piface/blob/master/CHANGELOG.md
https://github.com/blakejakopovic/pifaceLet me know if you have any issues. Cheers, Blake
—
Reply to this email directly or view it on GitHub.
Tested with Piface Ruby gem 0.4.0 and latest C libraries. No changes required.
Great. I forgot to mention that the gem should now automatically install the C library during gem install. So the steps involving downloading, and compiling the pfio C library aren't necessary anymore. I've had to work on a custom branch of the pfio library so that I can add non-breaking functionality going forward.
Blake. I noticed it took awhile longer to install, but didnt know why. I noticed there were some recent changes to the C libraries regarding IO numbering. How do you keep current with changes?
Elvis
On Apr 13, 2013, at 22:15, Blake Jakopovic notifications@github.com wrote:
Great. I forgot to mention that the gem should now automatically install the C library during gem install. So the steps involving downloading, and compiling the pfio C library aren't necessary anymore. I've had to work on a custom branch of the pfio library so that I can add non-breaking functionality going forward.
—
Reply to this email directly or view it on GitHub.
updated dependency and instructions to no longer require manual install of C piface libraries.
Yep. During gem install it will build the pfio libraries (included in the gem /etc/ path, so that they will be automatically installed.
Which changes did you see? The pfio library hasn't changed in 6 months. I have forked my own branch (locally), and am working on adding features like pullup control.
My focus with the library is to keep it as simple as possible. I want kids to be able to use it without having to learn a whole lot. So, my intention is to keep the inputs and outputs linked to 1-8 (and not use 0 as the first pin). I know the GPIO and wiringpi libraries starts from 0, however they are more tightly linked to GPIO pins - the Piface is different.
I agree, keep it as simple as possible. Starting from 1 matches the PF data sheet.
I saw this. thomasmacpherson/piface#8
Elvis
On Apr 14, 2013, at 12:34 AM, Blake Jakopovic notifications@github.com wrote:
Yep. During gem install it will build the pfio libraries (included in the gem /etc/ path, so that they will be automatically installed.
Which changes did you see? The pfio library hasn't changed in 6 months. I have forked my own branch (locally), and am working on adding features like pullup control.
My focus with the library is to keep it as simple as possible. I want kids to be able to use it without having to learn a whole lot. So, my intention is to keep the inputs and outputs linked to 1-8 (and not use 0 as the first pin). I know the GPIO and wiringpi libraries starts from 0, however they are more tightly linked to GPIO pins - the Piface is different.
—
Reply to this email directly or view it on GitHub.
I'll have a look and likely pull at least some of the changes into my branch. If it makes sense, I'll see if I can push my changes back into the pfio repo - but it's possible that our directions diverge.
If your gem is self contained that is much better.