I always use the override option so I know what version I'm using and like
Chris said, don't want to be locked into shipped version.
AppModule has
configuration.add(SymbolConstants.BOOTSTRAP_ROOT,
"context:assets/bootstrap");
configuration.add(SymbolConstants.JAVASCRIPT_INFRASTRUCTURE_PROVIDER,
"jquery");
No problems with bootstrap/jquery ever. When I first introduced this into
my workflow I checked the html source code was including the right stuff -
it never failed to deliver.
my bootstrap sources are in
src/main/webapp/assets/bootstrap/
This is the dist directory of a bootstrap sources d/l.
I don't recall doing much js modal stuff, but for 3rd party jquery and
jqueryui libs you need to @Import them in your base page/component - e.g.
jquery.cslider.js, owl.carousel.min.js, jquery.prettyPhoto.js. etc.
The order in which you import the js files has been a potential gotcha -
but this happens in plain old html anyway.
The other thing you may want to include is font awesome in your base
component
@Import{....
"context:css/font-awesome.min.css",
....}
On Tue, 07 Oct 2014 02:15:42 +1100, Chris Poulsen <mailingl...@nesluop.dk>
wrote:
We use the BOOTSTRAP_ROOT override to use a custom bootstrap build with
product specific styling and because we do not want to be locked on to
the
bootstrap version supplied with tapestry.
This has worked well so far.
If there are documentation pages mentioning disabling bootstrap as the
"recommended practice" they should most likely be revised.
In general the "recommended practice" is not to specify anything as the
framework aims to do the right thing by default.
--
Using Opera's mail client: http://www.opera.com/mail/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
