how to insert javascript source...
Sorry I can;t wirte English. *1. my java script source.* html body script type=text/javascript src=http://checkout.naver.com/customer/js/checkoutButton.js; charset=UTF-8/script table width=100% border=0 cellspacing=0 cellpadding=0 style=margin-top:3px; tr td width=80nbsp;/td td script type=text/javascript //![CDATA[ nhn.CheckoutButton.apply({ BUTTON_KEY: , TYPE: B, COLOR: 1, COUNT: 2, ENABLE: Y, :}); //]] /script /td td /td /tr /table /body /html 2. My Source VerticalPanel mainPanel = new VerticalPanel(); mainPanel.add( new imagePananel ()) mainPanel.add( new makeJavaScriptPanel()); private String makeJavaScriptPanel(){ StringBuilder sb = new StringBuilder(); sb.append(html); sb.append(body); sb.append(script type=\text/javascript\ src=\http://checkout.naver.com/customer/js/checkoutButton.js\; charset=\UTF-8\/script); sb.append(table width=\100%\ border=\0\ cellspacing=\0\ cellpadding=\0\ style=\margin-top:3px;\); sb.append(tr); sb.append(td width=\80\nbsp;/td); sb.append(td); sb.append(script type=\text/javascript\ ); sb.append(//![CDATA[); sb.append(nhn.CheckoutButton.apply({); sb.append(BUTTON_KEY: \F5AD74D3-DAAD-4ED8-B3C7-614240931115\, ); sb.append(TYPE: \B\, ); sb.append(COLOR: 1,); sb.append(COUNT: 2,); sb.append(ENABLE: \Y\,); sb.append(\\:\\); sb.append(});); sb.append(//]]); sb.append(/script); sb.append(/td); sb.append(td); sb.append(/td); sb.append(/tr); sb.append(/table); sb.append(/body); sb.append(/html); return new HTMLPanel(sb.toString) } https://lh6.googleusercontent.com/-dztc6ltirng/VHWMcs0uisI/AxA/nAsuxaT5hAA/s1600/complete.PNG watch attached image. javascript show this image... I want show... but script code not working.. I don't know how to this problem -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.5-rc1 feature uirender is not working as expected.
Hi all. I'm see this old topic but I stuck with this problem. I tried to remove the type tag but I'm getting an error anyway in compile time. @UiFactory either not working. Any clue? четверг, 26 июля 2012 г., 15:26:22 UTC+3 пользователь Vasu написал: Woow.. really quick thanks Rodrigo. Also would like to thanks Thomas for giving right direction. On Thursday, 26 July 2012 02:41:03 UTC+5:30, Rodrigo Chandia wrote: I think this patch (under review) fixes this issue: http://gwt-code-reviews.appspot.com/1794803 On Tuesday, July 24, 2012 3:27:29 PM UTC-4, Rodrigo Chandia wrote: Hmm, this seems like a bug to me. Hopefully I'll have a fix ready for rc2. On Mon, Jul 23, 2012 at 11:11 PM, Vasu wrote: Yea you are absolutely right. It worked when I removed type attribute from ui:with tag. I was wondering it has to identify type to call respective methods on the same and I realized that it tries to match the variable name with that of name of the parameter to render method (which I marked in blue color in below code). -- interface MyUiRenderer extends UiRenderer { void render(SafeHtmlBuilder sb, *Person person*); } -- So Finally working code looks like this. PersonCell.java -- public class PearsonCell extends AbstractCellPerson { interface MyUiRenderer extends UiRenderer { void render(SafeHtmlBuilder sb, Person person); } private static MyUiRendererrenderer= GWT.create(MyUiRenderer.class); @Override public void render(com.google.gwt.cell.client.Cell.Context context, Person value, SafeHtmlBuilder sb) { renderer.render(sb, value); } } -- PersonCell.ui.xml -- ui:UiBinder xmlns:ui='urn:ui:com.google.gwt.uibinder' ui:with field='person' / div First Name : span ui:text from='{person.getFname}' / /span p Last Name : span ui:text from='{person.getLname}' / /span /p p Email : span ui:text from='{person.getEmailid}' / /span /p /div /ui:UiBinder -- Thanks Thomas for your valuable inputs. Without that it would have been painful to identify the issue. Thanks, -Pandurang. On Thursday, 19 July 2012 13:34:11 UTC+5:30, Thomas Broyer wrote: On Thursday, July 19, 2012 5:36:13 AM UTC+2, Vasu wrote: Yes you were right, it is instantiating new Person object. But if I try to set Type to empty string validation fails and I cannot run the application. I didn't mean to set it to the empty string, but to not use the attribute: ui:with field=person / -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
GWT and JAXB Basics Runtime
I am using CXF JAXB generated classes in a GWT application. I would like equals() and hashCode() to be added to the generated classes. I have successfully used the JAXB2 Basics Plugins (http://confluence.highsource.org/display/J2B/JAXB2+Basics+Plugins) and the JAXB2 Basics Runtime with CXF in the Maven POM to generate them. However, the generated classes are now incompatible with GWT. The classes have dependencies which are not emulated by GWT, e.g., java.util.ResourceBundle, java.net.URL. I am considering using a CustomEqualsStrategy but that will still leave the org.jvnet.jaxb2_commons.locator.ObjectLocator class. Has anyone got this to work? (I also posted this on StackOverflow.) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: AST manipulation
Thanks for the answer. I'm going to experiment with it a little bit and make a fork on github. Maybe it will help in future. вторник, 25 ноября 2014 г., 22:04:31 UTC+2 пользователь Jens написал: If I remember correctly there was some talk about compiler plugins/hooks quite some time ago but no work has been done yet. So I would say: the idea exists but nothing has been planed so far. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Debugging workers
No idea ? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.7 and GSS
Ok you try to access the value of the constant via a method of your cssResource interface. Yes unfortunately there is bug there and the generator escape the content of the constant. Please open an issue ( https://code.google.com/p/google-web-toolkit/issues/entry) for that and I will fix it. Otherwise, if you use the constant in your css, it works as expected: @def CONTENT_HEADER literal(\27A1); .header:before { content: CONTENT_HEADER; } On Tue Nov 25 2014 at 11:56:49 PM Slava Pankov pank...@gmail.com wrote: :-) That's exactly what I did, but it's not working. In Java code I'm getting it exactly as String with value \27a1 (length == 5). On Tuesday, November 25, 2014 1:07:56 PM UTC-8, Julien Dramaix wrote: A space is missing in my previous post: @def CONTENT_HEADER \27A1; On Tue Nov 25 2014 at 10:07:49 PM Julien Dramaix julien@gmail.com wrote: literal method is not needed anymore (and is not supported by GSS). Just try: @def CONTENT_HEADER\27A1; And yes for syntax highlighting, you need to add .gss as extension of css file. On Tue Nov 25 2014 at 10:03:35 PM Slava Pankov pan...@gmail.com wrote: OK, one of my issues is resolved, so answering to myself :-) For *.gss highlighting in Eclipse see attached screenshot. But still no luck with unicode symbol in @def. On Monday, November 24, 2014 8:50:10 PM UTC-8, Slava Pankov wrote: Another problem: @def CONTENT_HEADER literal(\27A1); It was unicode character constant before gss, now I'm getting string literal(\27A1) instead of unicode symbol. On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote: What about syntax highlighting for *.gss files in Eclipse? *.css where supported by GPE CSS Resource Editor, but it does NOT support *.gss -- You received this message because you are subscribed to a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/to pic/google-web-toolkit/hpb1sz9CPsM/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-we...@googlegroups.com. Visit this group at http://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 a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/google-web-toolkit/hpb1sz9CPsM/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 http://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 Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: SuperDevMode not so super
I just got started with SDM but it seems like one cannot inspect variables in the java source maps, maybe I missunderstood the whole thing. It's nice that you can see the java source and step debug, but I really need to be able to inspect variables. For instance I somewhere read that you're supposed to be able to inspect overlay types, which I don't seem to be able to. Have I got something wrong, or did I hope for too much ? /Adrian -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Types not resolved when upgrading to GWT 2.7.0 ?
I am trying to upgrade to GWT 2.7.0 (from 2.6.1), and keeping getting these strange errors, below are a few of them. I compile with java 8, but did put the target and source on java 1.7. I tried several thinks, but can't get it resolved Any idea what this could be ? [INFO] [ERROR] Errors in 'jar:file:/1.2-SNAPSHOT/ited-gwt-client-1.2-SNAPSHOT-sources.jar!/com/EffectActionInsertOrAdd.java' [INFO] [ERROR] com.EffectAction cannot be resolved to a type [INFO] [ERROR] Errors in 'jar:file:/Maven/repository/com/google/gwt/gwt-user/2.7.0/gwt-user-2.7.0.jar!/com/google/gwt/emul/java/lang/Long.java' [INFO] [ERROR] Line 181: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 184: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 191: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 188: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) [INFO] [ERROR] Line 228: The method forDigit(int, int) in the type Character is not applicable for the arguments (int) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: SuperDevMode not so super
I just got started with SDM but it seems like one cannot inspect variables in the java source maps, maybe I missunderstood the whole thing. It's nice that you can see the java source and step debug, but I really need to be able to inspect variables. For instance I somewhere read that you're supposed to be able to inspect overlay types, which I don't seem to be able to. Have I got something wrong, or did I hope for too much ? Always keep in mind that source maps just overlays javascript to make it look familiar to you. You do not deal with java at all, it is still all javascript. In Chrome dev tools you can see the Scope Variables section on the right which shows you all variable values of the current scope. These are JavaScript variable names but should be easy to identify. When using Source Maps the code viewer in Chrome is more or less read only, so you can not hover anything to get more information about a variable. You also can't navigate your code inside Chrome dev tools by ctrl + click on a java class name of something like that. If you want that then use the experimental Eclipse plugin SDBG or use IntelliJ which both are able to connect to Chrome and show you debugging informations of Chrome inside your IDE. That way you get code navigation back and you can set breakpoints in your IDE instead of Chrome dev tools. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
Hmm sounds like a bug or you have two different gwt-user.jar on class path (2.6 and 2.7). Check mvn dependency:tree. Character.forDigit(int) does only exist in the super sourced version of Character and is used by super sourced versions of Character and Long. This change has been introduced by commit https://gwt.googlesource.com/gwt/+/84545ae6961e3b20891f917c0f58015f3f78c1b1 Looks like the compiler does see Character.forDigit(int) in the super sourced version of Character while analyzing the super sourced version of Long provided by GWT 2.7. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Problem with maven-gwt-plugin and GWT 2.1
Hi, Can you please explain what is removing the dependency to gwt-math mean. How to do it? On Monday, November 8, 2010 1:36:44 PM UTC+5:30, fclaeys wrote: Problem solved after removing the dependency to gwt-math. On 6 nov, 23:46, Jeff Larsen larse...@gmail.com wrote: Try upgrading to the new maven plugin 2.1 http://mojo.codehaus.org/gwt-maven-plugin/ On Nov 6, 1:55 pm, fclaeys claeys.fabr...@gmail.com wrote: Hi. I currently have the same problem. Have you found a solution for this problem ? On 4 nov, 14:32, Deyan Atanasov root2...@gmail.com wrote: Hi. I'm getting the following exception when compiling my project with GWT 2.1. and maven-gwt-plugin 1.3-SNAPSHOT fromhttp:// nexus.codehaus.org/snapshots repository. Validating newly compiled units [ERROR] Errors in 'jar:file:/C:/Users/Dido/.m2/repository/com/ google/gwt/gwt-user/2.1.0/gwt-user-2.1.0.jar!/com/google/gwt/emul/java/ lang/Enum.java' [ERROR] Line 31: enumType.enumValueOfFunc cannot be resolved or is not a field [ERROR] Errors in 'jar:file:/C:/Users/Dido/.m2/repository/com/ google/gwt/gwt-user/2.1.0/gwt-user-2.1.0.jar!/com/google/gwt/emul/java/ math/BitLevel.java' [ERROR] Line 55: val.sign cannot be resolved or is not a field [ERROR] Line 59: The method getFirstNonzeroDigit() is undefined for the type BigInteger [ERROR] Line 60: val.sign cannot be resolved or is not a field [ERROR] Line 61: val.numberLength cannot be resolved or is not a field [ERROR] Line 62: val.digits cannot be resolved or is not a field [ERROR] Line 67: val.digits cannot be resolved or is not a field [ERROR] Line 68: val.numberLength cannot be resolved or is not a field [ERROR] Line 69: val.digits cannot be resolved or is not a field [ERROR] Line 72: val.numberLength cannot be resolved or is not a field [ERROR] Line 83: val.sign cannot be resolved or is not a field [ERROR] Line 86: val.numberLength cannot be resolved or is not a field [ERROR] Line 87: val.digits cannot be resolved or is not a field [ERROR] Line 87: val.numberLength cannot be resolved or is not a field [ERROR] Line 89: val.sign cannot be resolved or is not a field [ERROR] Line 90: The method getFirstNonzeroDigit() is undefined for the type BigInteger [ERROR] Line 92: val.numberLength cannot be resolved or is not a field Any ideas ? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Widget package alternative in 2.7.0
No, they've just been, well, removed. I believe you can just use CellWidget with the appropriate Cell as an alternative. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.7 and GSS
Thanks, issue is opened: https://code.google.com/p/google-web-toolkit/issues/detail?id=9022 On Wednesday, November 26, 2014 4:37:54 AM UTC-8, Julien Dramaix wrote: Ok you try to access the value of the constant via a method of your cssResource interface. Yes unfortunately there is bug there and the generator escape the content of the constant. Please open an issue ( https://code.google.com/p/google-web-toolkit/issues/entry) for that and I will fix it. Otherwise, if you use the constant in your css, it works as expected: @def CONTENT_HEADER literal(\27A1); .header:before { content: CONTENT_HEADER; } On Tue Nov 25 2014 at 11:56:49 PM Slava Pankov pan...@gmail.com javascript: wrote: :-) That's exactly what I did, but it's not working. In Java code I'm getting it exactly as String with value \27a1 (length == 5). On Tuesday, November 25, 2014 1:07:56 PM UTC-8, Julien Dramaix wrote: A space is missing in my previous post: @def CONTENT_HEADER \27A1; On Tue Nov 25 2014 at 10:07:49 PM Julien Dramaix julien@gmail.com wrote: literal method is not needed anymore (and is not supported by GSS). Just try: @def CONTENT_HEADER\27A1; And yes for syntax highlighting, you need to add .gss as extension of css file. On Tue Nov 25 2014 at 10:03:35 PM Slava Pankov pan...@gmail.com wrote: OK, one of my issues is resolved, so answering to myself :-) For *.gss highlighting in Eclipse see attached screenshot. But still no luck with unicode symbol in @def. On Monday, November 24, 2014 8:50:10 PM UTC-8, Slava Pankov wrote: Another problem: @def CONTENT_HEADER literal(\27A1); It was unicode character constant before gss, now I'm getting string literal(\27A1) instead of unicode symbol. On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote: What about syntax highlighting for *.gss files in Eclipse? *.css where supported by GPE CSS Resource Editor, but it does NOT support *.gss -- You received this message because you are subscribed to a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/to pic/google-web-toolkit/hpb1sz9CPsM/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-we...@googlegroups.com. Visit this group at http://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 a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/google-web-toolkit/hpb1sz9CPsM/unsubscribe. To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscr...@googlegroups.com javascript:. To post to this group, send email to google-we...@googlegroups.com javascript:. Visit this group at http://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 Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.7 and GSS
Also I've added comment about unicode symbols higher than U+ to issue#9022 On Wednesday, November 26, 2014 11:54:20 AM UTC-8, Slava Pankov wrote: Thanks, issue is opened: https://code.google.com/p/google-web-toolkit/issues/detail?id=9022 On Wednesday, November 26, 2014 4:37:54 AM UTC-8, Julien Dramaix wrote: Ok you try to access the value of the constant via a method of your cssResource interface. Yes unfortunately there is bug there and the generator escape the content of the constant. Please open an issue ( https://code.google.com/p/google-web-toolkit/issues/entry) for that and I will fix it. Otherwise, if you use the constant in your css, it works as expected: @def CONTENT_HEADER literal(\27A1); .header:before { content: CONTENT_HEADER; } On Tue Nov 25 2014 at 11:56:49 PM Slava Pankov pan...@gmail.com wrote: :-) That's exactly what I did, but it's not working. In Java code I'm getting it exactly as String with value \27a1 (length == 5). On Tuesday, November 25, 2014 1:07:56 PM UTC-8, Julien Dramaix wrote: A space is missing in my previous post: @def CONTENT_HEADER \27A1; On Tue Nov 25 2014 at 10:07:49 PM Julien Dramaix julien@gmail.com wrote: literal method is not needed anymore (and is not supported by GSS). Just try: @def CONTENT_HEADER\27A1; And yes for syntax highlighting, you need to add .gss as extension of css file. On Tue Nov 25 2014 at 10:03:35 PM Slava Pankov pan...@gmail.com wrote: OK, one of my issues is resolved, so answering to myself :-) For *.gss highlighting in Eclipse see attached screenshot. But still no luck with unicode symbol in @def. On Monday, November 24, 2014 8:50:10 PM UTC-8, Slava Pankov wrote: Another problem: @def CONTENT_HEADER literal(\27A1); It was unicode character constant before gss, now I'm getting string literal(\27A1) instead of unicode symbol. On Monday, November 24, 2014 7:26:20 PM UTC-8, Slava Pankov wrote: What about syntax highlighting for *.gss files in Eclipse? *.css where supported by GPE CSS Resource Editor, but it does NOT support *.gss -- You received this message because you are subscribed to a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/to pic/google-web-toolkit/hpb1sz9CPsM/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-we...@googlegroups.com. Visit this group at http://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 a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/google-web-toolkit/hpb1sz9CPsM/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-we...@googlegroups.com. Visit this group at http://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 Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
@Jens: thanks for the input. No, I only have a 2.7 version, also in the dependency maven tree. But I think my own Character super version and that off GWT don't like each other. I notice that if I remove my version, I do get some other errors, but not the ones in my first post. Mine contains some methods like isSpace(char). Should they be merged? or does one overwrites the other completely? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Types not resolved when upgrading to GWT 2.7.0 ?
Oh you have your own Character emulation based on the one of GWT 2.6. Well of course you must merge them since you probably don't have your own version of Long and thus the GWT 2.7 version of Long expects that Character has the method forDigit(int,int). But your version currently does not have that method since it is based on GWT 2.6 code that you have copied back in the days. Things would be easier if you would checkout GWT, make a branch with your changes and then rebase that branch on top of master / 2.7 tag / 2.8 tag (in the future). That way the rebasing process would have merged things together (or end up in a conflict state that you must solve). We do that at work as well for a couple of custom patches and it works well. You never really get into an inconsistent state that way. -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: add mobile version to existing GWT app?
Hi, I have looked to both of them, and I found that they focus on the client side GUI. But the GUI is something I would like to do with the native Android SDK. What I would like to do is access the data on my tomcat server, just as I do it with GWT client applications. Assume a GWT chess app with a RPC service like this: boolean requestMove (int game,Field src,Field dst); Also assume that the client/server application is running fine and you simply want to add a mobile version to it. My approach would be to develop the GUI using the Android SDK. But this client also needs access to the RPC service mentioned above. The goal is to leave as much of the application logic at one place, the server in this case, while simply adding another presentation instance, the mobile phone in this case. How would you do this? Thanks Magnus -- You received this message because you are subscribed to the Google Groups Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: GWT 2.5-rc1 feature uirender is not working as expected.
you need to provide your code snippets which will enable us to help you. [image: Pandurang Patil on about.me] Pandurang Patil about.me/pandurangpatil http://about.me/pandurangpatil website: http://www.agnie.net twitter: @agniesoftware Cell : +91-9823241535 On Wed, Nov 26, 2014 at 12:15 AM, Aleksey Popryadukhin lynx...@gmail.com wrote: Hi all. I'm see this old topic but I stuck with this problem. I tried to remove the type tag but I'm getting an error anyway in compile time. @UiFactory either not working. Any clue? четверг, 26 июля 2012 г., 15:26:22 UTC+3 пользователь Vasu написал: Woow.. really quick thanks Rodrigo. Also would like to thanks Thomas for giving right direction. On Thursday, 26 July 2012 02:41:03 UTC+5:30, Rodrigo Chandia wrote: I think this patch (under review) fixes this issue: http://gwt-code-reviews.appspot.com/1794803 On Tuesday, July 24, 2012 3:27:29 PM UTC-4, Rodrigo Chandia wrote: Hmm, this seems like a bug to me. Hopefully I'll have a fix ready for rc2. On Mon, Jul 23, 2012 at 11:11 PM, Vasu wrote: Yea you are absolutely right. It worked when I removed type attribute from ui:with tag. I was wondering it has to identify type to call respective methods on the same and I realized that it tries to match the variable name with that of name of the parameter to render method (which I marked in blue color in below code). -- interface MyUiRenderer extends UiRenderer { void render(SafeHtmlBuilder sb, *Person person*); } -- So Finally working code looks like this. PersonCell.java -- public class PearsonCell extends AbstractCellPerson { interface MyUiRenderer extends UiRenderer { void render(SafeHtmlBuilder sb, Person person); } private static MyUiRendererrenderer= GWT.create(MyUiRenderer.class); @Override public void render(com.google.gwt.cell.client.Cell.Context context, Person value, SafeHtmlBuilder sb) { renderer.render(sb, value); } } -- PersonCell.ui.xml -- ui:UiBinder xmlns:ui='urn:ui:com.google.gwt.uibinder' ui:with field='person' / div First Name : span ui:text from='{person.getFname}' / /span p Last Name : span ui:text from='{person.getLname}' / /span /p p Email : span ui:text from='{person.getEmailid}' / /span /p /div /ui:UiBinder -- Thanks Thomas for your valuable inputs. Without that it would have been painful to identify the issue. Thanks, -Pandurang. On Thursday, 19 July 2012 13:34:11 UTC+5:30, Thomas Broyer wrote: On Thursday, July 19, 2012 5:36:13 AM UTC+2, Vasu wrote: Yes you were right, it is instantiating new Person object. But if I try to set Type to empty string validation fails and I cannot run the application. I didn't mean to set it to the empty string, but to not use the attribute: ui:with field=person / -- You received this message because you are subscribed to a topic in the Google Groups Google Web Toolkit group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/TWYcWRfICXk/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 http://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 Google Web Toolkit 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: SDM + gin + generated GinModule not working well together
Thanks for the patch, it works on the hello world project I made. However, it is still not enough for the bigger project I'm working on. I'll try to investigate and determine what's going on or reproduce it via a more complex example. Le vendredi 21 novembre 2014 00:04:03 UTC+1, John Stalcup a écrit : Though we do not make a promise to process GWT.create() of entry point types before any other GWT.create() calls, it was easy to restore this behavior in incremental, so I went ahead and did it ( https://gwt-review.googlesource.com/#/c/10410/). You should probably find a way not to depend on this in the future, as it is not promised and may change again. On Mon Nov 17 2014 at 2:07:02 PM Christopher Viel viel.chr...@gmail.com javascript: wrote: Hi, I'm gonna add some more background here. The generator generates a bunch of file and binds the interfaces using GIN. I would't say this is strictly necessary, but it brings the advantages of DI to the generated code. So we have an Entry Point that is an interface and a rebind rule. UserAgentAsserter uses a similar technique. What we also do is generate a Ginjector interface and put a *GWT.create(GeneratedGinjector.class)* call inside the generated entry point. That way GIN's generator is called after and everything should be resolvable. The generated ginjector is setup to look at a specific property to load additional gin modules. Here it happens that one of them is also generated. So all of that actually work with 2.7. What no longer works is if the entry point and the ginjector are no longer generated. If there is a GWT.create() call that resolves to a Ginjector from an explicit entry point, it fails. I'm not sure I'm being very clear here so here's an example: *MyModule.gwt.xml:* module entry-point class=com.project.EntryPointToGenerate/ entry-point class=com.project.ExplicitEntryPoint/ extend-configuration-property name=gin.ginjector.modules value=com.project.GeneratedGinModule/ generate-with class=com.project.EntryPointGenerator when-type-is class=com.project.EntryPointToGenerate/ /generate-with /module *EntryPointToGenerate:* public interface EntryPointToGenerate extends EntryPoint {} *EntryPointGenerator*: Generates *com.project.GeneratedGinModule* and an implementation of *EntryPointToGenerate* *ExplicitEntryPoint*: public class ExplicitEntryPoint implements EntryPoint { private static final ExplicitGinjector GINJECTOR = GWT.create( ExplicitGinjector.class); @Override public void onModuleLoad() {} } *ExplicitGinjector:* @GinModules( value = ExplicitGinModule.class, properties = gin.ginjector.modules ) public interface ExplicitGinjector extends Ginjector { /* snip */ } With this code in a regular compilation, EntryPointToGenerate is generated before ExplicitEntryPoint is traversed. With incremental compilation, ExplicitEntryPoint is traversed (and incidentally GINs generator is called) before EntryPointGenerator is called. I would expect the first entry point to be traversed at first, even if it means calling a generator. On Sunday, November 16, 2014 3:56:20 PM UTC-5, Nicolas Morel wrote: Hi, I'm currently testing GWT 2.7.0-rc1 and one of my project using GWTP Rest-Dispatch https://github.com/ArcBees/GWTP/wiki/Rest-Dispatch is not working under SDM. The compilation fails with this error : [ERROR] Unable to load gin module type [com.gwtplatform.dispatch.rest.client.RestGinModule], maybe you haven't compiled your client java sources? java.lang.ClassNotFoundException: com$gwtplatform$dispatch$rest$ client$RestGinModule at com.google.gwt.inject.rebind.GinBridgeClassLoader.findClass( GinBridgeClassLoader.java:150) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at com.google.gwt.inject.rebind.GinBridgeClassLoader.loadClass( GinBridgeClassLoader.java:108) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:340) at com.google.gwt.inject.rebind.GinjectorGenerator.loadClass( GinjectorGenerator.java:223) at com.google.gwt.inject.rebind.GinjectorGenerator. getPropertyModuleClasses(GinjectorGenerator.java:137) at com.google.gwt.inject.rebind.GinjectorGenerator.getModuleClasses( GinjectorGenerator.java:116) at com.google.gwt.inject.rebind.GinjectorGenerator.generate( GinjectorGenerator.java:72) at com.google.gwt.core.ext.IncrementalGenerator. generateNonIncrementally(IncrementalGenerator.java:40) The full stack trace is available in attachment. The problem has been reported to the GWTP team here https://github.com/ArcBees/GWTP/issues/614. The normal compilation works but not the incremental compile from SDM. I made a simple example available here https://github.com/nmorel/hello-gwt-rest-dispatch. From what I saw, the RestGinModule that gin is trying
[gwt-contrib] Re: GWT 2.7 Scheduler works different on mobile and desktop in SDM
Timer and Scheduler.scheduleDeffered would not be expected to be equivalent. They have two different semantics. Scheduler.scheduleDeffered - runs after the browser event loop returns. new Timer().schedule(1000) - runs 1000 ms after being scheduled. You can not expect Scheduler.scheduleDeffered to give consistent results across platform. Scheduler.scheduleFixedDelay would be more equivalent to Timer.schedule On Tuesday, November 25, 2014 6:47:04 AM UTC-7, confile wrote: It seems that the Scheduler works different on mobile and desktop when using SDM. I created a demo project ( https://github.com/confile/GWT-2.7-Scheduler-Test) to show the problem. This is a demo app to test how the GWT Scheduler works different on mobile and on desktop in Super Dev Mode. I printed the height of a HTMLPanel for three different cases. 1. right after the DOM elements are inserted into the page (GWTP onReveal()) 2. right after the DOM elements are inserted into the page and Scheduler with a deferred command is executed 3. right after the DOM elements are inserted into the page and a Timer after 1000mx is fired Here is the difference in the console output: Output on Desktop - height before Timer and Scheduler: 0 - height after Scheduler: 652 - height after Timer: 652 Output on Mobile (iPhone 5, iOS 7.1.1) - height before Timer and Scheduler: 0 - height after Scheduler: 425 - height after Timer: 817 -- 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/15602de8-3472-4b1d-a26c-492296b564cd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7 Scheduler works different on mobile and desktop in SDM
It is clear that Timer and Scheduler are different. My concern is that Scheduler.scheduleDeffered behaves so differnent on different platforms. What is the best way to handle this? Am Mittwoch, 26. November 2014 16:11:01 UTC+1 schrieb Jonathon Lamon: Timer and Scheduler.scheduleDeffered would not be expected to be equivalent. They have two different semantics. Scheduler.scheduleDeffered - runs after the browser event loop returns. new Timer().schedule(1000) - runs 1000 ms after being scheduled. You can not expect Scheduler.scheduleDeffered to give consistent results across platform. Scheduler.scheduleFixedDelay would be more equivalent to Timer.schedule On Tuesday, November 25, 2014 6:47:04 AM UTC-7, confile wrote: It seems that the Scheduler works different on mobile and desktop when using SDM. I created a demo project ( https://github.com/confile/GWT-2.7-Scheduler-Test) to show the problem. This is a demo app to test how the GWT Scheduler works different on mobile and on desktop in Super Dev Mode. I printed the height of a HTMLPanel for three different cases. 1. right after the DOM elements are inserted into the page (GWTP onReveal()) 2. right after the DOM elements are inserted into the page and Scheduler with a deferred command is executed 3. right after the DOM elements are inserted into the page and a Timer after 1000mx is fired Here is the difference in the console output: Output on Desktop - height before Timer and Scheduler: 0 - height after Scheduler: 652 - height after Timer: 652 Output on Mobile (iPhone 5, iOS 7.1.1) - height before Timer and Scheduler: 0 - height after Scheduler: 425 - height after Timer: 817 -- 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/93f92371-4bfe-42c3-a1c8-44390e3fb543%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 Scheduler works different on mobile and desktop in SDM
@confile it is not possible to run your example because it is missing dependencies. From reading the code, the problem you are having is probably not caused by the Scheduler but by the time taken to resolve test.jpg. After modifying an element it is not necessary to pause before calling getOffsetHeight(). The call itself will force a redraw and the value will not change over time unless the element itself changes. In this case the height of the image element is changing as test.jpg downloads, this is why your output is inconsistent. On Wed, Nov 26, 2014 at 6:45 PM, confile michael.gorsk...@googlemail.com wrote: It is clear that Timer and Scheduler are different. My concern is that Scheduler.scheduleDeffered behaves so differnent on different platforms. What is the best way to handle this? Am Mittwoch, 26. November 2014 16:11:01 UTC+1 schrieb Jonathon Lamon: Timer and Scheduler.scheduleDeffered would not be expected to be equivalent. They have two different semantics. Scheduler.scheduleDeffered - runs after the browser event loop returns. new Timer().schedule(1000) - runs 1000 ms after being scheduled. You can not expect Scheduler.scheduleDeffered to give consistent results across platform. Scheduler.scheduleFixedDelay would be more equivalent to Timer.schedule On Tuesday, November 25, 2014 6:47:04 AM UTC-7, confile wrote: It seems that the Scheduler works different on mobile and desktop when using SDM. I created a demo project (https://github.com/confile/ GWT-2.7-Scheduler-Test) to show the problem. This is a demo app to test how the GWT Scheduler works different on mobile and on desktop in Super Dev Mode. I printed the height of a HTMLPanel for three different cases. 1. right after the DOM elements are inserted into the page (GWTP onReveal()) 2. right after the DOM elements are inserted into the page and Scheduler with a deferred command is executed 3. right after the DOM elements are inserted into the page and a Timer after 1000mx is fired Here is the difference in the console output: Output on Desktop - height before Timer and Scheduler: 0 - height after Scheduler: 652 - height after Timer: 652 Output on Mobile (iPhone 5, iOS 7.1.1) - height before Timer and Scheduler: 0 - height after Scheduler: 425 - height after Timer: 817 -- 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/93f92371-4bfe-42c3-a1c8-44390e3fb543%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/93f92371-4bfe-42c3-a1c8-44390e3fb543%40googlegroups.com?utm_medium=emailutm_source=footer . 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/CAEqaEVjVa1_rOzCGtJ5ihsaLY5RwacoNxPvdp04crHGJxi2Q-g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 Scheduler works different on mobile and desktop in SDM
Richard what do you suggest to solve this problem? Am Mittwoch, 26. November 2014 19:01:02 UTC+1 schrieb Richard Wallis: @confile it is not possible to run your example because it is missing dependencies. From reading the code, the problem you are having is probably not caused by the Scheduler but by the time taken to resolve test.jpg. After modifying an element it is not necessary to pause before calling getOffsetHeight(). The call itself will force a redraw and the value will not change over time unless the element itself changes. In this case the height of the image element is changing as test.jpg downloads, this is why your output is inconsistent. On Wed, Nov 26, 2014 at 6:45 PM, confile michael@googlemail.com javascript: wrote: It is clear that Timer and Scheduler are different. My concern is that Scheduler.scheduleDeffered behaves so differnent on different platforms. What is the best way to handle this? Am Mittwoch, 26. November 2014 16:11:01 UTC+1 schrieb Jonathon Lamon: Timer and Scheduler.scheduleDeffered would not be expected to be equivalent. They have two different semantics. Scheduler.scheduleDeffered - runs after the browser event loop returns. new Timer().schedule(1000) - runs 1000 ms after being scheduled. You can not expect Scheduler.scheduleDeffered to give consistent results across platform. Scheduler.scheduleFixedDelay would be more equivalent to Timer.schedule On Tuesday, November 25, 2014 6:47:04 AM UTC-7, confile wrote: It seems that the Scheduler works different on mobile and desktop when using SDM. I created a demo project (https://github.com/confile/ GWT-2.7-Scheduler-Test) to show the problem. This is a demo app to test how the GWT Scheduler works different on mobile and on desktop in Super Dev Mode. I printed the height of a HTMLPanel for three different cases. 1. right after the DOM elements are inserted into the page (GWTP onReveal()) 2. right after the DOM elements are inserted into the page and Scheduler with a deferred command is executed 3. right after the DOM elements are inserted into the page and a Timer after 1000mx is fired Here is the difference in the console output: Output on Desktop - height before Timer and Scheduler: 0 - height after Scheduler: 652 - height after Timer: 652 Output on Mobile (iPhone 5, iOS 7.1.1) - height before Timer and Scheduler: 0 - height after Scheduler: 425 - height after Timer: 817 -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/93f92371-4bfe-42c3-a1c8-44390e3fb543%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/93f92371-4bfe-42c3-a1c8-44390e3fb543%40googlegroups.com?utm_medium=emailutm_source=footer . 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/8bb121c7-2372-4419-86e7-993d9e992cd3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 Scheduler works different on mobile and desktop in SDM
Guessing but you can probably use image addLoadHandler() to wait for the image to load before checking the height. A more complex alternative is to download the image using a getRequest and then transform it into a base64 dataUrl and use that as the src for your image. On Wed, Nov 26, 2014 at 8:31 PM, confile michael.gorsk...@googlemail.com wrote: Richard what do you suggest to solve this problem? Am Mittwoch, 26. November 2014 19:01:02 UTC+1 schrieb Richard Wallis: @confile it is not possible to run your example because it is missing dependencies. From reading the code, the problem you are having is probably not caused by the Scheduler but by the time taken to resolve test.jpg. After modifying an element it is not necessary to pause before calling getOffsetHeight(). The call itself will force a redraw and the value will not change over time unless the element itself changes. In this case the height of the image element is changing as test.jpg downloads, this is why your output is inconsistent. On Wed, Nov 26, 2014 at 6:45 PM, confile michael@googlemail.com wrote: It is clear that Timer and Scheduler are different. My concern is that Scheduler.scheduleDeffered behaves so differnent on different platforms. What is the best way to handle this? Am Mittwoch, 26. November 2014 16:11:01 UTC+1 schrieb Jonathon Lamon: Timer and Scheduler.scheduleDeffered would not be expected to be equivalent. They have two different semantics. Scheduler.scheduleDeffered - runs after the browser event loop returns. new Timer().schedule(1000) - runs 1000 ms after being scheduled. You can not expect Scheduler.scheduleDeffered to give consistent results across platform. Scheduler.scheduleFixedDelay would be more equivalent to Timer.schedule On Tuesday, November 25, 2014 6:47:04 AM UTC-7, confile wrote: It seems that the Scheduler works different on mobile and desktop when using SDM. I created a demo project (https://github.com/confile/GW T-2.7-Scheduler-Test) to show the problem. This is a demo app to test how the GWT Scheduler works different on mobile and on desktop in Super Dev Mode. I printed the height of a HTMLPanel for three different cases. 1. right after the DOM elements are inserted into the page (GWTP onReveal()) 2. right after the DOM elements are inserted into the page and Scheduler with a deferred command is executed 3. right after the DOM elements are inserted into the page and a Timer after 1000mx is fired Here is the difference in the console output: Output on Desktop - height before Timer and Scheduler: 0 - height after Scheduler: 652 - height after Timer: 652 Output on Mobile (iPhone 5, iOS 7.1.1) - height before Timer and Scheduler: 0 - height after Scheduler: 425 - height after Timer: 817 -- 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/93f92371-4bfe- 42c3-a1c8-44390e3fb543%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/93f92371-4bfe-42c3-a1c8-44390e3fb543%40googlegroups.com?utm_medium=emailutm_source=footer . 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/8bb121c7-2372-4419-86e7-993d9e992cd3%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/8bb121c7-2372-4419-86e7-993d9e992cd3%40googlegroups.com?utm_medium=emailutm_source=footer . 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/CAEqaEVj-ouJ3drkPPHMC_VS_bwRzNegzF8niv3kFUz0w_55%2BnA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.