1.5 IEventSink adapted as behavior
Hello, I am currently using the new inter-component events system to communicate between components. My primary use is to bubble up requests (ajax requests, switch panel events) to parent components. This enables decoupling inner panels so they can be reused more easily in other panels. I am now in a situation where I want to provide the same IEventSink behavior to multiple component types. No problem, I'll just create a Behavior for this I thought. The problem is that Behaviors are not included in the processing of IEvents. So, maybe IEventSink should be a special behavior that can be added to any Component instead of (or in addition to) an interface? What do you think? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 1.5 IEventSink adapted as behavior
hrm. add an rfe to add behaviors to event chain. -igor On Mon, Mar 7, 2011 at 11:21 AM, Bertrand Guay-Paquet ber...@step.polymtl.ca wrote: Hello, I am currently using the new inter-component events system to communicate between components. My primary use is to bubble up requests (ajax requests, switch panel events) to parent components. This enables decoupling inner panels so they can be reused more easily in other panels. I am now in a situation where I want to provide the same IEventSink behavior to multiple component types. No problem, I'll just create a Behavior for this I thought. The problem is that Behaviors are not included in the processing of IEvents. So, maybe IEventSink should be a special behavior that can be added to any Component instead of (or in addition to) an interface? What do you think? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: 1.5 IEventSink adapted as behavior
Ok I created https://issues.apache.org/jira/browse/WICKET-3516WICKET-3516 Add behaviors to the event processing chain On 07/03/2011 2:35 PM, Igor Vaynberg wrote: hrm. add an rfe to add behaviors to event chain. -igor On Mon, Mar 7, 2011 at 11:21 AM, Bertrand Guay-Paquet ber...@step.polymtl.ca wrote: Hello, I am currently using the new inter-component events system to communicate between components. My primary use is to bubble up requests (ajax requests, switch panel events) to parent components. This enables decoupling inner panels so they can be reused more easily in other panels. I am now in a situation where I want to provide the same IEventSink behavior to multiple component types. No problem, I'll just create a Behavior for this I thought. The problem is that Behaviors are not included in the processing of IEvents. So, maybe IEventSink should be a special behavior that can be added to any Component instead of (or in addition to) an interface? What do you think? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
