Correction: when I said that a browser needs to support sourcemaps to generate accurate stack traces, that wasn't entirely accurate. What a browser needs to support is the "stack" property of exception objects, which provides a JavaScript stack trace with both line and column numbers. It's the GWT compiler that uses a sourcemap to derive original Java line numbers and filenames from the browser-provided line and column numbers. This functionality is currently broken in GWT, however, and Chrome is currently the only browser that provides column numbers. And even if more browsers add column info in the future, it's almost certain that their stack trace formats will all be different, so we'll have to patch GWT every time a new browser adds the support. My proposed project will leave us in good shape to be able to do that easily.
On Wed, May 22, 2013 at 5:53 PM, Alex Epshteyn <alexander.epsht...@gmail.com > wrote: > Thanks for your comment. Let me respond to your points: > > 1) I've seen this point discussed before, and the standard > counter-argument is that the spirit of OSS is free as in "freedom," not > "beer." Lots of developers get paid to work on OSS projects. > > 2) This is actually one of the reasons I'm thinking about raising funds. > I am already on the verge of using my patch inside my own GWT-based app, > but if I get some funding I'd be able to justify taking the extra time to > make sure the patch will pass the review process. > > 3) I must point out that your third argument is not in the spirit of GWT, > which aims to support as many browsers as possible. > > As of today, you will not get good stack traces with GWT on any modern > browser, including WebKit. By "relevant information", I assume you mean > sourcemaps support. Well, Chrome is the only browser that currently > supports sourcemaps but GWT's existing support for generating stack traces > with that information is very buggy, and this is one of the things I'm > working on improving. I'm also not optimistic that sourcemaps will achieve > universal support any time soon, if ever. > > > > On Wed, May 22, 2013 at 4:38 PM, Jens <jens.nehlme...@gmail.com> wrote: > >> I dont think you will get paid for it, because: >> >> 1.) Its somewhat not in the spirit of open source software >> 2.) Your patch must go through review and there is no guarantee that it >> will be committed >> 3.) GWT will remove IE6/7 support soon and probably in 2014 also IE8 >> support. Also Opera moves to WebKit. That means that there is probably no >> need for StackTrace emulation anymore in the near future as modern browsers >> provide the relevant information. >> >> -- J. >> >> -- >> 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/hP8cQ7AdDUc/unsubscribe?hl=en >> . >> 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?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
