On Fri, 19 Oct 2012 23:29:34 -0300, Kalle Korhonen
<[email protected]> wrote:
I think you may be underestimating the value of the ecosystem around
the core Tapestry 5. By now, there are lots of well supported
libraries that are commonly used in Tapestry 5 projects. All in all,
just missing the Tapestry and T5 namespaces on the client doesn't look
all that bad to me but I think we could greatly ease the pains of
community upgrading with a long alpha cycle with public releases and
actively encouraging and helping the library developers to upgrade
their libraries to 5.4 before a GA release.
Agreed. Having a T5.4 which doesn't work at all with JavaScript code
written for T5.3- is a big no-no for me. We should have some way of making
that happen, even if we end up with a solution in which you either use a
T5.3- compatibility mode (which would be the current 5.3 one) or the new
T5.4 JavaScript foundation, but not the two at the same time.
Howard, are you saying that code that use JavaScriptSupport.addScript() et
all wouldn't work anymore in T5.4? Or just the code using the Tapestry and
T5 JavaScript objects?
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
