Oops! I didn't realize that it was a GXT specific construct. (I'm taking over code after a co-worker left for greener pastures, and I'm only just coming up to speed on GWT.)
Thanks for both the correction and the explanation, Josh! Apologies to the group for the misplaced posting. Josh Morris wrote: > This is more a GXT question than a GWT question. You might have more > luck posting on their forums. However, I did provide a quick overview > below. :) > > Most of the widgets in GXT use an implementation of ModelData for > their internal models. BeanModel is a generic implementation of the > ModelData interface provided by GXT. It wraps your objects in an > implementation of ModelData. However, it can be really annoying to use > compared to simply having your model object implement ModelData. There > are tools to automatically generate implementations for either of > these approaches. > > Using BeanModel: > http://www.extjs.com/blog/2008/07/14/preview-java-bean-support-with-ext-gwt/ > Using ModelData: http://code.google.com/p/unitt/wiki/modeldata > > > Josh > > > On Oct 19, 12:14 pm, "David C. Hicks" <[email protected]> wrote: > >> Can someone point me to an example that might shed some light on the >> proper use of BeanModel and/or ModelData? It almost seems like these >> two types are used interchangeably, but some API's prefer one or the >> other. I just haven't been able to find any good examples (ie. >> complete) that give me a clue how these should be properly used. >> >> I'm attempting to create some basic forms for adding/editing data. >> >> Thanks, >> Dave >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
