Upgrade to Hybrid mode

[myfrom]

It would be great if this element would support the latest Polymer 2.0 in hybrid mode.

Who will use the feature? Developers building 2.0 apps/elements
When will they use the feature? Whenever they want to use Polymer 2.0
What is the user’s goal? Having support for latest version of Polymer

It would require those four steps:

• Move style to <template> (It should be done even in 1.0)
• Replace content with slot
• Ensure CSS supports new specs
• Update bower.json
• Update tests
• Ensure scripts support new specs (doesn't require drastic changes, hybrid mode has got legacy functions)

[MeTaNoV]

@Witus13 After a short break, I'll be working on this one as a priority, do not hesitate to provide assistance in the upcoming PRs!

[brawat]

Hello @MeTaNoV any progress in upgrade, is there some work around that we can use iron-swipeable in polymer 2 or is there any alternative component with similar feature

[myfrom]

@brawat I was able to get 2.0-preview branch of this repo to work. However, when doing $ bower install you need to specify -F or answer tons of questions about which version to use

[brawat]

the current version of iron swipeable is not behaving as it was in polymer 1.0, i can see no such error, i tried to change content tags of iron-swipeable.html to slot as per polymer 2.0, in this case i am seeing all the different pages(swipeable pages) in a single page

[MeTaNoV]

@brawat I am still lacking time to finalise the upgrade and am really thankful for the contribution of @myfrom and others! It should be however finished by the Polymer Summit 2017, as well as some of my other components and some other new! Patience at this point is required!