Re: [SPAM] [nebula-dev] [CompositeTable] very bad scalability

[Tom Schindl <listom@xxxxxxxxxxxxxxx>]

André Dietisheim schrieb:
> Hi Tom
> 
> the progress on the bug you showed me is very promising! The 'problem'
> with the current celleditors is a pure productivity issue in my
> 'database-browser' rcp-client. Users complain that my users feel like
> there's one click too much, the one that's needed to activate the cell
> editor (and there's a supplementary one when the celleditor has a dialog).
> What they would like to have is something that feels like excel where you
> just start to edit when you're there.
> 
> Greets
> André
> 

At least the start of editing is possible when the bug is fixed because
we use an event to pass information to the cell-editors. So the first
keypress done by the user is passed to the editor which can do what ever
it thinks it has to do with it.

The current implementation provides the possibility to completely use
tables/trees without any mouse interaction. I even have patched for me
locally combo-editors to directly open the DropDown for users when they
click in and the same is possible for editors using Dialogs.

I'm also coming from Database Editing Applications (this is one of the
main areas in our company) and tried to address all usability issues our
customers had with SWT-Table/Tree and I think 3.3 will be a big boost
for those applications (Databinding + JFace-API are going to clean up
peoples code) not to talk about using Grid instead of Table because of
performance and missing features in Native Tables.

Even binding to CellEditors will maybe be possible see
https://bugs.eclipse.org/bugs/show_bug.cgi?id=144260.

Tom