Hi Eric, thanks for the feedback.
There are several reasons I'm doing it: - Polymer.dart is very limited without a set of elements - It helped a lot learning what Polymer can do - and how it is done by people with more Polymer knowledge than I have/had - I think it also helped the Polymer.dart team pushing Polymer.dart forward because I filed (a lot of) issues when polymer-elements used functionality not yet available in Polymer.dart. - the community seems to like the effort (according to the feedback). - I also ported several bugs ;-) which were found in the Dart polymer-elements and also reported to you (I myself filed a few) - probably a few more I can't think of currently ... I understand that the elements are evolving I don't want to complain. I just was a bit confused by the recent changes. What do you think is the best way to get updates about progress/changes/...? I subscribed most of the related GitHub repos but they repeatedly get lost because it seems they were recreated several times. Is there a public place where you maintain issues? Günter Mit freundlichen Grüßen Günter Zöchbauer [email protected] +43 (699) 10 18 87 15 On Tue, Apr 8, 2014 at 6:21 PM, Eric Bidelman <[email protected]> wrote: > I'm not sure there's much of a strategy other than cleaning up our > offerings and making it more clear what is fully baked vs. a WIP. > > We're still in the process of refining what that core-* element set is. > Some of the more useful polymer-* elements have been moved over and seen > updates, gotten documentation, cleaned up, etc.. Others have simply been > renamed (for now). Just note that the core-* set are the elements the > Polymer team will invest in moving forward. Everything in PolymerLabs > remains experimental until we feel it's ready for prime time. > > IMHO it's too soon to port an evolving set of elements...but no one is > stopping you :) > > > On Mon, Apr 7, 2014 at 11:07 PM, Günter Zöchbauer <[email protected]>wrote: > >> Hi, >> >> I'm porting polymer-elements to Dart. Currently I'm working on >> polymer-animation and polymer-overlay. >> I just saw that you moved several elements from PolymerLabs to Polymer >> and renamed them >> for example from polymer-overlay to core-overlay. >> In this case it seems you also stripped some functionality (no dependency >> on animation). >> Other elements seem unchanged apart from the new name at least at first >> glance. >> >> Can you please tell a a bit about the strategy behind this decision, so >> that I can decide where it >> makes sense to focus time and energy? >> >> Thanks! >> Günter >> >> 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/6ec44a0b-51b2-4f21-9fc5-ae541a662fd1%40googlegroups.com<https://groups.google.com/d/msgid/polymer-dev/6ec44a0b-51b2-4f21-9fc5-ae541a662fd1%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/CAGs5rfZ9Ksznuu76COL_qBKve7TL1Dv0bQFzfPeJyo9%2Bb57OdA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
