Re: [gwt-contrib] Re: Size of output is little large

2016-12-13 Thread Kirill Prazdnikov
That sounds very good, can you share the source ? The 3) and 4) is most interesting. Thanks Ray Cromwell: > > FYI: https://plus.google.com/+RayCromwell/posts/VK8URgZiLbS > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe f

Re: [gwt-contrib] Re: Size of output is little large

2016-12-13 Thread 'Ray Cromwell' via GWT Contributors
FYI: https://plus.google.com/+RayCromwell/posts/VK8URgZiLbS On Tue, Dec 13, 2016 at 10:23 AM, Colin Alworth wrote: > Class literals for any object which can be created need to exist for > getClass(), which is called by toString() at the very least - if the > compiler sees any Object.toString, it

[gwt-contrib] Re: Size of output is little large

2016-12-13 Thread Colin Alworth
Class literals for any object which can be created need to exist for getClass(), which is called by toString() at the very least - if the compiler sees any Object.toString, it must leave in all getClass methods - further reasoning about that might be tricky, and is a little out of my wheelhouse

[gwt-contrib] Re: Size of output is little large

2016-12-13 Thread Kirill Prazdnikov
Hello, Thanks for the explanation, did the job, and removed "$wnd.setTimeout($entry(assertCompileTimeUserAgent));" at the entry point. But document.compatMode.severity=IGNORE did not change anything in code generation, it still generates severity = ($clinit_DocumentModeAsserter$Severit

[gwt-contrib] Re: Size of output is little large

2016-12-12 Thread Colin Alworth
Without actually compiling the code (see my final paragraph...), you might not even need the safari permutation, but might get by with no UserAgent wiring at all. You could experiment with your inherits statements, and see if you can remove User, and only depend on com.google.gwt.core.Core from t