I still use this workaround.
To have it work with T4.1.3, I think you just need to set the event on a
form component (I use the submit button).
dojo.byId('submit').ajaxEvent=function(json) {};
then :
@EventListener(targets = "submit", events = "ajaxEvent")
public void onAjaxEvent(IRequestCycle c
Is anyone using this workaround on Tapestry 4.1.3? I'm getting some dojo
JavaScript error ("o[i] has no properties"), but it seems to work on Tap.
4.1.2.
Christian Dutaret-3 wrote:
>
> I found a nice solution using dojo's ability to listen to an arbitrary
> javascript function as if it were a
https://issues.apache.org/jira/browse/TAPESTRY-1405
In the meantime I'll use Christian's approach.
Thanks, J
On 5-Apr-07, at 11:19 AM, Julian Wood wrote:
Was this ever dealt with? Attaching an event listener to a radio
group component still doesn't work for me in the latest 4.1.2
snapshot
Was this ever dealt with? Attaching an event listener to a radio
group component still doesn't work for me in the latest 4.1.2
snapshot, though if i change it to a property selection, it does. I
couldn't find a JIRA issue which looked like it dealt with this
specifically - maybe http://iss
https://issues.apache.org/jira/browse/TAPESTRY-1132
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Ohh,Right, parameters . I don't know if a JIRA issue is opened for it
(support parameters using @EventListener, somehow..) , but that would be a
good start towards getting that resolved.
On 10/27/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
What I am hoping to do is something like this:
What I am hoping to do is something like this:
and code like this:
public void makeLink() {
IEventListener listener = getFoo().getEventListener("onclick");
listener.setEventHandler("bar");
listener.setParameters(new Object[]{ getCurrent().getEntityId()});
}
I'm not sure I understand what you mean. What model do you think would feel
more natural?
On 10/25/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
Is there any more on this?
I am just now starting to explore the EventListener model. I must
admit I find it a little odd that I can't wire things up
Is there any more on this?
I am just now starting to explore the EventListener model. I must
admit I find it a little odd that I can't wire things up
programatically. It feels wrong that I need to decide at compile time
that two components are talking to each other.
Or is there something new?
-
Hah! That's pretty cool. I like it :)
If someone files a bug in JIRA I'll look into the radio button stuff
.(though I thought I remembered there being a ticket for this already - at
least I know we had to deal with it in tacos )
On 10/4/06, Christian Dutaret <[EMAIL PROTECTED]> wrote:
I found
I found a nice solution using dojo's ability to listen to an arbitrary
javascript function as if it were a native event.
I attach an empty js function to an arbitrary DOM element like this:
document.getElementById('someDiv').clickRadio=function(radio) {};
and an onclick attribute to my radio but
I'm glad someone else has a need for this as well. From doing a little
bit of research the other day, I found @EventListener annotation that
was introduced into tapestry 4.1+ that "sort of" fixes the problem. I'm
currently using stable release of tapestry 4.0.2, so I didn't bother
going that r
Hi,
Is it possible to have an EventListener for events on components within a
@For loop? Typically, I have a set of radio buttons, which are rendered from
@Radio components within a @For loop (with a surrounding @RadioGroup
component), and I want to invoke a listener whenever an onclick event occ
13 matches
Mail list logo
