EditorComposite, it's not clear if you make your own when, or if, you should add sub-editor values to the collection that backs the EditorComposite. This burned us big time. driver.getPath() needs to be exposed somehow, I understand it isn't exposed here since entities are not mentioned
Should explicitly state editors can be read-only, would be worthwhile I think. Not everyone is going to assume that editors can be used for "details". The document uses Label but why not make it a bullet point? I also sent in a use case a while back, you might want to give it a look. It asks how you should do layout of editors when you don't have a 1:1 object hierarchy to match the editors. On Mon, Oct 11, 2010 at 2:54 PM, BobV <[email protected]> wrote: > http://code.google.com/p/google-web-toolkit/wiki/Editors > > What's missing? What's unclear? If you have been using the Editor > framework, what gotchas have you run into? > > -- > Bob Vawter > Google Web Toolkit Team > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
