IsRenderable

[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

[Jens]

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.

[Thomas Broyer]

On Wednesday, March 7, 2012 9:15:30 AM UTC+1, Chris Price wrote:

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?

I don't think IsRenderable is abandoned. I'm not sure it's really about a Closure-Library-style decorate either, but from what I recall it could be used that way I guess.

AFAIK (and IIRC), IsRenderable is used in UiBinder to build a single "huge" HTML string from many widgets, to parse things in one go: i.e. ask IsRenderable widgets to render themselves and "inline" that string into the parent's HTMLPanel content, and then attach the IsRenderable widgets back to what they generated. This bypasses the "placeholder" elements that need to be generated and then replaced by the widgets (using HTMLPanel's addAndReplaceElement).

 

[Chris Price]

Thanks, yea I had a look over them this morning when Alan said he'd
kicked the sync script. My reading of that thread was that the sync
scripts have started replicating the stuff that's meant for the
external repo but there might be more that's being worked on, i.e. -

"The GWT team is currently focused on an arc of work that has not been
released to the external repo yet."

I can understand if that wasn't the implication, still interested in
why development on IsRenderable stopped though?

Cheers,

Chris

> --
> 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 google-we...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-tool...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.