Interesting the Ajax call decorator mentioned above sounds like a good choice, I don't know the transactional steps for each solution, but to have the javascript written entirely in the page without requiring some sort of connection to the wicket server, does sound like it will be more immediate if your worried about that 1 or 2 seconds of idle time however you want to accomplish that. http://radio.javaranch.com/pascarello/2005/05/17/1116340367337.html If you need a script: function DisableEnableForm(xForm,xHow){ objElems = xForm.elements; for(i=0;i<objElems.length;i++){ objElems[i].disabled = xHow; } }
Just my two cents, Matthew Patrick Petermair wrote: > In our wicket application we are using a lot of Ajax links/forms. > Sometimes, those requests take a second or two. We now want to give the > user some feedback, that his request is being processed (to avoid double > clicking or the impression that the webapp is slow). -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Provide-the-user-with-immediate-feedback-tp3250978p3251879.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
