If you really want to have some fun, try defining your forms using a .xml file and then using XML::Simple to read the file into a hash and pass it to HTML::Template, then store user feedback in a separate .xml file, get XML::Simple to read that file into a hash and pass it to HTML::FillInForm .. then output the template with the form filled in. On the other end write the saved .xml file using the contents of $cgi->Vars and you've got an instant dynamic form reading from a master .xml template and store all user records in individual .xml files that can be editing simply.
Sorry for the run on sentence. > I think one of the advantages of the way all these modules have been designed is > that they follow the Unix mantra of making tools that do one task and do it > well. This allows you to hook many of them together to do complex very tasks > with minimal fuss. Here we have CGI::Application, HTML::Template and > HTML::FillInForm working in a very similar way that you might use something like > ps, grep and cut to get process information. I would probably throw > Data::FormValidator into this mix as well as a program that works well with others. > > Kudos to the developers of these modules for keeping their focus on the task > they are trying to solve, and not throwing the kitchen sink into the mix... > > Cees > > --------------------------------------------------------------------- > Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
