Quantify GWT Debug module overhead
Hi,
According to the literature adding the GWT Debug module to your project and add onEnsureDebugID to your widgets adds overhead[1]. Can someone be more specific on what this overhead is? Also why does GWT completely remove ids anyway? Does it have anything to do with experience of ASP.net[2]?
I am considering leaving the GWT Debug module in place for production. In any case I will profile my app to make my own measurements on what this 'overhead' means.
James
[2] http://codebetter.com/kylebaley/2011/05/05/tips-for-ui-tests-with-gwt-html-ids-or-how-to-buy-votes/
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/JL6uXsEX_noJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home