Is T 4.1.1 deprecated? The bug reported was for 4.1.1, not for
4.1.2-SNAPSHOT. The status should then be: Will not resolve.
Cheers,
Borut
On 3.4.2007 22:59, Jesse Kuhnert wrote:
Resolved as not valid. :)
Just so everyone else is clear, elements component event
listeners
work
I'm not sure that's how it normally works. It is resolved / fixed , just not
in 4.1.1. I couldn't even resolve it in 4.1.1 if I wanted to, because
4.1.2is the only next incremental version number available. What were
you
expecting me to do ?
On 4/4/07, Borut Bolčina [EMAIL PROTECTED] wrote:
Sorry, I was in a bad mood this morning.
Just now I tried again with 4.1.2 to see if OGNL-16 is still the problem
and guess what - it isn't. I will continue with 4.1.2-SNAPSHOT.
Thanks for all the hard work Jesse!
Best,
Borut
Jesse Kuhnert wrote:
I'm not sure that's how it normally works.
Hi all,
I cant get dojo EventListener to work.
The same happens with me :( Are there any preparatory steps to perform
to use EventListener? I have a template :
MyTemplate:
span jwcid=@Shell title=.:: Title ::.
doctype='HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN'
Jesse Kuhnert wrote:
Offhand I'd say the PageEvent object looks suspicious. It supports a
BrowserEvent object but might just pass your method by if it sees a
parameter it doesn't know about.
My experiments with a method with no arguments are also failing...
@EventListener(elements = someId,
Jesse Kuhnert wrote:
Offhand I'd say the PageEvent object looks suspicious. It supports a
BrowserEvent object but might just pass your method by if it sees a
parameter it doesn't know about.
What effects in the rendered page source should such annotation cause?
Currently I'm not seeing
Yeah you should see something along the lines of :
dojo.event.connect(dojo.byId(someId), ... .
towards the bottom of your page.
You might also try using Tapestry 4.1.2 instead of 4.1.1. They should
both work equally well but I can't remember if 4.1.1 had any issues in
this area or not.
On
I don't think onClick will be a valid js event name to listen to. In
this instance it has to be onclick .
On 4/3/07, Wojtek Ciesielski [EMAIL PROTECTED] wrote:
I've made it ultra-simple...:
SimplePage.java: ===
public abstract class SimplePage extends BasePage {
private static
Hello,
event listeners aren't called in components, only in pages. I had the
same problem and then moved the listener to enclosing page. See
@EventListener in Border post.
-Borut
On 3.4.2007 13:55, Wojtek Ciesielski wrote:
Hi all,
I cant get dojo EventListener to work.
The same happens
Ah .It could be that element event listeners don't work in
components, but component event listeners will work.
Did anyone file a bug for that?
On 4/3/07, Borut Bolčina [EMAIL PROTECTED] wrote:
Hello,
event listeners aren't called in components, only in pages. I had the
same problem and
Filed under
https://issues.apache.org/jira/browse/TAPESTRY-1398
Jesse Kuhnert wrote:
Ah .It could be that element event listeners don't work in
components, but component event listeners will work.
Did anyone file a bug for that?
On 4/3/07, Borut Bolčina [EMAIL PROTECTED] wrote:
Hello,
Resolved as not valid. :)
Just so everyone else is clear, elements component event listeners
work equally well in components as they do pages.
On 4/3/07, Borut Bolčina [EMAIL PROTECTED] wrote:
Filed under
https://issues.apache.org/jira/browse/TAPESTRY-1398
Jesse Kuhnert wrote:
Ah .It
12 matches
Mail list logo
