> I want to be able to have the same object do client-specific behaviour
> when on the client-side (UI etc.), and do some server-specific
> behaviour when on the server-side (database etc.). So I want the same
> object to hold both a Widget (unused/null on the server side) and a
> server-specific Java object (unused/null when on the client side).
>
> To achieve this, do I have to create some dummy GWT "emulation" for
> the unused/null server-specific object on the client side and can I do
> the same for the unused/null "Widget" on the server side? Or does it
> work straight out of the box when you put it in the "shared" package?
> If not, what's the best way of making this work?
>
> My reason is simplicity.
Pack as much as possible in the shared code, that is, to the extent
the emulated JRE admits of. Have helper classes in your server side
for database etc and in your client side for UI. This is close to
developing a client-server application in java swing. The emulated JRE
has nice java.util.Collection which is handy for domain modelling, UI
handling and persistence. I think this is not only a simple way of
developing but also maximally takes advantage of GWT.
J.Ganesan
www.DataStoreGwt.com
>I don't want to have to put their respective
> client and server behaviours away from the object.
--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment