Re: Overuse of "AssumedStale" Issue Tag

On Tuesday, May 28, 2013 10:10:31 AM UTC+2, Ed wrote:

For the latter two issues above, also note that our goal is to modularize GWT and externalize things 

How will this look like?

To my experience, currently it's very hard to  change/extend GWT core functionality. How will this change?

A few examples that popup: the classes Event, Element, HandlerManager (there are more) are very hard to change/extend because the methods/classes are final, or package protected or lack of interface usage.

Looking at the changes issues (AssumedStale) I don't get the impression that this will change soon as the issues about making classes like Event, Element, HandlerManager, etc... more flexible such that they can be extended, or all marked as "Not-Planned", "as-Designed", "AssumeStale"... 

Also a few issues about making more use of interfaces are "destroyed", which I think is needed to make GWT more "modular".

Please more insight?

Modular in the sense that gwt-user.jar will be split into smaller parts and you only include in your classpath the modules you need.

 

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.