Hi Huy, I am currently working on a related feature for tables a DataProvider which will load the data on demand. Hopefully we can use this to resolve these FormTable usability issues.
regards Malcolm Edgar On Thu, Mar 4, 2010 at 3:58 PM, <[email protected]> wrote: > Hi All, > > What do you guys think of this little change to FormTable ? > > 1. In FormTable.setRowList call setRenderSubmittedValues(false) ? > 2. In FormTable.onProcess (i.e a FormTable is submitted by a user) call > setRenderSubmittedValues(true). > > Reason for this is that it will make FormTable behave in a more unsurprising > manner when calling setRowList() after the FormTable is processed. > I can't see where you would call setRowList and want it to render the > submitted values except if the form was processed. > > My use case is as follows: > > 1. Select data from db > 2. setRowList on FormTable > 3. submit form > 4. update db > 5. select again from the db (because I'm using the db to order the data in a > complex way based on the form values entered) > 6. setRowList again on FormTable > > Without the above changes, I always have to call > setRenderSubmittedValues(false) if I call setRowList() after the FormTable > is processed. > > Thanks for listening. > > Huy > > >
