Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • elaborate on why we need another CGI framework? I use (and love) CGI::Application [uwinnipeg.ca], which already has built-in support for HTML::Template and plugin support for Template, Session Management, Input Validation, etc. There's also a lively community around those modules already and the module authors are happy to receive patches and/or other contributions for improvements.
    • Even if the new module shares some features with CGI::Application, I am very glad to have more publicly released code from Merlyn to review and learn from.
    • Answer #1: Why not?
      Answer #2: TMTOWTDI
      Answer #3: If you haven't written a CGI framework or a Templating system in Perl this month, can you really call yourself a Perl programmer?

      Choose any three. ;-)

    • Randal's explication of the Why of this module is serialized in his Linux Magazine May-July, 2005 column #70 [stonehenge.com] and #71 [stonehenge.com] and #72 [stonehenge.com] as motivated, worked example(s).

      My summary -

      CGI::Prototype offers a different way of factoring out the "you always had to write this glue code" code. Catalyst uses the Perl Attributes annotations to factor out glue-code, which is classy demonstration that attributes are a good idea. CGI::Prototype uses prototypical (instance-based, or nonce-class, or "Frame-Slot") inheritance.

      --
      Bill
      # I had a sig when sigs were cool
      use Sig;