Plugin created widgetset compile launch configuration should generate readable javascript by default

[makoivis]

Reported by Henri Muurimaa on 2 Oct 2009 18:58 UTC It's commonplace to have to read console error messages when writing widgets, but the compiler creates obfuscated javascript by default. The plugin-created launch configuration should include the -style DETAILED compiler parameter to make the error messages readable.

[makoivis]

Comment by Joonas Lehtinen on 2 Oct 2009 19:56 UTC IMO this is not a good idea - GWT defaults are ok. Most people do not want to read/debug the resulting javascript and change the compilation parameters for creating a production widget sets.

[makoivis]

Comment by Henri Muurimaa on 3 Oct 2009 12:42 UTC I'm not saying that the precompiled default widgetset should come unoptimized, but when writing custom widgets one runs into these problems all the time.

What's the measured performance hit for running unoptimized/readable javascript?

[makoivis]

Comment by Artur Signell on 6 Oct 2009 06:09 UTC I do not think this is a good idea. The default widgetset compiled with DETAILED is 3.4MB, compared to 0.4MB with OBF. Difference is 850%. I do not think anybody will ever change the default so DETAILED will lead to people deploying enormous widgetsets and wondering why the application takes a long time to load. Using OOPHM or the normal hosted mode you hardly ever need to read the javascript files anyway and can find your errors in the java code, which is in my opinion a much better and faster way.

[makoivis]

Comment by Henri Muurimaa on 6 Oct 2009 08:06 UTC Ok.

People will run into the javascript errors in the future though, so there should be a documented way how to deal with them (use OOPHM etc.).

[makoivis]

Comment by Joonas Lehtinen on 7 Oct 2009 10:28 UTC OOPHM is currently documented in

• http://vaadin.com/book/-/page/gwt.development.html
• http://vaadin.com/wiki/-/wiki/Main/OOPHM%20Step%20by%20Step

Any proposals on what kind of documentation we could add?

[makoivis]

Comment by Henri Muurimaa on 10 Oct 2009 17:19 UTC Replying to Joonas Lehtinen:

Any proposals on what kind of documentation we could add?

I'd like some general FAQ-type info on what to do when writing client side stuff that does not work or seems to fail silently. First step is to find the error message in the firebug console; this can be nontrivial to figure out, at least for people with little prior GWT experience.

[makoivis]

Modified by Artur Signell on 12 May 2014 07:42 UTC