It is definitely intended that the Editors (data bound widgets) will not require the RequestFactory.
On Wed, Jul 21, 2010 at 6:38 AM, Thomas Broyer <[email protected]> wrote: > > > On 20 juil, 03:15, jarrod <[email protected]> wrote: > > I've spent some time looking through the new RequestFactory and > > ValueStore packages in GWT 2.1-M2. I am excited to see data binding > > and validation creeping into the core GWT code. However, I have a bit > > of a concern that the current implementation is too specific to JPA- > > based applications. > > > > Will it be possible to take advantage of the upcoming data-aware > > widgets without using RequestFactory? > > Which data-aware widgets are you thinking about? > > If it's the Cell-based widgets, then yes, absolutely; and without > ValueStore either. > > If you're talking about EditorSupport, then it looks to me there's no > dependency over RequestFactory either, only on DeltaValueStore, which > is an interface so you're not bound to a specific implementation. > AbstractRecordEditActivity has a dependency on RequestFactory, but > it's just a "helper base class"; you can use EditorSupport within any > view that implements RecordEditView, independently of > AbstractRecordEditActivity. > Last, but not least, AbstractRecordEditActivity has a dependency on > RequestFactory only to retrieve a ValueStore/DeltaValueStore and make > a syncRequest in the end in saveClicked; and again, RequestFactory is > "just an interface", so you could provide your own implementation and > you could then use AbstractRecordEditFactory if you liked. > Sure it'd be a bit of work, but it seems to me it's possible. > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
