|
|
| Re: The future of table and tree [message #127316 is a reply to message #126781] |
Mon, 06 April 2009 10:54   |
 Rüdiger Herrmann
Messages: 581
Registered: July 2009 |
Senior Member |
|
|
Hi Austin,
thanks for your interest in helping with the Tree. Yes it was
discussed before to merge the client-side parts of Tree and Table.
And certainly, this is the way to go on the long run.
The current Tree implementation is very limited and that won't
change in 0.7.x. The 0.7.x tree is blocking most of the current bugs
filed against the Tree widget.
The 0.8 version seems to be a major rewrite and probably better
supported, but I still doubt that it will meet the requirements of
RAP with respect to aligning with SWT, support for virtual items and
'server-centricness', etc.
For grater improvements it would certainly be worth to wait for or
start working on the table/tree merger.
Does that answer your post?
Cheers,
Rüdiger
Austin Riddle wrote:
> Hello,
> I am finding myself working a lot on the RAP tree implementation
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=232406) and I keep
> wondering if the merging of tree and table on the RAP end is in the near
> or distant future. There is a lot of functionality that will be
> duplicated if/whenever tree catches up to table. I believe there has
> been a discussion on this point before, but I can't seem to find it in
> the newsgroups. I was about to implement the cell padding for trees but
> I see that there isn't a ThemeManager for tree as of yet. So could
> anyone give me a hint as to why tree is in the state that it is in?
> (e.g., Not enough time to implement; Big roadblocks; SWT implementation
> too limiting; Waiting for Qooxdoo 0.8 migration, etc.) I guess the real
> questions are: What is the plan for the tree implementation? and What
> are the reasons that I should or should not be working on tree?
>
> Thanks.
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03000 seconds
] 
Search
Help
Register
Login
Home
