Em Sun, 06 Jul 2008 20:01:55 -0300, Robert Zeigler <[EMAIL PROTECTED]>
escreveu:
Hi Thiago,
Hi, Robert!
Which you then document. Now your page catches:
onRemoveFrom... where ... is the id of the component in the page.
The ability to trigger new events based on existing ones is a really
p
Hi Thiago,
My recommendation would be to catch the events from your component,
and then trigger your own, custom events.
For your ActionLinks component, for example, you might have a handler
in the component:
onActionFromRemove(Object toRemove) {
resources.triggerEvent(...);
}
Then you
Em Fri, 04 Jul 2008 19:10:20 -0300, Stephane Decleire
<[EMAIL PROTECTED]> escreveu:
Isn't it the purpose of EventLink ?
I think so, but I've just discovered that after I sent that message. But
what about form submissions, for example? I wanted to do a component that
had a form with some
Isn't it the purpose of EventLink ?
Stephane
Thiago H. de Paula Figueiredo a écrit :
Em Fri, 04 Jul 2008 13:42:58 -0300, Thiago H. de Paula Figueiredo
<[EMAIL PROTECTED]> escreveu:
Say I have a List page. Inside it, I have an ActionLinks component.
Inside ActionLinks, I have an ActionLink wi
Em Fri, 04 Jul 2008 13:42:58 -0300, Thiago H. de Paula Figueiredo
<[EMAIL PROTECTED]> escreveu:
Say I have a List page. Inside it, I have an ActionLinks component.
Inside ActionLinks, I have an ActionLink with t:id remove. How, in the
List page, can I handle the action event from the remove
Say I have a List page. Inside it, I have an ActionLinks component. Inside
ActionLinks, I have an ActionLink with t:id remove. How, in the List page,
can I handle the action event from the remove ActionLink?
In other words, how can I handle events from a given component embedded in
another
