Agreed! The difference in JS size will not make much difference. So its boils down to only 1 benefit of disabling debugId in production, ie. 'Unneeded Runtime overhead', which I think is not a big benefit at all, as the overhead is totally negligible.
So, looks like its OK to keep the debug ID enable in production. Regards Gourab. On Fri, Feb 26, 2016 at 10:15 PM, Jens <[email protected]> wrote: > > Yes "processing of 'ensureDebugId()'" I meant, runtime overhead. >> And why do you think it won't require extra 'Javascript' download, as if >> you want to set debugIds you need to inherit Debug module. >> > > I just did not mention it because I thought it was a logical consequence > that your JS output will be larger when you enable debug ids. > > Whenever you set a debugId in UiBinder this results in code calling > UiObject.setDebugId("...."). By default (not inheriting Debug.gwt.xml) this > method does nothing and thus the method call is removed by the GWT > compiler. When you inherit Debug.gwt.xml then all these method calls can > not be removed as the implementation now does some work, so your JS will be > larger. However with server side gzip compression the difference in > download size will be pretty small. > > -- J. > > -- > You received this message because you are subscribed to the Google Groups > "GWT Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
