Right--it doesn't have to be 1:1 since the rules are simple. Also, for example, the utility should probably know that if certain plugins are specified, others are required whether specified or not, e.g., bootstrap-transitions.js, which seems likely to be forgotten is specifying the plugins which use it.
Bill On Apr 23, 2012, at 11:48 AM, JGAui wrote: > That's a great idea, but it breaks down on something like > bootstrap-typeahead.js (needs dropdown.less) > > Maybe I'll add a mapping file to do the work. Thanks for the suggestion > > On Monday, April 23, 2012 11:37:14 AM UTC-7, Bill Lazar wrote: >> >> Greg, >> >> Interesting utility, love seeing the community building things like this. >> >> A couple of suggestions: >> - Don't require users to specify the corresponding css files when >> specifying a JS plugin; e.g., if I'm including -j bootstrap-tooltip.js I >> shouldn't have to include -c tooltip.less. >> - Since the JS files are all named bootstrap-<plugin>.js the -j flag >> should just require the plugin name (tooltip, carousel) rather than the >> full file name. >> >> Both are based on the 'let the computer do as much work as possible' >> principle ;) >> >> Bill >> >> On Apr 23, 2012, at 10:33 AM, JGAui wrote: >> >>> I've written a simple command line tool called Boots. It simplifies >>> creating custom builds of bootstrap. >>> >>> Check it out here: http://projects.jga.me/boots/ >>> >>> Let me know if you have any feedback. >>> >>> Greg >>
