On Tuesday, July 15, 2014 10:54:04 AM UTC+2, Jens wrote:
>
> BTW, with Core, I mean literally com.google.gwt.core.Core (which includes 
>> the java.lang.emul as well) and we are not really dropping support; just 
>> changing the defaults when useragent is not available.
>> Currently IE8 was good enough to get the benefit I was looking for (i.e 
>> Object.create(null)) but I think we can simply bump up the minimum version 
>> to IE10 if there are other good benefits. I think it is fair to require 
>> UserAgent dependency for anything older.
>>
>
> And whats the general usefulness of such a change? Wouldn't any app 
> inherit UserAgent anyways because it gets inherited by basic things like 
> DOM.gwt.xml? I have a hard time imagining an "app" that gets compiled to JS 
> but only depends on Core and does not indirectly pull in UserAgent.
>

I believe Google builds applications that use Elemental and/or JsInterop, 
so they don't use c.g.g.dom.DOM or any other thing that inherits UserAgent.
Goktug also pointed out earlier in this thread "cross-compiled apps" where 
the UI is built with Closure Library. I suspect this might be the case of 
Google Drive (Spreadsheets) where GWT is only used to compile to JS those 
bits of Java that are shared with the server, Android app and iOS app 
(through J2ObjC); from what I understood, in Spreadsheets that would be the 
code necessary to parse and evaluate formulas. 

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/5983c844-563b-439d-9046-b122caee0605%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to