https://github.com/rubysolo/qrio
Talked to the author a few weeks back and I think this was still a WIP and maybe close to being done. I liked it because it was based off of chunky_png which can be easily speed up using oily_png.
- Ken
> --
> You received this message because you are subscribed to the Google Groups "Barby" group.
> To post to this group, send email to ruby-...@googlegroups.com.
> To unsubscribe from this group, send email to ruby-barby+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/ruby-barby?hl=en.
>
QRio looks like it's still very alpha and not ready for production usage, yet.
Kenny Meyer
IMHO, it makes very much sense that a barcode library also supports
reading barcodes not only generating them.
I have less knowledge about how to write such library from scratch,
and at the current moment I just need to get things done.
Currently there are two actively maintained stable solutions written
in Java (probably more):
- http://code.google.com/p/zxing/
- http://sourceforge.net/projects/zbar/
Zxing makes it needless to buy a barcode scanner. You just use your
Android phone, but I don't have one. (Dammit!)
Zbar makes it possible to use your webcam. I will give that a shot.
Anyway, I can't express you how much more I'd like to use a native
Ruby solution, than fucking around with Java dependencies. I'm still
looking :-)
Thanks for your feedback, guys.
Kenny Meyer
Kenny Meyer
Personally, I like the reading being separate from generation. In my solutions I need one or the other, and don't want the overhead of a bunch of unnecessary stuff.
Phil
--
Phil Ayres
617-794-2330
On Aug 13, 2011, at 10:27 AM, Kenny Meyer <knny...@gmail.com> wrote:
>> Zxing makes it needless to buy a barcode scanner. You just use your
>> Android phone, but I don't have one. (Dammit!)
> Pardon me. It also works through an applet.
>
> Kenny Meyer
>
>
>
> On Sat, Aug 13, 2011 at 1:23 PM, Kenny Meyer <knny...@gmail.com> wrote:
>> Zxing makes it needless to buy a barcode scanner. You just use your
>> Android phone, but I don't have one. (Dammit!)
>>
>