41–50 of 77 posts
Earlier quoted context omitted.
I'm curious, what's keeping you from trying Polymer? Its paper-elements are a very good implementation of Material Design, and the library is very light weight.
Most of my apps are built with Ember, and I just haven't quite figured out how to marry them both.
You don't have to do anything special.
1. import polymer html file 2. use it
thats all there is to it.
So, I just wanna say I am absolutely, incredibly excited for this. I've loved the design of paper-elements, but I don't want to attempt integrating Polymer into my projects. That being said, the use of BEM is a huge turn off. The markup for a simple card uses seventeen different classes, which is absolutely a nightmare to memorize. For comparison, a card from Materialize uses only five to seven classes (depending on…
Thanks for the feedback. We used BEM as we find it helps with the long-term maintainability of CSS/SASS codebases (there's also copy/paste support on all of our snippets). That said, if you find the use of BEM a turn-off, we welcome folks just taking our styles and adapting them to the naming scheme that makes most sense for them. Anything that helps.
Any idea when we can expect these to make it to polymer 1.0. Basic components like dropdowns/cards are missing atm .
What are the differences between this one and http://materializecss.com/ ?
It'd be great to see this work with Bootstrap.
[1] http://materialdesignblog.com/15-awesome-examples-of-materia...
Earlier quoted context omitted.
Most of my apps are built with Ember, and I just haven't quite figured out how to marry them both.
its just html tags? You don't have to do anything special. 1. import polymer html file 2. use it thats all there is to it.
Earlier quoted context omitted.
Most of my apps are built with Ember, and I just haven't quite figured out how to marry them both.
its just html tags? You don't have to do anything special. 1. import polymer html file 2. use it thats all there is to it.
If you use the newer, lighter-weight shady-dom version of the polyfill, which is a lot more responsive on non-Chrome browsers and doesn't introduce the bug indicated in [1], you must do all DOM manipulation via polymer's local DOM api, in order to properly distribute dom elements.[2]
That means, if you want to use polymer, you cannot use angular or ember (for example). Specifically, DOM manipulation via those libraries ends up just using regular calls against element.appendChild, but those appended elements, if they are polymer elements, end up not properly working (event listeners don't attach and styling modifiers don't apply), because you didn't use polymer.dom to go via polymer's local dom API.
I found out about all of this the hard way, and now I have a webapp that works great on chrome, but users cannot use the rich text editor on anything except chrome. Which eliminates all iOS browsers entirely.
1: https://github.com/webcomponents/webcomponentsjs#execcommand...
2:https://www.polymer-project.org/1.0/docs/devguide/local-dom....
So, I just wanna say I am absolutely, incredibly excited for this. I've loved the design of paper-elements, but I don't want to attempt integrating Polymer into my projects. That being said, the use of BEM is a huge turn off. The markup for a simple card uses seventeen different classes, which is absolutely a nightmare to memorize. For comparison, a card from Materialize uses only five to seven classes (depending on…
I'm curious, what's keeping you from trying Polymer? Its paper-elements are a very good implementation of Material Design, and the library is very light weight.