3 ms·
I would advise against the 'less-rails-bootstrap', 'compass-bootstrap' gems and whatnot (there's a whole bunch of them). I tried a few of them before resorting
by moe 15y ago
I would advise against the 'less-rails-bootstrap', 'compass-bootstrap' gems and whatnot (there's a whole bunch of them).
I tried a few of them before resorting to embedding bootstrap as plain less.
The gems did either not work at all for me or did not support 2.0-wip, and none had a clear upgrade-path (the sass-compiler chokes on 2.0).
Generally I've become strongly biased against the practice of bundling CSS/JS-libraries as gems. It never seems to work quite right (only jquery ever went smoothly for me) and they always seem to introduce an ungodly amount of magic. - When all you really want is drop a few static files into vendor/assets...
- shibboleth 15y agoI created a fork of less-rails-bootstrap a few weeks ago and put 2.0-wip on it pretty easily in an hour or so. A week or two after that 2.0-wip was pushed to the master branch on that project. What issues were you having exactly?
- sjp3 15y agoI updated a rails project yesterday that was using less-rails-bootstrap. The entire process to upgrade from 1.4 to 2.0 took a few seconds. The tedious part was updating css class names for alerts, modals, form styles, etc.
- l4u 15y agoIf you use scss/sass instead of less, try https://github.com/thomas-mcdonald/bootstrap-sass/tree/2.0 https://github.com/thomas-mcdonald/bootstrap-sass/tree/2.0