[Javascript] Prepacking the HTTP_POST array from JavaScript

[David Lovering]

Actually, I think the cumulative comments of you folks proved to have an
unexpected use.  I prepared an edited excerpt of them for my client, and he
forwarded them on to their IT group leader.  They apparently were surprised
that the VP in charge of software development would OK something that was
technically infeasible, and the powers that be are considering moving him
into a somewhat less technically demanding slot.  On a somewhat more
positive note, they are meeting next week to revise the project
specifications, presumably along "conventional" lines.  I've already heard
that the prohibition against "POST" forms transfers is going to be lifted,
and there may be other goodies in the offing as well.  My first task will be
to break these monolithic forms into functional subforms which are smaller
and more manageable, hence obviating the "hundreds" of fields issues.
[Incidently, the soon-to-be-former VP of software development was also the
chap who originally voted for using GoldMine and Remedy hooked together].

Yay!  Three cheers for the JavaScript List!

-- Dave Lovering

----- Original Message ----- 
From: "Chris Tifer" <christ at saeweb.com>
To: "[JavaScript List]" <javascript at LaTech.edu>
Sent: Tuesday, August 26, 2003 11:06 AM
Subject: Re: [Javascript] Prepacking the HTTP_POST array from JavaScript


> > Also, I'm not one of these joes who believes every form should
> > have six million hidden fields just to store the machine state if the
> state
> > can be derived from other DOM objects elsewhere in the environment.
>
> I would hope there's no joes that believes in having six million hidden
> fields.
> I build some rather extensive applications and I can not recall many (if
> any)
> times where I've ever needed more than a handful to 'persist state' per
se.
>
> This leads us back to my comments on your dillema last week. I still don't
> know
> exactly what you're doing but when you talk about hundreds - or even
> thousands
> I seem to recall - of form fields, I as a developer would HAVE to tell the
> user
> that their method is wrong somewhere. If they insisted on it being that
way,
> I
> don't think there's any way I could work with them because all they're
doing
> is
> tying your hands behind your back. You should lead THEM to their end goal.
> If they want to code it a certain way, have them code it that way...
>
> Chris Tifer
>
> _______________________________________________
> Javascript mailing list
> Javascript at LaTech.edu
> https://lists.LaTech.edu/mailman/listinfo/javascript
>
>