Greger,
Greger wrote:
Is there anything in particular that one should take into account regarding
modperl and design patterns vs trad CGI-scripting?
As for now, I return XML from the package methods, and use XSLT for the
transformation to XHTML. This works very well, seems flexible, but are
You might have a look at the following projects:
- AxKit1 - http://search.cpan.org/~msergeant/AxKit-1.6.2/
- AxKit2 - http://search.cpan.org/~msergeant/AxKit2-1.1/
- Apache2::TomKit - http://search.cpan.org/~tomson/Apache2-TomKit-0.01_6/
Tom
Greger schrieb:
Is there anything in particular that
On Wed, 13 Sep 2006 13:03:55 +0300
Greger [EMAIL PROTECTED] wrote:
Is there anything in particular that one should take into account
regarding modperl and design patterns vs trad CGI-scripting?
As for now, I return XML from the package methods, and use XSLT for
the transformation to XHTML.
I definitely recommend using a template engine and
using an Model-View-Controller (MVC) framework; the
template engine helps with the view part. I was first
introduced to it on the tutorials under documentation
on perl.apache.org. It took me a little while to
figure out how to create instantiate
Greger wrote:
As for now, I return XML from the package methods, and use XSLT for the
transformation to XHTML. This works very well, seems flexible, but are there
better ways?
I guess it all depends on what one is doing, naturally. In this case it is an
application using the mysql
On Sep 13, 2006, at 9:28 AM, Frank Wiles wrote:
What I typically recommend to people is that they use a template
engine like Template-Toolkit.org. You simply pass it a Perl data
structure and then you have all of the same transformation
possibilities as XSLT ( at least as I understand
On Wed, 13 Sep 2006 13:50:27 -0400, Jonathan Vanasco wrote
On Sep 13, 2006, at 9:28 AM, Frank Wiles wrote:
What I typically recommend to people is that they use a template
engine like Template-Toolkit.org. You simply pass it a Perl data
structure and then you have all of the same
Frank Wiles wrote:
What I typically recommend to people is that they use a template
engine like Template-Toolkit.org. You simply pass it a Perl data
structure and then you have all of the same transformation
possibilities as XSLT ( at least as I understand it ). And if you
ever need
