Jesse Erlbaum wrote: > > Since it is unlikely that a particular button will change its destination > run-mode, statically defining it in a template is a very valid solution.
This is what I usually do as well. I find defining the HTML elements directly in HTML makes them easier to develop and debug. I only really use the CGI.pm HTML generation features for some of the non-text box form elements, particularly the pop up menus. Often HTML::FillInForm will handle re-filling forms for me without even messing with CGI.pm for that case. -mark . . . . . . . . . . . . . . . . . . . . . . . . . . Mark Stosberg Principal Developer [EMAIL PROTECTED] Summersault, LLC 765-939-9301 ext 223 website development . . . . . http://www.summersault.com/ . . . . . . . --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
