Tuesday, June 29, 2010

Re: PropertyChangeSupport best practice

On 29 juin, 21:31, mkh <mike.hana...@gmail.com> wrote:
> Just getting started with GWT, and it seems ProperyChangeSupport is a
> basic requirement in widgets. But GWT does not emulate these classes,
> and GWTx is required. The GWTx project suggests much of this belongs
> in GWT, but as of 2.0.3 it is not there.
> So this makes me wonder if there is an alternative approach that
> official GWT prefers for property change support, and if so, someone
> getting started would be better off avoiding depending on GWTx.
> Some pointers to best practice for property support would be
> appreciated. I am currently looking at the book "GWT in Practice", and
> this is obviously out of date at this point.

AFAICT, GWT 2.1 (or maybe it'll wait 2.2) will provide an
EditorSupport facility, working with UiBinder to automatically
generate the "binding" code.
The problem with PropertyChangeSupport is generally that it brings
more bloat than it really helps.

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