in reply to Multiple template coordination using HTML::Template
You should look into CGI::Application, which tightly integrates HTML::Template into its core. Basically, with CGI::Application, each of your "faces" would be a runmode, and then your application has a "setup" method that helps define the flow of your application. Looking at the "setup" subroutine of a app built with CGI::Application, you can usually figure out what each "face" or runmode does.
The other advantage is the CGI::Application is a gentle introduction to OOP. You can easily create a "superclass" that holds methods that you share among different modules of your application- you might split your report functions from your file list functions, but you can then share methods among them simply via the superclass.
There are a lot of advantages to using this module- it forces you to code cleanly, you can easily change the functionality and templates used for an entire application without recoding, and it's mod_perl friendly, should your application ever reach that level.
Check it out!
-Any sufficiently advanced technology is
indistinguishable from doubletalk.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Multiple template coordination using HTML::Template
by ryan (Pilgrim) on Dec 30, 2001 at 06:49 UTC |