You are right about the prototype bit, Dimitris.
I confused JavaScript prototype with the Prototype framework, and there was
another JS lib
(unrelated to tapestry) in my code that was bringing in prototype and confused
me some more :)
Alas, all the other issues that I brought up are still valid
Datepicker does not depend on prototype from what i remember.Did you add
this to your appmodule?
@Contribute(Compatibility.class)
public static void disableScriptaculous(MappedConfiguration configuration)
{
configuration.add(Trait.SCRIPTACULOUS, false);
configuration.ad
FYI-
It appears that Datepicker is dependent on prototype. So, basically, every
page that uses dates
brings in prototype, even though I am trying to do clean-sheet JQuery /
Bootstrap development...
-
To unsubscribe, e-mail:
