There are several competing (or complemental) new/experimental (or deprecated) classes around, which deal with rendering Widgets in alternative (often lazy) ways in GWT:
- GXT2's lazy Component<http://grepcode.com/file/repo1.maven.org/maven2/com.extjs/gxt/2.2.0/com/extjs/gxt/ui/client/widget/Component.java> (which has been deprecated in GXT3) - LazyPanel<http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/LazyPanel.html> - PotentialElement<http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/PotentialElement.html> ["experimental"] - IsRenderable<http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/IsRenderable.html> ["very experimental"] and RenderablePanel<http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/RenderablePanel.html> ["experimental"] Seeing how GXT2 had problems with their lazy rendering, what can we expect from these concepts? Looking into trunk, IsRenderable seems to evolve (using a new RenderableStamper class), so there's probably something in the pipeline... I know, that this is not a concrete question - I'm just curious if someone has interesting information about this subject? -- 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/-/UCn2Y043zFQJ. 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.
