[gwt-contrib] Re: Official Gradle plugin
Ping. Would be great to get some feedback. Currently, the lack of a decision regarding a new build tool for GWT and thus the potential contribution of this plugin if Gradle will be chosen blocks pull requests. I am just guessing but I think Steffen might not be sure if CLA management is required for his project once he accepts pull requests while the possibility exists to contribute the whole project to GWT. -- 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/73e78f65-a985-48a3-b763-ddc3302bd54a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: How to get the full StackTrace when using SuperDevMode in GWT 2.7?
Yes, that's what I mean. If you use the latest trunk right now, you will see obfuscated method names in Safari. We need to improve that. You need to go back to 2.7 Final. On Tue, Dec 9, 2014 at 8:27 AM, Stephen Haberman wrote: > > > I use the latest trunk and also SDM with incremental compile. @Goktug > > could you please provide a sample project where obfuscation works > > which has the correct configuration? > > FWIW I'm using a snapshot of GWT master from ~last week, SDM, Chrome > 40.0.2214.28, and when I set a breakpoint in FooPresenter.java (which > does pull up via the Control-O shortcut), the call stack is: > > en_g$ > pn_g$ > qn_g$ > yJo_g$ > > > Oh right. > > So, Michael, in 2.7 release, SDM was outputting pretty names. However, > in master (e.g. post-2.7), after commit 676ca7532bd1387, the JS > function names are obfuscated again. > > However, per Goktug, the idea is that, in Chrome/FF/and Safari > soon-ish, the browser should use source maps to show the right names. > > I'm not entirely sure that's working for me in the Chrome debugger > right now, but it makes sense. (It says "Please wait a bit. source map > is being loaded!" but it's not loading...) > > Ah, okay, AFAICT it was because I had the debugger paused in a place > that was fired on page load, so the sourcemaps hadn't had a chance to > load yet, and the breakpoint was blocking that from happening... > > Nice. Now it basically works. I see in the call stack, on the right > side, the sourcemapped location of each function (e.g. Ur_g$ is > FooPresenter.java). > If you set -XmethodNameDisplayMode flag (e.g. -XmethodNameDisplayMode ONLY_METHOD_NAME) you should also see the nice function names. > > Chrome seems to lock up for a bit while loading the sourcemap file. But > looking pretty nice. > > Anyway, Michael, Gotkug is saying that if you have a browser like > Safari/Mobile Safari that isn't picking up the sourcemaps to show nicer > function names, you should revert to GWT 2.7 final. Or they may > possibly add a "still use pretty names" override if Safari doesn't get > around to showing the nicer, sourcemapped function names. > > - Stephen > > -- > 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/20141209102726.0ab0315f%40sh9 > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3PEAYuqbnfYdC%2BfPDrU0tkfRzwcrazqZ%3DmCuqpgdJ0%3Dg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [gwt-contrib] Re: How to get the full StackTrace when using SuperDevMode in GWT 2.7?
> I use the latest trunk and also SDM with incremental compile. @Goktug > could you please provide a sample project where obfuscation works > which has the correct configuration? FWIW I'm using a snapshot of GWT master from ~last week, SDM, Chrome 40.0.2214.28, and when I set a breakpoint in FooPresenter.java (which does pull up via the Control-O shortcut), the call stack is: en_g$ pn_g$ qn_g$ yJo_g$ Oh right. So, Michael, in 2.7 release, SDM was outputting pretty names. However, in master (e.g. post-2.7), after commit 676ca7532bd1387, the JS function names are obfuscated again. However, per Goktug, the idea is that, in Chrome/FF/and Safari soon-ish, the browser should use source maps to show the right names. I'm not entirely sure that's working for me in the Chrome debugger right now, but it makes sense. (It says "Please wait a bit. source map is being loaded!" but it's not loading...) Ah, okay, AFAICT it was because I had the debugger paused in a place that was fired on page load, so the sourcemaps hadn't had a chance to load yet, and the breakpoint was blocking that from happening... Nice. Now it basically works. I see in the call stack, on the right side, the sourcemapped location of each function (e.g. Ur_g$ is FooPresenter.java). Chrome seems to lock up for a bit while loading the sourcemap file. But looking pretty nice. Anyway, Michael, Gotkug is saying that if you have a browser like Safari/Mobile Safari that isn't picking up the sourcemaps to show nicer function names, you should revert to GWT 2.7 final. Or they may possibly add a "still use pretty names" override if Safari doesn't get around to showing the nicer, sourcemapped function names. - Stephen -- 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/20141209102726.0ab0315f%40sh9. For more options, visit https://groups.google.com/d/optout.
[gwt-contrib] Re: Why Table Layout in GWT?
Answered in https://groups.google.com/d/topic/google-web-toolkit/CO7-WtcYsEg Locking this thread now; please answer on the one linked above. On Tuesday, December 9, 2014 7:15:24 AM UTC+1, Mohammed wrote: > > Hi, > Why *table *layout is used in GWT?Why not *div *layout? > -- 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/369a738c-3b9a-44b4-b133-3353603ccd31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
