[gwt-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Brandon Donnelson]

I haven't dug in yet, just wanting to use it. That sounds promising. Using 
bookmarlets doesn't work when the module is embedded in another iframe. so 
the next issue I need to deal with is helping detect the module when it's 
not in the main body but in another iframe of the document. 

The other workaround is to implant the project.nocache.js js launching in 
the war and send it off to the external server. So this makes another 
problem I have hit a couple times. Where I change the var hostName = 
"127.0.0.1";  to a specific ip because I loaded the app with 
project.nocache.js. I like this hack but I'm wishing I could set that in 
the code server launcher arguments. 

Anyway it's all about using an external server. 

-- 
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/41735d5b-1848-44e6-be31-3a34d87ddec7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jsinterop with browser-specific api

[Thomas Broyer]

On Friday, September 9, 2016 at 8:32:08 PM UTC+2, Zufar Fakhurtdinov wrote:
>
> Hi all. I'm trying to understand how can I effective work with jsinterop 
> and browser-specific api.
> For example Fullscreen api is mostly work in latest browsers, but methods 
> are prefixed.
>
> Before jsinterop I was write something like this:
>
>
> public static native void leaveFullscreen() /*-{
>   if ($doc.cancelFullscreen) {
> $doc.cancelFullscreen();
>   } else if ($doc.mozCancelFullScreen) {
> $doc.mozCancelFullScreen();
>   } else if ($doc.webkitCancelFullScreen) {
> $doc.webkitCancelFullScreen();
>   }
>
> }-*/; 
>
> What should I do now? Add mozCancelFullScreen, webkitCancelFullScreen 
> methods to my jsinteropped Document interface? And then add static jsni 
> method 
> boolean exists(Object a)/*-{return a;}-*/; and add java method with "if 
> (exists(..))"  chain. 
> It looks very verbose and inefficiently.
>

Have a look at https://github.com/gwtproject/gwt/issues/9327

I'd do it like:

@JsOverlay
public void exitFullScreen() {
  if (getExitFullScreen() != null) {
nativeExitFullScreen();
  } else if (getMozCancelFullScreen() != null) {
mozCancelFullScreen();
  } else if (getWebkitExitFullscreen() != null) {
webkitExitFullscreen();
  } else if (getMsExitFullscreen() != null) {
msExitFullscreen();
  } else {
throw new UnsupportedOperationException();
  }
}

@JsMethod(name = "exitFullScreen") private native void 
nativeExitFullScreen();
@JsProperty(name = "exitFullScreen") private native Object 
getExitFullScreen();
@JsMethod private native void webkitExitFullscreen();
@JsProperty(name = "webkitExitFullscreen") private native Object 
getWebkitExitFullscreen();
@JsMethod private native void mozCancelFullScreen();
@JsProperty(name = "mozCancelFullScreen") private native Object 
getMozCancelFullScreen();
@JsMethod private native void msExitFullscreen();
@JsProperty(name = "msExitFullscreen") private native Object 
getMsExitFullscreen();

It's a bit verbose in the method declarations (but the idea of JsInterop is 
that this could be somehow 
generated; https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_API 
has the info in wiki format, there probably is a machine-readable format 
somewhere, from Closure externs 

 
or DefinitelyTyped; an equivalence table like in the MDN wiki could even 
allow generating that @JsOverlay method),
but the if-cascade is otherwise the same as the original JSNI method.

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

[Thomas Broyer]

As we've delayed the release a bit, let's add another documentation fix: 
https://gwt-review.googlesource.com/16860

On Thursday, September 8, 2016 at 4:27:36 PM UTC+2, Daniel Kurka wrote:
>
> Hi all,
>
> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email with 
> any outstanding reviews that you want to see included.
>
> -Daniel
>

-- 
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/7d8ef60a-3485-4b33-befe-8d1c15676cd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jsinterop with browser-specific api

[Kirill Prazdnikov]

Doing the same

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

jsinterop with browser-specific api

[Kirill Prazdnikov]

But above sample doing the name. Or you can create a baseclss and  3 impl and 
instantiate the correct one.

-- 
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 2.8.0 RC2 is here!

[Василий Старцев]

Hmm. This is help. Thank you. 

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

jsinterop with browser-specific api

[Zufar Fakhurtdinov]

Hi all. I'm trying to understand how can I effective work with jsinterop 
and browser-specific api.
For example Fullscreen api is mostly work in latest browsers, but methods 
are prefixed.

Before jsinterop I was write something like this:


public static native void leaveFullscreen() /*-{
  if ($doc.cancelFullscreen) {
$doc.cancelFullscreen();
  } else if ($doc.mozCancelFullScreen) {
$doc.mozCancelFullScreen();
  } else if ($doc.webkitCancelFullScreen) {
$doc.webkitCancelFullScreen();
  }

}-*/; 

What should I do now? Add mozCancelFullScreen, webkitCancelFullScreen 
methods to my jsinteropped Document interface? And then add static jsni 
method 
boolean exists(Object a)/*-{return a;}-*/; and add java method with "if 
(exists(..))"  chain. 
It looks very verbose and inefficiently.

-- 
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 2.8.rc2 doesn't work correctly for ie* values.

[Thomas Broyer]

AFAICT it worked the same with 2.7. With the default user.agent values, I 
get 3 permutations. The compilation-mappings.txt for the sample app created 
with webAppCreator and added collapse-property is:
45FECB51EB688981D36858C76F8E630A.cache.js
user.agent ie10

45FECB51EB688981D36858C76F8E630A.cache.js
user.agent ie9

9460A5DDEA149F39C5F568A01F09776F.cache.js
user.agent gecko1_8

9460A5DDEA149F39C5F568A01F09776F.cache.js
user.agent safari

D49362226B11A54324AFDC28060B5C94.cache.js
user.agent ie8

Devmode:devmode.js

Could it be because of other properties whose default value depend on 
user.agent, such as audioElementSupport, canvasElementSupport, 
dragEventSupport, touchEventSupport, and videoElementSupport?

On Friday, September 9, 2016 at 6:29:53 PM UTC+2, Rocco De Angelis wrote:
>
> Hi All,
>
> it seems that:
>
>  
>
> doesn't work correctly if my user.agent property contains an ie* value.
>
> For: 
>
>   and 
> 
>
>
> Two permutations will be generated: one for [gecko1_8, safari] and a 
> second for [ie9].
> Is that a bug or the does GWT team change something?
>
> BR
>
> Rocco 
>
>
>

-- 
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: ScriptInjector seems to be broken (2.8-SNAPSHOT)

['Goktug Gokdogan' via GWT Contributors]

We should hold up the release. There is another path around arrays as well.

On Fri, Sep 9, 2016 at 8:04 AM, Colin Alworth  wrote:

> Another issue at may warrant attention - https://github.com/
> gwtproject/gwt/issues/9424. This was brought up some time ago, but wasn't
> reduced to be reproducible until now (which is funny, given how minimal the
> test case is).
>
> On Fri, Sep 9, 2016 at 9:30 AM 'Daniel Kurka' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com> wrote:
>
>> +Goktug Gokdogan  +Roberto Lublinerman
>>   Should we be holding RC3, I guess so right?
>>
>> On Fri, Sep 9, 2016 at 4:12 PM Jens  wrote:
>>
>>>
>>> Can you file an issue and ping Daniel (by mail or hangout) to delay the
 RC3 a bit? (if not already too late, as it's 4pm cest)

>>>
>>> Done.
>>>
>>> --
>>> 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/6386bb88-f488-
>>> 4144-b830-99ddb387b677%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/CALLujirOwMPQTKzDuJtmtF0hF2bXV
>> r%3Dij-V240vzP6Bh5SMRAA%40mail.gmail.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/CAN%3DyUA3e16Cw5iFU9qDNAP7XYwnpZm571vhJtDSYycDGzdTEtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 RC2 is here!

[Thomas Broyer]

The arrays are normalized to start on Sundays (you'd find the same oddity with 
the French locale, as weeks start on Monday too in France), you need to use 
firstDayOfTheWeek and adjust your indexes accordingly:

 for (int i = 0; i < 7; i++) {
   ….weekdaysFull()[(i + ….firstDayOfTheWeek()) % 7)];
 }

http://www.gwtproject.org/javadoc/latest/com/google/gwt/i18n/shared/DateTimeFormatInfo.html#firstDayOfTheWeek()

-- 
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 2.8.0 RC2 is here!

[Василий Старцев]

sorry for my english)

In russia week starts with Monday (Понедельник)

Such a difference leads me to use workarround instead of 
*LocaleInfo.getCurrentLocale().getDateTimeFormatInfo()*

This case makes me in big disapointment: I run this code on JDK8
DateFormatSymbols symbols = new DateFormatSymbols(new Locale("ru"));
for (String day : symbols.getWeekdays()) {
System.out.println(day);
}

and got

воскресенье
понедельник
вторник
среда
четверг
пятница
суббота

It's totally wrong!

To be more preciese here is my use case: in GWT UI ComboBox with names of 
week days and my users are Russians and they used to use weeks with Monday 
as a first day.
The ideal solution is to fill this ComboBox with values from 
*LocaleInfo.getCurrentLocale().getDateTimeFormatInfo().weekdaysFullStandalone() 
*bot no way.

The order of week days in Russian is such as in Ierald locale en_IE example 



пятница, 9 сентября 2016 г., 17:42:20 UTC+3 пользователь Thomas Broyer 
написал:
>
>
>
> On Friday, September 9, 2016 at 4:34:02 PM UTC+2, Василий Старцев wrote:
>>
>> Great! But there is a bug:
>> *com.google.gwt.i18n.client.impl.cldr.DateTimeFormatInfoImpl_ru* still 
>> have wrong weekdays order.
>>
>> @Override
>> public String[] weekdaysFull() {
>>   return new String[] {
>>   "воскресенье",
>>   "понедельник",
>>   "вторник",
>>   "среда",
>>   "четверг",
>>   "пятница",
>>   "суббота"
>>   };
>> }
>>
>>
>>
>> should be 
>>
>>
>>
>> @Override
>> public String[] weekdaysFull() {
>>   return new String[] {
>>   "понедельник",
>>   "вторник",
>>   "среда",
>>   "четверг",
>>   "пятница",
>>   "суббота",
>>
>>   "воскресенье"
>>   };
>> }
>>
>>
>>
>> Please fix this.
>>
>>
> weekdaysFull starts on Sunday: 
> https://github.com/gwtproject/gwt/blob/caf2f6fa9a35a2602ea7b16426473dd9fcc92cea/user/src/com/google/gwt/i18n/shared/DefaultDateTimeFormatInfo.java#L333-L343
> and Google Translate tells me воскресенье (which you switched from the 
> first to the last position) is Sunday, and thus should be first here.
> So I see no bug there.
>
> BTW, you employed the word "still", but this had never been reported; and 
> the proper way to report a bug is to file an issue on the issue tracker on 
> GitHub: http://www.gwtproject.org/makinggwtbetter.html#issuetracking
>  
>

-- 
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 2.8.rc2 doesn't work correctly for ie* values.

[Rocco De Angelis]

Hi All,

it seems that:

 

doesn't work correctly if my user.agent property contains an ie* value.

For: 

  and 



Two permutations will be generated: one for [gecko1_8, safari] and a second 
for [ie9].
Is that a bug or the does GWT team change something?

BR

Rocco 


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

['Roberto Lublinerman' via GWT Contributors]

Arnaud, have you tried using -strict? GWT ignores compilation units with
errors if they are not explicitly reachable from the entry point. I assume
your Toto class is only referenced from JS. So if this class has any
compile error (like missing references) then GWT does not see the class,
much less know it is a JsType. Strict mode should give you an error in this
case.

On Fri, Sep 9, 2016 at 6:09 AM, Arnaud TOURNIER  wrote:

> I have one problem which is recurring, related to JsInterop.
>
> Sometimes the JsInterop JS stub is not generated because of (seemingly) an
> internal error in SuperDevMode (and GWTC it seems), but nothing is logged,
> so it's difficult to diagnose.
>
> For example, in an application (which does not inherits the User module),
> when i write a class like this, the JS stub is generated correctly :
>
> @JsInterop
> public class Toto
> {
> public void doSomething()
> {
> // really nothing here...
> }
> }
>
> But if i change it to :
>
> @JsInterop
> public class Toto
> {
> public void doSomething()
> {
> Window.alert( "yeah" );
> }
> }
>
> Then the JS stub is not generated (i mean the Toto constructor function is
> not made available to JS scope).
>
> I understand that Window.alert(...) is implemented in the User module and
> since i don't inherit from it, the thing cannot be generated. But no
> message is generated (neither by SDM nor by the GWTC if i remember well),
> which is then difficult to diagnose...
>
> Note : i should be able to produce a minimal repro case for this thing.
>
>
> Then sometimes, a @JsInterop class would not be exported to JS, but if i
> change its name then it's generated, which is... weird.
>
> For this one i am not sure i can give a minimal repro case because it
> happens on quite large projects (angular2 with gwt 2.8)...
>
>
> I saw another error:
>
> It was in a @JsInterop class, which called a template method (i mean with
>  in the signature of the method). I had to specify the  type to call
> it to have the SDM generating the class. If i didn't, the javac would infer
> correctly the  type (so no error appears in the IDE, which is Eclipse in
> my case), but it seemed that SDM did not manage to infer the type correctly
> because then the class would not be accessible from javascript... I can
> give you a sample file if you need.
>
>
> A last one : i tried migrating a big app from 2.7 to 2.8-rc2 (same problem
> with previous sub versions of the 2.8). The compiler goes on compiling then
> does the linking, but it suddenly crashes without saying anything (i tried
> TRACE and DEBUG log levels with no more useful information) and results in
> a maven build failure. The build is happening in maven. Since the app is
> quite big, i guess the problem comes from a dependency i use which is not
> 2.8 friendly (did not have enough time to investigate that deeply). But
> again, the problem is not that the compile does not work, but that no
> useful message is generated to understand the error.
>
> For this one, i can give you the code, but privately since it is a
> business app that is not open source...
>
> Thanks !
>
> Arnaud Tournier
> LTE Consulting
>
>
> Le jeudi 8 septembre 2016 16:27:36 UTC+2, Daniel Kurka a écrit :
>>
>> Hi all,
>>
>> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email
>> with any outstanding reviews that you want to see included.
>>
>> -Daniel
>>
> --
> 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/5e5b6585-aba1-
> 48ce-a5d6-6f9a702e801b%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/CAC7T7g%3DOvF6Bu%2BmFdYDmNF2F11zQgDxdFo65j6zTYnWFQr2ZXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Autocompletion with RPC under the MVP model : how to instanciate Suggestbox(suggestOracle) without refering any service into the view ?

[Eddy]

Thank you a lot for these detailed explanation which where very helpfull 
for me Thomas !

I add passed successfully all your methods, going through the proxy method, 
until the delegating object in order to be used with others views.
(just could you give me the utility about the case of the word final in the 
line "private final SuggestOracle oracle = new DelegatingSuggestOracle()" ?)

I have written the call of setSuggestOracle into the revealDisplay() of the 
presenter :
=> with your solution I am even be able to change the call of the service 
by a call of my existing injected model (which calls itself the service)

Many thanks Thomas !

Have a good week-end

Le vendredi 9 septembre 2016 10:38:52 UTC+2, Thomas Broyer a écrit :
>
>
>
> On Friday, September 9, 2016 at 9:31:27 AM UTC+2, Eddy wrote:
>>
>> Thank you for your first help Thomas !
>>
>> What I had tried is to write a get method from the view/display 
>> interface, which return the suggestBox object and which I had called from 
>> the presenter on the onBind or revealDisplay :
>> => I could redefine as the same the requestSuggestions() into the 
>> presenter but then I didn't know how to transmit it to the view / how to 
>> instanciate the visible SuggestBox object for showing it into the view 
>> (regarding the new SuggestBox(oracle) line).
>>
>
> Something like:
> in the presenter:
> public void getSuggestions(SuggestOracle.Request req, 
> SuggestOracle.Callback callback) {
>   service.getSuggestions(req, callback);
> }
>
> in the view:
> SuggestOracleCustom oracle = new SuggestOracleCustom() { 
> @Override
> public void requestSuggestions(SuggestOracle.Request req, 
> SuggestOracle.Callback callback) {
> presenter.getSuggestions(req, new 
> SuggestOracleCallbackCustom(req, callback));
> }
> };
> SuggestBox suggestBox = new SuggestBox(oracle);
> this.add(suggestBox);
>
> (put the SuggestOracleCallbackCustom where it needs to go, either 
> presenter or view, depends on what it does)
>  
>
>> Excuses-me but I am not familiar enough by making my own proxy / 
>> "delegating" etc. Can you give me some sample please ?
>>
>
> Something like:
> private SuggestOracle realOracle; // set by the presenter
> …
> SuggestBox suggestBox = new SuggestBox(new SuggestOracle() {
> @Override
> public boolean isDisplayStringHTML() {
> return realOracle.isDisplayStringHTML();
> }
> @Override
> public void requestDefaultSuggestions(SuggestOracle.Request 
> request, SuggestOracle.Callback callback) {
> realOracle.requestDefaultSuggestions(request, callback);
> }
> @Override
> public void requestSuggestions(SuggestOracle.Request req, 
> SuggestOracle.Callback callback) {
> realOracle.requestSuggestions(req, callback);
> }
> });
> this.add(suggestBox);
>
> That way, the realOracle can be replaced at any time, without the need to 
> re-build the SuggestBox.
> The anonymous SuggestOracle passed to the SuggestBox acts as a proxy 
> (façade) to the 'realOracle' (which is then the proxy's "delegate").
> If you need that pattern many times in your application, then create a 
> DelegatingSuggestOracle similar to the anonymous one but with the 
> realOracle as a field of the DelegatingSuggestOracle, with getter and 
> setter. Your view would then read:
>
> private final SuggestOracle oracle = new DelegatingSuggestOracle();
> …
> SuggestBox suggestBox = new SuggestBox(oracle);
> this.add(suggestBox);
> …
> public void setSuggestOracle(SuggestOracle oracle) { // called by the 
> presenter
>   this.oracle.setDelegate(oracle);
> }
>

-- 
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: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Colin Alworth]

Another issue at may warrant attention -
https://github.com/gwtproject/gwt/issues/9424. This was brought up some
time ago, but wasn't reduced to be reproducible until now (which is funny,
given how minimal the test case is).

On Fri, Sep 9, 2016 at 9:30 AM 'Daniel Kurka' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> +Goktug Gokdogan  +Roberto Lublinerman
>   Should we be holding RC3, I guess so right?
>
> On Fri, Sep 9, 2016 at 4:12 PM Jens  wrote:
>
>>
>> Can you file an issue and ping Daniel (by mail or hangout) to delay the
>>> RC3 a bit? (if not already too late, as it's 4pm cest)
>>>
>>
>> Done.
>>
>> --
>> 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/6386bb88-f488-4144-b830-99ddb387b677%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/CALLujirOwMPQTKzDuJtmtF0hF2bXVr%3Dij-V240vzP6Bh5SMRAA%40mail.gmail.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/CADcXZMz0S2wLjhN%2BKuTs4F84kUfnNHtqkDiKeJtjbqUf_piOhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 RC2 is here!

[Thomas Broyer]

On Friday, September 9, 2016 at 4:34:02 PM UTC+2, Василий Старцев wrote:
>
> Great! But there is a bug:
> *com.google.gwt.i18n.client.impl.cldr.DateTimeFormatInfoImpl_ru* still 
> have wrong weekdays order.
>
> @Override
> public String[] weekdaysFull() {
>   return new String[] {
>   "воскресенье",
>   "понедельник",
>   "вторник",
>   "среда",
>   "четверг",
>   "пятница",
>   "суббота"
>   };
> }
>
>
>
> should be 
>
>
>
> @Override
> public String[] weekdaysFull() {
>   return new String[] {
>   "понедельник",
>   "вторник",
>   "среда",
>   "четверг",
>   "пятница",
>   "суббота",
>
>   "воскресенье"
>   };
> }
>
>
>
> Please fix this.
>
>
weekdaysFull starts on 
Sunday: 
https://github.com/gwtproject/gwt/blob/caf2f6fa9a35a2602ea7b16426473dd9fcc92cea/user/src/com/google/gwt/i18n/shared/DefaultDateTimeFormatInfo.java#L333-L343
and Google Translate tells me воскресенье (which you switched from the 
first to the last position) is Sunday, and thus should be first here.
So I see no bug there.

BTW, you employed the word "still", but this had never been reported; and 
the proper way to report a bug is to file an issue on the issue tracker on 
GitHub: http://www.gwtproject.org/makinggwtbetter.html#issuetracking
 

-- 
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 2.8.0 RC2 is here!

[Василий Старцев]

Great! But there is a bug:
*com.google.gwt.i18n.client.impl.cldr.DateTimeFormatInfoImpl_ru* still have 
wrong weekdays order.

@Override
public String[] weekdaysFull() {
  return new String[] {
  "воскресенье",
  "понедельник",
  "вторник",
  "среда",
  "четверг",
  "пятница",
  "суббота"
  };
}



should be 



@Override
public String[] weekdaysFull() {
  return new String[] {
  "понедельник",
  "вторник",
  "среда",
  "четверг",
  "пятница",
  "суббота",

  "воскресенье"
  };
}



Please fix this.


-- 
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: ScriptInjector seems to be broken (2.8-SNAPSHOT)

['Daniel Kurka' via GWT Contributors]

+Goktug Gokdogan  +Roberto Lublinerman
  Should we be holding RC3, I guess so right?

On Fri, Sep 9, 2016 at 4:12 PM Jens  wrote:

>
> Can you file an issue and ping Daniel (by mail or hangout) to delay the
> RC3 a bit? (if not already too late, as it's 4pm cest)
>
>
> Done.
>
> --
> 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/6386bb88-f488-4144-b830-99ddb387b677%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/CALLujirOwMPQTKzDuJtmtF0hF2bXVr%3Dij-V240vzP6Bh5SMRAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Jens]

> Can you file an issue and ping Daniel (by mail or hangout) to delay the 
> RC3 a bit? (if not already too late, as it's 4pm cest)
>

Done.

-- 
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/6386bb88-f488-4144-b830-99ddb387b677%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Emulating CompletableFuture with Promise

[James Horsley]

This is brilliant. I would *love *to see this in GWT proper. Maybe even a
separate library temporarily since it won't make the 2.8.0 release train?

On Fri, Sep 9, 2016 at 2:41 PM Andrei Korzhevskii 
wrote:

> In this case I wanted 'new Promise', not 'Promise.resolve'. Thanks for
> spotting that out! I've updated my branch.
>
>
> On Tuesday, September 6, 2016 at 10:09:28 PM UTC+3, Ian Preston wrote:
>
>> For another hint, I think you don't want the "new" before
>> "Promise.resolve" on line 88 of impl/JsPromise :-)
>> What the best way for me to report bugs to you? A PR?
>>
> --
> 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: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Thomas Broyer]

Can you file an issue and ping Daniel (by mail or hangout) to delay the RC3 
a bit? (if not already too late, as it's 4pm cest)

On Friday, September 9, 2016 at 3:51:05 PM UTC+2, Jens wrote:
>
> Ok just tried it myself.
>
> Created a new, fresh project having world in my 
> host page using
>
> public void onModuleLoad() {
>   Global.window.alert("Element found: " + (Global.document.getElementById(
> "hello") != null));
> }
>
>
> GWT 2.8 RC2 returns true
>
> _.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
>   ($clinit_Global_0_g$() , $wnd.window.window).alert('Element found: ' + 
> jsNotEquals_0_g$(($clinit_Global_0_g$() , $wnd.window.document).
> getElementById('hello'), null));
> }
>
>
>
> GWT 2.8 SNAPSHOT (09.09.2016) returns false
>
> _.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
>   ($clinit_Global_0_g$() , window).alert('Element found: ' + 
> jsNotEquals_0_g$(($clinit_Global_0_g$() , document).getElementById('hello'
> ), null));
> }
>
>
>
> So I guess its a bug in GWT 2.8 SNAPSHOT as I think the JS output of GWT 
> 2.8 SNAPSHOT should be that way it is above if @JsType(isNative = true, 
> namespace = "window") is used. However elemental2 uses JsPackage.GLOBAL 
> as namespace.
>
>
> -- 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/48cd290e-c2c0-45a3-b555-29936103c8cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Jens]

Ok just tried it myself.

Created a new, fresh project having world in my host 
page using

public void onModuleLoad() {
  Global.window.alert("Element found: " + (Global.document.getElementById(
"hello") != null));
}


GWT 2.8 RC2 returns true

_.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
  ($clinit_Global_0_g$() , $wnd.window.window).alert('Element found: ' + 
jsNotEquals_0_g$(($clinit_Global_0_g$() , $wnd.window.document).
getElementById('hello'), null));
}



GWT 2.8 SNAPSHOT (09.09.2016) returns false

_.onModuleLoad_4_g$ = function onModuleLoad_3_g$(){
  ($clinit_Global_0_g$() , window).alert('Element found: ' + 
jsNotEquals_0_g$(($clinit_Global_0_g$() , document).getElementById('hello'), 
null));
}



So I guess its a bug in GWT 2.8 SNAPSHOT as I think the JS output of GWT 
2.8 SNAPSHOT should be that way it is above if @JsType(isNative = true, 
namespace = "window") is used. However elemental2 uses JsPackage.GLOBAL as 
namespace.


-- 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/25c12ba5-120c-47e0-b52a-c386691b9618%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is GWT is Dead?

[Pablo Nussembaum]

Google Inbox is 70% GWT code:

https://gmail.googleblog.com/2014/11/going-under-hood-of-inbox.html

https://news.ycombinator.com/item?id=8554339


On 06/09/16 17:06, Vassilis Virvilis wrote:
> ok then gmail being written in GWT is urban myth.
>
> However looks like google group is written in GWT 
> https://groups.google.com/forum/#!msg/google-web-toolkit/Mjjk5y9RQbw/hCWzIrZ1vzcJ
> 
>
> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi  > wrote:
>
> Gmail was created waaayyy before GWT was created.
>
> On 6 September 2016 at 21:31, Vassilis Virvilis  > wrote:
>
> About 1) Isn't gmail written in GWT? I think I have read it 
> somewhere...
>
> About 7) There is GWTcon2016 http://www.gwtcon.org/
>
> GWT doesn't look dead to me - but your questions have valid points.
>
>Vassilis
>
> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal  > wrote:
>
> Hi,
>
> I think GWT is not dead, but its development rate is decreased. I 
> think that last public product of Google which written in GWT was Inbox
> 
>  which 
> announced in late 2014. But AdWords
> 
>  
> (one of main GWT applications in Google) were re-written by Dart and 
> AngularJS (which announced in March 2016).
>
> There are some good points about GWT which mentioned in this post 
>  and some 
> pretty works about 2.8-RC2 release,
> JsInterop, GWTPolymer, GWTMaterial, Angular2Boot, ...
>
> But there are some vague points about GWT:
>
> 1. Which projects in Google written based on GWT in 2015-2016?
> 2. Were there any change in steering committee 
>  members (companies) in last two 
> years?
> 3. New GWT compiler (J2CL) when will be released? Is its 
> development started yet?
> 4. Why there is no official Java (GWT) version of Angular2 
>  (while there are JS, 
> TypeScript & Dart versions)?
> 5. How many people in Google work in GWT team (compared to Dart & 
> AngularJs teams)?
> 6. What is other companies roadmap about investment & development 
> based on GWT (like Vaadin, Sencha, ...)?
> 7. Is there any planned GWT Con or GWT Create conferences?
>
> I'm developing various applications with GWT for about 8 years 
> and I really enjoy it. It seems GWT development rate is not good enough 
> compared to other Google or Web tools and it makes
> me worried about its future.
>
> Is that correct?
>
> Regards.
>
>
> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres 
> > wrote:
>
> Just curious, what and why are you waiting GWT 3? GWT is 
> pretty awesome right now…
>
> On Tue, Sep 6, 2016 at 8:39 AM Ahamed  > wrote:
>
> Team,
>   My Apologies for asking this question again.
>
> Is GWT is Dead or Alive ? From past 2 years i am waiting 
> for GWT 3.0 but still is not released? Can any one from Steering committee 
> explain whats going on or Any progress on GWT
> 3.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 .
>
> -- 
> 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 

Re: Emulating CompletableFuture with Promise

[Andrei Korzhevskii]

In this case I wanted 'new Promise', not 'Promise.resolve'. Thanks for 
spotting that out! I've updated my branch.

On Tuesday, September 6, 2016 at 10:09:28 PM UTC+3, Ian Preston wrote:
>
> For another hint, I think you don't want the "new" before 
> "Promise.resolve" on line 88 of impl/JsPromise :-)
> What the best way for me to report bugs to you? A PR?
>

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

[Arnaud TOURNIER]

I have one problem which is recurring, related to JsInterop.

Sometimes the JsInterop JS stub is not generated because of (seemingly) an 
internal error in SuperDevMode (and GWTC it seems), but nothing is logged, 
so it's difficult to diagnose.

For example, in an application (which does not inherits the User module), 
when i write a class like this, the JS stub is generated correctly :

@JsInterop
public class Toto
{
public void doSomething()
{
// really nothing here...
}
}

But if i change it to :

@JsInterop
public class Toto
{
public void doSomething()
{
Window.alert( "yeah" );
}
}

Then the JS stub is not generated (i mean the Toto constructor function is 
not made available to JS scope).

I understand that Window.alert(...) is implemented in the User module and 
since i don't inherit from it, the thing cannot be generated. But no 
message is generated (neither by SDM nor by the GWTC if i remember well), 
which is then difficult to diagnose...

Note : i should be able to produce a minimal repro case for this thing.


Then sometimes, a @JsInterop class would not be exported to JS, but if i 
change its name then it's generated, which is... weird.

For this one i am not sure i can give a minimal repro case because it 
happens on quite large projects (angular2 with gwt 2.8)...


I saw another error:

It was in a @JsInterop class, which called a template method (i mean with 
 in the signature of the method). I had to specify the  type to call 
it to have the SDM generating the class. If i didn't, the javac would infer 
correctly the  type (so no error appears in the IDE, which is Eclipse in 
my case), but it seemed that SDM did not manage to infer the type correctly 
because then the class would not be accessible from javascript... I can 
give you a sample file if you need.


A last one : i tried migrating a big app from 2.7 to 2.8-rc2 (same problem 
with previous sub versions of the 2.8). The compiler goes on compiling then 
does the linking, but it suddenly crashes without saying anything (i tried 
TRACE and DEBUG log levels with no more useful information) and results in 
a maven build failure. The build is happening in maven. Since the app is 
quite big, i guess the problem comes from a dependency i use which is not 
2.8 friendly (did not have enough time to investigate that deeply). But 
again, the problem is not that the compile does not work, but that no 
useful message is generated to understand the error.

For this one, i can give you the code, but privately since it is a business 
app that is not open source...

Thanks !

Arnaud Tournier
LTE Consulting


Le jeudi 8 septembre 2016 16:27:36 UTC+2, Daniel Kurka a écrit :
>
> Hi all,
>
> I will be cutting rc3 tomorrow 1pm CEST, please respond to this email with 
> any outstanding reviews that you want to see included.
>
> -Daniel
>

-- 
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/5e5b6585-aba1-48ce-a5d6-6f9a702e801b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[David]

I'm sure my stuff was working fine with JsInterop 1.0 but with JsInterop
2.0 the only solution seems to be to use Global.top.window.document
As far as I remember I had it working somewhere half of July - but I might
be wrong. Can I force in maven to take a very specific snapshot version of
GWT 2.8.0, then I could double check ?

>From what you explain it seems like Global.window should have worked. But I
have this in my html:

I'm here!

Then when I try these:
Global.document.getElementById("test") -> null
Global.window.document.getElementById("test") -> null
Global.top.document.getElementById("test") -> [object HtmlDivElement]

Is this really how it should be ? I cannot use top since my app could be
embedded in an IFrame. I would have expected Global.document.getElementId
to have worked but it does not.

Anyway, maybe its because there is not enough docs available yet that I am
confused. Maybe it was accidentally working before and all this is just how
it is supposed to be ?


On Fri, Sep 9, 2016 at 12:13 PM Jens  wrote:

>
> This scoping is all very confusing :-).
>>
>> Anyway, this is what I am seeing with Elemental2:
>> - I have an application that generates HTML using a custom templating
>> system.
>> - I then put the HTML string in an Element with setInnerSafeHtml.
>> - After this I use Element2 to bind to the generated html. For that I was
>> using Global.document.getElementById(...).
>>
>> This used to work, but since a few weeks this stopped working.
>>
>> I now have to use Global.window.top.document.getElementById(...) to get
>> access to the ui dom nodes that I generated.
>>
>> Is this how it is supposed to be ? I was probably making the wrong
>> assumptions before ?
>>
>
> No. Elemental2's Global class uses @JsType(isNative = true, name =
> "window", namespace = JsPackage.GLOBAL) which translates to $wnd.window
> because JsInterop qualifies everything with $wnd (unless
> namespace="window" has been set as of the commit you have referenced
> before), JsPackage.GLOBAL is an empty namespace and window is the name.
>
> Are you sure nothing has changed in your app ?! I don't think something
> has changed in GWT as such (breaking) changes would normally cause more
> posts on gwt-contrib / gwt-user.
>
> -- 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/9b7a6321-c9ca-44a8-bd8d-01e6dc113f13%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/CABrJHW2JDzPyAHXD6MVgazyPGb_5t8tugTJqKrR4vbzVN5XCOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: chrome 53 styleSheet insertRule not working

[fenyoapa]

it is just one example


2016. szeptember 9., péntek 11:55:34 UTC+2 időpontban Thomas Broyer a 
következőt írta:
>
> Works for me (from the devtools console, but still).
> 53.0.2785.101 (64-bit) on Ubuntu 16.04.
>
> On Friday, September 9, 2016 at 11:41:12 AM UTC+2, fenyoapa wrote:
>>
>> hi,
>> it is maybe not a gwt issue, but it is in a gwt app.
>> This code snippet worked for years:
>>
>>
>> *$doc.styleSheets[0].insertRule('.aclassname { color:red;}', 0);*
>> but now in chrome 53.0.2785.101 m (64-bit) not work (css rules not 
>> applied)
>> It is working in FF/IE too, and worked in chrome 52.
>>
>

-- 
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: chrome 53 styleSheet insertRule not working

[fenyoapa]

2016. szeptember 9., péntek 11:41:12 UTC+2 időpontban fenyoapa a következőt 
írta:
>
> hi,
> it is maybe not a gwt issue, but it is in a gwt app.
> This code snippet worked for years:
>
>
> *$doc.styleSheets[0].insertRule('.aclassname { color:red;}', 0);*
> but now in chrome 53.0.2785.101 m (64-bit) not work (css rules not applied)
> It is working in FF/IE too, and worked in chrome 52.
>

-- 
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: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[Jens]

> This scoping is all very confusing :-).
>
> Anyway, this is what I am seeing with Elemental2:
> - I have an application that generates HTML using a custom templating 
> system.
> - I then put the HTML string in an Element with setInnerSafeHtml.
> - After this I use Element2 to bind to the generated html. For that I was 
> using Global.document.getElementById(...).
>
> This used to work, but since a few weeks this stopped working.
>
> I now have to use Global.window.top.document.getElementById(...) to get 
> access to the ui dom nodes that I generated.
>
> Is this how it is supposed to be ? I was probably making the wrong 
> assumptions before ?
>

No. Elemental2's Global class uses @JsType(isNative = true, name = 
"window", namespace = JsPackage.GLOBAL) which translates to $wnd.window 
because JsInterop qualifies everything with $wnd (unless namespace="window" 
has been set as of the commit you have referenced before), JsPackage.GLOBAL 
is an empty namespace and window is the name.

Are you sure nothing has changed in your app ?! I don't think something has 
changed in GWT as such (breaking) changes would normally cause more posts 
on gwt-contrib / gwt-user.

-- 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/9b7a6321-c9ca-44a8-bd8d-01e6dc113f13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is GWT is Dead?

[Gourab Panda]

Back 2010-2011(approx.) when I was using GWT, there were these discussion(*in
My Team*) on why GMAIL is reverting back it implementation from GWT to its
original implementation. Not sure about the authenticity of those news.

Found a link where there is similar discussion about this topic:
https://www.quora.com/Is-Gmail-built-on-Google-Web-Toolkit

On Fri, Sep 9, 2016 at 3:38 PM, Gourab Panda  wrote:

> Back 2010-2011(approx.) when I was using GWT, there were these
> discussion(in May) on why GMAIL is reverting back it implementation from
> GWT to its original implementation. Not sure about the authenticity of
> those news.
>
> Found a link where there is similar discussion about this topic:
> https://www.quora.com/Is-Gmail-built-on-Google-Web-Toolkit
>
> On Thu, Sep 8, 2016 at 3:03 AM, Paul Stockley 
> wrote:
>
>> I think you are getting confused with Goggle Wave.
>>
>> On Wednesday, September 7, 2016 at 5:07:41 AM UTC+1, Gourab wrote:
>>>
>>> >> ok then gmail being written in GWT is urban myth.
>>>
>>> It was rewritten in GWT and later reverted back to it's original
>>> implementation.
>>>
>>> On Wed, Sep 7, 2016 at 1:36 AM, Vassilis Virvilis 
>>> wrote:
>>>
 ok then gmail being written in GWT is urban myth.

 However looks like google group is written in GWT
 https://groups.google.com/forum/#!msg/google-web-toolkit/Mjj
 k5y9RQbw/hCWzIrZ1vzcJ

 On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi 
 wrote:

> Gmail was created waaayyy before GWT was created.
>
> On 6 September 2016 at 21:31, Vassilis Virvilis 
> wrote:
>
>> About 1) Isn't gmail written in GWT? I think I have read it
>> somewhere...
>>
>> About 7) There is GWTcon2016 http://www.gwtcon.org/
>>
>> GWT doesn't look dead to me - but your questions have valid points.
>>
>>Vassilis
>>
>> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal  wrote:
>>
>>> Hi,
>>>
>>> I think GWT is not dead, but its development rate is decreased. I
>>> think that last public product of Google which written in GWT was
>>> Inbox
>>> 
>>> which announced in late 2014. But AdWords
>>> 
>>> (one of main GWT applications in Google) were re-written by Dart and
>>> AngularJS (which announced in March 2016).
>>>
>>> There are some good points about GWT which mentioned in this post
>>> 
>>> and some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
>>> GWTMaterial, Angular2Boot, ...
>>>
>>> But there are some vague points about GWT:
>>>
>>> 1. Which projects in Google written based on GWT in 2015-2016?
>>> 2. Were there any change in steering committee
>>>  members (companies) in
>>> last two years?
>>> 3. New GWT compiler (J2CL) when will be released? Is its development
>>> started yet?
>>> 4. Why there is no official Java (GWT) version of Angular2
>>>  (while there
>>> are JS, TypeScript & Dart versions)?
>>> 5. How many people in Google work in GWT team (compared to Dart &
>>> AngularJs teams)?
>>> 6. What is other companies roadmap about investment & development
>>> based on GWT (like Vaadin, Sencha, ...)?
>>> 7. Is there any planned GWT Con or GWT Create conferences?
>>>
>>> I'm developing various applications with GWT for about 8 years and I
>>> really enjoy it. It seems GWT development rate is not good enough 
>>> compared
>>> to other Google or Web tools and it makes me worried about its future.
>>>
>>> Is that correct?
>>>
>>> Regards.
>>>
>>>
>>> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
>>> ign...@bacamt.com> wrote:
>>>
 Just curious, what and why are you waiting GWT 3? GWT is pretty
 awesome right now…

 On Tue, Sep 6, 2016 at 8:39 AM Ahamed  wrote:

> Team,
>   My Apologies for asking this question again.
>
> Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT
> 3.0 but still is not released? Can any one from Steering committee 
> explain
> whats going on or Any progress on GWT 3.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 

Re: Is GWT is Dead?

[Gourab Panda]

Back 2010-2011(approx.) when I was using GWT, there were these
discussion(in May) on why GMAIL is reverting back it implementation from
GWT to its original implementation. Not sure about the authenticity of
those news.

Found a link where there is similar discussion about this topic:
https://www.quora.com/Is-Gmail-built-on-Google-Web-Toolkit

On Thu, Sep 8, 2016 at 3:03 AM, Paul Stockley  wrote:

> I think you are getting confused with Goggle Wave.
>
> On Wednesday, September 7, 2016 at 5:07:41 AM UTC+1, Gourab wrote:
>>
>> >> ok then gmail being written in GWT is urban myth.
>>
>> It was rewritten in GWT and later reverted back to it's original
>> implementation.
>>
>> On Wed, Sep 7, 2016 at 1:36 AM, Vassilis Virvilis 
>> wrote:
>>
>>> ok then gmail being written in GWT is urban myth.
>>>
>>> However looks like google group is written in GWT
>>> https://groups.google.com/forum/#!msg/google-web-toolkit/
>>> Mjjk5y9RQbw/hCWzIrZ1vzcJ
>>>
>>> On Tue, Sep 6, 2016 at 10:38 PM, Alain Ekambi 
>>> wrote:
>>>
 Gmail was created waaayyy before GWT was created.

 On 6 September 2016 at 21:31, Vassilis Virvilis 
 wrote:

> About 1) Isn't gmail written in GWT? I think I have read it
> somewhere...
>
> About 7) There is GWTcon2016 http://www.gwtcon.org/
>
> GWT doesn't look dead to me - but your questions have valid points.
>
>Vassilis
>
> On Tue, Sep 6, 2016 at 2:38 PM, Ali Jalal  wrote:
>
>> Hi,
>>
>> I think GWT is not dead, but its development rate is decreased. I
>> think that last public product of Google which written in GWT was
>> Inbox
>> 
>> which announced in late 2014. But AdWords
>> 
>> (one of main GWT applications in Google) were re-written by Dart and
>> AngularJS (which announced in March 2016).
>>
>> There are some good points about GWT which mentioned in this post
>> 
>> and some pretty works about 2.8-RC2 release, JsInterop, GWTPolymer,
>> GWTMaterial, Angular2Boot, ...
>>
>> But there are some vague points about GWT:
>>
>> 1. Which projects in Google written based on GWT in 2015-2016?
>> 2. Were there any change in steering committee
>>  members (companies) in
>> last two years?
>> 3. New GWT compiler (J2CL) when will be released? Is its development
>> started yet?
>> 4. Why there is no official Java (GWT) version of Angular2
>>  (while there are
>> JS, TypeScript & Dart versions)?
>> 5. How many people in Google work in GWT team (compared to Dart &
>> AngularJs teams)?
>> 6. What is other companies roadmap about investment & development
>> based on GWT (like Vaadin, Sencha, ...)?
>> 7. Is there any planned GWT Con or GWT Create conferences?
>>
>> I'm developing various applications with GWT for about 8 years and I
>> really enjoy it. It seems GWT development rate is not good enough 
>> compared
>> to other Google or Web tools and it makes me worried about its future.
>>
>> Is that correct?
>>
>> Regards.
>>
>>
>> On Tue, Sep 6, 2016 at 10:26 AM, Ignacio Baca Moreno-Torres <
>> ign...@bacamt.com> wrote:
>>
>>> Just curious, what and why are you waiting GWT 3? GWT is pretty
>>> awesome right now…
>>>
>>> On Tue, Sep 6, 2016 at 8:39 AM Ahamed  wrote:
>>>
 Team,
   My Apologies for asking this question again.

 Is GWT is Dead or Alive ? From past 2 years i am waiting for GWT
 3.0 but still is not released? Can any one from Steering committee 
 explain
 whats going on or Any progress on GWT 3.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-we...@googlegroups.com.
 Visit this group at https://groups.google.com/grou
 p/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-we...@googlegroups.com.
>>> Visit 

Re: chrome 53 styleSheet insertRule not working

[Thomas Broyer]

Works for me (from the devtools console, but still).
53.0.2785.101 (64-bit) on Ubuntu 16.04.

On Friday, September 9, 2016 at 11:41:12 AM UTC+2, fenyoapa wrote:
>
> hi,
> it is maybe not a gwt issue, but it is in a gwt app.
> This code snippet worked for years:
>
>
> *$doc.styleSheets[0].insertRule('.aclassname { color:red;}', 0);*
> but now in chrome 53.0.2785.101 m (64-bit) not work (css rules not applied)
> It is working in FF/IE too, and worked in chrome 52.
>

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

chrome 53 styleSheet insertRule not working

[fenyoapa]

hi,
it is maybe not a gwt issue, but it is in a gwt app.
This code snippet worked for years:


*$doc.styleSheets[0].insertRule('.aclassname { color:red;}', 0);*
but now in chrome 53.0.2785.101 m (64-bit) not work (css rules not applied)
It is working in FF/IE too, and worked in chrome 52.

-- 
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: Working polymer example?

[zakaria amine]

Hi, 

you can try gwt-polymer-starter-kit: 
https://github.com/gwidgets/gwt-polymer-starter-kit

it's also available as a maven archetype: 
https://github.com/gwidgets/gwt-ui-archetypes

Le vendredi 9 septembre 2016 04:00:56 UTC+2, Transplant a écrit :
>
>
> I've left this alone in the hopes that it would mature with the 2.8 
> release, but I still cannot get a sample to run using the tutorial on the 
> gwtproject site. I have followed the instructions neurotically a couple of 
> times, but the only improvement from when I tried it in January is that now 
> a  element appears in the host page, but it has no styling 
> and does nothing.
>
> the webcomponents.js does load into the page but it throws these errors 
> into the browser console:
>
>
> 
>
>
> I am using maven 3.3.3 with GWT 2.8.0-rc2, polymer 
> with vaadin-gwt-polymer-elements 1.2.3.0.
>
> It seems clear that many people are working with it, but I cannot find the 
> proper incantation to get the sample project off the ground.
>
>
> I noticed that the gwt 2.8 webappcreator generates a pom using a different 
> GWT plugin than it used to. Could that be a factor?
> Any other ideas?
>
>
>
> On Wednesday, January 6, 2016 at 11:06:43 PM UTC-8, Transplant wrote:
>>
>>
>> Can anyone point me to a working example of Polymer and GWT? The tutorial 
>> on gwtproject.org does not compile with 2.7, and when you try it 
>> with 2.8 snapshot it gives you a page with an empty iframe in it. 
>>
>> Is anyone using it in a production application?
>>
>> 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: Autocompletion with RPC under the MVP model : how to instanciate Suggestbox(suggestOracle) without refering any service into the view ?

[Thomas Broyer]

On Friday, September 9, 2016 at 9:31:27 AM UTC+2, Eddy wrote:
>
> Thank you for your first help Thomas !
>
> What I had tried is to write a get method from the view/display interface, 
> which return the suggestBox object and which I had called from the 
> presenter on the onBind or revealDisplay :
> => I could redefine as the same the requestSuggestions() into the 
> presenter but then I didn't know how to transmit it to the view / how to 
> instanciate the visible SuggestBox object for showing it into the view 
> (regarding the new SuggestBox(oracle) line).
>

Something like:
in the presenter:
public void getSuggestions(SuggestOracle.Request req, 
SuggestOracle.Callback callback) {
  service.getSuggestions(req, callback);
}

in the view:
SuggestOracleCustom oracle = new SuggestOracleCustom() { 
@Override
public void requestSuggestions(SuggestOracle.Request req, 
SuggestOracle.Callback callback) {
presenter.getSuggestions(req, new 
SuggestOracleCallbackCustom(req, callback));
}
};
SuggestBox suggestBox = new SuggestBox(oracle);
this.add(suggestBox);

(put the SuggestOracleCallbackCustom where it needs to go, either presenter 
or view, depends on what it does)
 

> Excuses-me but I am not familiar enough by making my own proxy / 
> "delegating" etc. Can you give me some sample please ?
>

Something like:
private SuggestOracle realOracle; // set by the presenter
…
SuggestBox suggestBox = new SuggestBox(new SuggestOracle() {
@Override
public boolean isDisplayStringHTML() {
return realOracle.isDisplayStringHTML();
}
@Override
public void requestDefaultSuggestions(SuggestOracle.Request 
request, SuggestOracle.Callback callback) {
realOracle.requestDefaultSuggestions(request, callback);
}
@Override
public void requestSuggestions(SuggestOracle.Request req, 
SuggestOracle.Callback callback) {
realOracle.requestSuggestions(req, callback);
}
});
this.add(suggestBox);

That way, the realOracle can be replaced at any time, without the need to 
re-build the SuggestBox.
The anonymous SuggestOracle passed to the SuggestBox acts as a proxy 
(façade) to the 'realOracle' (which is then the proxy's "delegate").
If you need that pattern many times in your application, then create a 
DelegatingSuggestOracle similar to the anonymous one but with the 
realOracle as a field of the DelegatingSuggestOracle, with getter and 
setter. Your view would then read:

private final SuggestOracle oracle = new DelegatingSuggestOracle();
…
SuggestBox suggestBox = new SuggestBox(oracle);
this.add(suggestBox);
…
public void setSuggestOracle(SuggestOracle oracle) { // called by the 
presenter
  this.oracle.setDelegate(oracle);
}

-- 
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: ScriptInjector seems to be broken (2.8-SNAPSHOT)

[David]

This scoping is all very confusing :-).

Anyway, this is what I am seeing with Elemental2:
- I have an application that generates HTML using a custom templating
system.
- I then put the HTML string in an Element with setInnerSafeHtml.
- After this I use Element2 to bind to the generated html. For that I was
using Global.document.getElementById(...).

This used to work, but since a few weeks this stopped working.

I now have to use Global.window.top.document.getElementById(...) to get
access to the ui dom nodes that I generated.

Is this how it is supposed to be ? I was probably making the wrong
assumptions before ?



On Thu, Sep 8, 2016 at 11:17 PM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Global object is not scoped to window unless you explicitly say "window";
> so it should be $wnd by default.
>
> On Wed, Sep 7, 2016 at 2:50 AM, David  wrote:
>
>> I was depending on JsInterop Global.document to get access to UI
>> components generated by my template engine.
>> The Global object is now scoped window, so I guess it is accessing the
>> wrong document as well ?
>>
>>
>> On Wed, 7 Sep 2016 at 11:40, David  wrote:
>>
>>> I'm sure that it worked before. I'm also seeing some other issues where
>>> I am using JsInterop to interact with some generated HTML - but I am still
>>> investigating if that is due to changes in GWT or in our codebase.
>>>
>>> I did not work on this project for about 8 weeks, so I have quite a
>>> backlog to go through.
>>>
>>> On Tue, 6 Sep 2016 at 19:28, 'Goktug Gokdogan' via GWT Contributors <
>>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>>
 It is surprising as Jens pointed out, we always qualified references
 with $wnd until https://gwt-review.googlesource.com/#/c/15520/
 (submitted 5 weeks ago). So it shouldn't have worked earlier if you were
 not injecting it to TOP_WINDOW.
 If it worked earlier, then we unintentionally fixed a bug. Could you
 double check if this was working before so we can see if there are some
 other unintended behavior change introduced somewhere else?

 On Tue, Sep 6, 2016 at 2:43 AM, stuckagain 
 wrote:

> It was working fine before.
>
> Since it looks like JsInterop has changed recently (and it is still in
> beta) I will just update my code to either inject in the TOP_WINDOW or I
> try it with using window as namespace.
>
>
> On Monday, September 5, 2016 at 6:29:48 PM UTC+2, Jens wrote:
>>
>> Hm wondering how it ever worked for you as JsInterop usually
>> qualifies JS code with $wnd but your D3.js has been injected into the GWT
>> iframe. So AFAICT with JsInterop you would had to use TOP_WINDOW anyways.
>> You can make it work within the GWT iframe but then you can't use
>> JsPackage.GLOBAL but use a namespace that points to the iframe content
>> window.
>>
>> Also see:
>> https://groups.google.com/d/msg/google-web-toolkit/GcsWUuzexvE/ApUg3sLZCQAJ
>>
>> So it looks like this behavior has changed? But yes you would need to
>> use "window" now to references the iframe's content window if you inject
>> the code into the iframe.
>>
>> -- 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/7862784c-854a-4bb1-85c0-2b7734a984d3%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/CAN%3DyUA0RioQk7GatwdbkvwZKT6gKDEmB0daytVoKa9a%3DnGUd3A%40mail.gmail.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 

Re: Autocompletion with RPC under the MVP model : how to instanciate Suggestbox(suggestOracle) without refering any service into the view ?

[Eddy]

Thank you for your first help Thomas !

What I had tried is to write a get method from the view/display interface, 
which return the suggestBox object and which I had called from the 
presenter on the onBind or revealDisplay :
=> I could redefine as the same the requestSuggestions() into the presenter 
but then I didn't know how to transmit it to the view / how to instanciate 
the visible SuggestBox object for showing it into the view (regarding the 
new SuggestBox(oracle) line).

Excuses-me but I am not familiar enough by making my own proxy / 
"delegating" etc. Can you give me some sample please ?

Thanks in advance for the feedback,

Eddy

https://plus.google.com/u/0/112225624236959783711 is my google+ profil if 
you could write in french too (could provide my email too), I am happy to 
know french guys which use GWT and hope we will be able to exchange our 
works / tips in the future :-)

Le jeudi 8 septembre 2016 09:18:09 UTC+2, Thomas Broyer a écrit :
>
> You could route the requestSuggestions to your presenter instead if 
> directly to your service (the presenter simply behaving as a proxy/façade 
> to the service). 
>
> Or you could use a "proxy" Oracle where you can later set the "delegate" 
> (coming from the presenter)

-- 
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-contrib] Re: CodeServer with Bookmarklets not working in GWT 2.7 (2nd request)

[Thomas Broyer]

Doesn't CodeServer accept -setProperty? You could use that to pinpoint the 
property values so you only have one permutation when only user.agent is given.

-- 
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/fe7f6b31-c172-4043-a56e-0b43d716c4a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT 2.8.0 RC2 is here!

[Thomas Broyer]

First, you don't *have* to split your project, you have to *run* them 
separately (but then you'll probably have to tweak the classpath of each a bit).

Then, GWT RPC isn't a blocker for splitting your project (see my modular-webapp 
archetype at https://github.com/tbroyer/gwt-maven-archetypes)

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