Hi Ray, I can't answer you fully right now because I'm supposed to be leaving, but I'll think about your suggestion and get back to you. As it is, BoundFieldImpl constructs its editor lazily so perhaps a BoundField could be given an editor rather than constructing one itself.
Also, regarding the problem of binding fields to arbitrary widgets, my existing API works with Editor<T>s and Viewer<T>s. Both interfaces define a Widget asWidget() that is expected to return this. In other words, it's sort of assumed that implementations of Editor and Viewer are also subclasses of Widget. Perhaps we don't need to worry about arbitrary widgets because of that. If you want to look at my code, take a peek at HasTextEditor<T, W> in ca.petersens.gwt.databinding.client.ui. There could be more editors like it to support certain subtypes of Widget. Ian --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
