Perhaps I expressed myself incorrectly with regard to 'rebuilding the form'. The rebuilding of the form was not so much a concern as was sending it back to the client. The nature of the data entry that needs to be done (and its sheer volume) requires that the user be able to continue absolutely uninterrupted for whatever period of time he chooses.
A large proportion of the users will probably be accessing the page with dial-up accounts, running through antiquated South African telephone exchanges. A delay of even a few seconds per entry would be untenable, and such a delay would doubtless occur were I to adopt the usual Tapestry approach. Your second idea, however, sounds fantastic and I think I'll try that right now. James -----Original Message----- From: Richard Clark [mailto:[EMAIL PROTECTED] Sent: 20 November 2005 11:19 PM To: Tapestry users Subject: Re: JavaScript in forms with Tapestry You may want to try a small prototype using the usual Tapestry approach and user-test it. Tapestry caches page layouts in normal operation, so the submit-render cycle is very fast. "Waiting for the server to rebuild the form" may well take less time than you think. Then, if you find you still need to do this in JavaScript, you could have 2 forms -- the one that Tapestry sees (with a couple of hidden fields) and a dynamic form built by JavaScript. When the user hits submit, run a locak piece of JavaScript to package the data up yourself and shove it into the hidden field, then submit the static form to Tapestry. Take that block of data, unpack it yourself on the server (pretty simple to do in Java) and take it from there. ...Richard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
