It's a change that just missed the 1.0 cut off and was merged in a couple days later. So it's been sat there for 6 months and to be honest, I forgot that it hadn't already shipped. The entry in the change log was getting the sidebar etc caught up.
I am seeing that with this version it takes about twice as long to load the editor in the browser. With 1.0.6 it takes about two seconds, with the beta it takes about 4.5 seconds. That is running both node-red and the browser (Waterfox) on Ubuntu 19.10 on an i5. Switching between the versions shows a consistent difference.
Hi @Colin - can you give a sense of how large your workspace is? Rough number of tabs, nodes etc?
The introduction of the outliner does mean there is more work to do when loading up the editor initially - and there is probably still some room for optimisation there. This is also one of the reasons we introduced the progress bar on loading - is there a particular point on the progress bar where it pauses?
I have 17 tabs (several of which are disabled) and about 100 nodes I should think. It seems to take about about equal times loading nodes, loading flows and adding flows.
IMO, no big deal for the huge benefit of the new outliner. And the progress bar gives a nice feedback that work is being done instead of just blocking the UI.
The outliner in conjunction with groups will be a killer feature for these kind of projects we have to deal with. Especially that it reflects nested groups in the tree structure. A huge gain for a clean overview and flow structure.
Some additional ideas regarding the outliner:
a "collapse all" button for the tree
display the node type (especially if it should replace the "configuration node" sidebar)
automatically reflect the node selection of the workspace in the outline and vice versa; preferably to be toggled with a button, similar to the link with editor feature of the Eclipse IDE
All in all, a very impressive update. I am really looking forward to this next version! Thank you.
