On Wed, 06 Aug 2014 06:56:30 -0300, <peter.sk...@ooom.at> 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. (Great Job guys!! Thanks!)
Nevertheless in both of these projects I end up with modifying of one of
the tapestry own javascript modules, namely t5-core-dom-prototype.js
(t5-core-dom.coffee in the source distribution) in the dame way, by
adding a this function to the module exports:
You don't need to do that. Just monkey-patch it. This is JavaScript, so
all public functions are overridable. Check this:
http://me.dt.in.th/page/JavaScript-override/.
does not work with Ajax requests on IE8. It may be of little concern for
the most of you, but should someone need it, this is the solution. As
selector you define the form, which triggers the Ajax request.
Have you filed a JIRA about this?
I would appreciate if someone could share her/his experience with more
complex pages (several forms and several Ajax zones) working under T 5.4
especially in regard to performance. My feeling is that the reaction time
increased in T5.4 compared with 5.3.7 and that it is the client that
needs more time to trigger the actions.
Have you done any time measurements?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
