Form handling: Surely there's a better way

El_Zagna

Whenever I need to process a form I use the approach given here (an OnLamp.com article by David Sklar). The basic idea is to divide your form into three parts: showing, validating and processing. Since the submit button re-calls the form itself, there has to be a function to choreograph the logic depending on whether you are showing the form for the first time, validating, or processing.

I find this to be an awkward approach. I don't much like the idea of using the same form (or module, I suppose) to do three very different things. I also don't like getting and reestablishing all the data I need to keep everything in line. Finally I find myself using global variables all over the place.

Maybe I just don't have the technique down, but I'm hoping there is a better way of doing this. I realize that ultimately we're dealing with HTML, and maybe I've been spoiled with some of the things available in other more Object Oriented environments.

So, does anyone have a better approach?

ahundiak

As your linked article suggests, take a look at PEAR QuickForms as a way to encapsulate some of the form processing logic. As long as your apps fit into their view of the way forms should work then it certainly makes development easier and more robust.

Processing html forms in a robust manner is an inherently complex task.

El_Zagna

Thanks, ahundiak.

PEAR, eh? I took a look around their site and it looks like PEAR will be another significant learning curve, and ultimately I will be forced into a specific look and feel for PEAR generated pages. I'm not sure I'm up for that right now.

Do you use PEAR? Are you happy with it?

ahundiak

I only use a few of their libraries (Spreadsheet_Excel_Writer). Never did like their Forms implementation. Plus, PEAR is really designed for PHP 4. Most of their libraries will not take advantage of any new PHP 5 features.

On the other hand, it's not hard to walk through their examples. As I said before, form processing can be difficult. You really need to take the time and to study some implementations in order to understand the issues well enough to make an intelligent choice.

And PEAR at least has reasonable support and documentation.

El_Zagna

Well, ahundiak, I think you really answered my question in your first reply:

Processing html forms in a robust manner is an inherently complex task.

That's not the answer I was hoping for, but at least I won't spend any more time searching for a simple, elegant solution.