Re: [gwt-contrib] Re: Experimental release of Elemental2

2016-08-02 Thread 'Roberto Lublinerman' via GWT Contributors 
Looking at the elemental code that uses a lambda which will not be
EventHandler but a JsFunction. Could you try with an anonymous EventHandler
instead?

On Tue, Aug 2, 2016 at 1:51 AM, Steve Andrews 
wrote:

> I've created a quick test project and put it at
> https://github.com/steveandrews01/JsInteropTest
>
> The click listener only works if compiled with the flag set. If I run it
> without the flag and inspect the DOM in Chrome then the event listener is
> not attached to the button.
>
> (Changing the flag needs a SDM cache clear!)
>
> Steve
>
>
> On Monday, 1 August 2016 20:48:13 UTC+1, Goktug Gokdogan wrote:
>>
>> Can you share a small repro for this? (EventListener requiring
>> generateJsInteropExports)
>>
>> On Thu, Jul 28, 2016 at 12:27 AM, Steve Andrews 
>> wrote:
>>
>>> I've done some more testing and cleared my cache and can still only get
>>> EventListener to work with the generateJsInteropExports flag set.
>>>
>>> I've had another problem with EventListener on a select element but I'm
>>> using an external framework for my project (Materialize) and think that
>>> it's their framework that doesn't like the EventListener object. If I use a
>>> standard select element then it's working. I can get around this by adding
>>> the listener through a JQuery wrapper so no problem.
>>>
>>> I've also found that Window.location returns an Object - will this be
>>> sorted in a future release?
>>>
>>> Other than that Elemental is working well so far! Nice work!
>>>
>>> Steve
>>>
>>> On Friday, 22 July 2016 11:31:24 UTC+1, Jens wrote:


 It only works with the generateJsInteropExports flag set though.
>

 Sounds like a bug to me.

 -- J.

>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/16498b97-7d3d-44c7-b42b-e40be9de1e26%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/fca60fc6-7cfd-44ea-9728-295c77293d74%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAC7T7gnEftgbDyZ9_6hqQMonpyLoQW80YcX706jtPGYntKXx2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.8.0 RC1 is here!

2016-08-02 Thread Andrei Preda 
Thank you!!

On Monday, August 1, 2016 at 8:14:26 PM UTC+2, Thomas Broyer wrote:
>
> This is https://github.com/gwtproject/gwt/issues/9382 and is a bug in 
> gwt-jackson's POM.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/1647d424-322d-42bf-9ca6-8126023127c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.8.0 RC1 is here!

2016-08-02 Thread Frank Taffelt 
thanks for spotting in the right direction. yes i had an exclusion for the 
xerces in another dependency.


On Tuesday, August 2, 2016 at 2:56:19 AM UTC+2, Thomas Broyer wrote:
>
> Do you somehow exclude xerces?
> Here's dependency:tree excerpt from the "dynatablerf" sample; see how it 
> inherits 1.4.01 from xercesImpl 2.11.0:
>
> [INFO] +- com.google.gwt:gwt-dev:jar:2.8.0-rc1:provided
> [INFO] |  +- com.google.code.gson:gson:jar:2.6.2:provided
> [INFO] |  +- org.ow2.asm:asm:jar:5.0.3:provided
> [INFO] |  +- org.ow2.asm:asm-util:jar:5.0.3:provided
> [INFO] |  |  \- org.ow2.asm:asm-tree:jar:5.0.3:provided
> [INFO] |  +- org.ow2.asm:asm-commons:jar:5.0.3:provided
> [INFO] |  +- colt:colt:jar:1.2.0:provided
> [INFO] |  +- ant:ant:jar:1.6.5:provided
> [INFO] |  +- commons-collections:commons-collections:jar:3.2.2:provided
> [INFO] |  +- commons-io:commons-io:jar:2.4:provided
> [INFO] |  +- com.ibm.icu:icu4j:jar:50.1.1:provided
> [INFO] |  +- tapestry:tapestry:jar:4.0.2:provided
> [INFO] |  +- net.sourceforge.htmlunit:htmlunit:jar:2.19:provided
> [INFO] |  |  +- xalan:xalan:jar:2.7.2:provided
> [INFO] |  |  |  \- xalan:serializer:jar:2.7.2:provided
> [INFO] |  |  +- org.apache.commons:commons-lang3:jar:3.4:provided
> [INFO] |  |  +- org.apache.httpcomponents:httpclient:jar:4.5.1:provided
> [INFO] |  |  |  \- org.apache.httpcomponents:httpcore:jar:4.4.3:provided
> [INFO] |  |  +- org.apache.httpcomponents:httpmime:jar:4.5.1:provided
> [INFO] |  |  +- commons-codec:commons-codec:jar:1.10:provided
> [INFO] |  |  +- net.sourceforge.htmlunit:htmlunit-core-js:jar:2.17:provided
> [INFO] |  |  +- xerces:xercesImpl:jar:2.11.0:provided
> [INFO] |  |  |  \- xml-apis:xml-apis:jar:1.4.01:provided
> [INFO] |  |  +- net.sourceforge.nekohtml:nekohtml:jar:1.9.22:provided
> [INFO] |  |  +- net.sourceforge.cssparser:cssparser:jar:0.9.18:provided
> [INFO] |  |  +- commons-logging:commons-logging:jar:1.2:provided
>
> Maybe it could be linked to the version of Maven being used? Which version 
> are you using?
>
> On Monday, August 1, 2016 at 11:41:21 AM UTC+2, Frank Taffelt wrote:
>>
>> some steps further:
>>
>> [INFO] \- com.google.gwt:gwt-dev:jar:2.8.0-rc1:compile
>> [INFO]+- com.google.code.gson:gson:jar:2.6.2:compile
>> [INFO]+- org.ow2.asm:asm:jar:5.0.3:compile
>> [INFO]+- org.ow2.asm:asm-util:jar:5.0.3:compile
>> [INFO]|  \- org.ow2.asm:asm-tree:jar:5.0.3:compile
>> [INFO]| \- (org.ow2.asm:asm:jar:5.0.3:compile - omitted for 
>> duplicate)
>> [INFO]+- org.ow2.asm:asm-commons:jar:5.0.3:compile
>> [INFO]|  \- (org.ow2.asm:asm-tree:jar:5.0.3:compile - omitted for 
>> duplicate)
>> [INFO]+- colt:colt:jar:1.2.0:compile
>> [INFO]+- ant:ant:jar:1.6.5:compile
>> [INFO]+- commons-collections:commons-collections:jar:3.2.2:compile
>> [INFO]+- commons-io:commons-io:jar:2.4:compile
>> [INFO]+- com.ibm.icu:icu4j:jar:50.1.1:compile
>> [INFO]+- tapestry:tapestry:jar:4.0.2:compile
>> [INFO]+- net.sourceforge.htmlunit:htmlunit:jar:2.19:compile
>> [INFO]|  +- xalan:xalan:jar:2.7.2:compile
>> [INFO]|  |  \- xalan:serializer:jar:2.7.2:compile
>> [INFO]|  | \- xml-apis:xml-apis:jar:1.3.04:compile
>>
>> in the referenced xml-apis version 1.3.04 there is no 
>> class  org/w3c/dom/ElementTraversal. So adding a new dependency to xml-apis 
>> with version 1.4.01 fixed my build.  
>> btw: trying a clean dagger-guice-rf-activities (because it also uses UI 
>> binder) build also breaks on my system with the same error. 
>>
>> On Friday, July 29, 2016 at 5:47:36 PM UTC+2, Thomas Broyer wrote:
>>>
>>> I'd start with double-checking your dependencies. With 2.8 from the 
>>> Central repository, most dependencies that used to be bundled into the 
>>> gwt-user and gwt-dev JARs have now been unbundled and properly declared as 
>>> Maven dependencies, so you may have had exclusions that now need to be 
>>> removed.
>>> I just updated my archetypes to 2.8.0-rc1 and they still work OK (from 
>>> the tests): 
>>> https://travis-ci.org/tbroyer/gwt-maven-archetypes/builds/148343628
>>>
>>> On Friday, July 29, 2016 at 4:27:23 PM UTC+2, Frank Taffelt wrote:

 thanks for the rc.

 updated a project coming from 2.7.0. the project is mainly based on 
 thomas gwt maven-archetypes.

 the following build error is dumped doing an mvn package on the 
 gwt-compilation step:

 [INFO]   [WARN] Line 39 column 7: encountered "(". Was 
 expecting one of: 
 [INFO][ERROR] An internal compiler exception occurred
 [INFO] com.google.gwt.dev.jjs.InternalCompilerException: Unexpected 
 error during visit.
 [INFO]  at 
 com.google.gwt.dev.jjs.ast.JVisitor.translateException(JVisitor.java:111)
 [INFO]  at 
 com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:276)
 [INFO]  at 
 com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265)
 [INFO]  at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisito

Re: [gwt-contrib] Re: Experimental release of Elemental2

2016-08-02 Thread Steve Andrews 
I've created a quick test project and put it at 
https://github.com/steveandrews01/JsInteropTest

The click listener only works if compiled with the flag set. If I run it 
without the flag and inspect the DOM in Chrome then the event listener is 
not attached to the button.

(Changing the flag needs a SDM cache clear!)

Steve


On Monday, 1 August 2016 20:48:13 UTC+1, Goktug Gokdogan wrote:
>
> Can you share a small repro for this? (EventListener requiring 
> generateJsInteropExports)
>
> On Thu, Jul 28, 2016 at 12:27 AM, Steve Andrews  > wrote:
>
>> I've done some more testing and cleared my cache and can still only get 
>> EventListener to work with the generateJsInteropExports flag set.
>>
>> I've had another problem with EventListener on a select element but I'm 
>> using an external framework for my project (Materialize) and think that 
>> it's their framework that doesn't like the EventListener object. If I use a 
>> standard select element then it's working. I can get around this by adding 
>> the listener through a JQuery wrapper so no problem.
>>
>> I've also found that Window.location returns an Object - will this be 
>> sorted in a future release?
>>
>> Other than that Elemental is working well so far! Nice work!
>>
>> Steve
>>
>> On Friday, 22 July 2016 11:31:24 UTC+1, Jens wrote:
>>>
>>>
>>> It only works with the generateJsInteropExports flag set though.

>>>
>>> Sounds like a bug to me.
>>>
>>> -- J.
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/16498b97-7d3d-44c7-b42b-e40be9de1e26%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/fca60fc6-7cfd-44ea-9728-295c77293d74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.