I hate to speak for Thomas -- he's doing a pretty good job of it.

One thing, I think you need to come down off your "high-horse" that scripting is bigger-and-better -- that HTML is only good if you can boost it with scripting, and that the fault lies in the browser/hardware users are running. That is what I get out of your replies. That is not the case, and I think that is what Thomas is trying to tell you. But you need to listen.

Your board offers nothing above what a flat HTML/CGI board offers. Even less. I know. I have written driving board software as an exercise. It used only HTML, and it is head and shoulders above this software. The keyword should be "functional" software. If it lets the user do what the user wants it to do, not what the programmer wants it to do or to look like, or some standard the programmer puts forth, thinking they know more than the persons using the software. Anybody can glitz up the HTML (not anybody -- it takes a talent to provide the content programming above the functional programming, something I know I can't do).

I understand that you might be in a phase of writing the software, as an exercise or not, or that you might not be aware of what the user wants. But, you are not doing too good a job of listening, if you are in this phase.

There are so many things I could tell you about this software -- things that could be changed/corrected/added, but I'm not sure you would listen. You will probably only take this as an attack.