Speaking of documentaiton, is there any structured approach to documenting the get/post parameters for a perl web page?
I have a main menu type of of page I have inherited. The GUI designer is not a programmer seems to have a strong preference buttons instead of links or drop down menus. Each push button represents another target page which has its own set of get/post parameters which require its own, sometimes conflicting, hidden HTML fields. The code is SOOOOO ugly because the previous programmers had no naming conventions and did not understand SQL. Is there any structured approach to say: These hidden variables are for these destinatino pages. These are the get/post parameters for this page, etc...? and Here are the get/post params this page needs? Javadoc won't even help me with this (if I was using Java). Siegfried __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
