Yes, they will need to have compatible versions of Polymer to work together (to the best of my knowledge), just like jQuery plugins have to have a compatible version of jQuery to run properly.
This is going to be 100x more painful today than it will be once Polymer reaches 0.9/1.0 -- presumably at that point the API will be very stable and breaking changes will occur infrequently. On Sunday, November 23, 2014 7:32:14 PM UTC-8, Walter Rumsby wrote: > > Hi, > > As far as I can tell Polymer is a global object in the browser. > > Let's say I have a page that pulls in multiple components. Say a couple > from http://googlewebcomponents.github.io/ and say a couple I wrote > myself. For whatever reason I can't Vulcanize all the components together > (although I can Vulcanize the set from googlewebcomponents and the set I > wrote myself). > > Does this mean that both sets of components need to use the same Polymer > version when running on a page? I'm worried that unless there is guaranteed > backwards compatibility (which I assume can't be the case with a < 1.0.0 > release) then running the most recent version of Polymer isn't guaranteed > to work. > > Thanks, > Walter > 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/31a01898-88c9-4709-ab50-b83ec15da467%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
