In case of repeated buttons I think I would use a combination of a TableCellEditor and a TableCellRenderer with a button behind them, still only single instances serving many rows. There would only be a single event listener that would check selected row index. Would it make sense to have that in Wicket in the future? Might save a lot of memory.
If on the other hand this button would be only needed on specific cells, not the pure repeater scenario, then of course one would use simple button instances per cell as there would not be a significant memory saving. On Wed, 17 Feb 2010 13:37:01 -0800, you wrote: >On Wed, Feb 17, 2010 at 1:31 PM, <[email protected]> wrote: >> Swing uses a variety of TableCellRenderer on a per table instance >> basis. > >if you had a table cell that needed a button then you wouldnt use a >renderer.... [snip] > >-igor --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
