> Could you elaborate a bit more on this statement and also how it > impacts the direction future enhancements for cell widgets in general.
I agree that is a good question. Even more pessimistically/cynically (so take it with a grain of salt), is whether modern browsers will eventually be faster (or fast enough) with per-row/-cell event listeners than CellTable's 1-listener with manual-dispatching approach. Maybe not with the stock widgets, but some sort of not-flyweight, but-still-lightweight mini-widgets. Granted, CellTable is great for the hear and now (IE/etc.), so excuse/ignore my musing, especially about something I only superficially understand. Nonetheless, per the breaking change proposal, I'm impressed with your dedication to API compatibility, and the cleverness of the hack to do so. Any custom CellTable stuff I've done so far as been on the cell side and not the guts of CellTable itself. In that regard, it sounds like Cell.render will still take a SafeHtmlBuilder? Given the perf results you mentioned, should/will Cells eventually use the ElementBuilder API as well? - Stephen -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
