subject:"GWT Polymer"

Re: GWT Polymer

2017-04-24 Thread Manuel Carrasco Moñino

On Mon, Apr 24, 2017 at 3:27 PM, David <leeon2...@gmail.com> wrote:

> I noticed Vaadin TouchKit is a Apache licensed open source project. If I
> want to develop a mobile application, should I use TouchKit or Vaadin GWT
> polymer elements? I do appreciate your feedback about how to develop mobile
> application using Vaadin technology.
>

Right now you need TouchKit in Vaadin 8.0, until polymer is stable in a new
version of Vaadin. Keep tuned.

- Manolo


>
> David
>
> On Saturday, April 22, 2017 at 12:28:26 PM UTC-4, Manuel Carrasco wrote:
>>
>> 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.
>>
>> Thank you
>> - Manolo
>>
>>
>>
>> On Sat, Apr 22, 2017 at 3:43 PM, Nándor Előd Fekete <nandor...@gmail.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.
>>>>
>>>> https://github.com/manolo/gwt-polymer-elements/
>>>> https://github.com/manolo/gwt-api-generator/
>>>>
>>>> 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
>>>> - Manolo
>>>>
>>> --
>>> 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 google-web-toolkit+unsubscr...@googlegroups.com.
>>> To post to this group, send email to google-we...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

2017-04-24 Thread David

I noticed Vaadin TouchKit is a Apache licensed open source project. If I 
want to develop a mobile application, should I use TouchKit or Vaadin GWT 
polymer elements? I do appreciate your feedback about how to develop mobile 
application using Vaadin technology.

David

On Saturday, April 22, 2017 at 12:28:26 PM UTC-4, Manuel Carrasco wrote:
>
> 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.
>
> Thank you
> - Manolo 
>
>
>
> On Sat, Apr 22, 2017 at 3:43 PM, Nándor Előd Fekete <nandor...@gmail.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.
>>>
>>> https://github.com/manolo/gwt-polymer-elements/
>>> https://github.com/manolo/gwt-api-generator/
>>>
>>> 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
>>> - Manolo
>>>
>> -- 
>> 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 google-web-toolkit+unsubscr...@googlegroups.com .
>> To post to this group, send email to google-we...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

2017-04-22 Thread Manuel Carrasco Moñino

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.

Thank you
- Manolo

On Sat, Apr 22, 2017 at 3:43 PM, Nándor Előd Fekete <nandor.fek...@gmail.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.
>>
>> https://github.com/manolo/gwt-polymer-elements/
>> https://github.com/manolo/gwt-api-generator/
>>
>> 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
>> - Manolo
>>
> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

2017-04-22 Thread Manuel Carrasco Moñino

Francesco,  add a comment to this issue https://github.com/manolo/gwt-
polymer-elements/issues/151

Thank you
- Manolo

On Sat, Apr 22, 2017 at 10:47 AM, Francesco Izzi <francesco.i...@geosdi.org>
wrote:

> Ciao Manuel
>
> I would be happy to contribute in testing and reporting.
>
> Thanks
> Il giorno sab 22 apr 2017 alle 00:43 harshyadav <harsh.de...@gmail.com>
> ha scritto:
>
>> Thanks a lot Manuel.
>>
>> We use gwt polymer elements heavily and look forward for its future
>> development.
>> I would be happy to contribute in the best of my abilities: mainly
>> testing and reporting.
>>
>> Regards,
>> Harsh Yadav
>>
>> On Friday, April 21, 2017 at 3:10:06 PM UTC-4, Manuel Carrasco wrote:
>>>
>>> Hi all,
>>>
>>> From today, Vaadin has transferred the ownership of the
>>> gwt-polymer-elements and gwt-api-generator libraries to me.
>>>
>>> https://github.com/manolo/gwt-polymer-elements/
>>> https://github.com/manolo/gwt-api-generator/
>>>
>>> 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
>>> - Manolo
>>>
>> --
>> 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 google-web-toolkit+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Francesco Izzi
> CNR - IMAA
> geoSDI
> Direzione Tecnologie e Sviluppo
>
> C.da S. Loja
> 85050  Tito Scalo - POTENZA (PZ)
> Italia
>
> phone: +39 0971427310 <+39%200971%20427310>
> fax:   +39 0971 427271 <+39%200971%20427271>
> mob: +39 3666373172 <+39%20366%20637%203172>
> mail: francesco.i...@geosdi.org
> skype:  neofx8080
>
> web: http://www.geosdi.org
>
> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

2017-04-22 Thread Manuel Carrasco Moñino

Thank Harsh,

add a comment to this issue  https://github.com/manolo/gwt-
polymer-elements/issues/151, so as I know your github account and will add
as a contributor

- Manolo

On Sat, Apr 22, 2017 at 12:43 AM, harshyadav <harsh.de...@gmail.com> wrote:

> Thanks a lot Manuel.
>
> We use gwt polymer elements heavily and look forward for its future
> development.
> I would be happy to contribute in the best of my abilities: mainly testing
> and reporting.
>
> Regards,
> Harsh Yadav
>
> On Friday, April 21, 2017 at 3:10:06 PM UTC-4, Manuel Carrasco wrote:
>>
>> Hi all,
>>
>> From today, Vaadin has transferred the ownership of the
>> gwt-polymer-elements and gwt-api-generator libraries to me.
>>
>> https://github.com/manolo/gwt-polymer-elements/
>> https://github.com/manolo/gwt-api-generator/
>>
>> 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
>> - Manolo
>>
> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

2017-04-22 Thread Nándor Előd Fekete

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.
>
> https://github.com/manolo/gwt-polymer-elements/
> https://github.com/manolo/gwt-api-generator/
>
> 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
> - Manolo
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

2017-04-22 Thread Francesco Izzi

Ciao Manuel

I would be happy to contribute in testing and reporting.

Thanks
Il giorno sab 22 apr 2017 alle 00:43 harshyadav <harsh.de...@gmail.com> ha
scritto:

> Thanks a lot Manuel.
>
> We use gwt polymer elements heavily and look forward for its future
> development.
> I would be happy to contribute in the best of my abilities: mainly testing
> and reporting.
>
> Regards,
> Harsh Yadav
>
> On Friday, April 21, 2017 at 3:10:06 PM UTC-4, Manuel Carrasco wrote:
>>
>> Hi all,
>>
>> From today, Vaadin has transferred the ownership of the
>> gwt-polymer-elements and gwt-api-generator libraries to me.
>>
>> https://github.com/manolo/gwt-polymer-elements/
>> https://github.com/manolo/gwt-api-generator/
>>
>> 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
>> - Manolo
>>
> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Francesco Izzi
CNR - IMAA
geoSDI
Direzione Tecnologie e Sviluppo

C.da S. Loja
85050  Tito Scalo - POTENZA (PZ)
Italia

phone: +39 0971427310
fax:   +39 0971 427271
mob: +39 3666373172
mail: francesco.i...@geosdi.org
skype:  neofx8080

web: http://www.geosdi.org

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

2017-04-21 Thread harshyadav

Thanks a lot Manuel.

We use gwt polymer elements heavily and look forward for its future 
development.
I would be happy to contribute in the best of my abilities: mainly testing 
and reporting.

Regards,
Harsh Yadav

On Friday, April 21, 2017 at 3:10:06 PM UTC-4, Manuel Carrasco wrote:
>
> Hi all,
>
> From today, Vaadin has transferred the ownership of the 
> gwt-polymer-elements and gwt-api-generator libraries to me.
>
> https://github.com/manolo/gwt-polymer-elements/
> https://github.com/manolo/gwt-api-generator/
>
> 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
> - Manolo
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT Polymer

2017-04-21 Thread Manuel Carrasco Moñino

Hi all,

>From today, Vaadin has transferred the ownership of the
gwt-polymer-elements and gwt-api-generator libraries to me.

https://github.com/manolo/gwt-polymer-elements/
https://github.com/manolo/gwt-api-generator/

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
- Manolo

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

2016-11-30 Thread Thomas Buckel

Thanks for all the feedback.

Didn't know that GWT Material was wraps materializecss.

I think polymer is the future. However the more seamless integration of GWT
Material with GWT Widgets as well as a more gradual migration might give it
a bit of an edge for my use case. Also probably easier bringing the team up
to scratch with it as they know GWT.

Tough one.

Thomas

On 30 November 2016 at 11:45, Slava Pankov <pank...@gmail.com> wrote:

> I just don't get this trend with "burying" widgets and UiBinder. Even with
> Errai I don't see any meaningful replacement for composite UI, i.e. design
> simple blocks as ... and then reuse them with
> 
> Though with Polymer it looks like it's possible by defining web component
> for each logical block.
>
>
> On Wednesday, November 23, 2016 at 2:40:45 PM UTC-8, Amit Munwes wrote:
>>
>> I decided to go with Polymer:
>> 1. Very active framework and not specific to GWT developers - so you can
>> find answers/examples etc. easily as well as a growing set of web
>> components that can be used within your app
>> 2. High-end material design components, in browsers as well as mobile
>> devices
>> 3. Great documentation
>> 4. Future-proofing regarding GWT 3.0, using only JS-Interop with no
>> widgets
>> 5. I use Vaadin's generator directly (not the packaged JAR) so we can
>> upgrade Polymer version any time a new version is available
>>
>> On Friday, November 18, 2016 at 1:45:26 AM UTC+2, tbb wrote:
>>>
>>> Hi all,
>>>
>>> I've got a 3 year old enterprise GWT app which also has a mobile app
>>> based on GWT. Our current design style is based on Bootstrap. As things
>>> change, I'd like to freshen the UX by using Material Design. I've seen 2
>>> libraries: GwtMaterialDesign and gwt-polymer-elements.
>>>
>>> From what I can see:
>>> - Both showcases look great, esp both seem to have an "enterprise" class
>>> table/grid control.
>>> - GwtMaterialDesign: Read quite positive things in terms of community.
>>> - gwt-polymer-elements: By Vaadin which are quite active in the GWT
>>> world now, based on "real" Polymer elements and the new GWT 2.8 elemental
>>> (?)
>>>
>>> Would be great if anyone could comment on using either of them as I
>>> think once we've decided for one of the libraries, it will be hard to
>>> switch.
>>>
>>> Any feedback would be great!
>>>
>>> Thanks,
>>> Thomas
>>>
>>>
>>>
>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/google-web-toolkit/5HF8RKs_w3Y/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

2016-11-29 Thread Slava Pankov

I just don't get this trend with "burying" widgets and UiBinder. Even with 
Errai I don't see any meaningful replacement for composite UI, i.e. design 
simple blocks as ... and then reuse them with 

Though with Polymer it looks like it's possible by defining web component 
for each logical block.


On Wednesday, November 23, 2016 at 2:40:45 PM UTC-8, Amit Munwes wrote:
>
> I decided to go with Polymer:
> 1. Very active framework and not specific to GWT developers - so you can 
> find answers/examples etc. easily as well as a growing set of web 
> components that can be used within your app
> 2. High-end material design components, in browsers as well as mobile 
> devices
> 3. Great documentation
> 4. Future-proofing regarding GWT 3.0, using only JS-Interop with no widgets
> 5. I use Vaadin's generator directly (not the packaged JAR) so we can 
> upgrade Polymer version any time a new version is available
>
> On Friday, November 18, 2016 at 1:45:26 AM UTC+2, tbb wrote:
>>
>> Hi all,
>>
>> I've got a 3 year old enterprise GWT app which also has a mobile app 
>> based on GWT. Our current design style is based on Bootstrap. As things 
>> change, I'd like to freshen the UX by using Material Design. I've seen 2 
>> libraries: GwtMaterialDesign and gwt-polymer-elements. 
>>
>> From what I can see:
>> - Both showcases look great, esp both seem to have an "enterprise" class 
>> table/grid control.
>> - GwtMaterialDesign: Read quite positive things in terms of community.
>> - gwt-polymer-elements: By Vaadin which are quite active in the GWT world 
>> now, based on "real" Polymer elements and the new GWT 2.8 elemental (?)
>>
>> Would be great if anyone could comment on using either of them as I think 
>> once we've decided for one of the libraries, it will be hard to switch.
>>
>> Any feedback would be great!
>>
>> Thanks,
>> Thomas
>>
>>
>>
>>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

2016-11-24 Thread Kirill Prazdnikov


>
>
> 4. Future-proofing regarding GWT 3.0, using only JS-Interop with no widgets
>

And no JSNI ? 


-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

2016-11-23 Thread Amit Munwes

I decided to go with Polymer:
1. Very active framework and not specific to GWT developers - so you can 
find answers/examples etc. easily as well as a growing set of web 
components that can be used within your app
2. High-end material design components, in browsers as well as mobile 
devices
3. Great documentation
4. Future-proofing regarding GWT 3.0, using only JS-Interop with no widgets
5. I use Vaadin's generator directly (not the packaged JAR) so we can 
upgrade Polymer version any time a new version is available

On Friday, November 18, 2016 at 1:45:26 AM UTC+2, tbb wrote:
>
> Hi all,
>
> I've got a 3 year old enterprise GWT app which also has a mobile app based 
> on GWT. Our current design style is based on Bootstrap. As things change, 
> I'd like to freshen the UX by using Material Design. I've seen 2 libraries: 
> GwtMaterialDesign and gwt-polymer-elements. 
>
> From what I can see:
> - Both showcases look great, esp both seem to have an "enterprise" class 
> table/grid control.
> - GwtMaterialDesign: Read quite positive things in terms of community.
> - gwt-polymer-elements: By Vaadin which are quite active in the GWT world 
> now, based on "real" Polymer elements and the new GWT 2.8 elemental (?)
>
> Would be great if anyone could comment on using either of them as I think 
> once we've decided for one of the libraries, it will be hard to switch.
>
> Any feedback would be great!
>
> Thanks,
> Thomas
>
>
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT Polymer : The icons are not appearing in the UI

2016-11-21 Thread Dhinakar Reddy Pothireddi

Hi,

I tried to use the GWT Polymer and I am getting the UI with no icons.
This is my code
public void onModuleLoad() {

PaperButton button = new PaperButton("Press me!");
button.setRaised(true);
IronIcon icon = new IronIcon();
*icon.setIcon("menu");*
button.add(icon);
button.addClickHandler(new ClickHandler() {
@Override
public void onClick(ClickEvent event) {
// TODO Auto-generated method stub
Window.alert("Hello");
}
});
RootPanel.get().add(button);
}

<https://lh3.googleusercontent.com/-pjdCUb3esnE/WDKIdMIB4dI/Ij0/iIy_vMXgVNkzGv2d9xhep5pXG5iQ7T2sgCLcB/s1600/Capture.JPG>

I also tried few other widgets and they are also not showing up any icons. 
Did I miss something? Please help me. Thanks in advance.

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Material Design with GWT(Polymer wrapper)

2016-11-20 Thread Dhinakar Reddy Pothireddi



<https://lh3.googleusercontent.com/-pjdCUb3esnE/WDKIdMIB4dI/Ij0/iIy_vMXgVNkzGv2d9xhep5pXG5iQ7T2sgCLcB/s1600/Capture.JPG>
Hi Blaze,

I tried to use the GWT Polymer and I am getting the UI with no icons.
This is my code
public void onModuleLoad() {

PaperButton button = new PaperButton("Press me!");
button.setRaised(true);
IronIcon icon = new IronIcon();
icon.setIcon("menu");
button.add(icon);
button.addClickHandler(new ClickHandler() {
@Override
public void onClick(ClickEvent event) {
// TODO Auto-generated method stub
Window.alert("Hello");
}
});
RootPanel.get().add(button);
}

<https://lh3.googleusercontent.com/-pjdCUb3esnE/WDKIdMIB4dI/Ij0/iIy_vMXgVNkzGv2d9xhep5pXG5iQ7T2sgCLcB/s1600/Capture.JPG>

I also tried few other widgets and they are also not showing up any icons. 
Did I miss something? Please help me. Thanks in advance.

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

2016-11-18 Thread zakaria amine

gwt-polymer-elements and Polymer in general is about extending the web, it 
does provide a set of useful elements but it also allows you  to create 
your own customizable components with behavior, style...

GwtMaterialDesign is the look and feel of material design brought to GWT 
widgets, with some nice additions.  



Le vendredi 18 novembre 2016 00:45:26 UTC+1, tbb a écrit :
>
> Hi all,
>
> I've got a 3 year old enterprise GWT app which also has a mobile app based 
> on GWT. Our current design style is based on Bootstrap. As things change, 
> I'd like to freshen the UX by using Material Design. I've seen 2 libraries: 
> GwtMaterialDesign and gwt-polymer-elements. 
>
> From what I can see:
> - Both showcases look great, esp both seem to have an "enterprise" class 
> table/grid control.
> - GwtMaterialDesign: Read quite positive things in terms of community.
> - gwt-polymer-elements: By Vaadin which are quite active in the GWT world 
> now, based on "real" Polymer elements and the new GWT 2.8 elemental (?)
>
> Would be great if anyone could comment on using either of them as I think 
> once we've decided for one of the libraries, it will be hard to switch.
>
> Any feedback would be great!
>
> Thanks,
> Thomas
>
>
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

2016-11-18 Thread Rogelio Flores

The major differences I see between them are that gwt-polymer-elements wrap 
polymer, which uses web components, which might be more future-proof 
if/when web components become the preferred/standard way to build UI 
widgets. Also, it not only supports paper elements (think material design), 
but Iron, Vaadin, and other elements out of the box, in addition to giving 
you a framework to include any other web components that you might want to 
create or include (externally available).

GwtMaterialDesign, wraps materializecss (js/css) which doesn't use web 
components to create the material design L (correct me if I'm wrong), but 
does have an edge right now as far as L, theming, and charts.

So I would pick gwt-polymer-elements if I'm into web components (or have 
some that I want to integrate--be it my own or third-party), or even if I'm 
concerned about future-proofing my app a little more (assuming web 
components are the future), but GwtMaterialDesign gives you more and better 
widgets right now, although *only* with the Material Design L


On Thursday, November 17, 2016 at 4:45:26 PM UTC-7, tbb wrote:
>
> Hi all,
>
> I've got a 3 year old enterprise GWT app which also has a mobile app based 
> on GWT. Our current design style is based on Bootstrap. As things change, 
> I'd like to freshen the UX by using Material Design. I've seen 2 libraries: 
> GwtMaterialDesign and gwt-polymer-elements. 
>
> From what I can see:
> - Both showcases look great, esp both seem to have an "enterprise" class 
> table/grid control.
> - GwtMaterialDesign: Read quite positive things in terms of community.
> - gwt-polymer-elements: By Vaadin which are quite active in the GWT world 
> now, based on "real" Polymer elements and the new GWT 2.8 elemental (?)
>
> Would be great if anyone could comment on using either of them as I think 
> once we've decided for one of the libraries, it will be hard to switch.
>
> Any feedback would be great!
>
> Thanks,
> Thomas
>
>
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GwtMaterialDesign vs gwt-polymer-elements

2016-11-18 Thread Rodolfo Raya

Hi,

You can mix gwt-material and Vaadin's polymer elements in the same project.

After working for years with Sencha's GXT I decided to try gwt-material,
which looks a lot better and does not have the high cost of GXT. Migration
was easy and painless. When I found a bug in gwt-material uploader (the bug
has now been fixed), I tried the polymer uploader from Vaadin in the
project and it worked very well. Both libraries can coexist peacefully.

When the uploader was fixed, I decided to complete the project using
gwt-material only. Vaadin's polymer elements are nice but I like
gwt-material appearance more.

Regards,
Rodolfo
--
Rodolfo M. Raya
http://www.maxprograms.com

On Thu, Nov 17, 2016 at 8:45 PM, tbb <thomas.buc...@gmail.com> wrote:

> Hi all,
>
> I've got a 3 year old enterprise GWT app which also has a mobile app based
> on GWT. Our current design style is based on Bootstrap. As things change,
> I'd like to freshen the UX by using Material Design. I've seen 2 libraries:
> GwtMaterialDesign and gwt-polymer-elements.
>
> From what I can see:
> - Both showcases look great, esp both seem to have an "enterprise" class
> table/grid control.
> - GwtMaterialDesign: Read quite positive things in terms of community.
> - gwt-polymer-elements: By Vaadin which are quite active in the GWT world
> now, based on "real" Polymer elements and the new GWT 2.8 elemental (?)
>
> Would be great if anyone could comment on using either of them as I think
> once we've decided for one of the libraries, it will be hard to switch.
>
> Any feedback would be great!
>
> Thanks,
> Thomas
>
>
>
> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Rodolfo M. Raya <rmr...@maxprograms.com>
http://www.maxprograms.com

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GwtMaterialDesign vs gwt-polymer-elements

2016-11-17 Thread tbb

Hi all,

I've got a 3 year old enterprise GWT app which also has a mobile app based 
on GWT. Our current design style is based on Bootstrap. As things change, 
I'd like to freshen the UX by using Material Design. I've seen 2 libraries: 
GwtMaterialDesign and gwt-polymer-elements. 

>From what I can see:
- Both showcases look great, esp both seem to have an "enterprise" class 
table/grid control.
- GwtMaterialDesign: Read quite positive things in terms of community.
- gwt-polymer-elements: By Vaadin which are quite active in the GWT world 
now, based on "real" Polymer elements and the new GWT 2.8 elemental (?)

Would be great if anyone could comment on using either of them as I think 
once we've decided for one of the libraries, it will be hard to switch.

Any feedback would be great!

Thanks,
Thomas



-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Vaadin GWT Polymer Elements adds about 5000 new files to the release

2016-09-21 Thread Tony

thank you. I was able to exclude a large number of them via the 
appengine-web.xml using exclusion filters:  




thx for the quick reply. 

On Tuesday, September 20, 2016 at 5:27:14 PM UTC-4, zakaria amine wrote:
>
> gwt-polymer-elements adds the bower_components for polymer which contains 
> all the polymer elements to your module. It is added automatically because 
> it is in the public folder in the package com.vaadin.polymer. One solution 
> I can think of is to rebuild the library and exclude it from the jar. Check 
> out this: 
> https://github.com/vaadin/gwt-api-generator/blob/master/gulpfile.js, you 
> get rid of the bower taks. Then, you can use a tool like vulcanize which 
> allows to import only the polymer elements that you need in one file: 
> https://www.polymer-project.org/1.0/docs/tools/optimize-for-production 
>
>
>
> Le mardi 20 septembre 2016 19:31:33 UTC+2, Tony a écrit :
>>
>>
>> Anybody knows of a way to reduce the number of files? I'm asking because 
>> I'm deploying to appengine which has a limit of 1 files per version, 
>> per release and with several GWT modules and locales I'm already going over 
>> the limit. 
>>
>> Thank you
>> Tony
>>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Vaadin GWT Polymer Elements adds about 5000 new files to the release

2016-09-20 Thread zakaria amine

gwt-polymer-elements adds the bower_components for polymer which contains 
all the polymer elements to your module. It is added automatically because 
it is in the public folder in the package com.vaadin.polymer. One solution 
I can think of is to rebuild the library and exclude it from the jar. Check 
out 
this: https://github.com/vaadin/gwt-api-generator/blob/master/gulpfile.js, 
you get rid of the bower taks. Then, you can use a tool like vulcanize 
which allows to import only the polymer elements that you need in one 
file: https://www.polymer-project.org/1.0/docs/tools/optimize-for-production 



Le mardi 20 septembre 2016 19:31:33 UTC+2, Tony a écrit :
>
>
> Anybody knows of a way to reduce the number of files? I'm asking because 
> I'm deploying to appengine which has a limit of 1 files per version, 
> per release and with several GWT modules and locales I'm already going over 
> the limit. 
>
> Thank you
> Tony
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Vaadin GWT Polymer Elements adds about 5000 new files to the release

2016-09-20 Thread Tony

Hi

I was able to get the Vaadin GWT Polymer framework integrated into my 
project. However, it seems like just adding the vaadin polymer library 
caused the GWT application to now include a little over 5000 static files 
in the release. So adding this line in my gwt.xml  causes the staging directory to now have 
over 5000 files (up from about 15 without the import). 

Anybody knows of a way to reduce the number of files? I'm asking because 
I'm deploying to appengine which has a limit of 1 files per version, 
per release and with several GWT modules and locales I'm already going over 
the limit. 

Thank you
Tony

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: $wnd.HTMLImports is undefined when using Vaadin GWT Polymer Elements

2016-09-20 Thread Tony

I upgraded to vaadin-gwt-polymer-elements-1.2.3.1-SNAPSHOT-sources.jar and 
everything seems to be working now. 

On Friday, September 16, 2016 at 5:51:41 PM UTC-4, Tony wrote:
>
> I tried to use the Polymer widgets from Vaadin. However, no matter what I 
> do I keep getting the error below basically saying that $wnd.HTMLImports is 
> undefined. I even created a bare-bones project, just with the necessary 
> code to run an example and I still get this error. Any idea what's causing 
> it? 
>
> thank you
> tony
>
>
> Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError) : 
> Cannot read property 'whenReady' of undefined 
> TypeError: Cannot read property 'whenReady' of undefined
> at lQf_g$ (Polymer.java:364)
> at QPf_g$ (Polymer.java:277)
> at TQf_g$ (PolymerWidget.java:17)
> at u1f_g$ (PaperMaterial.java:39)
> at K$f_g$ (JavaApiWidget.java:17)
>
> the error is thrown in com.vaadin.polymer.Polymer.java on line 364 which 
> is this:
> $wnd.HTMLImports.whenReady(!e ? f : function() {
>
>   /**
>  * Executes a function after all imports have been loaded and when the
>  * passed element is ready to use.
>  */
> public static native void whenReady(Function f, Element e)
> /*-{
> $wnd.HTMLImports.whenReady(!e ? f : function() {
>   var id = setInterval(function() {
> if (@com.vaadin.polymer.Polymer::isRegisteredElement(*)(e)) {
>   clearInterval(id);
>   f(e);
> }
>   }, 0);
> });
> }-*/;
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

$wnd.HTMLImports is undefined when using Vaadin GWT Polymer Elements

2016-09-16 Thread Tony

I tried to use the Polymer widgets from Vaadin. However, no matter what I 
do I keep getting the error below basically saying that $wnd.HTMLImports is 
undefined. I even created a bare-bones project, just with the necessary 
code to run an example and I still get this error. Any idea what's causing 
it? 

thank you
tony


Caused by: com.google.gwt.core.client.JavaScriptException: (TypeError) : 
Cannot read property 'whenReady' of undefined 
TypeError: Cannot read property 'whenReady' of undefined
at lQf_g$ (Polymer.java:364)
at QPf_g$ (Polymer.java:277)
at TQf_g$ (PolymerWidget.java:17)
at u1f_g$ (PaperMaterial.java:39)
at K$f_g$ (JavaApiWidget.java:17)

the error is thrown in com.vaadin.polymer.Polymer.java on line 364 which is 
this:
$wnd.HTMLImports.whenReady(!e ? f : function() {

  /**
 * Executes a function after all imports have been loaded and when the
 * passed element is ready to use.
 */
public static native void whenReady(Function f, Element e)
/*-{
$wnd.HTMLImports.whenReady(!e ? f : function() {
  var id = setInterval(function() {
if (@com.vaadin.polymer.Polymer::isRegisteredElement(*)(e)) {
  clearInterval(id);
  f(e);
}
  }, 0);
});
}-*/;

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

2016-08-12 Thread Bruno Salmon

I mainly wanted to check if it was a GWT issue and it seems from what you 
say it's rather a gwt-polymer-elements issue.

I'm happy to stay with beta1 until this gwt-polymer-elements issue is 
resolved (I will open the issue once GWT 2.8.0 will be out).

Thanks

On Friday, 12 August 2016 17:26:57 UTC+2, Kristofer Blom wrote:
>
> We had this problem too. I built a new version of the library from current 
> source (instructions here <https://github.com/vaadin/gwt-polymer-elements>), 
> and that resolved at least that particular issue. The generated jar file 
> has 1.2.3.1 as version number, and our application seems to work well with 
> 2.8.0-rc1 now. 
>
> Kristofer 
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

2016-08-12 Thread Bruno Salmon

You're right, I use Polymer.importHref() too, but I don't want to move this 
directly in the html as our project supports different UI toolkits, not 
only polymer, so it depends on the configuration and imports need to be 
done at runtime.

So I think I will open an issue and stay with beta1 until the issue is 
resolved.

Thanks.

On Friday, 12 August 2016 17:12:55 UTC+2, zakaria amine wrote:
>
> You must be using Polymer.importHref() right ? and then you call  
> Polymer.ready() I had the same issue before, and I ended up 
> removing Polymer.importHref() and Polymer.ready(), and adding the imports 
> manually in the head, now it works fine. You can check out this commit in 
> my project here: 
> https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e
>   
> <https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e>
>
> If it does not work then you can open an issue, but you should now that 
> the project's contributors are very slow to respond...
>
> Le vendredi 12 août 2016 16:37:31 UTC+2, Bruno Salmon a écrit :
>>
>> Yes I'm using the latest gwt-polymer-elements version, so 1.2.3.0, and 
>> it works for me with beta1.
>>
>> The runtime error occurs also in production mode, not only in Dev mode.
>>
>> I don't call whenPolymerLoaded() directly in my code, I only use 
>> Polymer.ready(Element 
>> e, Function f) but I guess whenPolymerLoaded() is then called within the 
>> Vaadin implementation. 
>>
>> Actually I just would like to know if it's a gwt-polymer-elements 1.2.3.0 
>> issue (in this case I will wait Vaadin to deliver the next release that 
>> will work GWT 2.8.0) or if it's a GWT issue that needs to be fixed before 
>> 2.8.0 is out.
>>
>> Should I rather open an issue on the gwt-polymer-elements github project?
>>
>>
>> On Friday, 12 August 2016 14:49:04 UTC+2, zakaria amine wrote:
>>>
>>> Normally, the latest version gwt-polymer-elements 1.2.3.0 is not 
>>> supposed to work with beta1 but with SNAPSHOT or rc1, which version are you 
>>> using? 
>>>
>>> Another advise is try not use whenPolymerLoaded() in Dev mode, comment 
>>> it out and take out the statements inside it, use it only when deploying to 
>>> a server. 
>>>
>>>
>>> Le vendredi 12 août 2016 11:39:41 UTC+2, Bruno Salmon a écrit :
>>>>
>>>> Hi,
>>>>
>>>> I have a GWT Polymer Elements project that compiles and run ok with GWT 
>>>> 2.8.0-beta1.
>>>>
>>>> When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't 
>>>> run due to the follow runtime error:
>>>>
>>>> Uncaught TypeError: ok_0_g$.call_1_g$ is not a function
>>>> Polymer.java:159
>>>>
>>>> The Polymer.java:159 line is underlined in the code below:
>>>>
>>>> private static native void whenPolymerLoaded(Function ok)
>>>> /*-{
>>>> function done() {
>>>>   // Set our static reference to Base
>>>>   @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
>>>>   @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
>>>>   // Polymer dynamic loaded does not remove unresolved
>>>>   $doc.body.removeAttribute('unresolved');
>>>>   //
>>>>   *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
>>>> }
>>>> if (!$wnd.Polymer) {
>>>> var l = $doc.createElement('link');
>>>> l.rel = 'import';
>>>> l.href = 
>>>> @com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
>>>> l.onload = done;
>>>> $doc.head.appendChild(l);
>>>> } else {
>>>>done();
>>>> }
>>>> }-*/;
>>>>
>>>> I don't know if this is a GWT issue or a GWT Polymer Elements issue.
>>>> Any idea?
>>>>
>>>> Thanks.
>>>>
>>>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

2016-08-12 Thread Kristofer Blom

We had this problem too. I built a new version of the library from current 
source (instructions here <https://github.com/vaadin/gwt-polymer-elements>), 
and that resolved at least that particular issue. The generated jar file 
has 1.2.3.1 as version number, and our application seems to work well with 
2.8.0-rc1 now. 

Kristofer 

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

2016-08-12 Thread zakaria amine

You must be using Polymer.importHref() right ? and then you call  
Polymer.ready() I had the same issue before, and I ended up 
removing Polymer.importHref() and Polymer.ready(), and adding the imports 
manually in the head, now it works fine. You can check out this commit in 
my project here: 
https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e
  
<https://github.com/gwidgets/gwt-polymer-starter-kit/commit/7ce3c9523e3e7955f87659f9fcc4d03ac8928a5e>

If it does not work then you can open an issue, but you should now that the 
project's contributors are very slow to respond...

Le vendredi 12 août 2016 16:37:31 UTC+2, Bruno Salmon a écrit :
>
> Yes I'm using the latest gwt-polymer-elements version, so 1.2.3.0, and it 
> works for me with beta1.
>
> The runtime error occurs also in production mode, not only in Dev mode.
>
> I don't call whenPolymerLoaded() directly in my code, I only use 
> Polymer.ready(Element 
> e, Function f) but I guess whenPolymerLoaded() is then called within the 
> Vaadin implementation. 
>
> Actually I just would like to know if it's a gwt-polymer-elements 1.2.3.0 
> issue (in this case I will wait Vaadin to deliver the next release that 
> will work GWT 2.8.0) or if it's a GWT issue that needs to be fixed before 
> 2.8.0 is out.
>
> Should I rather open an issue on the gwt-polymer-elements github project?
>
>
> On Friday, 12 August 2016 14:49:04 UTC+2, zakaria amine wrote:
>>
>> Normally, the latest version gwt-polymer-elements 1.2.3.0 is not 
>> supposed to work with beta1 but with SNAPSHOT or rc1, which version are you 
>> using? 
>>
>> Another advise is try not use whenPolymerLoaded() in Dev mode, comment 
>> it out and take out the statements inside it, use it only when deploying to 
>> a server. 
>>
>>
>> Le vendredi 12 août 2016 11:39:41 UTC+2, Bruno Salmon a écrit :
>>>
>>> Hi,
>>>
>>> I have a GWT Polymer Elements project that compiles and run ok with GWT 
>>> 2.8.0-beta1.
>>>
>>> When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't run 
>>> due to the follow runtime error:
>>>
>>> Uncaught TypeError: ok_0_g$.call_1_g$ is not a function
>>> Polymer.java:159
>>>
>>> The Polymer.java:159 line is underlined in the code below:
>>>
>>> private static native void whenPolymerLoaded(Function ok)
>>> /*-{
>>> function done() {
>>>   // Set our static reference to Base
>>>   @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
>>>   @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
>>>   // Polymer dynamic loaded does not remove unresolved
>>>   $doc.body.removeAttribute('unresolved');
>>>   //
>>>   *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
>>> }
>>> if (!$wnd.Polymer) {
>>>     var l = $doc.createElement('link');
>>> l.rel = 'import';
>>> l.href = 
>>> @com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
>>> l.onload = done;
>>> $doc.head.appendChild(l);
>>> } else {
>>>done();
>>> }
>>> }-*/;
>>>
>>> I don't know if this is a GWT issue or a GWT Polymer Elements issue.
>>> Any idea?
>>>
>>> Thanks.
>>>
>>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

2016-08-12 Thread Bruno Salmon

Yes I'm using the latest gwt-polymer-elements version, so 1.2.3.0, and it 
works for me with beta1.

The runtime error occurs also in production mode, not only in Dev mode.

I don't call whenPolymerLoaded() directly in my code, I only use 
Polymer.ready(Element 
e, Function f) but I guess whenPolymerLoaded() is then called within the 
Vaadin implementation. 

Actually I just would like to know if it's a gwt-polymer-elements 1.2.3.0 
issue (in this case I will wait Vaadin to deliver the next release that 
will work GWT 2.8.0) or if it's a GWT issue that needs to be fixed before 
2.8.0 is out.

Should I rather open an issue on the gwt-polymer-elements github project?


On Friday, 12 August 2016 14:49:04 UTC+2, zakaria amine wrote:
>
> Normally, the latest version gwt-polymer-elements 1.2.3.0 is not supposed 
> to work with beta1 but with SNAPSHOT or rc1, which version are you using? 
>
> Another advise is try not use whenPolymerLoaded() in Dev mode, comment it 
> out and take out the statements inside it, use it only when deploying to a 
> server. 
>
>
> Le vendredi 12 août 2016 11:39:41 UTC+2, Bruno Salmon a écrit :
>>
>> Hi,
>>
>> I have a GWT Polymer Elements project that compiles and run ok with GWT 
>> 2.8.0-beta1.
>>
>> When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't run 
>> due to the follow runtime error:
>>
>> Uncaught TypeError: ok_0_g$.call_1_g$ is not a function
>> Polymer.java:159
>>
>> The Polymer.java:159 line is underlined in the code below:
>>
>> private static native void whenPolymerLoaded(Function ok)
>> /*-{
>> function done() {
>>   // Set our static reference to Base
>>   @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
>>   @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
>>   // Polymer dynamic loaded does not remove unresolved
>>   $doc.body.removeAttribute('unresolved');
>>   //
>>   *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
>> }
>> if (!$wnd.Polymer) {
>> var l = $doc.createElement('link');
>> l.rel = 'import';
>> l.href = 
>> @com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
>> l.onload = done;
>> $doc.head.appendChild(l);
>> } else {
>>done();
>> }
>> }-*/;
>>
>> I don't know if this is a GWT issue or a GWT Polymer Elements issue.
>> Any idea?
>>
>> Thanks.
>>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

2016-08-12 Thread zakaria amine

Normally, the latest version gwt-polymer-elements 1.2.3.0 is not supposed 
to work with beta1 but with SNAPSHOT or rc1, which version are you using? 

Another advise is try not use whenPolymerLoaded() in Dev mode, comment it 
out and take out the statements inside it, use it only when deploying to a 
server. 


Le vendredi 12 août 2016 11:39:41 UTC+2, Bruno Salmon a écrit :
>
> Hi,
>
> I have a GWT Polymer Elements project that compiles and run ok with GWT 
> 2.8.0-beta1.
>
> When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't run 
> due to the follow runtime error:
>
> Uncaught TypeError: ok_0_g$.call_1_g$ is not a function
> Polymer.java:159
>
> The Polymer.java:159 line is underlined in the code below:
>
> private static native void whenPolymerLoaded(Function ok)
> /*-{
> function done() {
>   // Set our static reference to Base
>   @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
>   @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
>   // Polymer dynamic loaded does not remove unresolved
>   $doc.body.removeAttribute('unresolved');
>   //
>   *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
> }
> if (!$wnd.Polymer) {
> var l = $doc.createElement('link');
> l.rel = 'import';
> l.href = 
> @com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
> l.onload = done;
> $doc.head.appendChild(l);
> } else {
>done();
> }
> }-*/;
>
> I don't know if this is a GWT issue or a GWT Polymer Elements issue.
> Any idea?
>
> Thanks.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Runtime error when switching a GWT Polymer Elements project from 2.8.0-beta1 to 2.8.0-rc1/rc2

2016-08-12 Thread Bruno Salmon

Hi,

I have a GWT Polymer Elements project that compiles and run ok with GWT 
2.8.0-beta1.

When switching to 2.8.0-rc1 or 2.8.0-rc2, it compiles ok but doesn't run 
due to the follow runtime error:

Uncaught TypeError: ok_0_g$.call_1_g$ is not a functionPolymer.java:159

The Polymer.java:159 line is underlined in the code below:

private static native void whenPolymerLoaded(Function ok)
/*-{
function done() {
  // Set our static reference to Base
  @com.vaadin.polymer.Polymer::Polymer = $wnd.Polymer;
  @com.vaadin.polymer.Polymer::Base = $wnd.Polymer.Base;
  // Polymer dynamic loaded does not remove unresolved
  $doc.body.removeAttribute('unresolved');
  //
  *ok.@com.vaadin.polymer.elemental.Function::call(*)()*;
}
if (!$wnd.Polymer) {
var l = $doc.createElement('link');
l.rel = 'import';
l.href = 
@com.vaadin.polymer.Polymer::absoluteHref(*)('polymer');
l.onload = done;
$doc.head.appendChild(l);
} else {
   done();
}
}-*/;

I don't know if this is a GWT issue or a GWT Polymer Elements issue.
Any idea?

Thanks.

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT polymer and Google App engine deploy

2016-06-24 Thread Jenny Zilverberg

We are building a new GWT module using GWT polymer. Our GWT version 
is 2.8.0-beta1 and vaadin-gwt-polymer-elements is 1.2.3.0 with Java 7 
(Google app engine is not supporting Java 8 yet)
When compiling GWT (using maven) polymer library is using bower to install 
all it's dependencies and creates a bower_components folder in the final 
package. We are deploying to Google app engine and Prism bower component 
has invalid chars in his path, which causing the deploy to fail. We can 
remove this library with a script from being deployed or find another 
workaround but wondering if anyone else has experienced with deploying GWT 
using Polymer to Google app engine and has some better idea. 

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-17 Thread Ed

Hi Vadim,

I just pulled down 2.8 SNAPSHOT, will give it a try,

Yes I was referencing your post.

Thanks for the info.


Regards,

Ed

On Thu, Dec 17, 2015 at 1:40 AM,  wrote:

> Dear Ed,
>
>You probably has already seen my post a week ago about Polymer
> Tutorial. I got reversed 2.7 GWT library and can answer your question --
> you can't use it with polymer. Version 2.7 misses JsInterop support
> required for Polymer. To get it work you need to use GWT 2.8 beta1 or
> SNAPSHOT. If you don't feel this is a viable solution - don't use it or
> wait until GWT release.
>
> On Wednesday, December 16, 2015 at 9:24:44 PM UTC+2, Ed wrote:
>>
>> I have been trying for days to get this operational.
>>
>> Does this even have a chance of working with 2.7?
>>
>> I have seen some data about using parts of 2.8 and 2.7 to make things
>> work.  I do not feel this is a viable solution.
>>
>> Any suggestions would be appreciated.
>>
>> Ed
>>
>> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-17 Thread Ed

@Evan

Yes the snapshots can be flaky

I will switch to beta 1

Thanks you for the reply.

Regards,

Ed

On Thu, Dec 17, 2015 at 10:45 AM, Evan Ruff  wrote:

> Hey Ed,
>
> 2.8-beta1 is available in Maven Central. I've been using it without
> problems and insulates you from the snapshot lifecycle. Overall, the
> snapshots are pretty dang stable but there are some build-breaking hiccups
> now and again.
>
> E
>
> On Thursday, December 17, 2015 at 4:41:02 AM UTC-5, Ed wrote:
>>
>> Hi Vadim,
>>
>> I just pulled down 2.8 SNAPSHOT, will give it a try,
>>
>> Yes I was referencing your post.
>>
>> Thanks for the info.
>>
>>
>> Regards,
>>
>> Ed
>>
>> On Thu, Dec 17, 2015 at 1:40 AM,  wrote:
>>
>>> Dear Ed,
>>>
>>>You probably has already seen my post a week ago about Polymer
>>> Tutorial. I got reversed 2.7 GWT library and can answer your question --
>>> you can't use it with polymer. Version 2.7 misses JsInterop support
>>> required for Polymer. To get it work you need to use GWT 2.8 beta1 or
>>> SNAPSHOT. If you don't feel this is a viable solution - don't use it or
>>> wait until GWT release.
>>>
>>> On Wednesday, December 16, 2015 at 9:24:44 PM UTC+2, Ed wrote:

 I have been trying for days to get this operational.

 Does this even have a chance of working with 2.7?

 I have seen some data about using parts of 2.8 and 2.7 to make things
 work.  I do not feel this is a viable solution.

 Any suggestions would be appreciated.

 Ed

 --
>>> 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 google-web-toolkit+unsubscr...@googlegroups.com.
>>> To post to this group, send email to google-we...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-17 Thread Evan Ruff

Hey Ed,

2.8-beta1 is available in Maven Central. I've been using it without 
problems and insulates you from the snapshot lifecycle. Overall, the 
snapshots are pretty dang stable but there are some build-breaking hiccups 
now and again.

E

On Thursday, December 17, 2015 at 4:41:02 AM UTC-5, Ed wrote:
>
> Hi Vadim,
>
> I just pulled down 2.8 SNAPSHOT, will give it a try,
>
> Yes I was referencing your post.
>
> Thanks for the info.
>
>
> Regards,
>
> Ed
>
> On Thu, Dec 17, 2015 at 1:40 AM,  wrote:
>
>> Dear Ed,
>>
>>You probably has already seen my post a week ago about Polymer 
>> Tutorial. I got reversed 2.7 GWT library and can answer your question -- 
>> you can't use it with polymer. Version 2.7 misses JsInterop support 
>> required for Polymer. To get it work you need to use GWT 2.8 beta1 or 
>> SNAPSHOT. If you don't feel this is a viable solution - don't use it or 
>> wait until GWT release. 
>>
>> On Wednesday, December 16, 2015 at 9:24:44 PM UTC+2, Ed wrote:
>>>
>>> I have been trying for days to get this operational.  
>>>
>>> Does this even have a chance of working with 2.7?
>>>
>>> I have seen some data about using parts of 2.8 and 2.7 to make things 
>>> work.  I do not feel this is a viable solution.
>>>
>>> Any suggestions would be appreciated.
>>>
>>> Ed
>>>
>>> -- 
>> 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 google-web-toolkit+unsubscr...@googlegroups.com .
>> To post to this group, send email to google-we...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-17 Thread Ed

@ALL

Up and working thanks to everyone.

I love Open Source!!

Regards,

Ed


On Thu, Dec 17, 2015 at 11:35 AM, Ed  wrote:

> @Evan
>
> Yes the snapshots can be flaky
>
> I will switch to beta 1
>
> Thanks you for the reply.
>
> Regards,
>
> Ed
>
> On Thu, Dec 17, 2015 at 10:45 AM, Evan Ruff  wrote:
>
>> Hey Ed,
>>
>> 2.8-beta1 is available in Maven Central. I've been using it without
>> problems and insulates you from the snapshot lifecycle. Overall, the
>> snapshots are pretty dang stable but there are some build-breaking hiccups
>> now and again.
>>
>> E
>>
>> On Thursday, December 17, 2015 at 4:41:02 AM UTC-5, Ed wrote:
>>>
>>> Hi Vadim,
>>>
>>> I just pulled down 2.8 SNAPSHOT, will give it a try,
>>>
>>> Yes I was referencing your post.
>>>
>>> Thanks for the info.
>>>
>>>
>>> Regards,
>>>
>>> Ed
>>>
>>> On Thu, Dec 17, 2015 at 1:40 AM,  wrote:
>>>
 Dear Ed,

You probably has already seen my post a week ago about Polymer
 Tutorial. I got reversed 2.7 GWT library and can answer your question --
 you can't use it with polymer. Version 2.7 misses JsInterop support
 required for Polymer. To get it work you need to use GWT 2.8 beta1 or
 SNAPSHOT. If you don't feel this is a viable solution - don't use it or
 wait until GWT release.

 On Wednesday, December 16, 2015 at 9:24:44 PM UTC+2, Ed wrote:
>
> I have been trying for days to get this operational.
>
> Does this even have a chance of working with 2.7?
>
> I have seen some data about using parts of 2.8 and 2.7 to make things
> work.  I do not feel this is a viable solution.
>
> Any suggestions would be appreciated.
>
> Ed
>
> --
 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 google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-we...@googlegroups.com.
 Visit this group at https://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>> --
>> 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 google-web-toolkit+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT Polymer Tutorial

2015-12-16 Thread Ed

I have been trying for days to get this operational.

Does this even have a chance of working with 2.7?

I have seen some data about using parts of 2.8 and 2.7 to make things
work.  I do not feel this is a viable solution.

Any suggestions would be appreciated.

Ed

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-16 Thread Michael Joyner


Could be a section issue. I use Gradle here.

On 12/16/2015 03:08 PM, Ed wrote:

Michael:

Thank you for you quick response. I have done this with no success. 
Perhaps I put it in the wrong section.


The docs are specific and I am a newbie to maven.

Ed

On Wed, Dec 16, 2015 at 2:41 PM, Michael Joyner > wrote:


For the Polymer tutorial to work with 2.7, you must be sure to
enable jsinterop mode 'JS'.

I haven't tried it with 2.8.0-BETA.


On 12/16/2015 02:23 PM, Ed wrote:

I have been trying for days to get this operational.

Does this even have a chance of working with 2.7?

I have seen some data about using parts of 2.8 and 2.7 to make
things work.  I do not feel this is a viable solution.

Any suggestions would be appreciated.

Ed

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com
.
To post to this group, send email to
google-web-toolkit@googlegroups.com
.
Visit this group at
https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


-- 
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 google-web-toolkit+unsubscr...@googlegroups.com
.
To post to this group, send email to
google-web-toolkit@googlegroups.com
.
Visit this group at
https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


--
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 google-web-toolkit+unsubscr...@googlegroups.com 
.
To post to this group, send email to 
google-web-toolkit@googlegroups.com 
.

Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-16 Thread Ed

Michael:

Thank you for you quick response. I have done this with no success. Perhaps
I put it in the wrong section.

The docs are specific and I am a newbie to maven.

Ed

On Wed, Dec 16, 2015 at 2:41 PM, Michael Joyner  wrote:

> For the Polymer tutorial to work with 2.7, you must be sure to enable
> jsinterop mode 'JS'.
>
> I haven't tried it with 2.8.0-BETA.
>
>
> On 12/16/2015 02:23 PM, Ed wrote:
>
> I have been trying for days to get this operational.
>
> Does this even have a chance of working with 2.7?
>
> I have seen some data about using parts of 2.8 and 2.7 to make things
> work.  I do not feel this is a viable solution.
>
> Any suggestions would be appreciated.
>
> Ed
>
> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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 google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-16 Thread Michael Joyner

For the Polymer tutorial to work with 2.7, you must be sure to enable 
jsinterop mode 'JS'.


I haven't tried it with 2.8.0-BETA.

On 12/16/2015 02:23 PM, Ed wrote:

I have been trying for days to get this operational.

Does this even have a chance of working with 2.7?

I have seen some data about using parts of 2.8 and 2.7 to make things 
work.  I do not feel this is a viable solution.


Any suggestions would be appreciated.

Ed

--
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 google-web-toolkit+unsubscr...@googlegroups.com 
.
To post to this group, send email to 
google-web-toolkit@googlegroups.com 
.

Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.


--
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer Tutorial

2015-12-16 Thread vadim

Dear Ed,

   You probably has already seen my post a week ago about Polymer 
Tutorial. I got reversed 2.7 GWT library and can answer your question -- 
you can't use it with polymer. Version 2.7 misses JsInterop support 
required for Polymer. To get it work you need to use GWT 2.8 beta1 or 
SNAPSHOT. If you don't feel this is a viable solution - don't use it or 
wait until GWT release. 

On Wednesday, December 16, 2015 at 9:24:44 PM UTC+2, Ed wrote:
>
> I have been trying for days to get this operational.  
>
> Does this even have a chance of working with 2.7?
>
> I have seen some data about using parts of 2.8 and 2.7 to make things 
> work.  I do not feel this is a viable solution.
>
> Any suggestions would be appreciated.
>
> Ed
>
>

-- 
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 google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer TODO sample

2015-08-24 Thread Cristiano Costantini

Hi Christian,
I'm interested on your alternative strategy, I however don't use Gradle,
and I've tried to convert it to a Maven project. It can be found here
https://github.com/cristcost/todo-gwt-polymer

It does not work yet:
if I import it in Eclipse and run,  SuperDevMode complains that
Component.java and TodoListType.java use lambda (even if I do use the
option -sourceLevel 1.8 on running SuperDevMode)

If I run it with maven and jetty (mvn clean install jetty:run) I get a
weird error on the Browser Javascript Console: Uncaught TypeError: Cannot
read property '$_nullMethod' of null (Note I removed the
src/main/webapp/Todo/Todo.nocache.js
file in order to run without SuperDevMode)...

Do you or anyone else have any suggestion for me to get  it working?

Thanks,
Cristiano

PS. I'm using a GWT 2.8.0-SNAPSHOT compiled from the master branch this
morning



Il giorno dom 23 ago 2015 alle ore 22:53 Christian Bauer 
christian.ba...@gmail.com ha scritto:

 I've been taking a break from my main application, and worked on an
 alternative strategy integrating Polymer and GWT 2.8 with JSInterop, you
 can find the result here:
 https://github.com/christianbauer/todo-gwt-polymer

 This code is very close to Polymer API and JavaScript, type-safety is
 therefore awful. A more powerful @JsFunction would be needed to scale this
 to more code.

 However there is no @JsExport in the code and with a few minor
 improvements, Polymer could be a great View language for GWT.

 Cheers,
 Christian

 --
 You received this message because you are subscribed to the Google Groups
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT Polymer TODO sample

2015-08-23 Thread Christian Bauer

I've been taking a break from my main application, and worked on an 
alternative strategy integrating Polymer and GWT 2.8 with JSInterop, you 
can find the result here: https://github.com/christianbauer/todo-gwt-polymer

This code is very close to Polymer API and JavaScript, type-safety is 
therefore awful. A more powerful @JsFunction would be needed to scale this 
to more code.

However there is no @JsExport in the code and with a few minor 
improvements, Polymer could be a great View language for GWT.

Cheers,
Christian

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT + Polymer - Script base detection breaks the encapsulation of GWT-backed web component (GWT 2.8-SNAPSHOT)

2015-08-04 Thread Ronny Roeller

Hi,

The script base detection in the module.nocache.js file in GWT
(2.8-SNAPSHOT) breaks the encapsulation of web components that have their
business logic provided by GWT.

GWT script base detection - provided by computeScriptBase() in
module.nocache.js - sets the path relative to the location of the host
HTML page instead of to the location of the Polymer component HTML file
(which is imported by the host page).
For example, component collaborne-hello-world is defined in
collaborne-hello-world.html (see link to code below). The component is used
by demo/index.html. Now, module.nocache.js tries to load the JavaScript
from demo/XXX.cache.js instead of hello/XXX.cache.js
GTW allows to manually set the script base via the meta property baseurl.
Unfortunately, the property is ignored if it's in the included web
component file (collaborne-hello-world.html).
The workaround is to defined the meta property in the host page
(demo/index.html), which now leaks out internal information about the
component to the host.

See:
https://github.com/Collaborne/gwt-polymer-component-example/blob/master/src/main/webapp/demo/index.html#L9

Ronny

--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Material Design with GWT(Polymer wrapper)

2015-03-16 Thread Blaze

I thought I wait maybe for Singular on this. But maybe in the next period 
Ill do it with a Template and PropertyAccess mechanism. 
This acctually is the most complex element because its binding bean values 
to the core list...

On Tuesday, March 3, 2015 at 11:56:25 PM UTC+1, Mat wrote:

 Thanks for sharing your great work.  Would be very useful to see the 
 polymer core-list integrated. 

 On Thursday, February 26, 2015 at 11:58:07 AM UTC, Blaze wrote:

 Tnx for the good words. 
 We see what singular will bring out when it becomes production candidate, 
 and then I can do something.

 This one is pretty much tested, we use it in one of our inhouse projects 
 with almost no problems at all.

 On Sun, Feb 22, 2015 at 2:02 PM, Alexander Zbiek 
 stronga...@googlemail.com wrote:

 Great work ! Always thought somebody might have done that.

 Keep up your good work. Perhaps it could be combined with gwt singular?

 --
 You received this message because you are subscribed to a topic in the 
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/google-web-toolkit/zVGA9fs_XxY/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-we...@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Material Design with GWT(Polymer wrapper)

2015-03-03 Thread Mat

Thanks for sharing your great work.  Would be very useful to see the 
polymer core-list integrated. 

On Thursday, February 26, 2015 at 11:58:07 AM UTC, Blaze wrote:

 Tnx for the good words. 
 We see what singular will bring out when it becomes production candidate, 
 and then I can do something.

 This one is pretty much tested, we use it in one of our inhouse projects 
 with almost no problems at all.

 On Sun, Feb 22, 2015 at 2:02 PM, Alexander Zbiek 
 stronga...@googlemail.com javascript: wrote:

 Great work ! Always thought somebody might have done that.

 Keep up your good work. Perhaps it could be combined with gwt singular?

 --
 You received this message because you are subscribed to a topic in the 
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/google-web-toolkit/zVGA9fs_XxY/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to 
 google-web-toolkit+unsubscr...@googlegroups.com javascript:.
 To post to this group, send email to google-we...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.




-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Material Design with GWT(Polymer wrapper)

2015-02-26 Thread Blagoja Chavkoski

Tnx for the good words.
We see what singular will bring out when it becomes production candidate,
and then I can do something.

This one is pretty much tested, we use it in one of our inhouse projects
with almost no problems at all.

On Sun, Feb 22, 2015 at 2:02 PM, Alexander Zbiek 
strongarmist...@googlemail.com wrote:

 Great work ! Always thought somebody might have done that.

 Keep up your good work. Perhaps it could be combined with gwt singular?

 --
 You received this message because you are subscribed to a topic in the
 Google Groups Google Web Toolkit group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/google-web-toolkit/zVGA9fs_XxY/unsubscribe
 .
 To unsubscribe from this group and all its topics, send an email to
 google-web-toolkit+unsubscr...@googlegroups.com.
 To post to this group, send email to google-web-toolkit@googlegroups.com.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Material Design with GWT(Polymer wrapper)

2015-02-22 Thread Alexander Zbiek

Great work ! Always thought somebody might have done that.

Keep up your good work. Perhaps it could be combined with gwt singular?

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Material Design with GWT(Polymer wrapper)

2015-02-19 Thread Blaze

Hi all,

I see a lot of people ask for Polymer in GWT. 
Here you make a public a wrapper that I extract it from un internal Project 
I have create it.

https://github.com/Baze985/GwtPolymer

hope you like it!


Cheers

p.s. Missing some of the components, but Ill try to add them in next 
period...

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

49 matches

Mail list logo