>
> I visibly don't need to rewrite the UiBinderGenerator, there's space left
> for non generating a field in com.google.gwt.uibinder.rebind.FieldWriter :
> it's specified in the javadoc
>
> The weired thing is that I don't understand from the comment *(In the
> rare case that** you need a field not to be initialized, initialize it to
> "null".)*
>
> what they want me to initialize to null: it's clearly visible in the
> implementation
> *com.google.gwt.uibinder.rebind.AbstractFieldWriter.write(IndentedWriter)*
> that if initializer is null, the code generation defalts to GWT.create
>
The code always wants a field initializer. If you don't specify one then
GWT.create() will be used to initialize a field. In some cases GWT.create()
won't work because you don't have or don't want to use the default
constructor, so you can define your own field initializer. Do a reference
search on setInitializer to see who is doing so.
The JavaDoc now says if you want to initialize a field to null, you must
define an initializer and that initializer should init that field to null
(e.g. setInitializer("null"))
-- J.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
