Component changes/mapping from 0.5 -> 0.8/0.9+

[emmanuel buah]

We've been using polymer 0.5 extensively and looking forward to the upcoming 0.9 with performance improvements. The one aspect we don't have much information on is component migration. We are starting to see iron components for 0.8+ but don't have a general roadmap of how the components are being migrated and how they relate/map to 0.5 elements.

Can someone offer insights on iron components and how they related to components in 0.5. I think the concern amongst some of my team members is that most of the core- elements might be going away or transitioned into paper elements. We use and liked the 0.5 core components because it offered an unstyled or uncustomized starting point for different themes/UI other than paper.

In short, here are the questions we could use answers to 

1. Are core-elements going away or will they be migrated

2. How does the new iron-elements in 0.8+ relate to components from 0.5. What's the mapping if any?

Having answers to these question will help existing 0.5 users prep for component migration. Change is hard but change without direction/insight is harder. 

[Anders Holmgren]

I agree. We really need a migration guide for the elements too.

Plus a status page for the port. In particular I'm interested in the status of core-list

[emmanuel]

I agree. They just publish a blog post (https://blog.polymer-project.org/announcements/2015/05/14/updated-elements/) on migration with explanation. I partially get the name change which personally is just semantics but we still don't know what core elements might not get migrated, if any. Its probably too early to trouble them with this but its would be nice. I will just wait till the dust settles and if there are elements left out of the core, I might just have to migrate them myself. That's the best we can do for now. 

On Fri, May 15, 2015 at 4:40 PM Anders Holmgren <andersm...@gmail.com> wrote:

I agree. We really need a migration guide for the elements too.

Plus a status page for the port. In particular I'm interested in the status of core-list

Follow Polymer on Google+: plus.google.com/107187849809354688692
---
You received this message because you are subscribed to a topic in the Google Groups "Polymer" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/polymer-dev/9uopgVmWxuk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/85372ce5-aa62-42ab-a083-cd6bd19bb247%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Taylor Savage]

Hi Anders and Emmanuel,

Thank you for the questions. Here are a couple specific answers:

1. Are core-elements going away or will they be migrated

The core-elements largely have become the iron-elements. The blog post explains in more detail the impetus for this change - largely the "core" name was just the wrong thing to call the old set, so we took the opportunity with the big 0.5=>0.8+ migration to set up a system for naming element "product lines" that will last for the long haul.

Most of the old core-elements have already been migrated to 0.9, and are available in the PolymerElements organization.

 

2. How does the new iron-elements in 0.8+ relate to components from 0.5. What's the mapping if any?

Early on into the port, chuckh created a really neat tool for following element port status here: http://chuckh.github.io/road-to-polymer/  - it's been so good we've been using this within the team. The "Polymer Elements Converted" section shows old name => new name mappings.

In general, we're trying to keep the same suffix name for each of the elements wherever it makes sense, so that the mapping is straightforward as possible.

We really need a migration guide for the elements too.... Plus a status page for the port.

Chuckh's tool is so good that it's our go-to for this. For most elements, the API is largely consistent, so the bulk of migration should be covered just in the differences between 0.5 and 0.8+ which is documented on the Polymer site.

We're also working on a brand new way to view element documentation, that will be live very shortly - we'll update when this is the case!

Thanks again for bearing with us here - it's a big transition with some definite rough edges, but one that we think will put the project on a great trajectory for the long-term.

Please let me know if you have any additional questions,

Taylor

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/CAH%2BOMnyH8MshqAugMEaunsZxZvxcQZcrEbdcjRmdZStJ%2BMBifw%40mail.gmail.com.

[emmanuel buah]

Thanks Taylor and for the team for all their hard work. We really appreciate your response. I have been keeping an eye on the migration proces through Chuckh's tool  and I think its great. What's missing is information about elements that wont make the migration since a status of "no" or "n/a" via Chuckh's tool can be integrated as 

1. Component hasn't be migrated yet

2. Component will not be migrated. 

It looks like the team is still working through what needs to or might migrate now. Hopefully, once the 0.9 components settle in post migration, users of 0.5 component can go ahead with comp migration.

[toduu]

What is the conversion for core-submenu?

[Anders Holmgren]

Yes thanks Taylor. +1 for any info on the un-migrated components (i.e. what is the plan for them)

[Taylor Savage]

Hey all,

Following up here. This was really good feedback to get, and our new "element product line" organization model helps us form roadmaps like this for each set of elements.

We've added Roadmaps now to the READMEs of our major product lines - iron-elements and paper-elements. If you have specific element requests, or there are elements that aren't listed in the roadmap that you're wondering about, please do file an issue on the iron-elements or paper-elements meta repo and we'll look to address them.

Hope this helps, and again, appreciate the feedback!

Taylor

To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/27983475-a4d9-4d84-9b10-54cad8875c08%40googlegroups.com.

[emmanuel buah]

Thanks. This info is very helpful.

[Anders Holmgren]

Yes a big thanks for that. Exactly what was needed

[Valentin Kalinin]

+1 for seeing status of elements as suggested here.

Asking for core-scaffold conversion info, since it one of most common UI base for apps in my opinion.

воскресенье, 17 мая 2015 г., 3:34:30 UTC+3 пользователь emmanuel buah написал: