Thank you Sowdri,

Looking at the issue opened and the notes associated with it. It might
not solve the things that I want to do entirely. Having the
EditTextCell workable seems to be part of the solution. Another part
would require gutting the CellTable to work with the editor driver
correctly, since the driver is stateful and meant to be used to edit a
single entityProxy at a time. Which means it probably can't layout all
the rows using flyweight pattern where a column from different rows
have the same uiField name.... which is not possible.

I think it can be done if I layed out the column once using uiField
for use with editor framework, let the CellTable layout the table as
usual. And on initialization, hide those uifields and put in listener
to listen for row selection so when it change, the listener will
reinitialize the driver with the selected entityProxy, Listener/
Updater will need to be added as well to listen for user modification
so it can copy the changes to the hidden uiFields and eventually flush
the driver and fires the persist request on a requestContext.

I am just thinking out loud how I might do it if I am to really do it.
The GWT team, having more intimate knowledge on the cell widgets and
CellTable might do it differently though. But as it stands now, its
too much work for me at the moment. I will update this thread if I
eventually get around doing it. :>

Thanks,
Joseph

-- 
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.

Reply via email to