I did a model level sort, it works fine except when adding dynamically an item that should occupy the first position, the tree is no longer coherent!

When you said : “Using a TreeViewer in VIRTUAL-Mode with an ordinary content provider should create the TreeItems only when shown” does it mean all TreeItems are created lazily or only “Children” items ?

In fact I forgot to mention in my post than my TreeViewer mainly contains “Root elements” (only ~1% of the 60 000 entries have a parent).
So what I mean by “Performances Problems” is : Root elements are all created at once even if they are not visible.

The snippet 02 in the JFace’s snippets can be used to reproduce this …

In fact I just had a quick look into TreeViewer class and the following lines made me think that VIRTUAL style must be used with Lazy content providers:

treeControl.addListener(SWT.SetData, new Listener() {
public void handleEvent(Event event) {
if (contentProviderIsLazy) {
TreeItem item = (TreeItem) event.item;
…..
}
}
});

If my viewer doesn’t have a LazyContentProvider the SWT.SetData listener isn’t used … Am I right or did I miss something ?

I will keep an eye on the bug #157228.

Xavier, i will get a try concerning sorting and filtering at model level, and of course let you know ;o)

50 000 rows is not so big.
If you really want sorting and filtering, perhaps you can do that at model level (ContentProvider level) instead of at UI level ?

XR

The debug framework has its own asynchronous viewer framework with some filtering capability (no sorting). There has been ongoing discussions about making the API available outside of debug, possibly combing work done by JFace.

Our experience in RSSOwl2 has also been that the creation of UI elements is the bottleneck.

“Someone told me on the Eclipse Platform newsgroup that the request to support SWT.VIRTUAL style and sorting and filtering for TreeViewer is already in the “pipe””

That’s interesting. We would benefit from that too.

Ismael