Re: GWT 2.7.0 is here
I find the source maps works sometimes, but sometimes not. I've heard other say the same as well. Haven't been able to reproduce it with any level of consistency either so who knows what's causing it! On Monday, 24 November 2014 23:17:56 UTC, jaga wrote: Yes. I noticed it needs double the memory. Also the -port parameter does not seem to work in Eclipse. Finally, and most importantly, I could not get the source maps to work. They don't appear in chrome dev tools. I had it all working in 2.6.1. -- 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 dev plugin stopped working on Chrome 39
Thank you Jens, this make a sense! SuperDevMode has ugly debugging. Unforutnately... Do you know where Chrome 38 OSX can be downloaded? Chrome is now 64 bit on OS X and the plugin is only 32 bit. So you have to use a different/older browser or use SuperDevMode. -- 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 dev plugin stopped working on Chrome 39
SuperDevMode has ugly debugging. Unforutnately... Do you know where Chrome 38 OSX can be downloaded? Not really, you have to google yourself. I use SuperDevMode. -- 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: GWT dev plugin stopped working on Chrome 39
Search Portable Chrome, make sure it's the 32 bit version. Since its another year away, I wonder what the possibility of getting one more build of the browser DevMode plugin? Maybe plug some memory leaks and recompile it so it will work with 64 bit Chrome, where possible? On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote: Thank you Jens, this make a sense! SuperDevMode has ugly debugging. Unforutnately... Do you know where Chrome 38 OSX can be downloaded? Chrome is now 64 bit on OS X and the plugin is only 32 bit. So you have to use a different/older browser or use SuperDevMode. -- 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.
AST manipulation
Hello, Are there any plans to allow manipulate AST tree during compilation? Some limited hooks will allow to avoid GWT.create everywhere generated stuff is required. thanks -- 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.
Debugging workers
Hi, Does someone have some tips to debug code that's run in a worker ? SDM takes care of nearly all my debug needs, but there's still this limitation, that hurts hard right now. Sure, I can debug the generated js code, but even prettyfied, the generated code is not really easy to read (big chunks of js instead of nice small classes, long function names etc.) Mickaël -- 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.
UiBinder library
Hello, Does GWT license allows for the separation of functionality into a separate library GWT? Trying to separate UIBinder to a separate library with GWT 2.6.0 and modify UiBinder but now I have this error: Compiling module org.yournamehere.Main Computing all possible rebind results for 'org.yournamehere.client.DynamicForm.DynamicFormUiBinder' Rebinding org.yournamehere.client.DynamicForm.DynamicFormUiBinder Invoking generator runtimeuibinder.rebind.UiBinderGenerator [ERROR] Generator 'runtimeuibinder.rebind.UiBinderGenerator' threw an exception while rebinding 'org.yournamehere.client.DynamicForm.DynamicFormUiBinder' java.lang.RuntimeException: com.google.gwt.uibinder.elementparsers.HasWidgetsParser must extend ElementParser at runtimeuibinder.rebind.UiBinderWriter.getParserForClass(UiBinderWriter.java:1269) at runtimeuibinder.rebind.UiBinderWriter.getParsersForClass(UiBinderWriter.java:1293) at runtimeuibinder.rebind.UiBinderWriter.parseElementToField(UiBinderWriter.java:933) at runtimeuibinder.rebind.UiBinderParser.parse(UiBinderParser.java:146) at runtimeuibinder.rebind.UiBinderWriter.parseDocumentElement(UiBinderWriter.java:1368) at runtimeuibinder.rebind.UiBinderWriter.parseDocument(UiBinderWriter.java:1073) at runtimeuibinder.rebind.UiBinderGenerator.generateOnce(UiBinderGenerator.java:177) at runtimeuibinder.rebind.UiBinderGenerator.generate(UiBinderGenerator.java:129) at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(IncrementalGenerator.java:40) at com.google.gwt.core.ext.IncrementalGenerator.generateNonIncrementally(IncrementalGenerator.java:40) at com.google.gwt.dev.javac.StandardGeneratorContext.runGeneratorIncrementally(StandardGeneratorContext.java:676) at com.google.gwt.dev.cfg.RuleGenerateWith.realize(RuleGenerateWith.java:41) at com.google.gwt.dev.shell.StandardRebindOracle$Rebinder.rebind(StandardRebindOracle.java:79) at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:276) at com.google.gwt.dev.shell.StandardRebindOracle.rebind(StandardRebindOracle.java:265) at com.google.gwt.dev.DistillerRebindPermutationOracle.getAllPossibleRebindAnswers(DistillerRebindPermutationOracle.java:91) at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.handleGwtCreate(UnifyAst.java:387) at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.handleMagicMethodCall(UnifyAst.java:465) at com.google.gwt.dev.jjs.impl.UnifyAst$UnifyVisitor.endVisit(UnifyAst.java:255) at com.google.gwt.dev.jjs.ast.JMethodCall.traverse(JMethodCall.java:244) at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265) at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:117) at com.google.gwt.dev.jjs.ast.JCastOperation.traverse(JCastOperation.java:65) at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265) at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:117) at com.google.gwt.dev.jjs.ast.JDeclarationStatement.traverse(JDeclarationStatement.java:48) at com.google.gwt.dev.jjs.ast.JModVisitor$ListContextImmutable.traverse(JModVisitor.java:170) at com.google.gwt.dev.jjs.ast.JModVisitor.acceptWithInsertRemoveImmutable(JModVisitor.java:336) at com.google.gwt.dev.jjs.ast.JBlock.traverse(JBlock.java:83) at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273) at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:138) at com.google.gwt.dev.jjs.ast.JVisitor.accept(JVisitor.java:134) at com.google.gwt.dev.jjs.ast.JMethodBody.traverse(JMethodBody.java:82) at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265) at com.google.gwt.dev.jjs.ast.JMethod.visitChildren(JMethod.java:449) at com.google.gwt.dev.jjs.ast.JMethod.traverse(JMethod.java:418) at com.google.gwt.dev.jjs.ast.JModVisitor.traverse(JModVisitor.java:361) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:273) at com.google.gwt.dev.jjs.ast.JModVisitor.accept(JModVisitor.java:265) at com.google.gwt.dev.jjs.impl.UnifyAst.mainLoop(UnifyAst.java:940) at com.google.gwt.dev.jjs.impl.UnifyAst.exec(UnifyAst.java:665) at com.google.gwt.dev.jjs.JavaToJavaScriptCompiler.precompile(JavaToJavaScriptCompiler.java:672) at
Re: UiBinder library
Does GWT license allows for the separation of functionality into a separate library GWT? GWT is Apache 2.0 license and I think the actual packaging should not matter as long as your separate library complies with the Apache 2.0 license. java.lang.RuntimeException: com.google.gwt.uibinder.elementparsers.HasWidgetsParser must extend ElementParser The RuntimeException is thrown if a ClassCastException has occurred. So I would guess your library has messed up HasWidgetsParser somehow or you have a ClassLoader issue. The idea behind the ClassLoader issue is that a class that is loaded by two different ClassLoaders can not be cast to itself if both ClassLoaders are involved. Since you have gwt-user.jar on class path and also your custom library you now have several UiBinder related classes twice on class path. If now HashWidgetsParser extends ElementParser has been loaded by ClassLoader A and the ElementParser.class used in the cast statement found in UiBinderWriter (see your stack trace) has been loaded by ClassLoader B then you will get a ClassCastException if you try to cast HasWidgetsParser/ElementParser (from ClassLoader A) to ElementParser (from ClassLoader B). I don't know the UiBinder code very well so no idea if that can actually happen but at least it is something worth checking. If I were you I would checkout the GWT 2.6.0 tag from git, then change UiBinder they way you want it and finally build your own customized GWT 2.6.0 version. If you later want to upgrade to GWT 2.7 you checkout the 2.7 tag and rebase your commits on top of it to keep your changes. -- 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.
Gwt 2.7
I tried to update to 2.7.0 today. Got weird message about trying to load undefined.nocache.js with a blank page as result. Running chrome. Anybody ideas. Going back to 2.6 for now. Got functions to implement :-) Als the memory usage is huge. I set the xmx to 4g. I hoped it would be better with 2.7. Marteijn -- 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
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: UiBinder library
You're right. Thanks for the clarification RG Łukasz W dniu 25.11.2014 o 20:45, Jens pisze: Does GWT license allows for the separation of functionality into a separate library GWT? GWT is Apache 2.0 license and I think the actual packaging should not matter as long as your separate library complies with the Apache 2.0 license. java.lang.RuntimeException: com.google.gwt.uibinder.elementparsers.HasWidgetsParser must extend ElementParser The RuntimeException is thrown if a ClassCastException has occurred. So I would guess your library has messed up HasWidgetsParser somehow or you have a ClassLoader issue. The idea behind the ClassLoader issue is that a class that is loaded by two different ClassLoaders can not be cast to itself if both ClassLoaders are involved. Since you have gwt-user.jar on class path and also your custom library you now have several UiBinder related classes twice on class path. If now HashWidgetsParser extends ElementParser has been loaded by ClassLoader A and the ElementParser.class used in the cast statement found in UiBinderWriter (see your stack trace) has been loaded by ClassLoader B then you will get a ClassCastException if you try to cast HasWidgetsParser/ElementParser (from ClassLoader A) to ElementParser (from ClassLoader B). I don't know the UiBinder code very well so no idea if that can actually happen but at least it is something worth checking. If I were you I would checkout the GWT 2.6.0 tag from git, then change UiBinder they way you want it and finally build your own customized GWT 2.6.0 version. If you later want to upgrade to GWT 2.7 you checkout the 2.7 tag and rebase your commits on top of it to keep your changes. -- 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 mailto:google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com mailto: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 2.7 and GSS
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 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
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 pank...@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/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: GWT 2.7 and GSS
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.dram...@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 pank...@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/ 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: GWT dev plugin stopped working on Chrome 39
SuperDevMode debugging is not so convenient as DevMode, but with SDBG https://github.com/sdbg/sdbg it's almost OK for me. Also with new GPE it's very easy to switch between SuperDevMode and DevMode debugging, so I use both of them now. On Tuesday, November 25, 2014 5:49:40 AM UTC-8, jonl wrote: Search Portable Chrome, make sure it's the 32 bit version. Since its another year away, I wonder what the possibility of getting one more build of the browser DevMode plugin? Maybe plug some memory leaks and recompile it so it will work with 64 bit Chrome, where possible? On Tuesday, November 25, 2014 3:21:28 AM UTC-7, Igor Zubchenok wrote: Thank you Jens, this make a sense! SuperDevMode has ugly debugging. Unforutnately... Do you know where Chrome 38 OSX can be downloaded? Chrome is now 64 bit on OS X and the plugin is only 32 bit. So you have to use a different/older browser or use SuperDevMode. -- 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
:-) 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 javascript: 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 javascript: 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/ 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: ClassCastException when trying SuperDevMode on my application with 2.7
Thanks. So far I have been unable to isolate this into a smaller example. I've tried some very basic entrypoint classes and added the external modules I use like the Openlayers gwt wrapper and the gwttime (which has one of its classes mentioned in the trace). They all have worked fine. Open to any suggestions for how to get more information about what's going on that I can report back... Roland On Saturday, November 22, 2014 1:20:45 PM UTC-6, John Stalcup wrote: It sounds like one of the registered EntryPoint classes or something that one of the EntryPoint classes is being rebound to does not implement the EntryPoint interface. On Sat, Nov 22, 2014, 1:29 AM Thomas Broyer t.br...@gmail.com javascript: wrote: +cc stalcup@ Any idea John? Roland, can you make a small repro-case? On Saturday, November 22, 2014 12:38:16 AM UTC+1, Roland wrote: With the advent of 2.7 I am determined to get going with SuperDevMode. However, once my development environment (Eclipse) is all set to run the code server when I try to load my application using SuperDevMode I get the following error. This actually happens whether I compile with debug mode on or debug mode off when loading the code this way. I don't know what piece of the tool chain is reporting the error, but this shows up in my JavaScript console. Uncaught java.lang.ClassCastExceptionCast.java:59 dynamicCast_0_g$ gov_00046noaa_00046pmel_00046tmap_00046las_00046UI__ EntryMethodHolder.java:3 init_2_g$ModuleUtils.java:44 initializeModules_0_g$ Impl.java:247 apply_1_g$ Impl.java:306 entry0_0_g$ Impl.java:72 (anonymous function) ModuleUtils.java:55 gwtOnLoad_0_g$ PeriodPrinter.java:40 (anonymous function) This happens both when I try Firefox 33.0 and Chrome Version 39.0.2171.65 (64-bit) as the browser. The application runs fine as a production app if I compile it and deploy it to the server from the command line. I could also debug it using Classic Development Mode using FF 24 just prior to now when I was using GWT 2.5. I run in MyEclipse 2015 on Ubuntu 14.04 if that makes a difference. If this is a problem with the framework and not my application I'm happy to help try to gather the information to get it fixed, but I would need some guidance for how to gather the details needed to debug. Thanks, Roland -- 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.
request factory and pure js client
I have a successful GWT/AppEngine/Objectify application that communicates via RequestFactory. I've seen some nice things with jsinterop integrating js modules into GWT. Is there a way to package the request factory client code so that it can be called from a javascript client? It would be nice to reuse the server side code rather than rewriting it. -- -- Andy Stevko === If everything seems under control, you're just not going fast enough. M. Andretti -- 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
Hi, I can't find any information about a possible alternative to the 'widget' package removed in 2.7.0. Are they bundled in another jar somewhere? All the release notes http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0_RC1 say is: The deprecated com.google.gwt.widgets package is removed. Thanks in advance, Pete -- 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-contrib] Ant Build failing with OutOfMemory Errors after upgrading to 2.7
Hello, we have a very large GWT project with only client code (approx. 1 million LoC , everything in a single module) and an Jenkins job up running which uses ant to build the project and to deploy the code on our test environment and productive servers. It uses about 2 GB as Heapsize value for the builds. With GWT 2.6.1 the builds take about 12-15 minutes to finish (with 8 permutations: gecko and webkit, german and english locales and debug messages off / on) but after upgrading to 2.7.0 they're always failing due to OutOfMemory errors. To get them pass I have to increase heapsize to a minimum of 4GB or better 6GB. I tried already to turn off the compiler optimization (level 0 instead of 9) and tested some options like draftCompile, but still the builds are failing. What happens there during compilation so that it needs at least the double of memory space? Do you have some suggestions so I can optimize my builds (run faster, need less memory)? Thanks in advance, Paul -- 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/38149b55-9080-469f-8456-0c55dacf7ed9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Invesigating OOPHM chrome dev tools js extension creation
I'm also interested in this. Check http://sdbg.github.io/ for a GWT-friendly JavaScript+Sourcemaps debugger for Eclipse. As for avoiding page refreshes, it is a great idea but as Ray said once, it would require significant work in GWT itself as well. For more details, you may want to check my Chrome LiveEdit and SDM thread in this group: https://groups.google.com/forum/#!searchin/google-web-toolkit-contributors/chrome$20liveedit$20and$20sdm/google-web-toolkit-contributors/W-oKhuuT0S8/yLM_UL-bTRUJ There is also the problem that if you decide to base hot patching on top of Chrome LiveEdit (which is not necessarily required, the way JavaScript works!), LiveEdit seems to have an upper limit on the JS file size it can swallow (around 10Mb). If your JS is bigger than that, the browser simply crashes. Hot-patching on recompile is explored in these SDBG classes: https://github.com/sdbg/sdbg/tree/master/com.github.sdbg.integration.jdt/src/com/github/sdbg/integration/jdt/gwt At the current stage, hot-patching works only via page refresh (which kinda defeats the whole purpose), due to (a) the changes required to the GWT JS code emitter itself, and (b) because of the aforementioned Chrome LiveEdit limitation. 24 ноември 2014, понеделник, 21:57:15 UTC+2, Brandon Donnelson написа: Ah ha, nice. Thanks for sharing. I remember seeing Lief's work now that you bring that up. Ok I'm ending my OOPHM hacking, although I'd like to look at the possibility of using IDE to remotely control browser dev tools and work with the SDM systems, or in other words I like what Ray said. Like working with break points in the browser source maps could be synced the IDE breakpoints. Would be nifty to look into js modifications done in incremental compile and inject them into the browser instead of waiting for them to be loaded again on refresh. Thanks, Brandon On Monday, November 24, 2014 10:30:24 AM UTC-8, Goktug Gokdogan wrote: Somebody previously experimented with it: https://github.com/Legioth/devmodejs On Mon, Nov 24, 2014 at 9:49 AM, 'Ray Cromwell' via GWT Contributors google-web-toolkit-contributors@googlegroups.com wrote: If you mean replacing the DevMode plugin with pure JS in Chrome Dev Tools, I don't think it's practical. You need synchronously re-entrant code execution. Javascript's only synchronous blocking call is XHR sync. But you also need re-entrancy, and when you are debugging/pausing execution, you run into additional hurdles. Many people have tried hacks to do this, with Applets, with XHR, it's possible in theory if you rewrite all code sent to the browser to use continuations. I would advocate just continuing to make IDE integration with SDM better. On Mon, Nov 24, 2014 at 9:38 AM, Brandon Donnelson branfl...@gmail.com wrote: I'm investigating the possibility of creating a js chrome dev tools extension to talk OOPHM with GPE OOPHM. So far it looks potential feasible to use what's in place on in GPE to do the communicating with some new browser extension. Although I do see having to write some new bidirectional options to sync up the log entries and maybe adding some new parsing ability for sdm output. For those who might know some about the OOPHM process, would you see any hang ups in writing a chrome dev tools javascript extension? Thanks, Brandon -- 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/a1363906-faef-427d-b8f6-c9209dce891a%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/CAPVRV7cKBFJeg8S-1B_Mzw%2BGMb21k-3qkRO-jzb%2B0-hQkR%3D4VQ%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/bcf01e57-63c7-48c1-9655-65e67815af0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Digest for google-web-toolkit-contributors@googlegroups.com - 5 updates in 1 topic
You may check the sdbg project which aims to drive the chrome debugger from eclipse. You get an experience really close to the old dev mode, like working with breakpoints from eclipse Thanks Arnaud Le mar. 25 nov. 2014 11:55, null google-web-toolkit-contributors@googlegroups.com a écrit : google-web-toolkit-contributors@googlegroups.com https://groups.google.com/forum/?utm_source=digestutm_medium=email/#!forum/google-web-toolkit-contributors/topics Google Groups https://groups.google.com/forum/?utm_source=digestutm_medium=email/#!overview https://groups.google.com/forum/?utm_source=digestutm_medium=email/#!overview Topic digest View all topics https://groups.google.com/forum/?utm_source=digestutm_medium=email/#!forum/google-web-toolkit-contributors/topics - Invesigating OOPHM chrome dev tools js extension creation #msg-f:1485740903908296447_group_thread_0 - 5 Updates Invesigating OOPHM chrome dev tools js extension creation http://groups.google.com/group/google-web-toolkit-contributors/t/12d9b2a202e349e3?utm_source=digestutm_medium=email Brandon Donnelson branflake2...@gmail.com: Nov 24 09:38AM -0800 I'm investigating the possibility of creating a js chrome dev tools extension to talk OOPHM with GPE OOPHM. So far it looks potential feasible to use what's in place on in GPE to do the communicating with some new browser extension. Although I do see having to write some new bidirectional options to sync up the log entries and maybe adding some new parsing ability for sdm output. For those who might know some about the OOPHM process, would you see any hang ups in writing a chrome dev tools javascript extension? Thanks, Brandon Ray Cromwell cromwell...@google.com: Nov 24 09:49AM -0800 If you mean replacing the DevMode plugin with pure JS in Chrome Dev Tools, I don't think it's practical. You need synchronously re-entrant code execution. Javascript's only synchronous blocking call is XHR sync. But you also need re-entrancy, and when you are debugging/pausing execution, you run into additional hurdles. Many people have tried hacks to do this, with Applets, with XHR, it's possible in theory if you rewrite all code sent to the browser to use continuations. I would advocate just continuing to make IDE integration with SDM better. On Mon, Nov 24, 2014 at 9:38 AM, Brandon Donnelson Manuel Carrasco Moñino man...@apache.org: Nov 24 07:28PM +0100 Leif at Vaadin already was exploring the possibility of having a devmode in pure JS, his experimental work is at https://github.com/Legioth/devmodejs, afaik although it's feasible (he succeed debugging some stuff) it is very slow, apart from other issues like memory allocation, etc. On Mon, Nov 24, 2014 at 6:49 PM, 'Ray Cromwell' via GWT Contributors Goktug Gokdogan gok...@google.com: Nov 24 10:30AM -0800 Somebody previously experimented with it: https://github.com/Legioth/devmodejs On Mon, Nov 24, 2014 at 9:49 AM, 'Ray Cromwell' via GWT Contributors Brandon Donnelson branflake2...@gmail.com: Nov 24 11:57AM -0800 Ah ha, nice. Thanks for sharing. I remember seeing Lief's work now that you bring that up. Ok I'm ending my OOPHM hacking, although I'd like to look at the possibility of using IDE to remotely control browser dev tools and work with the SDM systems, or in other words I like what Ray said. Like working with break points in the browser source maps could be synced the IDE breakpoints. Would be nifty to look into js modifications done in incremental compile and inject them into the browser instead of waiting for them to be loaded again on refresh. Thanks, Brandon On Monday, November 24, 2014 10:30:24 AM UTC-8, Goktug Gokdogan wrote: Back to top #msg-f:1485740903908296447_digest_top You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page https://groups.google.com/forum/?utm_source=digestutm_medium=email/#!forum/google-web-toolkit-contributors/join . To unsubscribe from this group and stop receiving emails from it send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. -- 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/CANjaDnepc8tF_svXcQ7jqTEfqW4Vz63jYx-EoBWWwVaoKjmaaQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] GWT 2.7 Scheduler works different on mobile and desktop in SDM
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/e3ece950-6898-4663-9201-f56e148789c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: Recompile issue coming up on sdm start, gwt 2.7.0-snapshot
As I can see in gwt 2.7.0 release it was not fixed. collapse-all-properties doesn't help :( -- 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/60aca37e-9722-4240-b9d5-34f329b02948%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Chrome LiveEdit and SDM
Hm, from what it sounds like, instead of hot patching, it'd be more practical and easier to change my debugging strategy and especially since the refresh time is so fast now using incremental compiles. I suppose I leave that behind for now. It seems more practical to refresh than fight the reality of hot patching, which is probably not what folks would want to hear. And this probably has to do with the design challenge for those who are debugging apps that with an authentication process to run through before they get to the widgets there working on, which docs could be used to help guide through this type of process. Thanks for the feedback, Brandon On Saturday, September 6, 2014 11:42:38 AM UTC-7, Ray Cromwell wrote: HotPatching via recompilation will require significant work in SDM. If you just did the naive thing and patched in the JS that changed, stuff would break: 1) clinit()s which have already been called would be restored, so classes would get initialized twice 2) some instance fields of the class would get reinitialized 3) callbacks held by JSNI closures might still point to old code in some circumstances I think SDM mode would have to do minimally the following: 1) collect only the JS that actually changed 2) don't emit clinits for already live classes, and if the user added a new clinit to an existing class or a new statically initialized field, force a full refresh 3) don't re-emit field initializers for existing fields on classes, only for new added fields 4) if method signatures change, may have to force a full refresh 5) the code must be patched in via linker-dependent scope injection as if it were an AsyncFragment On Sat, Sep 6, 2014 at 9:05 AM, Ivan Markov ivan@gmail.com javascript: wrote: Another option would be to abandon Chrome LiveEdit completely in favor of a do-it-yourself approach. JavaScript does allow functions and variables redefinition, so maybe we can just inject another script inside the iframe with the newly recompiled permutation? (To have this instantaneous, only a script containing the changed types should be injected, however I'm not sure if/what needs to be fixed so that sourcemaps continue to work after that.) -- 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/eeeb5252-162b-4381-a3fa-14da59fa9873%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/eeeb5252-162b-4381-a3fa-14da59fa9873%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/71857207-4bfe-4ebb-a1e3-a266880f2db7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
