I wonder if you can elaborate a bit more on some of your points, or maybe point out where the flaw in my thinking is. I think that a HasDataEditor could be used correctly to achieve this, except for two points: HasDataEditor doesn't hold changes and flush them out when asked to, and bug 5981 <http://code.google.com/p/google-web-toolkit/issues/detail?id=5981>(which I've posted a possible fix for, but seems to not have gotten any attention).
A HasDataEditor subclass with a set of changes to make could deal with this - those changes could be queued up as in the CwCellSampler<http://gwt.google.com/samples/Showcase/Showcase.html#%21CwCellSampler>, and flushed when the HasDataEditor gets a call to flush(). As time permits I've been working on a tool to help with CellTable setup, mostly building of columns, and this could easily be extended to queue up changes for the editor. I've begun work on such a feature, but your suggestion that these may be incompatible gives me pause. Issue 5981 seems to be a simple typo preventing entityproxies from being correctly passed into LeafValueEditors (and possibly ValueAwareEditors). With that cleared up and a clean way to queue up list changes, I think binding a CellTable should become quite straightforward. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
