It uses Angular for all its fancy templates and whatnot.
This makes me sad.
Is it possible to integrate this into an Ember app? I know its like asking the Dark and Light sides of the force to dance together at the prom, but one can hope.
I’m still looking at it myself, but I think it’ll take a little work to get a good implementation for ember. I’d like to see an ember-cli addon that uses liquidfire instead of their motion ui, obviously components for everything, and services for model managers and such.
There is also other interest so I’m sure we’ll see something down the road. Personally, I’m waiting for foundation apps 1.0 stuff to shake out, see what Bootstrap 4 offers, and ember 2.0 featuresets to come out before maybe working on an addon myself.
At this point, I think the best option to use Foundation for Apps within an ember-cli project would be to install via bower (manual install section) and use the sass addon (since css isn’t distributed). Although I haven’t done anything myself just yet.
Yep, I would be really interested in Foundation for Apps as well to work with Ember. And I agree with @Panman8201 that we wouldn’t really need the animations, but can use liquid-fire for it. I have used an early version in the past, before the angular implementations and the grid (imo the most important bit) just worked out of the box. Not sure if that changed now, but I wouldn’t see a reason for it having changed.
It seems like Ember need a UI base that could be used with either Foundation, Bootstrap, Material or any css framework. I would prefer people work on a single unified approach than an addon for Foundation, one for Bootstrap, etc.
The core code to create dropdown etc is not different in many of those CSS lib. The main problem is that the markup and class differs between them.
I think it would be possible to load a base component and have different flavor for each CSS lib: overwrite the handlebars, configure the classes, etc.