Hi Folks, Could you please comment on various PDF generators that one may use. Thanks. Lalit Send instant messages to your online friends http://au.messenger.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060221/8b319788/attachment.html
On Feb 21, 2006, at 1:42 PM, jeff thompson wrote:> Hi Folks, > > Could you please comment on various PDF generators that one may use.pdf-writer has a good variety of features and the author is pretty active. http://rubyforge.org/projects/ruby-pdf/ -- Eric Hodel - drbrain@segment7.net - http://segment7.net This implementation is HODEL-HASH-9600 compliant http://trackmap.robotcoop.com
Eric Hodel wrote:> On Feb 21, 2006, at 1:42 PM, jeff thompson wrote: > >> Hi Folks, >> >> Could you please comment on various PDF generators that one may use. > > > pdf-writer has a good variety of features and the author is pretty > active. > > http://rubyforge.org/projects/ruby-pdf/ >+1 I use this in a production application, works great. -- Jack Christensen jackc@hylesanderson.edu
Hi Jeff, It''s worth noting that of all the PDF generating libraries listed here: http://wiki.rubyonrails.com/rails/pages/HowtoGeneratePDFs only PDF::Writer (aka pdf-writer above) allows generating shapes (at least to my knowledge). Rob Kaufman On 2/21/06, Jack Christensen <jackc@hylesanderson.edu> wrote:> Eric Hodel wrote: > > > On Feb 21, 2006, at 1:42 PM, jeff thompson wrote: > > > >> Hi Folks, > >> > >> Could you please comment on various PDF generators that one may use. > > > > > > pdf-writer has a good variety of features and the author is pretty > > active. > > > > http://rubyforge.org/projects/ruby-pdf/ > > > +1 > > I use this in a production application, works great. > > -- > Jack Christensen > jackc@hylesanderson.edu > > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
So, I guess pdf::writer is the last word? Thanks all for your input. Cheers. Jeff Send instant messages to your online friends http://au.messenger.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060223/b8c07b21/attachment.html
Another vote for pdf::writer - it works well. Regards Dave M. On 23/02/06, jeff thompson <jeffcric@yahoo.co.nz> wrote:> So, I guess pdf::writer is the last word? Thanks all for your input. Cheers. > Jeff > > > > Send instant messages to your online friends http://au.messenger.yahoo.com > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails > > >
So with PDF::Writer how are you guys handling the conflict with transaction-simple? I have PDF::Writer working with Rails, but I had to replace transaction-simple in ActiveRecord with 1.30. But in doing that, the ActiveRecord tests fail at the transaction_test. The application works, possibly because I don''t use any transactions, but I don''t feel altogether comfortable. It''s interesting that if I run just transaction_test.rb it passes, but if I run the whole test suite (using the Mysql adapter) it always fails at line 201 of transaction_test.rb. Are you guys replacing transaction-simple? Have you noticed this issue? Thanks, Tom On 2/22/06, David Mitchell <monch1962@gmail.com> wrote:> Another vote for pdf::writer - it works well. > > Regards > > Dave M. > > On 23/02/06, jeff thompson <jeffcric@yahoo.co.nz> wrote: > > So, I guess pdf::writer is the last word? Thanks all for your input. Cheers. > > Jeff > > > > > > > > Send instant messages to your online friends http://au.messenger.yahoo.com > > _______________________________________________ > > Rails mailing list > > Rails@lists.rubyonrails.org > > http://lists.rubyonrails.org/mailman/listinfo/rails > > > > > > > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
On 3/5/06, Tom Wilcoxen <tomwilcoxen@gmail.com> wrote:> So with PDF::Writer how are you guys handling the conflict with > transaction-simple? I have PDF::Writer working with Rails, but I had > to replace transaction-simple in ActiveRecord with 1.30. But in doing > that, the ActiveRecord tests fail at the transaction_test. The > application works, possibly because I don''t use any transactions, but > I don''t feel altogether comfortable. > > It''s interesting that if I run just transaction_test.rb it passes, but > if I run the whole test suite (using the Mysql adapter) it always > fails at line 201 of transaction_test.rb. > > Are you guys replacing transaction-simple? Have you noticed this issue?I''d like to hear more about this. Others have reported this infrequently, but often enough that I am aware of it. I have recommended that the Rails team remove transaction simple from the distribution and instead supply Transaction::Simple as a gem or other dependency or at least to switch to Transaction::Simple 1.3 (PDF::Writer requires features available only in Transaction::Simple 1.3; future versions of the Ruby PDF tools will probably require a later version if I can figure out how to fix some serious problems with the Transaction::Simple model). Other than removing transaction-simple from the Rails distribution, I can offer no other fix. -austin -- Austin Ziegler * halostatue@gmail.com * Alternate: austin@halostatue.ca
Austin Ziegler wrote:> I have > recommended that the Rails team remove transaction simple from the > distribution and instead supply Transaction::Simple as a gem or other > dependency or at least to switch to Transaction::Simple 1.3 > (PDF::Writer requires features available only in Transaction::Simple > 1.3; future versions of the Ruby PDF tools will probably require a > later version if I can figure out how to fix some serious problems > with the Transaction::Simple model). Other than removing > transaction-simple from the Rails distribution, I can offer no other > fix.This might be a good time to remind the core team, as they are on the downhill run towards Rails 1.1 Justin