After reading your last comment that made you unhappy ;) I checked it
out
Yeah - putting assets in ${context} is going to be removed in tapestry-5.5
and is there for backwards compat for 5.3
So after reading [1] & [2] & [3] and a few failed attempts
moved bootstrap main dir from src/m
Well I got my app to launch. Not sure if its correct... i thought everything is
suppose to go into the META-INF/assets directory according to the new
documentation
anyway
I had to eliminate
@Contribute(ModuleManager.class)
public static void setupBaseModules {...}
altogether... t-5.4-b
The transition functions also live in bootstrap.js - something I was happy
to not know before :(
you'll have to do more testing on the non-tapestry side - i've cobbled
together what works for me, un-optimized, i.e. full dist.
so ... when you run an app in node and browse to it, is transiti
my last reply bothers me though...
transition.js is built into bootstrap.js
so I assume there will be a conflict somehow ?
Thanks Chris for your gracious help
its really appreciated.
YEAH... there is an upper dir in my node platform housing the js file
Transition.js for bootstrap. I didnt know if it was touchable ornot...it was
not built into the dist dir
And I am not sure if they are usable as-is or if they were
then I added this
@Contribute(ModuleManager.class)
public static void setupBaseModules(MappedConfiguration
configuration,
@Path("context:assets/js/bootstrap.min.js") Resource bootstrap,
@Path("context:assets/js/jquery.min.js") Resource jquery )
{
confi
hi ken,
short answer:
download transition.js into your js directory. does your custom
distribution contain the relevant js?
test your distribution against plain html/css/js from
http://getbootstrap.com/getting-started/#examples
unabridged:
I just looked in _my_ src/main/webapp/assets/boo
