in reply to Re: Trying to understand how CGI::Prototype::Hidden, Template Toolkit and CGI.pm work together.
in thread Trying to understand how CGI::Prototype::Hidden, Template Toolkit and CGI.pm work together.

Thanks, I was thinking I could use respond_per_page to move to a different page but I wasn't sure. And thanks for the tip on how to deal with end_form. I was using a foreach loop and it was looking very ugly. :)

  • Comment on Re^2: Trying to understand how CGI::Prototype::Hidden, Template Toolkit and CGI.pm work together.

Replies are listed 'Best First'.
Re^3: Trying to understand how CGI::Prototype::Hidden, Template Toolkit and CGI.pm work together.
by jeffa (Bishop) on Mar 09, 2005 at 20:34 UTC

    Since CGI.end_form really just spits out a single closed form tag, why not replace it with a literal </form>? This is what i have been doing when i use the CGI TT plugin.

    UPDATE: I really have no idea why. I am sure someone had good intentions ... but somehow painted themselves in a corner. Hind sight is 20/20 ... and from my recent work experience i have learned that some things can't be easily fixed.

    jeffa

    L-LL-L--L-LL-L--L-LL-L--
    -R--R-RR-R--R-RR-R--R-RR
    B--B--B--B--B--B--B--B--
    H---H---H---H---H---H---
    (the triplet paradiddle with high-hat)
    

      Thanks for the info. Just out of curiosity, do you know why end_form was written the way it was?