In my experience, yes, that's reasonable...but don't expect your learning to stop at that 4 to 5 weeks since there's a lot of stuff under that top layer :)
Also, you might well find that Polymer doesn't meet all your needs....it is quite a different animal to other libraries out there...so you might find that you'll want to try to use another lib too. I haven't found such a need personally, but some colleagues have been using requirejs and low-dash. It really depends on the app you're porting, imo. Perhaps it's best to really examine how polymer can be used first and see how it can fit into your current app's architecture - perhaps it's not a matter or porting at all, but identifying what can be made into stand-alone components and using polymer for those....the work can then be done in stages :) That's my tuppence-worth anyway. Hth. Max. 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/CAMZCrPh3jHFMgf8BJcjNjMg3LdU1m1yRHYZufQFyEBtGVDUs1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
