Ah good good..
I'm not sure if it was announced yet or not but I'll probably be integrating
the new 0.9 version of dojo in a 4.2 tapestry release. The internal
bickering is done and the performance / no code bloat people have won. The
library has also been broken up into three modules to make t
> What do you mean by forbidden? And also by changing page
> properties in an XHR request?
>
> I do this quite often myself so maybe it's just a matter of
> ~when~ you try to change the properties.
Oops, silly mistake in the component. It works perfectly well.
>
> p.s. Have you guys noticed
What do you mean by forbidden? And also by changing page properties in an
XHR request?
I do this quite often myself so maybe it's just a matter of ~when~ you try
to change the properties.
p.s. Have you guys noticed any performance gains? Besides ognl I've been
squeezing every millisecond out tha
vide for some symmetry between native browser
> events and
> > custom methods. I don't really want to make you unhappy,
> however ...
> > ;)
> >
> > > -----Original Message-----
> > > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
> > >
MAIL PROTECTED]
> Sent: Tuesday, May 08, 2007 12:01 AM
> To: Tapestry users
> Subject: Re: How to pass custom arguments to @EventListener
>
> I've been wary of trying to serialize function parameters as
> that could get very tricky on non simple object structures.
> (json recursi
is clearly something which belongs to the
page.
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 08, 2007 8:20 AM
> To: users@tapestry.apache.org
> Subject: RE: How to pass custom arguments to @EventListener
>
> I'm
> Sent: Tuesday, May 08, 2007 12:01 AM
> To: Tapestry users
> Subject: Re: How to pass custom arguments to @EventListener
>
> I've been wary of trying to serialize function parameters as
> that could get very tricky on non simple object structures.
> (json recursion and
I've been wary of trying to serialize function parameters as that could get
very tricky on non simple object structures. (json recursion and such)
I guess if they were acceptable to send to the server "as is" doing the
equivalent of a toString() on them I could add that in. (but not be happy
abou
