Re: GWT SDM Polymer

Are there recommendations for GWT/polymer versions that play nice together? And by polymer version I guess I mean the vaadin artifact that is the wrapper for polymer. vaadin-gwt-polymer-elements

I am using 1.2.3.0 and gwt-2.8.0-rc2 and it does not appear to work, I get an error in Polymer.java:159: ok_0_g$.call_0_g$ is not a function. I also dont understand why the tutorial says to use scope: provided in maven for the artifact.

I am struggling to get this to work. For reference the relevant section of code in Polymer.java is (line reads)  ok.@com.vaadin.polymer.elemental.Function::call(*)();


    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();
        }
    }-*/;

On Monday, December 21, 2015 at 3:14:37 AM UTC-8, Ed wrote:

@ VADIM Thank You!!!

I think I have solved the issue by switching to a pure maven build rather that using the gwt plugin.

I think having multiple projects using multiple JDK. GWT Versions may have confused Eclipse MARS.

So I refreshed the build into a new directory using:

2.8.0-SNAPSHOT

MAVEN

POLYMER 1.2.1.0

ECLIPSE Mars.1

Now SDM provides access without the JSINTEROP errors.

The purpose of this is exploration and prototyping of a UI using POLYMER and modern design methodilogies.

I was a newbie to maven but an quickly coming to be a fan. (Used ant for many many years).

Thank You,

Ed

On Mon, Dec 21, 2015 at 3:34 AM, <va...@ant.ee> wrote:

Hello Ed,

        I am working with polymer elements 1.2.1.0 and GWT 2.8.0-beta1 closely and I found one missing thing at your configuration. Particularly at your gwt.xml should be:

  <inherits name="com.vaadin.polymer.

Elements"/>
  <set-configuration-property name="CssResource.enableGss" value="true"/>
    
       The problem may be connected to GSS that is switched off by default, but  must be "ON" for polymer elements to work.  If you still use old CSS style you may add one more string:

  <set-configuration-property name="CssResource.legacy" value="true" />

       This will temporary enable CSS->GSS auto conversion. But I will not suggest you to work with conversion, because it will be deprecated later on

Regards,

--
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+unsubscribe@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+unsubscribe@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.