Re: cgi::application authentication

Replies are listed 'Best First'.
Re^2: cgi::application authentication by neptuneray (Sexton) on Sep 21, 2009 at 18:26 UTC
Good job, Scorpio. I wish that I had read your doc first! Would've saved me a nice Sunday afternoon ... Anyway, today I am beginning to integrate HTML::FormFu into my CGI::App. I am currently using the Template Toolkit, but I have hand-coded all the templates, store them in one big subdirectory, and have a lot of logic to tell which one to call. I would prefer to streamline this and "objectify" it. I looked at Mark's Data::FormValidator, but it seemed to me that FormFu did more of what I wanted (comments, anyone?). The only problem I see now is an absence of any examples in FormFu about a good CGI::App integration policy (or plugin), but instead, lots of references to Catalyst integration. I am just a little leery of the learning curve to approach Catalyst. I found CGI::App to be simple to grok, as long as you know "regular" Perl (not Moose-extended Perl) and how CGI works.	[reply]

Replies are listed 'Best First'.

Re^2: cgi::application authentication
by neptuneray (Sexton) on Sep 21, 2009 at 18:26 UTC

Anyway, today I am beginning to integrate HTML::FormFu into my CGI::App. I am currently using the Template Toolkit, but I have hand-coded all the templates, store them in one big subdirectory, and have a lot of logic to tell which one to call.

I would prefer to streamline this and "objectify" it. I looked at Mark's Data::FormValidator, but it seemed to me that FormFu did more of what I wanted (comments, anyone?).

The only problem I see now is an absence of any examples in FormFu about a good CGI::App integration policy (or plugin), but instead, lots of references to Catalyst integration. I am just a little leery of the learning curve to approach Catalyst. I found CGI::App to be simple to grok, as long as you know "regular" Perl (not Moose-extended Perl) and how CGI works.

[reply]