Ahhhh...I had almost forgotten what your original question was. I wouldn't
try this yet with EventListener. Use onchange="tapestry.form.submitForm('your
form id')" for now.I haven't added the logic to manage hidden form field data ~yet~, but after I do that is what will make this work without re-loading the whole page. You can of course do this right now already using AjaxEventSubmit from tacos. Ultimately, from the tapestry developers perspective nothing will be different in these ajax calls than what you would do during normal full-page reload development. Form data values will still get updated, etc... Only when you want to start doing effects/updating things/etc will you have to think about ajax. This is already "fairly" transparent in Tacos but will hopefully be completely transparent/easy to do in tap 4.1. It will also cater to those people (myself included) that do like to get down/dirty with all of the javascript code/ajax calls so that you can use as little or as much of what the framework provides without getting into cluster-f#$ territory. On 6/28/06, Kevin Menard <[EMAIL PROTECTED]> wrote:
On Wed, 28 Jun 2006 14:26:43 -0400, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > Sure, does "async=true|false" sound like a good parameter name? (It'll > only > apply when using submitForm) That works for me. While that should take care of my problem, does that mean there's no way to force the page to re-render when submitted asynchronously? If that's the case, how can those values be used within the page. Please note my ignorance of nearly all things ajax. -- Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
