I haven't looked closely at prototype.js, or the getTransport function. That
said, Javascript is a dynamic language that allows you to redefine
functions, why not just load prototype.js and then load your extension js
with the new implementation of getTransport?
Josh
On Feb 13, 2008 3:45 AM, leb
With a bit of research I answered my own question!
Thanks again for your help.
lebenski wrote:
>
> This looks great thank you. I am new to Tapestry and can't find the file
> containing application defaults that you mention. Could you please
> provide further details about exactly which file
You don't need to modify any file, you can do it the Tapestry way, by
contributing to a service.
You should read this to understand the concept better:
http://tapestry.apache.org/tapestry5/tapestry-ioc/symbols.html
In your use case you should add the following method to you module
builder class:
This looks great thank you. I am new to Tapestry and can't find the file
containing application defaults that you mention. Could you please provide
further details about exactly which file I need to modify.
Many Thanks,
Ben.
HugoPalma wrote:
>
> I don't think you can remove the inclusion of
I don't think you can remove the inclusion of the prototype.js, but you
should be able to change the base path where Tapestry looks for the
scriptaculous files enabling you to provide your own implementation.
Tapestry adds the "tapestry.scriptaculous.path" symbol to the factory
defaults with the v
FYI I am using Tapestry 5.0.7-SNAPSHOT.
--
View this message in context:
http://www.nabble.com/Help%21-Turning-off-auto-import-of-prorotype.js-from-Tapestry-JAR-tp15456459p15456463.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
Hi,
I have a requirement to remove the auto import of the tapestry bundled
version of prototype.js. I am implementing this:
http://www.jimbojw.com/wiki/index.php?title=SWFHttpRequest_Flash/Ajax_Utility
to facilitate cross-domain javascript. The elegant implementation of this
requires a minor ch
