Hello all I have been using PerForm quite a bit to do a web based app for managing an online journal. I am not sure what developments are planned for it but I have a few questions. I have made some modifications to PerForm and would like feedback. Also who should I email with the patches?
1) I have modified PerForm to allow arrays of form inputs. For example I can have an array of text entry fields called tfarticles. As the form loads, the load_tfarticles callback is called but the index of the field is passed as a parameter too so I can put the different article names in the text fields according to the index. I made modifications to PerForm.pm and the stylesheet to allow this and it works well for me. 2) There was a problem when passing params in the URL to PerForm. When I do a submit, I want the param to remain intact but the code was loosing it. I modified PerForm.pm to keep the param but I'm not sure if the way I did it was 100% best practice. I can't remember why using a hidden field didn't work but I had trouble with it. 3) Many of my forms have multiple submit buttons that do different things. The validation process becomes a bit tricky since I need to check different things depending on which button was pressed. I was thinking it would be good for me if I modified PerForm.pm yet again to allow me to 'die' when handling a submit button press if the combination of form data is not right. An <error> tag could be added to my doc at the end of the form and my stylesheet would pick it up and display it. This would be much better than the standard Apache error that I get otherwise. I don't want to make my users have to re-enter all the form values so redirecting to an error display page and making them click the 'back' button would be annoying. Who should I email with the patches? Should I patch the documentation? matt reply to [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
