Re: [nebula-dev] draw2d/gc cells?

[André Dietisheim <dietisheim@xxxxxxxxx>]

Hi Dave

> 1) To not have any distinction between view/edit mode by default.  If
> you want that distinction, you can program it.  But you don't have to
> have it if you don't want it.  I've seen situations where if you click
> wrong, the focus goes to the table control behind the cell editor.  If
> you do away with cell editors, this no longer is an issue.

This capability unfortunately is very limited by the upper performance
limits in SWT and it's reached with 300-400 widgets. Limits are even
more prohibitive if the user wants to use compositetable in
simultaneousy present editorparts (or viewparts or whatever the
richclient uses). In consequence it is very useful for special editor
like your day-editor but not useable for classic table-widgets which
have to scale up to a large number of cells.
Investigating a bit in swing I saw that this limit must be prohibitive
in swing, too (and swing swing a lot better). They 'rubberstamp'
cell-controls to the table-canvas and do not use real controls for the
cells.

> 2) The event model allows you to implement a semantic where you
> validate and save data on row focus lost rather than on focus lost of
> each control.  This can be important in client-server situations to
> limit the amount of network traffic induced by interactive editing.
> 

this is a good point! Although it only counts in clients without local
buffer and a large number of concurrent clients.

My investigations in swing showed be an interesting approach for my aim
to have compositeTable scale up to those classic use cases:
We could have the real controls in the prototype row only and show
'screen-shots' of them in the rows of the compoitetable. The
rubberstamps of the real controls would have to be updated on refresh.
Editing the cells would have the real controls positioned above the
rubberstamps. The user experience should be perfect as I expect the user
not to notice the switch.

What's your opinion on this stuff?

Greetings
André

> 
> Regards,
> 
> Dave
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Mon, 19 Mar 2007 21:05:15 +0100
> From: Andr? Dietisheim <dietisheim@xxxxxxxxx>
> Subject: Re: [nebula-dev] [CompositeTable] draw2d/gc cells?
> To: Nebula Dev <nebula-dev@xxxxxxxxxxx>
> Message-ID: <1174334715.6267.21.camel@pmobilead>
> Content-Type: text/plain; charset=utf-8
> 
> Hi Dave
> 
> sorry for not being precise enugh in my last posting:
> I can't see any benefits in using composite table for the classic
> database-browser use cases (large table, takes approx half the
> screen).
> The only benefit I can spot is being able to mix real controls with
> 'draw2d/gc-cells' (controls in all cells does not scale sufficiently a
> table without switch label/celleditor does not scale enough in big
> tables). I wonder if you see any other benefits. I'd continue my
> efforts
> towards this direction if I see real gains.
> 
> Regards
> Andr�� 
> 
> On Mon, 2007-03-19 at 10:36 -0500, David J. Orme wrote:
> > Sure, you can do Draw2d or canvas-drawn cells.  Anything you can do
> in
> > a custom SWT control you can do in a CompositeTable cell.
> > 
> > 
> > Regards,
> > 
> > Dave Orme
> > ------------------------------
> > 
> > Message: 7
> > Date: Sat, 17 Mar 2007 12:59:39 +0100
> > From: Andr? Dietisheim <dietisheim@xxxxxxxxx>
> > Subject: Re: [nebula-dev] [CompositeTable] draw2d/gc cells?
> > To: Nebula Dev <nebula-dev@xxxxxxxxxxx>
> > Message-ID: <1174132779.4988.8.camel@pmobilead>
> > Content-Type: text/plain; charset=UTF-8
> > 
> > Hi Dave
> > 
> > I unfortunately had to drop my plan to use compositetable in my
> client
> > and try to find a solution to the bugs in the current virtual
> > tableviewer implementation. My customer change is 2 weeks ahead and
> I
> > am
> > thinking to the further improvements of the compositetable to push
> > performance limits further.
> > I started analyzing your dayeditor and I am thinking of drawing
> cells
> > not as controls but using gc/draw2d. Thinking of this stuff and
> > comparing to the latest jface-wrapper to the native table I think
> that
> > there's not much benefit to use compositetable as table replacement
> > for
> > the 'classic' cases. The only one I can detect is that it would be
> > possible to mix controls with 'gc-cells' (ex. classic label/image
> > cells
> > draw by gc/draw2d and checkbox-controls. What's you opinion? 
> > 
> > Regards
> > Andr������
> > 
> > 
> > !DSPAM:45fea116176512139619397! 
> > _______________________________________________
> > nebula-dev mailing list
> > nebula-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/nebula-dev
> > 
> > 
> > !DSPAM:45fea116176512139619397!
> 
> 
> 
> ------------------------------
> 
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev
> 
> 
> End of nebula-dev Digest, Vol 12, Issue 14
> ******************************************
> _______________________________________________
> nebula-dev mailing list
> nebula-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/nebula-dev