Gwt第三方组件、框架介绍

我發現GWT-EXT是使基於Ext-js，而EXT-GWT是基於GWT方式所實現，可是在EXT-GWT核心部份仍然用
自己自訂的核心，在EXT-GWT很多都用com.extjs.gxt.ui.client.core.Template實現組件，好像GWT
各種所廷伸專案項目所訂制的組件方式都不一樣，還有發現寫一個組件必須用比較多的代碼，即使
初步了解GWT，可是在深入了解的階段，好像比較難了解的。

一、能不能提供學習的流程，比如先學GWT-EXT再學其它框架諸如此類方式。

二、還有現在基於GWT的架構組件那麼多，你在開發時還會自己寫組件嗎？

謝謝。

如果对组件的美工要求不高的话，我还是喜欢自己开发组件的 

stone,用过smartgwt没有，觉得这个怎么样

So what's so smart about SmartGWT? Let me try to explain. SmartGWT is not just another Widget library. While most Ajax frameworks focus primarily on presentation and displaying mostly read-only data, either local or via XML / JSON, SmartClient was built with server side integration in mind. Most enterprise applications are not just about about data presentation, but about being able to propagate data changes made by the user to the backend. So while its tempting to use library X that has a cool tree widget, it's not until you actually try to use it your application that you encounter the real world hard problems. For example, how do you take data from your business objects on the server to not only display in a tree widget, but also be able to update your data model when, say, the user reorders the tree nodes or make edits / deletes in the UI. How do you display hierarchical data where nodes may have hundreds of children? And so on..