after investigating CompositeCell or directly extending AbstractCell,
it is my understanding that to create custom cell,
the only option at the moment is to embed HTML markup in the render method as below.
in other words, we cannot create a custom composite widget with UiBinder,
and add it to the cell.
am I correct on this ?
}
--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Also, we're working on a variation of UiBinder that can generate HTML strings and works with Cells. That should make it easier to template complex cells using HTML/XML.
Thanks,
John LaBanca
jlab...@google.com
On Wed, Feb 2, 2011 at 2:46 AM, zixzigma <zixz...@gmail.com> wrote:I realized what I was doing wrong.
I was trying to do everything in the custom cell.
I decided to handle things at CelLTable level, instead of cell level.
so I defined a SingleSelectionModel, and when the row is selected,
I change the flag within this selectionModel, which is related to the CellTable,
instead of capturing low level click event in the cell.
still I need to work on some of its details,
since there are some minor problems.
Thank you for your insights, it helped a lot.
--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
If can see the solution with the getElement() working, but it is at best
cumbersome and at worst a lot of hacking getting your custom widgets to work
properly.
The high performance argument can not really convince me, as it should not
throttle your application all to much if it has to manage one active edit widget.