Hello, I'm a member of the Angular 2.0 team. So, perhaps I can provide some information form our perspective.
One of the main goals of Angular 2.0 is the ability to work with WebComponents. This means *any* WebComponent, including those built with WebComponent libraries such as Polymer and XTags. We've got some of this working already in our templating engine, including two-way databinding to XTags components. We've also go a demo that shows Angular's depdency injection working to inject a custom Polymer component with services. Integration is a pretty important story for us. I think it's important to point out that Angular is really designed around optimizing *application* development (including DI, routing, templating and decorator directives, more advanced databinding) while Polymer is really optimized around *custom element* development. So, it has basic templating and binding and a strong component model. The idea here is that if you want to build a generally re-usable component across frameworks, you would do it with WebComponents directly or Polymer. I expect the community is going to generate a ton of creative content in this way. But, when you want to build an application, you would just import those Polymer elements and use them directly in your Angular app. You would also write application-specific components in Angular. Does that help clarify things a bit from our perspective? PS - The Angular issue and the code you've looked at is probably not our latest templating implementation. That repo has been very volatile over the last few months. At this moment, the branch representing our latest prototype is called "custom-element". You will find the XTag and Polymer integration examples in there. On Friday, June 27, 2014 5:37:33 AM UTC-4, [email protected] wrote: > > Hi all, > > I have a couple question about the future of AngularJS, specifically about > the upcoming 2.0 version, and how it relates to Polymer. I've been through > previous posts on the forums, articles about it on the web and all the > answers I could find from last year. > > Polymer seems to focus on composition of elements on a page, these > elements can be visible or not and can have associated behaviour, combined > with data binding and event dispatching it makes it very easy to share > state and trigger updates when information is changed. Polymer doesn't seem > to address the problem of routing in a Single Page Application (although > there appears to be a few fledgling attempts in the Web Components > community to provide "router" elements). > > In the Topeka example application from the Polymer team, the "sign in" > view doesn't appear to have any kind of representation in the URL. No > hash-fragment, no direct way to reach that view. They do use HTML5 > pushState for history though, although this is manually wired up. > > As far as I can see Polymer handles templating, data binding, data > persistence (via "core-localstorage" etc), modularity (via HTML imports) > and AJAX (via "core-ajax"). The only things that is missing is routing. > > Most questions about how Polymer fits into other frameworks generates the > response "They're just DOM elements, anything that understands the DOM will > understand Polymer elements." This isn't strictly fair when we can already > see that the Angular 2.0 templating will need some additional work to > integrate with Web Components: > https://github.com/angular/templating/issues/9 > > > Where does Angular 2.0 fit alongside Polymer if routing is addressed? How > will they work together? Does Polymer plan to enable support for building > Single Page Applications? > > > Cheers, > > Mo. > 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/59abfa24-6fc2-43eb-8f38-3b435f393182%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
