question about critique from angular

99 views
Skip to first unread message

agd...@gmail.com

unread,
Dec 29, 2014, 3:05:11 PM12/29/14
to polym...@googlegroups.com
Hi
I can not really decide which of the many available solutions should I use for my next projects.
Polymer looks quite good, but during my research I found this: https://docs.google.com/document/d/16O2Im1ekfdJ4FU8FBbVRYGjqsXjmcV3tYFg1vyfhYC8/edit
I might want to use Polymer with Angular and I worry that the two won't play together.
Are the issues mentioned in the above document still relevant ?
Thanks
Gabor

Rob Dodson

unread,
Dec 29, 2014, 5:33:23 PM12/29/14
to agd...@gmail.com, polymer-dev
Yes today there is still the issue that angular cannot bind to data coming out of a Polymer element.

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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/9d7a234e-e79c-4e76-8bb6-e3e5b767290e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sébastien Cevey

unread,
Dec 29, 2014, 5:52:47 PM12/29/14
to Rob Dodson, polym...@googlegroups.com, agd...@gmail.com

The following issue was a complete blocker for us to use Web components and AngularJS together:

https://github.com/angular/angular.js/issues/8598

In short, Angular hit a known shortcoming of the platform polyfills which meant including the platform script completely broke the app in FF.

Does anyone know if it has been fixed at either end?

I unfortunately can't test right now, but should be a matter of updating the jsbin example to pull the latest versions of Angular and webcomponents-js.


For more options, visit https://groups.google.com/d/optout.


Visit theguardian.com. On your mobile and tablet, download the Guardian iPhone and Android apps theguardian.com/guardianapp and our tablet editions theguardian.com/editions.  Save up to 57% by subscribing to the Guardian and Observer - choose the papers you want and get full digital access.  Visit subscribe.theguardian.com

This e-mail and all attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender and delete the e-mail and all attachments immediately. Do not disclose the contents to another person. You may not use the information for any purpose, or store, or copy, it in any way.  Guardian News & Media Limited is not liable for any computer viruses or other material transmitted with or as part of this e-mail. You should employ virus checking software.
 
Guardian News & Media Limited is a member of Guardian Media Group plc. Registered Office: PO Box 68164, Kings Place, 90 York Way, London, N1P 2AP.  Registered in England Number 908396


agd...@gmail.com

unread,
Dec 29, 2014, 5:55:24 PM12/29/14
to polym...@googlegroups.com, agd...@gmail.com
Hi Rob,

Thanks for your answer. I saw that angular can not bind to data from Polymer elements and I also saw a few possible workarounds.
What I tried to find out with my question is whether Polymer tries to address the "problems" that are mentioned in that document ?
From the document I could not find out when it was written.
I saw a talk about the upcoming 0.8 version on youtube and to me it sounded like a major rework so I wondered that maybe such a major rework could also
fix some of those shortcomings.

Thanks

Gabor

Rob Dodson

unread,
Dec 29, 2014, 6:11:31 PM12/29/14
to Sébastien Cevey, polymer-dev, agd...@gmail.com
Does anyone know if it has been fixed at either end?

Not that I know of. That thread seemed to trail off on the Angular side. Might be worth pinging them again? 

Rob Dodson

unread,
Dec 29, 2014, 6:19:28 PM12/29/14
to Gabor Dolla, Steve Orvell, polymer-dev
That doc is new to me so I'm not sure if those points are being specifically addressed. +sorvell who may know more.

Sébastien Cevey

unread,
Jan 1, 2015, 10:52:38 AM1/1/15
to Rob Dodson, Gabor Dolla, Steve Orvell, polymer-dev
I've bumped the thread at https://github.com/angular/angular.js/issues/8598 after confirming that the bug still occurs with the latest version of angular and webcomponents, let's see if we hear back from the Angular team.

As far as I'm concerned, this completely undermines the core idea that webcomponents could be the future bricks that other frameworks such as angular would build upon, and it'd be a shame not to get fixed ASAP so people can actually start experimenting in that direction...

It'd be interesting to hear from people who may have experienced with web components in combination with other frameworks (ember, etc). I must say I haven't seen much in that light online to this date.


For more options, visit https://groups.google.com/d/optout.



--
Sébastien Cevey
Software Developer
Reply all
Reply to author
Forward
0 new messages