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 issues.
On Sep 5, 2013, at 4:54 PM, Dimitris Zenios wrote:
> 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<Trait,
> Boolean> configuration)
> {
> configuration.add(Trait.SCRIPTACULOUS, false);
> configuration.add(Trait.INITIALIZERS, false);
> }
>
>
>
> On Thu, Sep 5, 2013 at 11:52 PM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote:
>
>> 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: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
