Community
Participate
Working Groups
The TableViewer framework should support the new capabilities of the SWT Table widget: the VIRTUAL style, per-cell foreground and background color and font. As it is now, users have to choose between the viewer framework and the highly desirable table features.
We likely do not have time to do this in the 3.0 timeframe
Is there any chance for guidance on how the API will look? We're starting a project where the central component is a TableTree, and would like to use the Viewer framework! We could make our own modifications, but it would be nice to have what we do match up with the ultimate release at least give or take some refactoring..
Kim has looked into this and might have some suggestions
I'd wager we'd create ITableColorProvider and ITableFontProvider, which would behave similarly to ITableLabelProvider. In the table viewer implementation we'd check to see if your ITableColorProvider was also an instance of these two and alter the TableItem properties accordingly.
I see. And how about the VIRTUAL table style? Wouldn't taking advantage of this imply a change to the content provider interface?
I'm afraid I'm not well aquainted enough with VIRTUAL to make the call there... bounce back to Tod?
Neither am I. Either way this is a large amount of work that we likely will not get to until 3.1
Does SWT.VIRTUAL make much sense in terms of a table with sorting applied by the TableViewer? In order to perform the sorting, the table viewer is going to have to roll through all the items, which defeats the purpose of SWT.VIRTUAL. Of course, a table viwer could start its life without sorting, playing nice with SWT.VIRTUAL. If sorting is then applied to the TableViewer, the result might be quite expensive time-wise. Something tells me that the sorting on a massive table may be best done on a seperate thread than the UI. I can see how this would get complicated. Filtering would be nice to have with SWT.VIRTUAL, and that looks easier. Just as an aside -- I feel very strongly that Eclipse would be well served by resources being put behind completing a world-class Table, Tree, and TableTree implementation. Certainly most business RCP apps need these particular widgets to be second-to-none in terms of power and flexibility, and this is one area where Swing (especially with 3rd party controls) has SWT beat at the moment. I realize some of this enhancement has been done in 3.0, but it feels to me like there is a long way to go and this isn't a particularly high priority. That concerns me.
*** Bug 58655 has been marked as a duplicate of this bug. ***
Reopening now that 3.0 has shipped
Can you give an example of "per-cell foreground and background color and font" The interface IColorProvider requires the implementation of the methods public Color getForeground(Object arg0) and public Color getBackground(Object arg0) which don't specify the column index. So how can you do this?
We have released the ITableColorProvider into the 3.1. stream to handle this sort of thing.
Is this the same as bug 72358?
Thanks Ed - now it is as we have addressed the other features. I am going to close this as all except SWT.VIRTUAL support is done - please feel free to add yourself if you interested to Bug 72358.
Verified the support in 20040921
