ember-cli-bootstrap-sassy | a fork of ember-cli-bootstrap-sass | Style Language library
kandi X-RAY | ember-cli-bootstrap-sassy Summary
kandi X-RAY | ember-cli-bootstrap-sassy Summary
fork of ember-cli-bootstrap-sass without any references to now defunct bootstrap_for_ember.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ember-cli-bootstrap-sassy
ember-cli-bootstrap-sassy Key Features
ember-cli-bootstrap-sassy Examples and Code Snippets
Community Discussions
Trending Discussions on ember-cli-bootstrap-sassy
QUESTION
We start with a new application, using Ember 3.8 and bootstrap/SASS. There seem to be two add-ins available which support bootstrap within Ember, ember-boostrap and ember-cli-bootrap-sassy.
While the former implements ember components for most of the bootstrap features and also "replaces" the original bootstrap.js by it's own implementation, with the latter, it seems I can still use all the original components and js implementations.
From first glace, I would be much more comfortable with ember-cli-bootrap-sassy, since I could still use all bootstrap examples from the web, and having a "customized" version of bootstrap.js also seem somewhat counter-intuitive to me. Also, what about all the bootstrap features ember-bootstrap does not implement, but I still require? It seems like I might be ending with an appliation which would use ember-bootstrap, but additionally uses all sorts of "workarounds" for things not implemented.
Since I don't have much experience in this field, I would be glad for some recommendations and insights from experts.
...ANSWER
Answered 2019-Mar-05 at 11:50So first of all a disclaimer: as the author of ember-bootstrap
, I am certainly a bit biased here! ;)
But I think I have strong arguments in favor of ember-bootstrap
, otherwise I wouldn't have invested that ton of work. So the main one is that it follows the programming model of Ember, while using bootstrap.js
directly doesn't and would often feel awkward in an Ember app:
- You use components to render things, which in turn render the trivial markup that Bootstrap expects, rather than spreading Bootstrap flavored static markup all over the app
- Components in
ember-bootstrap
strictly follow the so called "Data down Actions up" (DDAU) programming model in Ember - that means through declaratively assigning properties which create data bindings, the state of your app "flows" through your UI, so the rendered DOM is a direct function of your state. This is the "Data down" part, which is different than having to imperatively "call" things to achieve the same effect (like
$('#myModal').modal('show')
) - When the user interacts with your UI, actions are called, which are handled somewhere up the component tree (e.g. in a controller). These transform your state, which is used to update the UI again (unidirectional data flow)
If that sound too abstract, take this simple example of a modal component. In ember-bootstrap
you would do something like this:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install ember-cli-bootstrap-sassy
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page