Re: [gwt-contrib] GWT 2.7 : precompile and incremental flags
Just curious, but didn't svn change (maybe a year ago or so?) to only using one top-level .svn folder, similar to Git's top-level .git folder, and not having .svn littered throughout the file system? - Stephen You're right, but we have scripts that still rely on .svn folders, so we can't update to a newer version at the moment. -- 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/1cb2136d-564b-4e09-bcf8-a2a780f40e38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] 2.7.0-beta1 deferredjs bypasses application cache
On Monday, October 20, 2014 10:49:13 PM UTC+2, Thomas Broyer wrote: IIRC, Brian changed the behavior of the xsiframe linker to match the direct-install linker, because most browsers would otherwise not display the source maps. There should be flag to turn it off and go back to the previous behavior. Here's the commit that changed xsiframe behavior: https://gwt.googlesource.com/gwt/+/ab905f749cb81e930c9240f3c67acbcf96a4a4e2 It actually depends (by default, if not overridden) whether you use -style PRETTY (or DETAILED) or not (i.e. OBF or OBFUSCATED) See https://code.google.com/p/google-web-toolkit/issues/detail?id=8578#c5 for the rationale. -- 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/ee970214-9fd0-46be-aa9a-17cb299d491b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] 2.7.0-beta1 deferredjs bypasses application cache
Thanks, just checked and set-configuration-property name=installCode value=true / also fixes the problem, so I'll use that instead of adding the linker. On Wed, Oct 22, 2014 at 11:27 AM, Thomas Broyer t.bro...@gmail.com wrote: On Monday, October 20, 2014 10:49:13 PM UTC+2, Thomas Broyer wrote: IIRC, Brian changed the behavior of the xsiframe linker to match the direct-install linker, because most browsers would otherwise not display the source maps. There should be flag to turn it off and go back to the previous behavior. Here's the commit that changed xsiframe behavior: https://gwt.googlesource.com/gwt/+/ab905f749cb81e930c9240f3c67acbcf96a4a4e2 It actually depends (by default, if not overridden) whether you use -style PRETTY (or DETAILED) or not (i.e. OBF or OBFUSCATED) See https://code.google.com/p/google-web-toolkit/issues/detail?id=8578#c5 for the rationale. -- 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/ee970214-9fd0-46be-aa9a-17cb299d491b%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/ee970214-9fd0-46be-aa9a-17cb299d491b%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/CAEqaEVgPwynDckdFajax0igbx3EfEKy0TdPF8HOkAobsnSxYkg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] GWT 2.7 SDM incremental output too large
Hi, Our app produces permutations about 3.5mb in size when doing optimized production builds. It is roughly 150.000 fields across 12.000 types (according to the first SDM incremental compile output). I tried that app with several browsers (all Mac OS) to see how things work with SDM incremental compile: - Opening the native dev tools of *Firefox 33* and switching to the debugger tab freezes Firefox for several (5+) minutes until it finally displays all source mapped java files. And thats for each page reload. Breakpoints work but since you can not see which source line is mapped you might need to guess a bit until you find a spot where the breakpoint actually works (or look it up on the code server). But because of the reload times debugging is literally unusable. Maybe it is possible to use FireFox remote debugging in IntelliJ. Haven't tried that yet. - *Safari 7* also has quite some lag. The reason is that Safari Dev Tools store each XHR request done to fetch a source mapped file from code server. If you now want to search for a Java file in the browser the search lags quite a bit because it also filters all these 1000+ XHR requests. But thats a Safari issue one must accept for now. I also noticed that sometimes the CodeServer responds with 404 for all source mapped files that are generated by GWT generators, e.g. GET /sourcemaps/app/3427F4D36ECEACFA71B338AB1AE1396C_sourcemap.json sent source map for module 'app' in 269 ms GET /sourcemaps/app/gen/com/google/gwt/cell/client/TextInputCell_TemplateImpl.java Sent error page: unknown source file: gen/com/google/gwt/cell/client/TextInputCell_TemplateImpl.java When I open up the CodeServer web site at ip:9876/sourcemaps/app/ I can see an entry for gen/com/google/gwt/cell/client/ . Once I enter it I can see the TextInputCell_TemplateImpl.java however if I want to open it in the browser the CodeServer can not find it and reports an error. Thats something I haven't noticed in Chrome so far. Finally setting break points in the source mapped Java file does not seem to work at all in Safari 7. Breakpoints are accepted but never hit by the debugger. I tried several different code lines (all are marked as black lines on the code server sourcemap html output so they should have valid mappings). - In *IE 11* it also takes quite some time until source mapped java files appear in the dev tools (similar to FireFox). Once they appear, file filtering is pretty slow but I can live with that. However if I want to set a breakpoint in any of my files then the breakpoint is actually placed in a GWT file called ModuleUtils.java. No idea why but that also makes debugging impossible. Trying to open the pure JS file does not work either. So in short, although incremental compilation is pretty cool all non Google Chrome browsers have issues with our app because 1.) the pure JS size produced by incremental compile is too large (Safari actually showed the total size of resources downloaded and it shows 75MB) and 2.) handling the source map does not work well and break points might be dead. For IE we can still use classic DevMode but for FireFox, Safari and mobile browsers debugging doesn't work well for large apps. -- J. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/f9a27e73-0e13-4b06-971d-4c3e954fe1a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: GWT 2.7 SDM incremental output too large
Our application is roughly the same size (3.5mb) and I have never been able to debug using source maps in firefox. It freezes when it has to load them. I have also tried remote javascript debugging with super devmode from IntelliJ. I can typically step over a couple of breakpoints and then it drops the connection. So I still use DevMode with Firefox 24 ESR when I have to debug. Works fine in chrome. Best regards Rene Den onsdag den 22. oktober 2014 11.52.40 UTC+2 skrev Jens: Hi, Our app produces permutations about 3.5mb in size when doing optimized production builds. It is roughly 150.000 fields across 12.000 types (according to the first SDM incremental compile output). I tried that app with several browsers (all Mac OS) to see how things work with SDM incremental compile: - Opening the native dev tools of *Firefox 33* and switching to the debugger tab freezes Firefox for several (5+) minutes until it finally displays all source mapped java files. And thats for each page reload. Breakpoints work but since you can not see which source line is mapped you might need to guess a bit until you find a spot where the breakpoint actually works (or look it up on the code server). But because of the reload times debugging is literally unusable. Maybe it is possible to use FireFox remote debugging in IntelliJ. Haven't tried that yet. - *Safari 7* also has quite some lag. The reason is that Safari Dev Tools store each XHR request done to fetch a source mapped file from code server. If you now want to search for a Java file in the browser the search lags quite a bit because it also filters all these 1000+ XHR requests. But thats a Safari issue one must accept for now. I also noticed that sometimes the CodeServer responds with 404 for all source mapped files that are generated by GWT generators, e.g. GET /sourcemaps/app/3427F4D36ECEACFA71B338AB1AE1396C_sourcemap.json sent source map for module 'app' in 269 ms GET /sourcemaps/app/gen/com/google/gwt/cell/client/TextInputCell_TemplateImpl.java Sent error page: unknown source file: gen/com/google/gwt/cell/client/TextInputCell_TemplateImpl.java When I open up the CodeServer web site at ip:9876/sourcemaps/app/ I can see an entry for gen/com/google/gwt/cell/client/ . Once I enter it I can see the TextInputCell_TemplateImpl.java however if I want to open it in the browser the CodeServer can not find it and reports an error. Thats something I haven't noticed in Chrome so far. Finally setting break points in the source mapped Java file does not seem to work at all in Safari 7. Breakpoints are accepted but never hit by the debugger. I tried several different code lines (all are marked as black lines on the code server sourcemap html output so they should have valid mappings). - In *IE 11* it also takes quite some time until source mapped java files appear in the dev tools (similar to FireFox). Once they appear, file filtering is pretty slow but I can live with that. However if I want to set a breakpoint in any of my files then the breakpoint is actually placed in a GWT file called ModuleUtils.java. No idea why but that also makes debugging impossible. Trying to open the pure JS file does not work either. So in short, although incremental compilation is pretty cool all non Google Chrome browsers have issues with our app because 1.) the pure JS size produced by incremental compile is too large (Safari actually showed the total size of resources downloaded and it shows 75MB) and 2.) handling the source map does not work well and break points might be dead. For IE we can still use classic DevMode but for FireFox, Safari and mobile browsers debugging doesn't work well for large apps. -- J. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/69d8d8a2-367e-4339-92fe-708841d23e30%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin
Thank you for that, but right know my main target is to move our projects to GWT 2.7 and migrate our developers to SDM. Regards, Matic On Tuesday, October 21, 2014 8:50:01 PM UTC+2, Brandon Donnelson wrote: Ah, thanks for sharing. I just wanted to double check. By the way if you're interested in the GPE preview, I've got that handy if you want to try it out. On Tuesday, October 21, 2014 10:00:54 AM UTC-7, Matic Petek wrote: Yes, it was my mistake when I upgrade from 2.6 to 2.7 snapshot. Not it is working. I just want to write it in forum if someone else would have the some problem... Thank you for help. Regards, Matic On Tuesday, October 21, 2014 6:41:11 PM UTC+2, Brandon Donnelson wrote: Manolo is correct, the superdevmode-launcher-legacy.jar is not needed with GWT 2.7. It can be used with GWT 2.5.x and 2.6.x. Did you add that to the classpath? Brandon On Tuesday, October 21, 2014 6:03:14 AM UTC-7, Manuel Carrasco Moñino wrote: You shouldn't put never that .jar in your classpath. GPE takes care of adding it to the launcher classpath when you run superdevmode and your gwt is not 2.7. On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek matic...@gmail.com wrote: I have superdevmode-launcher-legacy.jar in classpath and it is not compatible with GWT 2.7. Regards, Matic On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote: I suspect the sdk isn't what you think it is if its not working. Can you check the classpath and see if it was updated? On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote: Hi, I would like to test new compile per file option, but we run our project from Eclipse and we don't use Maven. So I have perform the following steps : 1) Download JAR files from https://oss.sonatype.org/ content/repositories/google-snapshots/com/google/gwt/ gwt-servlet.jar gwt-user.jar gwt-dev.jar gwt-codeserver.jar on 1.9.2014 date 2) Create new Google - Web Toolkit configuration 3) select this configuration on my Eclipse project. But when I run hosted mode, I get the error below. Any idea if I'm doing something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest version of GWT. Thank you. Regards, Matic Exception in thread main java.lang.NoSuchMethodError: com.google.gwt.dev.javac.CompilationStateBuilder.init( Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943) at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498) at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097) at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863) at com.google.gwt.dev.DevMode.main(DevMode.java:379) -- 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/f10b78d5-b358-4d18-abb5-3a9d49a2c429%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%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/87525c88-6a47-4b34-8312-8af86aa0c04d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin
Hi Brandon, The GWTP plugin has GPE as a dependency. Can you send me a link to the preview please. On Wed, Oct 22, 2014 at 5:16 PM, Matic Petek maticpe...@gmail.com wrote: Thank you for that, but right know my main target is to move our projects to GWT 2.7 and migrate our developers to SDM. Regards, Matic On Tuesday, October 21, 2014 8:50:01 PM UTC+2, Brandon Donnelson wrote: Ah, thanks for sharing. I just wanted to double check. By the way if you're interested in the GPE preview, I've got that handy if you want to try it out. On Tuesday, October 21, 2014 10:00:54 AM UTC-7, Matic Petek wrote: Yes, it was my mistake when I upgrade from 2.6 to 2.7 snapshot. Not it is working. I just want to write it in forum if someone else would have the some problem... Thank you for help. Regards, Matic On Tuesday, October 21, 2014 6:41:11 PM UTC+2, Brandon Donnelson wrote: Manolo is correct, the superdevmode-launcher-legacy.jar is not needed with GWT 2.7. It can be used with GWT 2.5.x and 2.6.x. Did you add that to the classpath? Brandon On Tuesday, October 21, 2014 6:03:14 AM UTC-7, Manuel Carrasco Moñino wrote: You shouldn't put never that .jar in your classpath. GPE takes care of adding it to the launcher classpath when you run superdevmode and your gwt is not 2.7. On Tue, Oct 21, 2014 at 2:31 PM, Matic Petek matic...@gmail.com wrote: I have superdevmode-launcher-legacy.jar in classpath and it is not compatible with GWT 2.7. Regards, Matic On Friday, September 5, 2014 5:40:55 PM UTC+2, Brandon Donnelson wrote: I suspect the sdk isn't what you think it is if its not working. Can you check the classpath and see if it was updated? On Monday, September 1, 2014 6:09:18 AM UTC-7, Matic Petek wrote: Hi, I would like to test new compile per file option, but we run our project from Eclipse and we don't use Maven. So I have perform the following steps : 1) Download JAR files from https://oss.sonatype.org/ content/repositories/google-snapshots/com/google/gwt/ gwt-servlet.jar gwt-user.jar gwt-dev.jar gwt-codeserver.jar on 1.9.2014 date 2) Create new Google - Web Toolkit configuration 3) select this configuration on my Eclipse project. But when I run hosted mode, I get the error below. Any idea if I'm doing something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest version of GWT. Thank you. Regards, Matic Exception in thread main java.lang.NoSuchMethodError: com.google.gwt.dev.javac.CompilationStateBuilder.init(Lcom/ google/gwt/core/ext/TreeLogger;Ljava/io/File;)V at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943) at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498) at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097) at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863) at com.google.gwt.dev.DevMode.main(DevMode.java:379) -- 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+unsubscribe@ googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/google-web-toolkit-contributors/f10b78d5-b358- 4d18-abb5-3a9d49a2c429%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/f10b78d5-b358-4d18-abb5-3a9d49a2c429%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/87525c88-6a47-4b34-8312-8af86aa0c04d%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/87525c88-6a47-4b34-8312-8af86aa0c04d%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/CAEqaEViTNi8Mzh1KsUp6YobKp2MZTTcJBfPXoZVFxmQZ%2Bs__OA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 SDM incremental output too large
Post 2.7, we're going to look into pruning down the incremental output. However, this won't solve poor sourcemap implementations in other browsers. One option is to get source-map support improved directly in Eclipse/IntelliJ, so that the Javascript-based developer tools are not used, rather, the IDEs connect to the Browsers via remote debugging protocols, but the SourceMap/indexing/navigation is done by Eclipse/IntelliJ. On Wed, Oct 22, 2014 at 3:42 AM, Rene Hangstrup Møller rhmol...@gmail.com wrote: Our application is roughly the same size (3.5mb) and I have never been able to debug using source maps in firefox. It freezes when it has to load them. I have also tried remote javascript debugging with super devmode from IntelliJ. I can typically step over a couple of breakpoints and then it drops the connection. So I still use DevMode with Firefox 24 ESR when I have to debug. Works fine in chrome. Best regards Rene Den onsdag den 22. oktober 2014 11.52.40 UTC+2 skrev Jens: Hi, Our app produces permutations about 3.5mb in size when doing optimized production builds. It is roughly 150.000 fields across 12.000 types (according to the first SDM incremental compile output). I tried that app with several browsers (all Mac OS) to see how things work with SDM incremental compile: - Opening the native dev tools of Firefox 33 and switching to the debugger tab freezes Firefox for several (5+) minutes until it finally displays all source mapped java files. And thats for each page reload. Breakpoints work but since you can not see which source line is mapped you might need to guess a bit until you find a spot where the breakpoint actually works (or look it up on the code server). But because of the reload times debugging is literally unusable. Maybe it is possible to use FireFox remote debugging in IntelliJ. Haven't tried that yet. - Safari 7 also has quite some lag. The reason is that Safari Dev Tools store each XHR request done to fetch a source mapped file from code server. If you now want to search for a Java file in the browser the search lags quite a bit because it also filters all these 1000+ XHR requests. But thats a Safari issue one must accept for now. I also noticed that sometimes the CodeServer responds with 404 for all source mapped files that are generated by GWT generators, e.g. GET /sourcemaps/app/3427F4D36ECEACFA71B338AB1AE1396C_sourcemap.json sent source map for module 'app' in 269 ms GET /sourcemaps/app/gen/com/google/gwt/cell/client/TextInputCell_TemplateImpl.java Sent error page: unknown source file: gen/com/google/gwt/cell/client/TextInputCell_TemplateImpl.java When I open up the CodeServer web site at ip:9876/sourcemaps/app/ I can see an entry for gen/com/google/gwt/cell/client/ . Once I enter it I can see the TextInputCell_TemplateImpl.java however if I want to open it in the browser the CodeServer can not find it and reports an error. Thats something I haven't noticed in Chrome so far. Finally setting break points in the source mapped Java file does not seem to work at all in Safari 7. Breakpoints are accepted but never hit by the debugger. I tried several different code lines (all are marked as black lines on the code server sourcemap html output so they should have valid mappings). - In IE 11 it also takes quite some time until source mapped java files appear in the dev tools (similar to FireFox). Once they appear, file filtering is pretty slow but I can live with that. However if I want to set a breakpoint in any of my files then the breakpoint is actually placed in a GWT file called ModuleUtils.java. No idea why but that also makes debugging impossible. Trying to open the pure JS file does not work either. So in short, although incremental compilation is pretty cool all non Google Chrome browsers have issues with our app because 1.) the pure JS size produced by incremental compile is too large (Safari actually showed the total size of resources downloaded and it shows 75MB) and 2.) handling the source map does not work well and break points might be dead. For IE we can still use classic DevMode but for FireFox, Safari and mobile browsers debugging doesn't work well for large apps. -- J. -- You received this message because you are subscribed to the Google Groups GWT Contributors group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/69d8d8a2-367e-4339-92fe-708841d23e30%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
Re: [gwt-contrib] 2.7.0-beta1 deferredjs bypasses application cache
Just an update in case someone else runs into this issue installCode = true does not fix the problem, I'm back to adding std linker. On Wed, Oct 22, 2014 at 11:43 AM, Richard Wallis rdwal...@gmail.com wrote: Thanks, just checked and set-configuration-property name=installCode value=true / also fixes the problem, so I'll use that instead of adding the linker. On Wed, Oct 22, 2014 at 11:27 AM, Thomas Broyer t.bro...@gmail.com wrote: On Monday, October 20, 2014 10:49:13 PM UTC+2, Thomas Broyer wrote: IIRC, Brian changed the behavior of the xsiframe linker to match the direct-install linker, because most browsers would otherwise not display the source maps. There should be flag to turn it off and go back to the previous behavior. Here's the commit that changed xsiframe behavior: https://gwt.googlesource.com/gwt/+/ab905f749cb81e930c9240f3c67acbcf96a4a4e2 It actually depends (by default, if not overridden) whether you use -style PRETTY (or DETAILED) or not (i.e. OBF or OBFUSCATED) See https://code.google.com/p/google-web-toolkit/issues/detail?id=8578#c5 for the rationale. -- 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/ee970214-9fd0-46be-aa9a-17cb299d491b%40googlegroups.com https://groups.google.com/d/msgid/google-web-toolkit-contributors/ee970214-9fd0-46be-aa9a-17cb299d491b%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/CAEqaEViiYXhbnQ6F32mN52dPQyvOK66zhZDZogEgtviV%2BMU5Qg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 SDM incremental output too large
Good point. When I tried remote js debugging with sourcemaps from intellij I thought about the irony og the setup. You have the source in your IDE. Then you push the source and mappings to the compiled output into the browser, and then you remote control the debugger from the IDE. It would be awesome if I could just have the browser run the compiled and minimized code, and my IDE could do the mapping between original source and compiled output. -- 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/e718fd83-c3c7-49b5-8fe3-294622047266%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: GWT 2.7 SDM incremental output too large
We're planning to do some work (link time pruning) to reduce incremental output size some time before the end of the year. On Wed, Oct 22, 2014 at 9:33 AM, Rene Hangstrup Møller rhmol...@gmail.com wrote: Good point. When I tried remote js debugging with sourcemaps from intellij I thought about the irony og the setup. You have the source in your IDE. Then you push the source and mappings to the compiled output into the browser, and then you remote control the debugger from the IDE. It would be awesome if I could just have the browser run the compiled and minimized code, and my IDE could do the mapping between original source and compiled output. -- 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/e718fd83-c3c7-49b5-8fe3-294622047266%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/CAFw3gJ9u87g%3D6RNSEBPtazo3F0WUhWEiZnJ7ix7x%3DjG0jyw%3D6Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
