so when I hit the submit button the app will move to the next pageThe basic strategy there is that your submit button returns you to the same page, and in your "respond_per_page" method, you recognize the submit button and return the new page.
The whole point of "state" is that the dispatcher can figure out what code should be used to respond to a given form. So it isn't a form in a user's browser that changes state, it's the respond controller that changes state.
And yeah, that's a messy interaction between end_form and Template Toolkit. You have to add .join("") to the result of end_form. Feh. This will be clearer in the updated docs.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
In reply to Re: Trying to understand how CGI::Prototype::Hidden, Template Toolkit and CGI.pm work together.
by merlyn
in thread Trying to understand how CGI::Prototype::Hidden, Template Toolkit and CGI.pm work together.
by rlb3
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |