homework done
> On Wed, 06 Aug 2014 10:38:40 -0300, wrote:
>
>> Hi Thiago,
>
> Hi!
>
>> thanks for the useful link.
>> Many thanks also for the hint - I don't event have to monkey path the
>> t5-dom module, as the "on" method in this module is public. It is enough
>> to call it with the "selector
I am using prototype. What kind of problem is it?
> Are you running with jQuery or Prototype? I just found a Zone event
> problem
> today and when I switched to jQuery it went away.
>
>
> On Wed, Aug 6, 2014 at 12:49 PM, Thiago H de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
>> On Wed, 06 A
Are you running with jQuery or Prototype? I just found a Zone event problem
today and when I switched to jQuery it went away.
On Wed, Aug 6, 2014 at 12:49 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Wed, 06 Aug 2014 12:22:24 -0300, wrote:
>
> I shall do it as soon as pos
On Wed, 06 Aug 2014 12:22:24 -0300, wrote:
I shall do it as soon as possible
Thanks in advance. :) Posting bugs is a contribution to the project. ;)
thanks for your experience. I will try to do some systematical
measurements of the response times on the front end and back end
separately soo
>
>> Hi Thiago,
>
> Hi!
>
>> thanks for the useful link.
>> Many thanks also for the hint - I don't event have to monkey path the
>> t5-dom module, as the "on" method in this module is public. It is enough
>> to call it with the "selector" as the first parameter instead of
>> document.
>
> Nice!
>
On Wed, 06 Aug 2014 10:38:40 -0300, wrote:
Hi Thiago,
Hi!
thanks for the useful link.
Many thanks also for the hint - I don't event have to monkey path the
t5-dom module, as the "on" method in this module is public. It is enough
to call it with the "selector" as the first parameter instead
Hi Thiago,
thanks for the useful link.
Many thanks also for the hint - I don't event have to monkey path the
t5-dom module, as the "on" method in this module is public. It is enough
to call it with the "selector" as the first parameter instead of document.
I haven't filled Jira yet. This is a new
On Wed, 06 Aug 2014 06:56:30 -0300, wrote:
Hi everybody,
Hi!
I am preparing the migration of two tapestry projects from 5.3.7 to 5.4.
A
strong motivation for this is the fact, that die client (java script)
interface is much clearer and easier to handle and to extend in Tapestry
5.4. (Gr
Hi everybody,
I am preparing the migration of two tapestry projects from 5.3.7 to 5.4. A
strong motivation for this is the fact, that die client (java script)
interface is much clearer and easier to handle and to extend in Tapestry
5.4. (Great Job guys!! Thanks!)
Nevertheless in both of these pr
