I created a module with a provider and service that integrates W3C Custom Element APIs w/ Angular element directives.
https://github.com/dgs700/angular-custom-element You can define custom elements in a .config block x-tags style, and then data-bind their custom properties to a matching directive. Trying to follow, as best as possible, the thinking in the design docs for 2.0 component directives. The idea is to be able to export / import and share the elements (web components) w/ other frameworks in the page, and be suitable for production code in current (modern) browsers. Given that this module doesn't actually solve any immediate functionality problem, its tough getting people to use and test it for feedback. I'm particularly interested in the *future patterns and best practices* concerning stuff like how much data or functionality to encapsulate or initialize in the element vs. keeping in the framework, i.e. directive controller, and how. Also interested in inter-element communication, events, etc. So putting this out there if anyone has some spare time to kill. -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
