Thanks for looking into how to improve Java stack traces. I agree that we could do a better job. However, there are some problems with your approach:
First of all, we can't guarantee that we will accept this change. That doesn't seem very fair to whoever might be donating money. I would like to make sure we come up with a solution taking the best features of everyone's ideas, while remaining as simple as possible. See the discussion about GWT.create() improvements for an example. So the final result will likely be modified and include ideas from multiple contributors, though course the person who volunteers to do most of the work often has the largest influence. And simple patches aren't a solo effort because someone has to review them and try them out. With a project as complex and widely used as GWT, the drawbacks to a change may be unexpected. It's unfortunate, but we often find that after committing a change to Google's codebase, we discover problems that nobody thought of in review and we not caught by GWT's own tests. It's much easier to test a change if it's broken up into smaller patches. So if possible it's best to split up a larger feature into smaller patches and consider each of them on their merits. For example, if some things are just bug fixes, we should review and commit them separately. This is often a good way to get started in the community - before trying something large, fix simpler bugs. This gives us a chance to get to know your work through smaller and less risky changes, and you'll likely learn things along the way. Resist the urge to add more features since that makes a change riskier and harder to get agreement on. - Brian On Mon, Aug 19, 2013 at 1:06 PM, Alex Epshteyn <alexander.epsht...@gmail.com > wrote: > Hello folks, > > I just wanted to remind everyone that the last day to fund this project is > this Friday, August 23. > > I've been using this framework in production in my app now for 2 months, > and it works great. Have logged 70,000 perfect stack traces so far! > Already fixed 3 major bugs in my GWT-based UI code that I would NEVER > found otherwise. > > Let's get this capability into GWT by the end of the year. Please donate! > > Thanks, > Alex > > > > On Wednesday, July 17, 2013 4:56:40 PM UTC-4, Alex Epshteyn wrote: >> >> Dear fellow GWT users, >> >> I would like to announce that I have finally solved what I always thought >> to be GWT's greatest weakness: its lack of debugging information for >> client-side exceptions in production. >> >> With my patch, your deployed app will be able to report stack traces like >> this: >> >> com.google.gwt.core.client.**JavaScriptException: (TypeError) : a is null >> com.google.gwt.dom.client.**DOMImplMozilla.$**getBodyOffsetLeft(** >> DOMImplMozilla.java:145) >> com.google.gwt.user.client.ui.**PopupPanel.$setPopupPosition(** >> Document.java:1287) >> com.google.gwt.user.client.ui.**PopupPanel.setPopupPosition(** >> PopupPanel.java:884) >> com.google.gwt.user.client.ui.**PopupPanel.PopupPanel(** >> PopupPanel.java:453) >> com.typeracer.commons.client.**widgets.EnhancedPopup.** >> EnhancedPopup(EnhancedPopup.**java:32) >> com.typeracer.commons.client.**widgets.PopupWithIcon.**PopupWithIcon(** >> PopupWithFocusableTextBox.**java:28) >> com.typeracer.main.client.**controller.**TyperacerUncaughtExceptionHand** >> ler$1.execute(**TyperacerUncaughtExceptionHand**ler.java:55) >> com.google.gwt.core.client.**impl.SchedulerImpl.**runScheduledTasks(** >> SchedulerImpl.java:50) >> etc... :-) >> >> >> instead of the current state of affairs that looks like this: >> >> lineNumber: 3190 columnNumber: 15354: a is null; (TypeError) fileName: >> http://localhost:8088/**9C4DC2D905BEA407601C92C56B43E3**B8.cache.html<http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html> >> >> stack: @http://localhost:8088/**9C4DC2D905BEA407601C92C56B43E3** >> B8.cache.html:2422<http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2422> >> >> Rub@http://localhost:8088/**9C4DC2D905BEA407601C92C56B43E3** >> B8.cache.html:2423<http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2423> >> >> dSb@http://localhost:8088/**9C4DC2D905BEA407601C92C56B43E3** >> B8.cache.html:3190<http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:3190> >> >> tA@http://localhost:8088/**9C4DC2D905BEA407601C92C56B43E3** >> B8.cache.html:2810<http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2810> >> >> Xmb@http://localhost:8088/**9C4DC2D905BEA407601C92C56B43E3** >> B8.cache.html:2289<http://localhost:8088/9C4DC2D905BEA407601C92C56B43E3B8.cache.html:2289> >> >> etc... :-( >> >> >> I am asking the community to support me in finishing this effort and >> integrating my patch into GWT. Please take a look and what I've done, and >> consider making a donation: >> >> http://igg.me/at/gwt-stack-**traces/x/3494291<http://igg.me/at/gwt-stack-traces/x/3494291> >> >> I am an indie developer and I just need some funding to continue this >> work. I'm looking for both grassroots and corporate sponsorship for my >> quest of improving GWT's error reporting and debugging support. >> >> I've written a detailed white paper ( http://goo.gl/YGsrQ ) that >> describes how my solution works and why it is necessary. I welcome your >> feedback! >> >> Thanks! >> Alex >> > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > 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. > 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. For more options, visit https://groups.google.com/groups/opt_out.
