Closed sgasser closed 9 years ago
Not being super familiar with the actual spec, in what ways has material css deviated? It does seem silly to have 2 (or more) add-ons with the same goal but I have to be honest that I don't love the angular material experience on my android phone. I did happen to notice @miguelcobain has asked the same question. I'd like to hear what the two of you think would be the best for both projects whether that be to combine them, leave this one, whatever.
id use ember paper but it doesntt have grid like bootstrap or materialize.....i totally get that its not a css framework...but if they'd add a responsive grid as a component,....that would be awesome...
-ember paper does not have a top nav-->i didn't find it, which is awesome
ember -materialize-components are something that ember -paper may look upto...ie the card-reveal component... :+1: a parallax one :+1: top-nav with mobile reponsiveness :+1: a pagination-one :+1:
some ideas that materialize has are awesome like scrollspy :+1: ...
if we can find a way to get the awesome materialize-like components working on ember-paper that would be awesome
but its sad that everyone is duing his own thing.
i would love it if we left ember-materialize in a state where when the addon is added, everything works from those materialize components that need jquery initialization to those that don't ,so those ones could have their own components made, just to avoid having to hack around when trying to get something to work, but the other components, i have to agree we are doing duplicate work
angular material has some really awesome stuff * but they use a really ugly font :-) its much cooler on reacts material addon
but otherwise i don't think using materialize without components is that hard,but definately ember paper should borrow from materialize
@BransonGitomeh Ember-paper has a (still undocumented) flex grid (more info).
angular material has some really awesome stuff * but they use a really ugly font :-) its much cooler on reacts material addon
The font is roboto in both of them. Not sure what do you mean.
@sgasser I raised a similar question before https://github.com/miguelcobain/ember-paper/issues/17 as you know. The conclusion was that ember-paper has a value on its own. Many arguments are in that issue.
From what I could find, there isn't any complete material design implementation. Ember-paper borrowed a lot from Angular material, but not all of them. Material menus, for example, is something we're working that isn't on Angular material. Maybe someday we will be the ones inspiring angular material folks (would be glad if that happened!).
I like also the idea that ember-materialize should only be a wrapper with a minimal configuration like jquery initialization, etc.
And we all should work together on Ember Paper.
@rynam0 what do you think? Are you interesting to work on Ember Paper?
I could imagine myself contributing to ember-paper when we have the components in place that require jquery initialization.
A new addon has entered the space: ember-material-design https://github.com/mike1o1/ember-material-design/issues/8
YAP, AND IT LOOKS GOOD, REALLY GOOD :-)
There is another Material design addon for Ember called Ember Paper by @miguelcobain.
Materialize CSS has much more css elements, javascript plugins, components, etc. But Materialize CSS isn't the most adherent to the spec. Ember Paper look much better based on Angular Material and things are done the ember way and no external libraries are included or required,.
Should we all work on the Ember Paper and ember-cli-materialize will be only a wrapper for Materialize CSS without components?