Re: [Catalyst] Which C::View::PDF should I use?
On 5 Mar 2010, at 05:38, Charlie Garrison wrote: I'm not looking to create PDFs from code, I'll be using an existing PDF and replacing values. And both C::V::P::Reuse C::V::P::API2 seem to handle that in effectively the same way. Yeah, they're both basically just wrappers.. PDF::Reuse is supposed to make it easier to reuse PDFs, whereas API2 is more powerful (and more cryptic :).. They're both being used successfully by people as far as I know, so pick whichever one appeals most :) Cheers t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Which C::View::PDF should I use?
We use simple View::TT and then a Filter: [%- USE Latex; FILTER latex(pdf) -%] Its perfekt! Tomas Doran schrieb: On 5 Mar 2010, at 05:38, Charlie Garrison wrote: I'm not looking to create PDFs from code, I'll be using an existing PDF and replacing values. And both C::V::P::Reuse C::V::P::API2 seem to handle that in effectively the same way. Yeah, they're both basically just wrappers.. PDF::Reuse is supposed to make it easier to reuse PDFs, whereas API2 is more powerful (and more cryptic :).. They're both being used successfully by people as far as I know, so pick whichever one appeals most :) Cheers t0m ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ -- Mit freundlichen Grüßen Felix Antonius Wilhelm Ostmann --- Websuche Search Technology GmbH Co. KG Martinistraße 3, D-49080 Osnabrück, Germany --- Tel.: +49 541 40666-0, Fax: +49 541 40666-22 Email: i...@websuche.de, Web: www.websuche.de --- AG Osnabrück - HRA 200252, Ust-IdNr.: DE814737310 --- Komplementärin: Websuche Search Technology Verwaltungs GmbH AG Osnabrück - HRB 200359, Geschäftsführer: Ansas Meyer --- ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Which C::View::PDF should I use?
Good evening, On 5/03/10 at 11:15 AM +0100, Felix Antonius Wilhelm Ostmann ostm...@websuche.de wrote: We use simple View::TT and then a Filter: [%- USE Latex; FILTER latex(pdf) -%] Its perfekt! I like that conceptually, but just to be clear, that is latex code being converted to PDF, correct? Due to time constraints I can't learn another formatting language for this project. I may choose to learn it for another project though (which does have more complex PDF requirements). Tomas Doran schrieb: They're both being used successfully by people as far as I know, so pick whichever one appeals most :) So for now I'll follow t0m's advice and choose one of the C::V::PDF modules. Thanks to both of you for the feedback. Charlie -- Ꮚ Charlie Garrison ♊ garri...@zeta.org.au 〠 PO Box 141, Windsor, NSW 2756, Australia O ascii ribbon campaign - stop html mail - www.asciiribbon.org http://www.ietf.org/rfc/rfc1855.txt ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Which C::View::PDF should I use?
Charlie Garrison schrieb: I like that conceptually, but just to be clear, that is latex code being converted to PDF, correct? Yes, you must write latex ... this do always my coworkers for me ;) -- Mit freundlichen Grüßen Felix Antonius Wilhelm Ostmann --- Websuche Search Technology GmbH Co. KG Martinistraße 3, D-49080 Osnabrück, Germany --- Tel.: +49 541 40666-0, Fax: +49 541 40666-22 Email: i...@websuche.de, Web: www.websuche.de --- AG Osnabrück - HRA 200252, Ust-IdNr.: DE814737310 --- Komplementärin: Websuche Search Technology Verwaltungs GmbH AG Osnabrück - HRB 200359, Geschäftsführer: Ansas Meyer --- ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
[Catalyst] Best practices: XML output from static XML
Hi, I need to generate an XML output (Content-type: application/xml), but this XML output is the XML content which is stored in an XML file. I don't need to dinamically generate this XML content. I have searched in google but I don't find any catalyst view module for managing this case. I don't know if exists any module for generating XML output from a static file as, for example, Catalyst::View::XSLT module (http://search.cpan.org/~janus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pm) does. That is, generate an output from a static file, in this case, an XML output. I am not finding much information about designing your own views in Catalyst, or at least, I don't see much flexibility. All examples I have found need to be generated, through the helper view, with TT template or any other templates. Is it possible to create your own view, with no template, and for example, in my case, read the output from a static file and send this output to the client? (I don't know exactly how Views works in Catalyst, though I have already read Catalyst tutorial and cookbook) Thanks in advanced, David ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Best practices: XML output from static XML
On Fri, Mar 5, 2010 at 5:10 AM, David oldskif...@yahoo.es wrote:
Hi,
I need to generate an XML output (Content-type: application/xml), but this
XML output is the XML content which is stored in an XML file. I don't need
to dinamically generate this XML content.
I have searched in google but I don't find any catalyst view module for
managing this case. I don't know if exists any module for generating XML
output from a static file as, for example, Catalyst::View::XSLT module
(http://search.cpan.org/~janus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pm)
does. That is, generate an output from a static file, in this case, an XML
output.
I am not finding much information about designing your own views in
Catalyst, or at least, I don't see much flexibility. All examples I have
found need to be generated, through the helper view, with TT template or any
other templates.
Is it possible to create your own view, with no template, and for example,
in my case, read the output from a static file and send this output to the
client? (I don't know exactly how Views works in Catalyst, though I have
already read Catalyst tutorial and cookbook)
Thanks in advanced,
David
Well, you could do your own view or just rely on
Catalyst::Plugin::Static::Simple:
http://search.cpan.org/~mstrout/Catalyst-Plugin-Static-Simple-0.29/lib/Catalyst/Plugin/Static/Simple.pm#serve_static_file_$file_path
You could wrap this in a view:
package MyApp::View::StaticFile;
use parent 'Catalyst::View';
sub process {
my ( $self, $c ) = @_;
$c-serve_static_file( $c-stash-{static_file} );
}
1;
Then just do $c-forward( $c-view('StaticFile') ); after setting the stash key.
-Jay
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
RE: [Catalyst] Best practices: XML output from static XML
Maybe I am missing something but why is a view needed? If you are serving up a static file and its xml why don’t you just serve that file statically based on path? Is the header content-type not getting set properly for that file? Thanks, -- Ali Mesdaq (CISSP, GIAC-GREM) Sr. Security Researcher Websense Security Labs http://www.WebsenseSecurityLabs.comhttp://www.websensesecuritylabs.com/ -- From: David [mailto:oldskif...@yahoo.es] Sent: Friday, March 05, 2010 5:10 AM To: catalyst@lists.scsys.co.uk Subject: [Catalyst] Best practices: XML output from static XML Hi, I need to generate an XML output (Content-type: application/xml), but this XML output is the XML content which is stored in an XML file. I don't need to dinamically generate this XML content. I have searched in google but I don't find any catalyst view module for managing this case. I don't know if exists any module for generating XML output from a static file as, for example, Catalyst::View::XSLT module (http://search.cpan.org/~janus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pmhttp://search.cpan.org/%7Ejanus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pm) does. That is, generate an output from a static file, in this case, an XML output. I am not finding much information about designing your own views in Catalyst, or at least, I don't see much flexibility. All examples I have found need to be generated, through the helper view, with TT template or any other templates. Is it possible to create your own view, with no template, and for example, in my case, read the output from a static file and send this output to the client? (I don't know exactly how Views works in Catalyst, though I have already read Catalyst tutorial and cookbook) Thanks in advanced, David Click herehttps://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg== to report this email as spam. Protected by Websense Hosted Email Security -- www.websense.com ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Best practices: XML output from static XML
Thanks Jay.
I thought of that solution too when I had a look at
Catalyst::Plugin::Static::Simple. But in this case, my doubt was, and is, how
should I create the view through the helper?
Most of the examples for creating views are TT views, so they create it as
'script/hello_create.pl view my_TT_view TT'.
David
De: J. Shirley jshir...@gmail.com
Para: The elegant MVC web framework catalyst@lists.scsys.co.uk
Enviado: vie,5 marzo, 2010 16:45
Asunto: Re: [Catalyst] Best practices: XML output from static XML
On Fri, Mar 5, 2010 at 5:10 AM, David oldskif...@yahoo.es wrote:
Hi,
I need to generate an XML output (Content-type: application/xml), but this
XML output is the XML content which is stored in an XML file. I don't need
to dinamically generate this XML content.
I have searched in google but I don't find any catalyst view module for
managing this case. I don't know if exists any module for generating XML
output from a static file as, for example, Catalyst::View::XSLT module
(http://search.cpan.org/~janus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pm)
does. That is, generate an output from a static file, in this case, an XML
output.
I am not finding much information about designing your own views in
Catalyst, or at least, I don't see much flexibility. All examples I have
found need to be generated, through the helper view, with TT template or any
other templates.
Is it possible to create your own view, with no template, and for example,
in my case, read the output from a static file and send this output to the
client? (I don't know exactly how Views works in Catalyst, though I have
already read Catalyst tutorial and cookbook)
Thanks in advanced,
David
Well, you could do your own view or just rely on
Catalyst::Plugin::Static::Simple:
http://search.cpan.org/~mstrout/Catalyst-Plugin-Static-Simple-0.29/lib/Catalyst/Plugin/Static/Simple.pm#serve_static_file_$file_path
You could wrap this in a view:
package MyApp::View::StaticFile;
use parent 'Catalyst::View';
sub process {
my ( $self, $c ) = @_;
$c-serve_static_file( $c-stash-{static_file} );
}
1;
Then just do $c-forward( $c-view('StaticFile') ); after setting the stash key.
-Jay
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Best practices: XML output from static XML
Well, as Catalyst works under MVC model, I thought that a best practice would be to use a view module although in this case, obiously, the view task is insignificant. David De: Mesdaq, Ali ames...@websense.com Para: The elegant MVC web framework catalyst@lists.scsys.co.uk Enviado: vie,5 marzo, 2010 19:04 Asunto: RE: [Catalyst] Best practices: XML output from static XML Maybe I am missing something but why is a view needed? If you are serving up a static file and its xml why don’t you just serve that file statically based on path? Is the header content-type not getting set properly for that file? Thanks, -- Ali Mesdaq (CISSP, GIAC-GREM) Sr. Security Researcher Websense Security Labs http://www.WebsenseSecurityLabs.com -- From:David [mailto:oldskif...@yahoo.es] Sent: Friday, March 05, 2010 5:10 AM To: catalyst@lists.scsys.co.uk Subject: [Catalyst] Best practices: XML output from static XML Hi, I need to generate an XML output (Content-type: application/xml), but this XML output is the XML content which is stored in an XML file. I don't need to dinamically generate this XML content. I have searched in google but I don't find any catalyst view module for managing this case. I don't know if exists any module for generating XML output from a static file as, for example, Catalyst::View::XSLT module (http://search.cpan.org/~janus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pm) does. That is, generate an output from a static file, in this case, an XML output. I am not finding much information about designing your own views in Catalyst, or at least, I don't see much flexibility. All examples I have found need to be generated, through the helper view, with TT template or any other templates. Is it possible to create your own view, with no template, and for example, in my case, read the output from a static file and send this output to the client? (I don't know exactly how Views works in Catalyst, though I have already read Catalyst tutorial and cookbook) Thanks in advanced, David Click here to report this email as spam. Protected by Websense Hosted Email Security — www.websense.com ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Best practices: XML output from static XML
On Fri, Mar 5, 2010 at 10:46 AM, David oldskif...@yahoo.es wrote: Thanks Jay. I thought of that solution too when I had a look at Catalyst::Plugin::Static::Simple. But in this case, my doubt was, and is, how should I create the view through the helper? Most of the examples for creating views are TT views, so they create it as 'script/hello_create.pl view my_TT_view TT'. David I'd really recommend just creating a sample application you can mess with, like 'catalyst.pl Foo' -- I do this frequently when testing new things. Then just script/foo_create.pl view StaticFile would create a skeleton view. When you supply additional arguments (the TT) then you are looking at basing your view off the helper, which is sourced from Catalyst::View::Helper::TT. It's fully optional, and omitting that will just create a very basic package. Of course you don't have to use any of this, you can just edit lib/MyApp/View/MyView.pm directly and code it up -- it's just a simple perl package (like what I wrote out above). -J ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
RE: [Catalyst] Best practices: XML output from static XML
To me this sounds like it’s the same issue as serving static images you wouldn’t create a view for that unless you need to wrap it around some application logic. Or at least that’s what it sounds like to me based on the information provided. We could take the MVC concept really far and say that static files need to have a filesystem Model with Controller logic for finding the files and each have their own View for each filetype. Thanks, -- Ali Mesdaq (CISSP, GIAC-GREM) Sr. Security Researcher Websense Security Labs http://www.WebsenseSecurityLabs.comhttp://www.websensesecuritylabs.com/ -- From: David [mailto:oldskif...@yahoo.es] Sent: Friday, March 05, 2010 10:49 AM To: The elegant MVC web framework Subject: Re: [Catalyst] Best practices: XML output from static XML Well, as Catalyst works under MVC model, I thought that a best practice would be to use a view module although in this case, obiously, the view task is insignificant. David De: Mesdaq, Ali ames...@websense.com Para: The elegant MVC web framework catalyst@lists.scsys.co.uk Enviado: vie,5 marzo, 2010 19:04 Asunto: RE: [Catalyst] Best practices: XML output from static XML Maybe I am missing something but why is a view needed? If you are serving up a static file and its xml why don’t you just serve that file statically based on path? Is the header content-type not getting set properly for that file? Thanks, -- Ali Mesdaq (CISSP, GIAC-GREM) Sr. Security Researcher Websense Security Labs http://www.WebsenseSecurityLabs.comhttp://www.websensesecuritylabs.com/ -- From: David [mailto:oldskif...@yahoo.es] Sent: Friday, March 05, 2010 5:10 AM To: catalyst@lists.scsys.co.uk Subject: [Catalyst] Best practices: XML output from static XML Hi, I need to generate an XML output (Content-type: application/xml), but this XML output is the XML content which is stored in an XML file. I don't need to dinamically generate this XML content. I have searched in google but I don't find any catalyst view module for managing this case. I don't know if exists any module for generating XML output from a static file as, for example, Catalyst::View::XSLT module (http://search.cpan.org/~janus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pmhttp://search.cpan.org/%7Ejanus/Catalyst-View-XSLT-0.08/lib/Catalyst/View/XSLT.pm) does. That is, generate an output from a static file, in this case, an XML output. I am not finding much information about designing your own views in Catalyst, or at least, I don't see much flexibility. All examples I have found need to be generated, through the helper view, with TT template or any other templates. Is it possible to create your own view, with no template, and for example, in my case, read the output from a static file and send this output to the client? (I don't know exactly how Views works in Catalyst, though I have already read Catalyst tutorial and cookbook) Thanks in advanced, David Click herehttps://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg== to report this email as spam. Protected by Websense Hosted Email Security — www.websense.comhttp://www.websense.com ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Best practices: XML output from static XML
On Fri, Mar 5, 2010 at 11:31 AM, Mesdaq, Ali ames...@websense.com wrote: To me this sounds like it’s the same issue as serving static images you wouldn’t create a view for that unless you need to wrap it around some application logic. Or at least that’s what it sounds like to me based on the information provided. We could take the MVC concept really far and say that static files need to have a filesystem Model with Controller logic for finding the files and each have their own View for each filetype. I would say that putting it into a view allows a greater degree of future-proof and foresight. Putting it into the controller would work fine, up until you need to serve another static file (or a different file), or add an access control layer, or switch to use sendfile, or switch to start serving from something like MogileFS. If you put it all the above in one method, why put it in a controller rather than a view? In all of what you said you haven't actually said what is wrong with using a view. I would certainly recommend that serving static files would be done by the webserver and render this moot. However, if you want to use Catalyst to serve a static file (which would only make sense if there *is* application logic) putting this in a View would be the Right Way. -Jay ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
RE: [Catalyst] Best practices: XML output from static XML
Catalyst to serve a static file (which would only make sense if there *is* application logic) putting this in a View would be the Right Way. Yes my point exactly. That’s why I was comparing it to serving static image files and how it's similar to this situation because there seems to be no application logic at all needed for this example so putting it in a view just to follow the design pattern does not make sense to me. That’s why I gave the previous example as an example of overkilling with the design pattern where it really serves no purpose. I completely agree that it makes much more sense to leverage the webserver for dealing with static files when necessary/possible. Thanks, -- Ali Mesdaq (CISSP, GIAC-GREM) Sr. Security Researcher Websense Security Labs http://www.WebsenseSecurityLabs.com -- -Original Message- From: J. Shirley [mailto:jshir...@gmail.com] Sent: Friday, March 05, 2010 12:20 PM To: The elegant MVC web framework Subject: Re: [Catalyst] Best practices: XML output from static XML On Fri, Mar 5, 2010 at 11:31 AM, Mesdaq, Ali ames...@websense.com wrote: To me this sounds like it’s the same issue as serving static images you wouldn’t create a view for that unless you need to wrap it around some application logic. Or at least that’s what it sounds like to me based on the information provided. We could take the MVC concept really far and say that static files need to have a filesystem Model with Controller logic for finding the files and each have their own View for each filetype. I would say that putting it into a view allows a greater degree of future-proof and foresight. Putting it into the controller would work fine, up until you need to serve another static file (or a different file), or add an access control layer, or switch to use sendfile, or switch to start serving from something like MogileFS. If you put it all the above in one method, why put it in a controller rather than a view? In all of what you said you haven't actually said what is wrong with using a view. I would certainly recommend that serving static files would be done by the webserver and render this moot. However, if you want to use Catalyst to serve a static file (which would only make sense if there *is* application logic) putting this in a View would be the Right Way. -Jay ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/ Protected by Websense Hosted Email Security -- www.websense.com ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] KiokuDB, MongoDB and the NoSQL thing
Thanks for the link Darren. I will read and ponder. Also of interest, I seen that Search::GIN has had a new release. The post also mentions some docs explaining queries, but I have not found them yet. Active Search::GIN development would encourage KiokuDB usage I would think. Thanks for the posts regarding this topic. S. Kiehn Darren Duncan wrote: Here's something timely on Ars, in that I just discovered it now around the time of this discussion thread: http://arstechnica.com/business/data-centers/2010/02/-since-the-rise-of.ars It lays out a summary of how the SQL and NoSQL worlds compare, and what sort of trade-offs you get for each choice, and it introduces several specific NoSQL projects. I also learned something, such that what CouchDB and MongoDB specifically represent data with is JSON documents. So basically, what you pick out of today's choices depends on your priorities. ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Which C::View::PDF should I use?
Good afternoon, On 5/03/10 at 1:32 PM -0800, S.A. Kiehn keenli...@ymail.com wrote: I am not a very experienced developer, but I was able to learn and use PDF::Reuse. I made a PDF template (11 page report) that I needed to intersperse data throughout. Using Catalyst::View::PDF::Reuse I was able to achieve a good result. I believe it is intended to be a reuse (of a PDF template) rather than a PDF creation tool, but it would work for that as well. To use with a report was a little tougher as I had to be creative to do wrapping. It is probably best to use where the location to place values on a template remains consistent (invoice, certificate). And I apparently mis-read the POD before. I thought there was a function to *replace* text in an existing PDF with values from my app. (I should not have stared researching this so late in the day.) So how do people insert values into an existing PDF? Do you have to determine X/Y position for each value to be added to the PDF? I was expecting to be able to replace a unique string from the PDF with a value from my app. For some reason I though Catalyst::View::PDF::Reuse was doing more magic than it really is. Is there a simpler approach (other than C::V::PDF::Reuse) for creating PDFs with values from my app? Once I hand this app to my customer, they need to be able to add new fields to a dynamically generated form config. My plan was to have a html 'template' version of the form with unique values for each field, which the customer can print to PDF and then re-use in the app. Is there some way to determine the X/Y position of existing text in the PDF at runtime? On 5/03/10 at 11:15 AM +0100, Felix Antonius Wilhelm Ostmann ostm...@websuche.de wrote: We use simple View::TT and then a Filter: [%- USE Latex; FILTER latex(pdf) -%] Can anyone advise how long the learning curve is for latex (for basic usage)? Would I be better off spending my time learning that? Thanks, Charlie -- Ꮚ Charlie Garrison ♊ garri...@zeta.org.au 〠 PO Box 141, Windsor, NSW 2756, Australia O ascii ribbon campaign - stop html mail - www.asciiribbon.org http://www.ietf.org/rfc/rfc1855.txt ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
Re: [Catalyst] Which C::View::PDF should I use?
Good afternoon, On 6/03/10 at 2:40 PM +1100, Kieren Diment dim...@gmail.com wrote: Depends how specific your layout requirements are and the kind of document you want to produce. LaTeX is pretty straightforward really, but you don't really have the fine grained control that other document formats have, so if you have exotic layout requirements it's going to be annoying. http://stp.lingfil.uu.se/~zrajm/nerd/LaTeX/quickguide.html is a good enough start. You don't need to know all of that. Thanks, that was a good intro. It looks like I could almost get away with a simple LaTeX table for the form. But I can see myself getting bogged down by the details; I think latex is going to be too hard for this project. I may still come back to it as best option though. And it was good to get the LaTeX basics, I can start thinking about how I can use it for the next project. Thanks again for the info. Charlie -- Ꮚ Charlie Garrison ♊ garri...@zeta.org.au 〠 PO Box 141, Windsor, NSW 2756, Australia O ascii ribbon campaign - stop html mail - www.asciiribbon.org http://www.ietf.org/rfc/rfc1855.txt ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
