Community
Participate
Working Groups
Currently, explorer.createTree is the only API we are using to render all the model items in one shot. But for use cases that need longer time to build up the explorer model, we may want kind of incremental rendering mechanism to render during progress. Comparing any two folders is an example. I am rendering the compare result in a flat explorer model while the compare is still going. I have to call the .createTree function multiple times but every time it just renders everything in the model. It seems OK visually but I think we need a better API so that we can see the real incremental rendering.
moving out of 1.0, even if I did this I don't see us having time to adopt the changes.
moving milestone to 2.0 M1 for future triage.
Agree. The original idea was to not put anything in the DOM until it's ready to go, so that there isn't a lot of DOM manipulation/ripple going. But for complex trees, it takes too long, and we might want to add to the DOM in blocks...
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
It turns out that our find reference tooling feature needs this badly for search panel.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html