that this does not happen, when the ListEditor manages a list of
LeafValueEditors, which is not the case in my application. I am a
little bit confused about the whole LeafValueEditor-concept. Should my
ListEditor always be composed of LeafValueEditors?
-of course not, i think it can be composed of ANY Editors
Can i put a more
complex editor for an entity with multiple editable properties in a
LeafValueEditor?
complex editor for an entity with multiple editable properties in a
LeafValueEditor?
yes you can
The documentation says "LeafValueEditor is used for non-object,
immutable, or any type that the Editor framework should not descend
into."
However the whole ListEditor seems to be designed around it,
especially HasDataEditor, so either ListEditor/HasDataEditor in its
current state is bugged and not very useful when it comes to complex,
mutable entities, or LeafValueEditor can be somehow wrapped around the
complexity. Could someone clarify this?
The documentation says "LeafValueEditor is used for non-object,
immutable, or any type that the Editor framework should not descend
into."
However the whole ListEditor seems to be designed around it,
especially HasDataEditor, so either ListEditor/HasDataEditor in its
current state is bugged and not very useful when it comes to complex,
mutable entities, or LeafValueEditor can be somehow wrapped around the
complexity. Could someone clarify this?
ListEditor is a kind of CompositeEditor, the doc said: the
-- ListEditor
type is a CompositeEditor<List<T>, T, E extends Editor<T>>
; that is, ListEditor will accept a List<T> and will edit some unknown number of T
's using the Editor type E
. 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