sjivan wrote:
hucmuc wrote:
I find it pretty surprising and concerning that it took SmartClient a number of years to realize that the skin or themes are not visually right. Whereas the extjs look felt right from the start.
The standard response from SmartClient has always been is to wait for the next theme and then it falls flat. Hope, you have influence in this area.
I've shown the SmartGWT/SmartClient showcase to the people at work and the reaction has not been positive. I didn't have this problem with gwt-ext.
I do like the SmartGWT library and the interface.
I agree that the current skins don't live up to the high standard of the rest of the library in terms of API's and functionality. The users have spoken loud and clear regarding the skins and the SmartClient folks are treating this as high priority. I'm giving my feedback as well. In the mean time please continue evaluating SmartGWT knowing that the SmartClient folks are committed to creating high quality skins, even if it requires a little further polishing after the initial release based on user feedback. The key takeaway for me is that they are listening and responding to user feedback very promptly.
Sanjiv
The other thing that is bugging me is the integration. It seems to me that there should be a GwtProxyDataSource or some way to integrate seamlessly into the existing widgets that uses MY framework. I try to avoid any proprietary integration because I don't want to be dependent on that. My decision was vindicated due to the extjs fiasco.
The stock answer from SmartClient is to use the EE if you want seamless integration etc. But I can't justify 1K per developer in costs. Ideally, I want to create a DataSource that basically points to a server side function and returns a generic object that can be used by the widget.
You are right. The API and architecture is better than extjs. I know I will figure this out just like I did with my seamless integration with gwt-ext widgets. Just need the time.
