On Thu, May 1, 2008 at 4:25 AM, Chris Lewis <[EMAIL PROTECTED]> wrote: > Why would you need to submit the form when a value is selected from the > list? If you know the available DBs before hand, then you know the > default ports. Store those as a client-side JSON object and use the > select's onchange event.
> ... > While tapestry's Ajax support is still in the oven, it has @OnEvent > which does something similar [to Wicket]. I don't want to submit the form. It just appeared that that was the only way to use the zone parameter on BeanEditForm to get what I want. It looks like you're proposing two alternatives: 1) Do it all client-side using JavaScript: That would work for this case, since I do know the mapping from DB types to DB ports in advance. I see two flaws, however. The main one is that I have other, similar cases in mind in which I'd need server-side computation to update the form in response to field-change events. Second, I don't know JavaScript well and don't like it, so I'd really rather keep it neatly encapsulated in components that somebody else writes. 2) Use @OnEvent: Do form fields issue events, or is that planned for the future? If they do so now, could you tell me the event name for a drop-down selection-made event, or tell me how to find it for myself? I don't see any mention of events in the code for Select, AbstractField, or Field. Or do I need to use a mix-in? As for Ajax support being still in the oven, I'm really hoping it's coming out soon. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
