Dear Onno,
I understand your solution, but that just introduces a second "tapestry
supported" javascript library. What if yet another library is better at
some point, or some people prefer another one like yui or dojo (remember
this was the "preferred" in t4 days, not that long ago).
Do we really want to include jQuery as well in tapestry itself?
I would suggest having one or more projects on tapestry360 which contain
the javascript libraries. These can then be included using
@IncludeJavaScriptLibrary and a classpath location (preferably defined
as a constant), avoiding the double inclusion.
Kind regards,
Joachim
Onno Scheffers wrote:
The reason that happens is because jQuery isn't officially supported, so
each component would ship with jQuery..
The way I set things up currently, jQuery is supported like Prototype or
Blackbird are supported. So jQuery will be shipped with Tapestry. This will
make sure all component-creators use the same version.
They can have it included into the page by using the
@IncludeJavaScriptLibrary annotation and a predefined path
(tapestry.jquery). Tapestry automatically makes sure only 1 version is ever
included into the page, even if multiple component include it.
The double inclusion will only be a problem if you're using different 3rd
party Tapestry components that each also ship with the full plugin. Then the
same library is included twice simply beause they are on different paths.
regards,
Onno
--
Joachim Van der Auwera
PROGS bvba, progs.be
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
