I have a rather large progressive web form. That is to say that as the form progresses in status, more of the form becomes 'available'. I want to be able to control the form fields depending on the status as follows:

Status: <SELECT> list with <OPTION>'s such as Stage1, Stage2, Stage3 and Stage4 (always available)
If Stage1 is selected, then only the first part of the form is available - maybe form items 10-20. The rest of the form should be visible, but readonly)
x days later, the status is then changed (by user) to Stage2 at which point both the first (10-20 items) and second (21-32 items) are available. Again, the rest of the form visible, but readonly.
This then continues right through all the status levels.

I think that I could figure this out, but just wanted some input into how YOU would go about this in the easiest, most efficient way. Also, should I control the form with client-side Javascript or server-side asp ???

Any thoughts, ideas, recommodations would be much appreciated. Sample script or links would be even better.

That is one possibility, but if the user changes the status, the page will need to be reloaded.
Before that happens, I will need to write any changes to the database (does the user want to commit changes???). 

Therefore, maybe Javascript would be better???

What I am after from this thread is a discussion on what you guys would do. Also, the pro's and con's of the various available options.

I forgot to mention, this is for an intranet web application which is going to be used by no more than 10 people.

The fact that i0t is internal means that we do not have to worry about JS being disabled.

Does that change your view on issue ???

Thx

My vote is for server side. Simply break the steps into separate pages and show what is applicable on that page. Store the current status in a database or file somewhere.

A rule of thumb I try to remember is to not cause the user to scroll down more than 1 page (for average resolution) for any pages on the site. There are exceptions of course, but this might help in your case.

Cheers,
Andrew

another vote for server-side, not only will it be a whole heck of a lot of coding in javascript (yick!), but it'll run slow on the browser checking that many fields

i don't use the reason "they might have javascript disabled".. if someone has that going on, half the sites on the net wouldn't work, lol

while i'm sure you'd be able to "name 5 that work to one that doesn't", it all really comes down  to a matter of programming style

Most of my code depends on certain things, sometimes Javascript is required for something to work, i can live with the minimal number of people who for some reason have "javascript turned off"....

maybe i'm living in a tunnel or something, but my main web site has 27,000+ signups, and i have no complaints of something not working or what not because a window wouldn't popup or a mousover wouldn't work or a field was disabled/enabled via javascript....

I guess that (for me anyway) it depends on the project. Sometimes client-side, sometimes server-side, but mostly both.

I am lucky enough to work in a 'controlled environment' and only have to worry about IE (ok, so that makes me lazy, stupid, etc !!!). If one of my apps relies upon JS and a user has disabled JS, then we just tell them to comply with the company standarad and enable it.

my apologies, my apoligizes.. didnt realize someone would take "half" so literally..

as for data verification...  client-side for those who support it so that it'll save a trip to the server (and give "real time" validation), but ALWAYS server side to catch all situations

maybe seems like "much"?.. but as said above.. programming preferences.... which i believe was the "spirit of this thread"

Absolutely Morningz - I wasn't necessarily looking for THE answer, but just wanted to get some ideas and opinions.

The beauty (or sometimes pain in the arse) with this industry is that there is rarely one single right way of doing things. There is more than 1 way to skin a cat !!!

ljamal wrote: What does an app do that would cause it to not function correctly if Javascript is disabled? Try as I may, I haven't been able to think of a scenario where Javascript is absolutely necessary.

but using something like Client Side script is all about improving the visitor's experience on the site.....  and (at work) making the application more user friendly for non-internet types (javascript to validate, help, show immediately on the browser), or on my personal stuff using javascript to make the site more "wow" than all my competition sites, i think spending the time, and maybe even requiring javascript be turned on, to code with client and server script going is a good thing.....

besides, i take it since you don't code against anything that someone can turn off, how do you handle someone having their IE security set to max??  this setting stops all cookies, which also stops session from working properly

i am just trying to chime in that there is no way in hell one is going to be able to code a page that satisfies every browser, every platform, every setting... you'd NEVER get any work done, lol

look! even this forum software: http://www.morningz.com/images/temp/javascript_off.jpg - http://www.morningz.com/images/temp/javascript_off.jpg

at some point, a programmer/developer has to draw the line on requirements.... you'll be way behind the curve if you don't

my 2 cents....