SmartGWT for existing application

I’m currently evaluating the use of SmartGWT because the widgets really do look stunning and the promised features including the data integration sound very appealing to me.

The problem is that I can’t start from scratch with that application I had to take over from another team.
It’s built with pure GWT only and some custom widgets to control the HTML code generated. The server is accessed through one giant service facade that extends GWT RemoteService. The facade delegates to business services which in turn invoke the DAOs which represent the persistence layer (or its abstraction).

A few questions/assumptions:

[Mix widgets]
It’s not recommended/feasible to mix an existing GUI with some SmartGWT widgets as the style sheets (the existing and the SmartGWT skin) would collide?
I tried a SmartGWT “Hello World” dialog (SC.say()) in our GUI and the conflicting CSS makes it look awful. We could try to work around it, but to me this looks like a dead-end.

[New GUI, existing server part]
If we were to re-implement the GUI and use SmartGWT components (incl. its skins) only, how troublesome would it be the feed the widgets with data from the existing RPC-based service facade? Is there a DataSource abstraction that could leverage this approach or is it a no-go, too?

[Custom skin]
The three existing skins look impressive but neither of them really fit the color scheme of what we have in mind. The upcoming gray skin is a lot closer, though. How much work is involved in creating a new skin from scratch? Of course, we could try to tinker with one of the existing CSSs but 1300 images per skin is a scary figure…

Your feedback is most welcome.
Marcel

The SmartClient skinning system will let you use different style names for any colliding styles. However as mentioned elsewhere we would recommend not intermixing components any more than you have to.

As far as reusing existing GWT-RPC services, this thread shows a good approach for now and more sophisticated support is coming soon.

Thanks, that’s enough to make me stop considering this a valid approach.

Thanks for the link. I’ll go over that example. Could you maybe elaborate on “more sophisticated support is coming soon” a little bit. How soon? In what areas are being worked on for that support.

I would also like to see an answer to this question as I will need to use this feature.

Support that will allow you to call a GWT-RPC service for each of the CRUD operations a DataSource defines, and construct a DSResponse from the result, which you can then provide to the DataSource to complete the request/response cycle.