On Saturday, October 8, 2016 at 10:29:27 PM UTC+1, Richard Feldman wrote: > > I'm catching up on this thread...so much impressive progress! :D > > It seems like: > > - registerElement is enough to get node "my-component" and on > "my-component-event" (with a custom decoder) working in Elm > - With the webcomponents-lite.min.js polyfill (16K gzipped), you can > get registerElement working on IE11+ > - Polymer components in particular... > - Require using Bower > - Reuquire at least webcomponents.min.js polyfill (36K gzipped) for > Polymer components which depend on Shadow DOM > - Polymer 1.0 components that use Shady DOM should still work with > the smaller webcomponents-lite polyfill > > Chrome has support for webcomponents built in, so you do not even need webcomponents.js at all. Firefox seems ok with the shady DOM version, so works with webcomponents-lite.js.
Also, I looked a bit into creation webcomponents without polymer, but you really are starting with basics that polymer provides for you. Polymer comes in -micro, and -mini flavours too, the feature of the various flavours are listed here: https://www.polymer-project.org/1.0/docs/devguide/experimental We are currently using the full version, so that we can do: app = Elm.Component.embed(this.$.embed, { count: this.count }); and Polymer knows from this.$ which DOM node to attach Elm too. Also we are using proeprty change notifications from the full version, so it looks likely that the full version of polymer is needed if using polymer, and that polymer is a very useful library for basing this on. Next up, run vulcanize to assess the size cost of full polymer and the various webcomponents.js if they are also bundled. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
