Compatibility with Ruby 1.9.2 #14

tpberntsen opened this Issue Dec 1, 2011 · 7 comments

5 participants



Thanks for a great gem.

I've read in another post that you're working on a 1.9.2 compatible version, which would be absolutely fantastic to have.

Are you still working on it, and if so, when do you then expect to release it?



Sorry I don't know, very few people have expressed an interest or provided any help with upgrading. I don't use Ruport in any of my active projects at the moment so haven't had any commercially-available time to work on it. Maybe over Christmas I will have time off to work on open source.


That's quite understandable and thanks a lot.

We probably can't contribute man hours do strengthen the development right now, but perhaps we could help make a donation to support the development. Do you accept donations?


That's a kind offer, it's not something I've really thought about. I'd definitely be welcome to anything that lets me spend time working on Ruport. The main requirement for Ruby 1.9 compatibility is replacing PDF Writer with Prawn for PDF generation.

Were you hoping to be able to upgrade before the end of the year?


So beside Prawn, what else would be required to update the source for Ruby 1.9? I've been using Ruport for some report generation with Ruby 1.9.3 and Rails 3.2.1, but haven't needed any output formats other than HTML. With that in mind, I haven't run into any issues.

I've been programming with Rails off and on for about 4 years now and am looking to take a stab at my first OpenSource project. This one seems like it would be challenging, yet solvable.

Odaeus - Is this something you think I'd be able to take on?


Yeah, compatibility with 1.9 would be freaking awesome. I am working a project requiring reporting capability running on ruby 1.9 and have been studying ruport for the past couple of days, only to run into the pdf-writer issue just now. Ruport seems amazingly useful, I can't fathom why it hasn't yet received a compatibility update for 1.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment