On Tue, 2005-02-15 at 17:00, dan wrote: > Matt M. wrote: > >>Any feedback will be appreciated. > > > > > > > > why reinvent the wheel? > > > > take a look at: > > http://pear.php.net/package/Html_quickform > > > > To the people who want to truly understand how the system works, the > wheel, as it stands, is wothless :) > > I know I can use a drop-in solution, and I might consider it in the > future. However, if I understood in more detail the entire process, I > would be able to troubleshoot and add advanced features to the wheel. > > That's how I look at it, anyway. > I like the attitude from a learning standpoint but since you asked for feedback you could have at least acknowledged the guys effort in offerin one solution. This thread is very similar to another one today. and the answer is the same. use some sort of conditional construct to determine how you are being requested and process accordingly. I usually set a hidden variable that can be checked to let me know what to do. if (isset($_POST[myvar] && $_POST[myvar] = "expected value"){ # perform second phase form } else { #do form phase one stuff. print "<input type=hidden name=myvar value='expected value'>\n"; } one of many ways to do it. I have to say I have done quite a bit of this sort of thing and it gets really confusing to maintain if there is a lot of logic involved. One one hand it is nice to know you only have to change one file if a change is needed ( especially if there are changes to the parameters being passed from the entry side to the processing side. I have yet to feel strongly one way or the other whether it is better to use a single file or multiples. Bret -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
