Hey polymer folks, I use angular in my big project for a lot of the heavy lifting - app scaffold, dependency injection, routing, and so forth. I'm currently using polymer 0.5 mainly to utilize the core- and paper-components as a UI library. I built like one custom element of my own, an iconset (I had some others, but it ended up being easier to just compose polymer stuff into angular directives). I'd hoped to stick with 0.5 until angular 2.0 solidified, which apparently makes webcomponent integration a bit easier.
Some of my users don't use chrome, and this presents a particular problem, because it seems like there's an incompatibility between webcomponents.js (the heavy one with polymer 0.5.5) and quilljs (a nice text editor that uses a great rich-text internal representation instead of html and emits deltas against that). Quilljs chokes from time to time on document.getTreeWalker(node) - the nodes its getting are not instances of Node, according to Firefox and (some) Safari. This kind of makes sense, but is unfortunate. This happens even in a basic test case with a quill object on screen and webcomponents.js loaded and nothing else. I've confirmed that webcomponents-lite 0.7.0 is however compatible with quilljs. So my goal now is to port my UI from using polymer's 0.5.5 library to the paper- and iron- stuff of 0.9. I recognize that not all the polymer elements have been ported across yet, but the key structural ones I use (header panel, drawer panel, toolbar) all exist. Ideally, I want to have a handle on this whole process so that when google i/o is over and there's at least the expected level of releases in the rest of the polymerelements stuff (there's a lot of momentum already), that the port will be mostly done. If I can get the interface built, I can go in and fiddle with the CSS I was using in place of the theming controls that you now provide. That said, I *was* using ng-polymer-elements to handle property binding and general boilerplate stuff for the communication between angular and polymer. I doubt that this library has been updated; it's still in 0.2.0 and hasn't been touched in a while. Given the differences to polymer between 0.9 and 0.5, it's probably not going to work. So. Given this setup, and a real desire to use the polymer library with angular 1.4, has anyone done anything along these lines? Any pointers? I started super-basic, just changing my dependencies and running, but I'm already running into some issues with the angular bootstrap cycle. At the very least, I'll post updates so other people can follow along if they end up doing the same thing. e Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CABsi40JkajVZKHdneTwV3f6tVt-%2BnfUx7KrTpcx8yZPJYP90hg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
