On Saturday, December 25, 2010 12:54:51 AM UTC+1, Matthew Hill wrote:
>
> Hi.
>
> After reading
> this<http://code.google.com/webtoolkit/doc/latest/DevGuideUiEditors.html>
> page,
> I'm still unclear as to what editors are and what they are for.
>
>
> - What are they for?
>
>
Data binding (using flow
synchronization<http://martinfowler.com/eaaDev/FlowSynchronization.html>
)
>
> - Can you give me some example use-cases?
>
>
See the Expenses and DynaTableRf samples (DynaTableRf might be easier to
read and understand)
>
> - What advantages do they offer over editing without this framework?
>
>
It cuts down boilerplate by an order of magnitude!
On Saturday, December 25, 2010 11:45:43 PM UTC+1, Matthew Hill wrote:
>
> Hi; thanks for your answer!
>
> I'm beginning to understand it better now. A few more questions though...:
>
>
> - Is it best used with RequestFactory?
>
>
Not necessarily. It works equally well with POJOs ("simple beans"). The main
differences between RequestFactoryEditorDriver and SimpleBeanEditorDriver
are:
- setViolations (see
http://code.google.com/p/google-web-toolkit/issues/detail?id=5567)
- *kind of* observer
synchronization<http://martinfowler.com/eaaDev/MediatedSynchronization.html>through
EntityProxyChange events, though it appears to have
a bug
<http://code.google.com/p/google-web-toolkit/issues/detail?id=5819>(haven't
tested it yet myself)
>
> - What are the pros and cons?
>
> Cons? you might have to create your own Editor-s in some cases (or at the
very least Renderer-s and Parser-s), and there are a few bugs.
Pros: cuts down a lot of boilerplate / flow-synchronization code, that you
then don't have to unit-test yourself.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
