We built Polymer to be just exactly "the kind we like" ( http://i.imgur.com/PIfD0.jpg), so we tend to use it exclusively.
But our intent has always been to support interoperability, so that users could choose whatever superstructure they prefer. Scott On Fri, Jun 27, 2014 at 10:37 AM, <[email protected]> wrote: > Hi all, > > First of all, big thanks to Mo for asking the question. I've just watched > the Polymer videos from Google I/O 2014 on the technology and it looks > amazing. > > I would like to ask if the Polymer team considers the platform ready to be > used as a standalone system to build single page applications? or do you > recommend a framework of some kind (is Angular 2.0 ready enough yet?) or > EmberJS to provide the application structure? > > Cheers, > > Chris > > > On Friday, June 27, 2014 10:37:33 AM UTC+1, [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/cbc9f816-1e03-4d67-a170-bcdb38ccc621%40googlegroups.com > <https://groups.google.com/d/msgid/polymer-dev/cbc9f816-1e03-4d67-a170-bcdb38ccc621%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > 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/CAHbmOLYWrFw5RqNXmZQLRwr068bYtsAgR0fK6eYN-cOsa3g83A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
