|
|
|
|
|
|
|
|
Re: Group By for Tree grid [message #1372340 is a reply to message #1368580] |
Wed, 21 May 2014 15:56   |
Eclipse User |
|
|
|
I will be grateful to you if I can contribute this to the community. I will definitely post you the complete patch or if possible the demo application. My team is testing it in all possible ways, as soon as they say good to go, I will provide you the deliverables.
I also want you to know that I have also create a patch for my application called as NatTableEditSupport, it's soul propose is to provide any kind of editor to column with it's validator, filter editor, and filter category and is highly customisable and it's implementation is as simple as jface cell editor.
I have a point to make, if I consider my entire look on nattable I found it work awesome on the static data but fails on dynamic data not in terms of rows but on columns. In tree implementation I need to pass the children, we need to write a format basically content provider to fetch the parent which I feel is opposite and kill the partial lazy loading for ex when user expand the parent children loads, this will end up modifying the input list which need to pass it to the tree.
I feel nattable should be loosely integrate with glaze list. It has it's know problem I mean to say let's leave the implementation on to developers.
Thank you so much for giving me this privilege, I will post you soon with updates.
Suresh Chamuah
|
|
|
Re: Group By for Tree grid [message #1373553 is a reply to message #1372340] |
Thu, 22 May 2014 04:09  |
Eclipse User |
|
|
|
Quote:NatTableEditSupport, it's soul propose is to provide any kind of editor to column with it's validator, filter editor, and filter category
I can have a look at it if you like to contribute. It sounds like some wrapper to make it easier to configure editing.
Quote:if I consider my entire look on nattable I found it work awesome on the static data but fails on dynamic data not in terms of rows but on columns
I disagree with that. If you need dynamic columns you need to implement a IDataProvider that can handle that. While rows are typically items in a collection, columns are not as they are usually item properties. NatTable supports different row/column definitions, but you need to take care of that yourself. There is even an example for dynamic columns in the examples app.
Quote:I feel nattable should be loosely integrate with glaze list. It has it's know problem I mean to say let's leave the implementation on to developers.
If you don't like GlazedLists, don't use it. All features in NatTable can be implemented using different list implementations. The interfaces can all be found in the core package. That's why the GlazedLists support is in an extension package! So it is loosely coupled. We just provide some default implementations based on GlazedLists. The only exception to that is the groupby feature, which is currently only implemented using GlazedLists.
|
|
|
Powered by
FUDForum. Page generated in 1.40437 seconds