Model, TreeModel, BeanModel... etc.

[dali]

I'm currently evaluating GXT, I really like the ExtJS and GWT frameworks, however I'm really not convinced I want to use the data binding implementation of the com.extjs.gxt.ui.client.data API. In order to use all (or at least majority) of the GXT widgets does it require use of the data API? I would hope that this is an optional data binding add on feature and doesn't need to be used.

Any insight?

Thanks,
David

[gslender]

yes, but what don't you like about the model approach ?

[dali]

yes, but what don't you like about the model approach ?

It's not that I don't like the model approach, I can see great value with it's implementation and the potential to enable the binding of a widget with the model (I don't think this is implemented as of yet is it? It's scheduled for version 1.2?).

However, what I like about GWT in general is that its a toolkit and doesn't impose a framework. With the Model approach I don't see any easy way of using my Hibernate POJO's without converting them into Model instances, which basically is like creating DTO's for everything. Even the use of the BeanModel does not suit my purposes as it imposes restrictions to the bean structure (i.e. enforces use of Lists, cannot handle Map's etc.).

Ideally, the GXT widgets would just be extensions of the GWT widgets, or widget replacements. The data binding and Model requirements would be an added feature set that you could use if you wanted.

I've created my own GWT Generator which handles Hibernate POJO's and tracks modifications to the bean and its nested properties, it supports Map and List updates as well as PropertyChangeEvents. I'm looking into having it implement the ModelData interface, however I don't have enough understanding of its requirements and might not have enough time to spend on attempting the integration.

Thanks.