in reply to Re: Re: Best method for dynamic page generation?
in thread Best method for dynamic page generation?

By the way that you are generalizing your needs, it sounds like the module that I am studying: CGI::Application that combined with HTML::Template , would be able to do a lot in one single (and hidden) module.

The interesting thing of all this is that it is easy to follow an interactive dialog with every user and returning what is required in every case. The cgi script is very simple, and it only creates an instance of your CGI::Application module. I am planning to use it with a Session module. As if it were a commercial transaction. Just to learn!

  • Comment on Re: Re: Re: Best method for dynamic page generation?

Replies are listed 'Best First'.
Re: Re: Re: Re: Best method for dynamic page generation?
by stonecolddevin (Parson) on Jan 04, 2004 at 04:12 UTC

    INCREDIBLY, I just got Class::DBI to work :-)
    I'm not exactly liking the idea of changing my templates to XML, but I think it would be a *great* idea to have a module/script that takes ALL database information and catalogues it into XML format, so when the user using my message board app (the idea is to create a message board for myself, and distribute the code), they can transfer the messages EASILY to any other languages or versions of the board. I like that.

    On CGI::Application, before I go and research it, what kind of differences does it have and what kind of benefits does it have over CGI.pm? Faster? More suited for "production scale" projects?

    Thanks so much to all who have helped thus far :-)

    dhoss
    "and I wonder, when I sing along with you if everything could ever feel this real forever? if anything could ever be this good again? the only thing I'll ever ask of you, you've gotta promise not to stop when I say 'when'", she sang
[reply]
      i just started using CGI::Application this week, so my opinion may not be totally informed.

      it's sort-of a subclass of CGI. it provides you a way to *organize* your run-modes ( actions ) in your application with a defined set of parameters and matching subroutines. something like: 

      "foo_action" => \&foo(),
"bar_action" => \&bar()

      [download]
      and later in your module: 
      sub foo {
   my $self = shift;
   # do stuff
}

      [download]
      it's something i used to do by hand. CGI::Application organizes it a bit more, and makes it a touch easier to come back to and debug, esp. if you're not the original coder.
[reply]
[d/l]
[select]

        Oh, BRILLIANCE.

        Does it allow you to take query parameters to match your subroutines?

        "and I wonder, when I sing along with you if everything could ever feel this real forever? if anything could ever be this good again? the only thing I'll ever ask of you, you've gotta promise not to stop when I say 'when'", she sang
[reply]

In Section Seekers of Perl Wisdom