date:20160919

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

2016-09-19 Thread Freddy Boucher

+1 for https://gwt-review.googlesource.com/#/c/14430/
It's a big one!
I opened a GitHub ticket for 
it: https://github.com/gwtproject/gwt/issues/9427

Thanks


On Monday, September 19, 2016 at 7:45:43 PM UTC+10, Jakob Jarosch wrote:
>
> Hi,
> even it is a bit late, but we where a bit surprised that a merge request, 
> opened half a year ago, was still not merged.
> The bug forces us to maintain our own GWT.
> https://gwt-review.googlesource.com/#/c/14430/
>
> And then some not so important things (but its really sad, that no one 
> cares about the merge requests...):
> https://gwt-review.googlesource.com/#/c/11520/
> https://gwt-review.googlesource.com/#/c/11470/
> https://gwt-review.googlesource.com/#/c/11414/
> https://gwt-review.googlesource.com/#/c/11460/
>
> Yes, I can see some of them are now in a merge conflict state, but a year 
> ago they were not.
> I can see that this looks for everyone as a Google only project when 
> nothing gets reviewed/merged. So it's no surprise that no one is motivated 
> to contribute.
>
> Regards,
> Jakob
>
> On Saturday, September 10, 2016 at 3:35:37 PM UTC+2, Arnaud TOURNIER wrote:
>>
>> Makes sense! So better to have a "nostrict" option for the special cases
>> Thanks
>>
>> Le sam. 10 sept. 2016 14:57, Jens  a écrit :
>>
>>>
>>> Thank you I will try that -strict option.

 My suggestion is that exported @JsType (when the -generateJsExport 
 option is turned on) should be considered as entrypoints and generate 
 compilation errors, what do you think ?

>>>
>>> I think that -strict should be the default everywhere. I don't really 
>>> see any value at all in not using -strict. Maybe some people do but then 
>>> they should disable -strict. I use it since I use GWT and never had a 
>>> reason to not use it.
>>>
>>> -- J.
>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "GWT Contributors" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/google-web-toolkit-contributors/33Zw3nP3q7o/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, 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/d28e825a-c095-4812-a1c8-99527ba88f06%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/b41c168e-9aae-42c6-a1cb-acf123acbbdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: DateTimeFormat issue

2016-09-19 Thread Freddy Boucher

Thanks!

I tested the patch and it fixes the issue.

I opened a GitHub ticket to track 
it: https://github.com/gwtproject/gwt/issues/9427



On Monday, September 19, 2016 at 9:10:21 PM UTC+10, Paul Robinson wrote:
>
> Looks to me like this bug:
>   https://gwt-review.googlesource.com/#/c/14430/
>
> which was (coincidentally?) mentioned today here:
>   
> https://groups.google.com/d/msg/google-web-toolkit-contributors/33Zw3nP3q7o/eUSj5-eKEwAJ
>
> Paul
>
> On Mon, Sep 19, 2016 at 2:39 AM, Freddy Boucher  > wrote:
>
>> Hi,
>>
>> Can someone help me to understand why this test fails (I'm using GWT 
>> 2.7.0):
>>
>> package com.threatmetrix.ccc.portal.widgets.barchart.client;
>>
>> import com.google.gwt.i18n.client.DateTimeFormat;
>> import com.google.gwt.i18n.client.TimeZone;
>> import com.google.gwtmockito.GwtMockitoTestRunner;
>> import org.junit.Assert;
>> import org.junit.Test;
>> import org.junit.runner.RunWith;
>>
>> import java.util.Date;
>>
>> @RunWith(GwtMockitoTestRunner.class)
>> public class DateTimeTest {
>> @Test
>> public void working() {
>> Date date = new Date(145739520l);
>> DateTimeFormat format = 
>> DateTimeFormat.getFormat(DateTimeFormat.PredefinedFormat.ISO_8601);
>> String formattedDate = format.format(date, 
>> TimeZone.createTimeZone(0));
>>
>> Assert.assertEquals("2016-03-08T00:00:00.000+00:00", formattedDate);
>> Assert.assertEquals(date, format.parse(formattedDate));
>> }
>>
>>
>> @Test
>> public void notWorking() {
>> Date date = new Date(145963908l);
>> DateTimeFormat format = 
>> DateTimeFormat.getFormat(DateTimeFormat.PredefinedFormat.ISO_8601);
>> String formattedDate = format.format(date, 
>> TimeZone.createTimeZone(0));
>>
>> Assert.assertEquals("2016-04-03T23:18:00.000+00:00", formattedDate);
>> Assert.assertEquals(date, format.parse(formattedDate));
>> }
>> }
>>
>>
>> Results:
>>
>>- DateTimeTest#*working()*: OK
>>- DateTimeTest#*notWorking()*: there is a difference of 1 day between 
>>the *Expected* and the *Actual* date
>>
>>
>> Log:
>>
>> java.lang.AssertionError: 
>> Expected :Sun Apr 03 09:18:00 AEST 2016
>> Actual   :Mon Apr 04 09:18:00 AEST 2016
>>   
>>
>>
>>
>> at 
>> com.threatmetrix.ccc.portal.widgets.barchart.client.DateTimeTest.notWorking(DateTimeTest.java:32)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at 
>> com.google.gwtmockito.GwtMockitoTestRunner.run(GwtMockitoTestRunner.java:301)
>> at 
>> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
>> at 
>> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
>> at 
>> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:262)
>> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at java.lang.reflect.Method.invoke(Method.java:497)
>> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
>>
>> 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-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: frame.setUrl() does not work with Chrome

2016-09-19 Thread Howard Yeh

For what it's worth, frame.setUrl works fine across browsers for me.  Did 
you check your JS in Chrome?


On Saturday, September 17, 2016 at 3:45:24 PM UTC-7, 
muhamed.el...@gmail.com wrote:
>
> I am trying to call a javascript function through those lines
>
> *String js = "javascript:showNumber(5);void(0)";*
> *frame.setUrl(js);*
>
> This work properly in Firfox but it does not work in Chrome, any one can 
> help ?
>
> 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: jsInterop cast to JavaScriptObject

2016-09-19 Thread Marcio Alves

Thanks!

Em segunda-feira, 19 de setembro de 2016 13:12:06 UTC-3, Bauna escreveu:
>
> Hi Marcio,
> You can check: https://github.com/GWTReact/gwt-interop-utils that several 
> helper to convert java to js and back.
> Regards,
> -- 
> Bauna
>
> On 16/09/16 15:47, Marcio Alves wrote:
>
> Hi,  
>
>Is it possible to casto a jsInterop object to a JavaScriptObject? 
>
>I am trying to use GWT-Polymer's IronList, but it requires a 
> JsArray.
>
>I managed to create my JsArray from a JSNI code, but I don't know how 
> to create it in Java, since the class do not extends from JavaScriptObject.
>
> Thanks,
> Marcio Alves
>
>
> -- 
> 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: jsInterop cast to JavaScriptObject

2016-09-19 Thread Pablo Nussembaum

Hi Marcio,
You can check: https://github.com/GWTReact/gwt-interop-utils that several 
helper to convert java to js and back.
Regards,
-- 
Bauna

On 16/09/16 15:47, Marcio Alves wrote:
> Hi, 
>
>Is it possible to casto a jsInterop object to a JavaScriptObject? 
>
>I am trying to use GWT-Polymer's IronList, but it requires a 
> JsArray.
>
>I managed to create my JsArray from a JSNI code, but I don't know how to 
> create it in Java, since the class do not extends from JavaScriptObject.
>
> Thanks,
> Marcio Alves
>
>
> -- 
> 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: DateTimeFormat issue

2016-09-19 Thread Paul Robinson

Looks to me like this bug:
  https://gwt-review.googlesource.com/#/c/14430/

which was (coincidentally?) mentioned today here:

https://groups.google.com/d/msg/google-web-toolkit-contributors/33Zw3nP3q7o/eUSj5-eKEwAJ

Paul

On Mon, Sep 19, 2016 at 2:39 AM, Freddy Boucher 
wrote:

> Hi,
>
> Can someone help me to understand why this test fails (I'm using GWT
> 2.7.0):
>
> package com.threatmetrix.ccc.portal.widgets.barchart.client;
>
> import com.google.gwt.i18n.client.DateTimeFormat;
> import com.google.gwt.i18n.client.TimeZone;
> import com.google.gwtmockito.GwtMockitoTestRunner;
> import org.junit.Assert;
> import org.junit.Test;
> import org.junit.runner.RunWith;
>
> import java.util.Date;
>
> @RunWith(GwtMockitoTestRunner.class)
> public class DateTimeTest {
> @Test
> public void working() {
> Date date = new Date(145739520l);
> DateTimeFormat format = 
> DateTimeFormat.getFormat(DateTimeFormat.PredefinedFormat.ISO_8601);
> String formattedDate = format.format(date, 
> TimeZone.createTimeZone(0));
>
> Assert.assertEquals("2016-03-08T00:00:00.000+00:00", formattedDate);
> Assert.assertEquals(date, format.parse(formattedDate));
> }
>
>
> @Test
> public void notWorking() {
> Date date = new Date(145963908l);
> DateTimeFormat format = 
> DateTimeFormat.getFormat(DateTimeFormat.PredefinedFormat.ISO_8601);
> String formattedDate = format.format(date, 
> TimeZone.createTimeZone(0));
>
> Assert.assertEquals("2016-04-03T23:18:00.000+00:00", formattedDate);
> Assert.assertEquals(date, format.parse(formattedDate));
> }
> }
>
>
> Results:
>
>- DateTimeTest#*working()*: OK
>- DateTimeTest#*notWorking()*: there is a difference of 1 day between
>the *Expected* and the *Actual* date
>
>
> Log:
>
> java.lang.AssertionError:
> Expected :Sun Apr 03 09:18:00 AEST 2016
> Actual   :Mon Apr 04 09:18:00 AEST 2016
>   
>
>
>
> at com.threatmetrix.ccc.portal.widgets.barchart.client.
> DateTimeTest.notWorking(DateTimeTest.java:32)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.google.gwtmockito.GwtMockitoTestRunner.run(
> GwtMockitoTestRunner.java:301)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(
> JUnit4IdeaTestRunner.java:117)
> at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(
> JUnit4IdeaTestRunner.java:42)
> at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(
> JUnitStarter.java:262)
> at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
>
> 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.
>

-- 
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-contrib] Re: Last call for 2.8.0-RC3

2016-09-19 Thread Jakob Jarosch

Hi,
even it is a bit late, but we where a bit surprised that a merge request, 
opened half a year ago, was still not merged.
The bug forces us to maintain our own GWT.
https://gwt-review.googlesource.com/#/c/14430/

And then some not so important things (but its really sad, that no one 
cares about the merge requests...):
https://gwt-review.googlesource.com/#/c/11520/
https://gwt-review.googlesource.com/#/c/11470/
https://gwt-review.googlesource.com/#/c/11414/
https://gwt-review.googlesource.com/#/c/11460/

Yes, I can see some of them are now in a merge conflict state, but a year 
ago they were not.
I can see that this looks for everyone as a Google only project when 
nothing gets reviewed/merged. So it's no surprise that no one is motivated 
to contribute.

Regards,
Jakob

On Saturday, September 10, 2016 at 3:35:37 PM UTC+2, Arnaud TOURNIER wrote:
>
> Makes sense! So better to have a "nostrict" option for the special cases
> Thanks
>
> Le sam. 10 sept. 2016 14:57, Jens  a 
> écrit :
>
>>
>> Thank you I will try that -strict option.
>>>
>>> My suggestion is that exported @JsType (when the -generateJsExport 
>>> option is turned on) should be considered as entrypoints and generate 
>>> compilation errors, what do you think ?
>>>
>>
>> I think that -strict should be the default everywhere. I don't really see 
>> any value at all in not using -strict. Maybe some people do but then they 
>> should disable -strict. I use it since I use GWT and never had a reason to 
>> not use it.
>>
>> -- J.
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "GWT Contributors" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-web-toolkit-contributors/33Zw3nP3q7o/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, 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/d28e825a-c095-4812-a1c8-99527ba88f06%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/3e4b22d8-1324-417d-8762-73e3d9844323%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

Re: DateTimeFormat issue

Re: frame.setUrl() does not work with Chrome

Re: jsInterop cast to JavaScriptObject

Re: jsInterop cast to JavaScriptObject

Re: DateTimeFormat issue

Re: [gwt-contrib] Re: Last call for 2.8.0-RC3

7 matches

Site Navigation

Mail list logo

Footer information