You are right Nándor, Vaadin is going to replace our current widgetset by polymer based elements.
One of the ways we explored in our labs is to wrap every single polymer element with a GWT Widget or Element, and this is the reason we published the gwt-polymer-elements. Additionally we explored other ways such as direct usage of webcomponents directly from the Vaadin server side. And even we explored in our labs how to use polymer in other platforms like Angular, etc.
As I mentioned in my first email Vaadin main motivation on doing that is leaving framework communities lead their integration with polymer, and Vaadin Elements UI Team to focus on delivering polymer Components.
So the strategy of Vaadin is that our widgetset uses standards so as it can be used in any platform including our Vaadin Framework. It is not happening currently because our framework widgetset is only usable from vaadin, even it cannot be used from GWT.
Said that, this does not mean that Vaadin is abandoning GWT, we just want to use webcomponents standards for the UI part of the Vaadin Framework, so as it can be used at the same time in any framework and we can obtain more feedback to improve them. Obviously, since Vaadin is an open-source Company, our polymer elements are Apache licensed.
Additionally, Vaadin indirectly support gwt-polymer-elements since we can still use our Company time aka 'Community Friday' to collaborate with the project. But Vaadin thinks that it should be owned by the GWT community, because they are the best to contribute with ideas and to feature it.
On Sat, Apr 22, 2017 at 3:43 PM, Nándor Előd Fekete <email@example.com> wrote:
Hello Manuel,--wasn't Vaadin going into the direction of migrating it's client side components to web components in the Vaadin Framework itself? If not, can you shed some light on the motivation behind the decision?Thanks!
On Friday, April 21, 2017 at 9:10:06 PM UTC+2, Manuel Carrasco wrote:Hi all,From today, Vaadin has transferred the ownership of the gwt-polymer-elements and gwt-api-generator libraries to me.Vaadin decision is based on encouraging communities to maintain polymer bridges for their favourites frameworks, hence Vaadin can focus their efforts on delivering high quality UI elements made in Polymer. It also happened recently with the Angular2Polymer bridge.I will design a roadmap for the next months.I'm looking for contributors so let me know who is interested on any matter: coding, testing, reporting, answering, etc, and I will grant access to the repos.Thanks- ManoloYou received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+
To post to this group, send email to google-web-toolkit@
Visit this group at https://groups.google.com/
For more options, visit https://groups.google.com/d/
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.