Re: GWT 2.7.0 Compile Errors

[Majdi ABDELMOULA]

Hello Thomas ,

I use gxt 2.3.1a , that you send me, to develop an application , but i have 
this problem : SimpleComboBox do not show the vertical scroll bar when i 
have many data !! i have the same problem for the compoment "TimeField" , i 
do not see the scroll vertical bar !! 
I see that the problem come from the file  gxt-all.css !! How can i resolve 
this problem ???

the code CSS that describe " SimpleCombobox " is : 

.x-combo-list {
border:1px solid;
zoom:1;
overflow:hidden;

}
.x-combo-list-inner {
overflow:auto;
  
position:relative;  
zoom:1;
overflow-x:hidden;
}
.x-combo-list-hd {
border-bottom:1px solid;
padding:3px;
   
}

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

gxt combobox not scroll vertical

[Majdi ABDELMOULA]

I use gxt 2.3.1a to develop an application , but i have this problem : 
SimpleComboBox do not show the vertical scroll bar when i have many data !! 
i have the same problem for the compoment "TimeField" , i do not see the 
scroll vertical bar !! 
I see that the problem come from the file  gxt-all.css !! How can i resolve 
this problem ???

the code CSS that describe " SimpleCombobox " is : 

.x-combo-list {
border:1px solid;
zoom:1;
overflow:hidden;

}
.x-combo-list-inner {
overflow:auto;
  
position:relative;  
zoom:1;
overflow-x:hidden;
}
.x-combo-list-hd {
border-bottom:1px solid;
padding:3px;
   
}

-- 
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: Need some help with debugging an issue in GWT SDM compiler

[Kirill Prazdnikov]

the bug here has been for long time already, 
sometimes SDM woks, sometimes not and yo have to rebuild with temp-clean
this is not C++ compiler

суббота, 17 декабря 2016 г., 4:24:31 UTC+3 пользователь Nándor Előd Fekete 
написал:
>
> Well, yes, of course, I can always start from scratch, but that's around 
> 3+ minutes (it's a bigger project), which is worse than what I currently 
> do, "touching" the Java source file that the compiler is having problem 
> generating correct code for. The biggest problem is that it's breaking my 
> workflow, and I'd rather spend some time finding a probable bug in the 
> compiler itself and give back to the community by fixing it than constantly 
> working around the issue.
>
> On Saturday, December 17, 2016 at 2:11:09 AM UTC+1, Kirill Prazdnikov 
> wrote:
>>
>> mvn clean and clean temp folder before compile will help
>>
>>
>>  суббота, 17 декабря 2016 г., 0:49:30 UTC+3 пользователь Nándor Előd 
>> Fekete написал:
>>>
>>> Hi!
>>>
>>> I have this strange problem in SDM, where a method in the generated 
>>> output JS gets defined under a name, but gets referenced under another name.
>>>
>>> I'll try to show it through actual compiled JS code vs original code.
>>>
>>> function *getBoundingClientRect_3_g$*(this$static_0_g$, 
>>> withinOffsetParent_0_g$){
>>>   $clinit_ElementOverlayMixin_0_g$();
>>>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>>>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>>>   if (is_4_g$(offsetParent_0_g$)) {
>>> parentBCR_0_g$ = 
>>> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
>>> true);
>>> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
>>> parentBCR_0_g$.getTop_15_g$();
>>> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
>>> parentBCR_0_g$.getLeft_16_g$();
>>>   }
>>>else {
>>> deltaY_0_g$ = getScrollTop_4_g$();
>>> deltaX_0_g$ = getScrollLeft_6_g$();
>>>   }
>>>   return 
>>> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>>>  
>>> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
>>> }
>>> getBoundingClientRect_3_g$.displayName = 
>>> 'ElementOverlayMixin.$getBoundingClientRect';
>>>
>>>
>>> This is the original Java source of the method:
>>>
>>> public final ClientRect *getBoundingClientRect*(boolean 
>>> withinOffsetParent) {
>>> float deltaY;
>>> float deltaX;
>>> Element offsetParent = getOffsetParent();
>>> if (Element.is(offsetParent)) {
>>> ClientRect parentBCR = ElementOverlayMixin.as(offsetParent).
>>> *getBoundingClientRect*(true);
>>> deltaY = offsetParent.getScrollTop() - parentBCR.getTop();
>>> deltaX = offsetParent.getScrollLeft() - parentBCR.getLeft();
>>> } else {
>>> deltaY = Window.getScrollTop();
>>> deltaX = Window.getScrollLeft();
>>> }
>>> return withinOffsetParent ? getBoundingClientRect().translated(deltaX, 
>>> deltaY) : getBoundingClientRect();
>>> }
>>>
>>> I've highlighted the important parts with bold+red/green. Note that it's 
>>> a recursive method invoking itself on another object. In the generated 
>>> output, the name of the function in the function declaration and the name 
>>> used while referring to the same function is different.
>>>
>>> After a "touch" on the source code file, the compiler now generates the 
>>> correct JS output:
>>>
>>> function *$getBoundingClientRect_2_g$*(this$static_0_g$, 
>>> withinOffsetParent_0_g$){
>>>   $clinit_ElementOverlayMixin_0_g$();
>>>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>>>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>>>   if (is_4_g$(offsetParent_0_g$)) {
>>> parentBCR_0_g$ = 
>>> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
>>> true);
>>> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
>>> parentBCR_0_g$.getTop_15_g$();
>>> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
>>> parentBCR_0_g$.getLeft_16_g$();
>>>   }
>>>else {
>>> deltaY_0_g$ = getScrollTop_4_g$();
>>> deltaX_0_g$ = getScrollLeft_6_g$();
>>>   }
>>>   return 
>>> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>>>  
>>> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
>>> }
>>>
>>> $getBoundingClientRect_2_g$.displayName = 
>>> 'ElementOverlayMixin.$getBoundingClientRect';
>>>
>>> I'm using incremental mode, but I think it happened on the first 
>>> compilation too with all previous compilation caches cleared.
>>>
>>> Do you guys have any tips on where to look in the compiler code where 
>>> the method name handling / mangling happens?
>>>
>>> Many thanks!
>>>
>>> Nandi.
>>>
>>>

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

Re: Need some help with debugging an issue in GWT SDM compiler

[Nándor Előd Fekete]

Well, yes, of course, I can always start from scratch, but that's around 3+ 
minutes (it's a bigger project), which is worse than what I currently do, 
"touching" the Java source file that the compiler is having problem 
generating correct code for. The biggest problem is that it's breaking my 
workflow, and I'd rather spend some time finding a probable bug in the 
compiler itself and give back to the community by fixing it than constantly 
working around the issue.

On Saturday, December 17, 2016 at 2:11:09 AM UTC+1, Kirill Prazdnikov wrote:
>
> mvn clean and clean temp folder before compile will help
>
>
>  суббота, 17 декабря 2016 г., 0:49:30 UTC+3 пользователь Nándor Előd 
> Fekete написал:
>>
>> Hi!
>>
>> I have this strange problem in SDM, where a method in the generated 
>> output JS gets defined under a name, but gets referenced under another name.
>>
>> I'll try to show it through actual compiled JS code vs original code.
>>
>> function *getBoundingClientRect_3_g$*(this$static_0_g$, 
>> withinOffsetParent_0_g$){
>>   $clinit_ElementOverlayMixin_0_g$();
>>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>>   if (is_4_g$(offsetParent_0_g$)) {
>> parentBCR_0_g$ = 
>> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
>> true);
>> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getTop_15_g$();
>> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getLeft_16_g$();
>>   }
>>else {
>> deltaY_0_g$ = getScrollTop_4_g$();
>> deltaX_0_g$ = getScrollLeft_6_g$();
>>   }
>>   return 
>> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>>  
>> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
>> }
>> getBoundingClientRect_3_g$.displayName = 
>> 'ElementOverlayMixin.$getBoundingClientRect';
>>
>>
>> This is the original Java source of the method:
>>
>> public final ClientRect *getBoundingClientRect*(boolean 
>> withinOffsetParent) {
>> float deltaY;
>> float deltaX;
>> Element offsetParent = getOffsetParent();
>> if (Element.is(offsetParent)) {
>> ClientRect parentBCR = ElementOverlayMixin.as(offsetParent).
>> *getBoundingClientRect*(true);
>> deltaY = offsetParent.getScrollTop() - parentBCR.getTop();
>> deltaX = offsetParent.getScrollLeft() - parentBCR.getLeft();
>> } else {
>> deltaY = Window.getScrollTop();
>> deltaX = Window.getScrollLeft();
>> }
>> return withinOffsetParent ? getBoundingClientRect().translated(deltaX, 
>> deltaY) : getBoundingClientRect();
>> }
>>
>> I've highlighted the important parts with bold+red/green. Note that it's 
>> a recursive method invoking itself on another object. In the generated 
>> output, the name of the function in the function declaration and the name 
>> used while referring to the same function is different.
>>
>> After a "touch" on the source code file, the compiler now generates the 
>> correct JS output:
>>
>> function *$getBoundingClientRect_2_g$*(this$static_0_g$, 
>> withinOffsetParent_0_g$){
>>   $clinit_ElementOverlayMixin_0_g$();
>>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>>   if (is_4_g$(offsetParent_0_g$)) {
>> parentBCR_0_g$ = 
>> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
>> true);
>> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getTop_15_g$();
>> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
>> parentBCR_0_g$.getLeft_16_g$();
>>   }
>>else {
>> deltaY_0_g$ = getScrollTop_4_g$();
>> deltaX_0_g$ = getScrollLeft_6_g$();
>>   }
>>   return 
>> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>>  
>> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
>> }
>>
>> $getBoundingClientRect_2_g$.displayName = 
>> 'ElementOverlayMixin.$getBoundingClientRect';
>>
>> I'm using incremental mode, but I think it happened on the first 
>> compilation too with all previous compilation caches cleared.
>>
>> Do you guys have any tips on where to look in the compiler code where the 
>> method name handling / mangling happens?
>>
>> Many thanks!
>>
>> Nandi.
>>
>>

-- 
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: Need some help with debugging an issue in GWT SDM compiler

[Kirill Prazdnikov]

mvn clean and clean temp folder before compile will help


 суббота, 17 декабря 2016 г., 0:49:30 UTC+3 пользователь Nándor Előd Fekete 
написал:
>
> Hi!
>
> I have this strange problem in SDM, where a method in the generated output 
> JS gets defined under a name, but gets referenced under another name.
>
> I'll try to show it through actual compiled JS code vs original code.
>
> function *getBoundingClientRect_3_g$*(this$static_0_g$, 
> withinOffsetParent_0_g$){
>   $clinit_ElementOverlayMixin_0_g$();
>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>   if (is_4_g$(offsetParent_0_g$)) {
> parentBCR_0_g$ = 
> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
> true);
> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
> parentBCR_0_g$.getTop_15_g$();
> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
> parentBCR_0_g$.getLeft_16_g$();
>   }
>else {
> deltaY_0_g$ = getScrollTop_4_g$();
> deltaX_0_g$ = getScrollLeft_6_g$();
>   }
>   return 
> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>  
> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
> }
> getBoundingClientRect_3_g$.displayName = 
> 'ElementOverlayMixin.$getBoundingClientRect';
>
>
> This is the original Java source of the method:
>
> public final ClientRect *getBoundingClientRect*(boolean 
> withinOffsetParent) {
> float deltaY;
> float deltaX;
> Element offsetParent = getOffsetParent();
> if (Element.is(offsetParent)) {
> ClientRect parentBCR = ElementOverlayMixin.as(offsetParent).
> *getBoundingClientRect*(true);
> deltaY = offsetParent.getScrollTop() - parentBCR.getTop();
> deltaX = offsetParent.getScrollLeft() - parentBCR.getLeft();
> } else {
> deltaY = Window.getScrollTop();
> deltaX = Window.getScrollLeft();
> }
> return withinOffsetParent ? getBoundingClientRect().translated(deltaX, 
> deltaY) : getBoundingClientRect();
> }
>
> I've highlighted the important parts with bold+red/green. Note that it's a 
> recursive method invoking itself on another object. In the generated 
> output, the name of the function in the function declaration and the name 
> used while referring to the same function is different.
>
> After a "touch" on the source code file, the compiler now generates the 
> correct JS output:
>
> function *$getBoundingClientRect_2_g$*(this$static_0_g$, 
> withinOffsetParent_0_g$){
>   $clinit_ElementOverlayMixin_0_g$();
>   var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
>   offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
>   if (is_4_g$(offsetParent_0_g$)) {
> parentBCR_0_g$ = 
> *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
> true);
> deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
> parentBCR_0_g$.getTop_15_g$();
> deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
> parentBCR_0_g$.getLeft_16_g$();
>   }
>else {
> deltaY_0_g$ = getScrollTop_4_g$();
> deltaX_0_g$ = getScrollLeft_6_g$();
>   }
>   return 
> withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
>  
> deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
> }
>
> $getBoundingClientRect_2_g$.displayName = 
> 'ElementOverlayMixin.$getBoundingClientRect';
>
> I'm using incremental mode, but I think it happened on the first 
> compilation too with all previous compilation caches cleared.
>
> Do you guys have any tips on where to look in the compiler code where the 
> method name handling / mangling happens?
>
> Many thanks!
>
> Nandi.
>
>

-- 
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: Is there a possiblity to display a message on the page you are redirected to?

[Olar Andrei]

Hello,

Thanks, I've done this using the cookie suggestion.

On Sat, Dec 17, 2016 at 12:27 AM, Vassilis Virvilis 
wrote:

> You can pass a url fragment argument like
> Window.Location.replace(GWT.getHostPageBaseURL() + "#error=Something bad
> happened");
> and then in your login page you have to check for url fragments (after #).
>
> Similarly if you don't want to pollute your urls you can
>
>- set a cookie
>- use sessionStorage
>- use localStorage
>
> to communicate the error state to the new page.
>
> Hope that helps
>
> Vassilis
>
>
>
>
>
> On Sat, Dec 17, 2016 at 12:22 AM, Olar Andrei 
> wrote:
>
>> Hello,
>>
>> I have this small example. I am on the user page. In the constructor the
>> UserInfo object is set. If something happens I want to redirect back to the
>> login page, which I do like in the example below. Is there a possibility to
>> display a message back on the login page like "An error eccurred bla bla
>> bla. Please log in again." ?
>>
>> Thanks in advance.
>>
>> public UserPanel() {
>> setUserInfo();
>>
>> if (userInfo == null) {
>> Window.Location.replace(GWT.getHostPageBaseURL());
>> }
>>
>> container = new MaterialContainer();
>> container.setFontSize("1em");
>>
>> Widget mainMenu = createMenu();
>> initWidget(mainMenu);
>> }
>>
>>
>> --
>> 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.
>>
>
>
>
> --
> Vassilis Virvilis
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/google-web-toolkit/3Bdp0kiOi1s/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: IDEs, Dagger2 and annotationProcessorPaths

[Raphael André Bauer]

Thanks for all the hints. maven-processor-plugin seems to work with
the IDEs, but I will have to do some more testing. A bit unfortunate
that tooling for Dagger2 does not work out of the box...

Cheers,

Raphael

On Thu, Dec 15, 2016 at 8:37 PM, Lars  wrote:
> Thanks for the answer! I tried to put it to the Dagger Discuss group, but 
> without luck/access to post. But may could give stackoverflow a try...
>
> --
> 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: Is there a possiblity to display a message on the page you are redirected to?

[Vassilis Virvilis]

You can pass a url fragment argument like
Window.Location.replace(GWT.getHostPageBaseURL() + "#error=Something bad
happened");
and then in your login page you have to check for url fragments (after #).

Similarly if you don't want to pollute your urls you can

   - set a cookie
   - use sessionStorage
   - use localStorage

to communicate the error state to the new page.

Hope that helps

Vassilis





On Sat, Dec 17, 2016 at 12:22 AM, Olar Andrei  wrote:

> Hello,
>
> I have this small example. I am on the user page. In the constructor the
> UserInfo object is set. If something happens I want to redirect back to the
> login page, which I do like in the example below. Is there a possibility to
> display a message back on the login page like "An error eccurred bla bla
> bla. Please log in again." ?
>
> Thanks in advance.
>
> public UserPanel() {
> setUserInfo();
>
> if (userInfo == null) {
> Window.Location.replace(GWT.getHostPageBaseURL());
> }
>
> container = new MaterialContainer();
> container.setFontSize("1em");
>
> Widget mainMenu = createMenu();
> initWidget(mainMenu);
> }
>
>
> --
> 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.
>



-- 
Vassilis Virvilis

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

Is there a possiblity to display a message on the page you are redirected to?

[Olar Andrei]

Hello,

I have this small example. I am on the user page. In the constructor the 
UserInfo object is set. If something happens I want to redirect back to the 
login page, which I do like in the example below. Is there a possibility to 
display a message back on the login page like "An error eccurred bla bla 
bla. Please log in again." ?

Thanks in advance.

public UserPanel() {
setUserInfo();

if (userInfo == null) {
Window.Location.replace(GWT.getHostPageBaseURL());
}

container = new MaterialContainer();
container.setFontSize("1em");

Widget mainMenu = createMenu();
initWidget(mainMenu);
}


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

Need some help with debugging an issue in GWT SDM compiler

[Nándor Előd Fekete]

Hi!

I have this strange problem in SDM, where a method in the generated output 
JS gets defined under a name, but gets referenced under another name.

I'll try to show it through actual compiled JS code vs original code.

function *getBoundingClientRect_3_g$*(this$static_0_g$, 
withinOffsetParent_0_g$){
  $clinit_ElementOverlayMixin_0_g$();
  var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
  offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
  if (is_4_g$(offsetParent_0_g$)) {
parentBCR_0_g$ = *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
true);
deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getTop_15_g$();
deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getLeft_16_g$();
  }
   else {
deltaY_0_g$ = getScrollTop_4_g$();
deltaX_0_g$ = getScrollLeft_6_g$();
  }
  return 
withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
 
deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
}
getBoundingClientRect_3_g$.displayName = 
'ElementOverlayMixin.$getBoundingClientRect';


This is the original Java source of the method:

public final ClientRect *getBoundingClientRect*(boolean withinOffsetParent) 
{
float deltaY;
float deltaX;
Element offsetParent = getOffsetParent();
if (Element.is(offsetParent)) {
ClientRect parentBCR = ElementOverlayMixin.as(offsetParent).
*getBoundingClientRect*(true);
deltaY = offsetParent.getScrollTop() - parentBCR.getTop();
deltaX = offsetParent.getScrollLeft() - parentBCR.getLeft();
} else {
deltaY = Window.getScrollTop();
deltaX = Window.getScrollLeft();
}
return withinOffsetParent ? getBoundingClientRect().translated(deltaX, 
deltaY) : getBoundingClientRect();
}

I've highlighted the important parts with bold+red/green. Note that it's a 
recursive method invoking itself on another object. In the generated 
output, the name of the function in the function declaration and the name 
used while referring to the same function is different.

After a "touch" on the source code file, the compiler now generates the 
correct JS output:

function *$getBoundingClientRect_2_g$*(this$static_0_g$, 
withinOffsetParent_0_g$){
  $clinit_ElementOverlayMixin_0_g$();
  var deltaX_0_g$, deltaY_0_g$, offsetParent_0_g$, parentBCR_0_g$;
  offsetParent_0_g$ = $getOffsetParent_0_g$(this$static_0_g$);
  if (is_4_g$(offsetParent_0_g$)) {
parentBCR_0_g$ = *$getBoundingClientRect_2_g$*(as_58_g$(offsetParent_0_g$), 
true);
deltaY_0_g$ = $getScrollTop_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getTop_15_g$();
deltaX_0_g$ = $getScrollLeft_0_g$(offsetParent_0_g$) - 
parentBCR_0_g$.getLeft_16_g$();
  }
   else {
deltaY_0_g$ = getScrollTop_4_g$();
deltaX_0_g$ = getScrollLeft_6_g$();
  }
  return 
withinOffsetParent_0_g$?$getBoundingClientRect_1_g$(this$static_0_g$).translated_1_g$(deltaX_0_g$,
 
deltaY_0_g$):$getBoundingClientRect_1_g$(this$static_0_g$);
}

$getBoundingClientRect_2_g$.displayName = 
'ElementOverlayMixin.$getBoundingClientRect';

I'm using incremental mode, but I think it happened on the first 
compilation too with all previous compilation caches cleared.

Do you guys have any tips on where to look in the compiler code where the 
method name handling / mangling happens?

Many thanks!

Nandi.

-- 
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: Experimental release of Elemental2

[Hua Zhang]

*A new experimental version of Elemental2 using the new JsInterop 
specification has been pushed on Sonatype today.*

I just tested websocket functionality of Elemental2, it works very fine for 
me.

I am curious if there is any functionality difference between Elemental1 
and 2?

When can I expect a stable release of Elemental2?

-- 
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/0c55d84a-dad5-46a0-bf6c-07ae295f104f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GWT and Bazel

[Thomas Broyer]

On Thursday, December 15, 2016 at 9:36:22 PM UTC+1, Konstantin Solomatov 
wrote:
>
> Does anybody use rules for bazel from here: 
> https://github.com/bazelbuild/rules_gwt? It seems that these rules are 
> quite immature. Does anybody try to use it? Are there any alternatives to 
> this?
>

At least Erik Kuefler (the author) uses them with his team at Xperiel.
 

> It has dev mode, but it works only with the source folders from the module 
> where you declare gwt_application. Are there any ways to workaround this 
> implementation.
>

>From the documentation there's a java_roots attribute to gwt_application 
(but generally with Bazel you'd put everything into a single source root, 
contrary to many other build tools like Maven or Gradle)

-- 
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: Editors : n relations with same editor

[129pierre]

Sorry for the noise. Editors works fine.

It was just a problem with RadioButton that have the same name. I have to 
make them distinct 



Le jeudi 15 décembre 2016 19:16:36 UTC+1, 129pierre a écrit :
>
> Hi,
>
> Let's say I have a Person with 2 Address
> In my main editor PersonEditor, I have defined 2 sub editors 
>  
>
> @UiField(provided=true)   AddressEditor address = new AddressEditor();
> @UiField(provided=true)  AddressEditor address2= new AddressEditor();
>
> They are  both visible but only the last one has its data binded correctly.
>
> Did I miss something ? It 'is possible to use a generic editor many times ?
>
> Thanks in advance for any help
>
> Pierre
>

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