iron-data-table
iron-data-table copied to clipboard
Saulis
Polymer 2.0
There are some blockers:
-
iron-data-tabledepends oniron-listwhich is blocked by https://github.com/Polymer/polymer/issues/4154 -
iron-data-tableusesPolymer.StyleTransformerto expose rows and cells. This will be moved to shadycss for using with 2.0, and that library is not released yet.
@web-padawan point 1 above is closed by Polymer team. Are we waiting on second one only now?
I'd prefer to wait until Polymer 2.0 gets released, as well as web-component-tester 6.0 which will support testing for both 1.7 and 2.0 versions with different dependencies.
There are some other caveats related to templatizer bugs, especially.
It'll be some time before 2.0 is officially "released". However, many of Polymer Elements are already available in 2.0 preview. As far as I understand - all dependencies must be 2.0 compatible for an app to start testing/migration, so if one is lagging too far behind it might become an issue... just my 2c
agree with @govis. Libraries like these are really key to the adoption of Polymer components (read web components) across frameworks. While I understand the resource and time constraints, I still hope to see more traction in staying at par with the pre-release cycles.
Custom Elements v1 polyfill and HTML imports v1 polyfill are both WIP at the moment.
This makes cross-browser testing unreliable for a while.
iron-data-table is not as simple as most of official UI elements. So I think it is a bit early to port it over right now, although this could be useful to check if some bugs are fixed.
i think @Saulis has switched to vaadin-grid project. It's very similar to iron-data-table and it works on polymer-2.
@dam0vm3nt correct; I had the chance to talk to the Vaadin team at Polymer Summit 2017 and they strongly suggested switching to vaadin-grid, which they described as the production quality rewrite of iron-data-table, which they considered to be more of a proof-of-concept. We are planning to take this route in our projects.
@n1ywb I figured it out after noticing how similar were those two projects but thank you for confirming this from a direct source.
I missed the chance to go to the summit but I watched the streaming and it was great. Can't look forward for modules and lit-html ... although I'm a bit worried about having html templates inside javascript, but I guess that with proper tooling suppport this will be no such a problem.
It's pretty trivial to smosh the HTML into the JS at build time; I can think of a half dozen ways to do it without even trying hard. But I think there has been some backlash against the new "less html" direction, which is in stark contrast with the old "less javascript" direction. The Polymer team seemed contrite during the QA session and committed themselves to exploring potential solutions so I'm hopeful they'll come up with something. That said lit-html opens some pretty interesting possibilities for template composition which hasn't been possible since polymer 0.5.
On Wed, Aug 30, 2017 at 3:31 AM, Vittorio Ballestra < [email protected]> wrote:
@n1ywb https://github.com/n1ywb I figured it out after noticing how similar were those two projects but thank you for confirming this from a direct source.
I missed the chance to go to the summit but I watched the streaming and it was great. Can't look forward for modules and lit-html ... although I'm a bit worried about having html templates inside javascript, but I guess that with proper tooling suppport this will be no such a problem.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Saulis/iron-data-table/issues/178#issuecomment-325907379, or mute the thread https://github.com/notifications/unsubscribe-auth/AATWIZ845jTkmbjH7Bw-iiy_pdjuCkGAks5sdQ_fgaJpZM4LVMxp .
-- 73 de n1ywb