What is the best for to do reports in Rails?

Hello,

Whats best to do reports in rails:

A) ruport: http://rubyreports.org/
B) PDF:Writer : http://rubyforge.org/projects/ruby-pdf/
C) …

Thanks any help.
Helder

JasperReports + Rails
http://wiki.rubyonrails.com/rails/pages/HowtoIntegrateJasperReports

On Jun 9, 12:22 pm, Helder H. [email protected]

On Jun 9, 6:22 am, Helder H. [email protected]
wrote:

Hello,

Whats best to do reports in rails:

A) ruport:http://rubyreports.org/
B) PDF:Writer :http://rubyforge.org/projects/ruby-pdf/
C) …

Someone else mentioned JasperReports which is probably the best choice
if you already have reports written or would prefer to define your
reports in XML. Ruport is a pretty low level toolset, but many of our
users are pretty happy with it, especially because we make integration
with ActiveRecord pretty easy via acts_as_reportable.

I would not recommend using PDF::Writer directly for anything at this
point. Even if you don’t use any other functionality in ruport, our
Formatter::PDF adds interface improvements while fixing a number of
serious issues in PDF::Writer at the same time. Most of these patches
came from Austin, but do not exist in the released PDF::Writer code.
(Memory patches, bug fixes, etc)

It really depends on what you’re trying to do and how much you want to
roll up your sleeves. Searching through the Ruport archives for Rails
might prove helpful, and if you have any questions, just let us know
on the list. (http://list.rubyreports.org)

-greg

Why not fork PDF::Writer if you can’t get the original maintained. It
would be useful to have a PDF system that worked cleanly with Rails.

On Jun 10, 5:23 am, Neil W. [email protected] wrote:

Why not fork PDF::Writer if you can’t get the original maintained. It
would be useful to have a PDF system that worked cleanly with Rails.

You wouldn’t be the first, second, or third to suggest that we do
that. We don’t really want the added responsibility and are trying to
be diplomatic about it. We’ve even tried to find a maintainer to work
with Austin, but things are moving very slowly. If a fork happens,
we’d be willing to patch back all the stuff that’s in Ruport, though.

On Jun 9, 9:10 pm, Gregory B. [email protected] wrote:

I would not recommend using PDF::Writer directly for anything at this
point. Even if you don’t use any other functionality in ruport, our
Formatter::PDF adds interface improvements while fixing a number of
serious issues in PDF::Writer at the same time. Most of these patches
came from Austin, but do not exist in the released PDF::Writer code.
(Memory patches, bug fixes, etc)

By the way, if there is sufficient interest, we can think about moving
these patches into their own gem, like pdf_writer_fixes or something
of the like…

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs