Take a look at the new commits in the SVN. Nothing about IsRenderable ;-) Its more likely that GWT 2.5 will contain all or some of: - further JavaScript optimizations by using the closure compiler during GWT compilation - new code splitter algorithm to minimize the size of the initial and left over fragment - SourceMap support - Faster Dev mode - Java7 support (Java6 EOL is November 2012)
-- J. Am Mittwoch, 7. März 2012 09:15:30 UTC+1 schrieb Chris Price: > > Eric Clayberg recently mentioned that there was an arc of work > on-going by the GWT team that wasn't being released to the external > repo. I was wondering if this arc of work has anything to do with > IsRenderable? It looks like it was actively developed for about 3 > months 6 months ago but there hasn't been any activity since [1]. > > If I have the right idea about it, i.e. that It is a stepping stone > towards a Closure-Library style decorate pattern (i.e. server-render, > client-attach), it would seem on the surface to be a big performance > win. However, the comments about it being highly experimental put me > off trying it for client work. If there isn't any on-going development > with it, I'd be interested in knowing why it was abandoned, did it > turn out not to be a performance win, is it simply a lack of resources > or was there another reason? > > Cheers, > > Chris > > > [1] > http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/IsRenderable.java > > Am Mittwoch, 7. März 2012 09:15:30 UTC+1 schrieb Chris Price: > > Eric Clayberg recently mentioned that there was an arc of work > on-going by the GWT team that wasn't being released to the external > repo. I was wondering if this arc of work has anything to do with > IsRenderable? It looks like it was actively developed for about 3 > months 6 months ago but there hasn't been any activity since [1]. > > If I have the right idea about it, i.e. that It is a stepping stone > towards a Closure-Library style decorate pattern (i.e. server-render, > client-attach), it would seem on the surface to be a big performance > win. However, the comments about it being highly experimental put me > off trying it for client work. If there isn't any on-going development > with it, I'd be interested in knowing why it was abandoned, did it > turn out not to be a performance win, is it simply a lack of resources > or was there another reason? > > Cheers, > > Chris > > > [1] > http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/IsRenderable.java > > -- 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/-/z-SOCh3PN4EJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
