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.
  • CGIP is deliberately very thin. It is a framework which abstracts away the most boring parts of every web app I've ever written. It's true that if CGIP::Hidden doesn't do what you want, you're left with only the thin framework above it. One of my long-term todo tasks was to make that a bit more pluggable, to handle the style that better suits REST-ful APIs in addition to hidden-field state passing, but none of my clients had that as a problem, so I didn't add it yet. :)

    Your comment about data-push vs callback is a bit misplaced though. Certainly, prototype-based programming supports both manners, and my clients have used both, sometimes together. The rendering phase should generally not change the state of the app, but could use either data added during render_enter or computed during render itself via callback. Template Toolkit makes both accesses with the same syntax, so you can even move from one to the other. Maybe you missed that because there was no examples of computing and preloading during render_enter in the sparse documentation. I do have examples of that in my presentations.

    --
    • Randal L. Schwartz
    • Stonehenge