Are you sure? How can @OnEvent solve the example I gave? Keep in mind that L and E are separate components. E is a reusable editor that doesn't know about L. L is a reusable filter and list that doesn't know about E, and which kindly provides a public method to allow others to ask it to refresh itself.
On 20/03/2014, at 12:42 AM, Lance Java wrote: > Hi Geoff, I'm thinking this can also be done with the onevent mixin I > mentioned earlier. Since it can send a (configurable) list of clientside > field values to the serverside event, you can send all field values that > your event cares about. > > If two fields (eg select menus, text fields) determine the behaviour, send > both. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
