Now when we got to the stage w v5 with all nice looking sidebars and layout possibilities, would it make sense to bring up a feature I really missed since long? Mentioned long time ago actually....
Having the possibility to re-arrange tabs also in the explorer. Just dragging and dropping them to their new position. For small systems with a few tabs this would not be so beneficial. If you on the other hand have a lot of tabs, like in the example below, it would be a more efficient way, you would not have to click on arrows at the top, just use the slider in the explorer to move up and down. Would love to see that!
As an alternative, I created myself a flow stack panel:
What it does is keep track of the flow tabs I've opened recently. It's stack since when a tab is opened for the first time, it's placed on the top of the stack.
In the animation, the overview of 50 flow tabs in the explorer becomes unwieldy, so the stack keeps track of the recently opened tabs. So before starting some task, I clear the stack and then begin working. Once I've identified all the tabs needed, I switch to the stack and toggle between the tabs I've viewed.
When I click on a flow in the stack, the previous flow tab is highlighted in blue - allowing me to toggle between the last two flows easily.
This is a workaround I came up with to manage my innumerable flows and one that I prefer since it also provides a focus on a subset of flows without having to hide flows in the browser.
So good, so handy, really like it, a perfect solution!
As you say, if have many tabs, it is currrently hard to re-arrange them. Especially if you then create a new one that by default is added at the end and would like it to appear as the first. The shift-click area in between existing tabs is very narrow, makes it sensitive and many times the new tab appears at the end anyway
Yes, it is like magic!! I now have npm installable versions for Node-RED v4 & v5. Both are working really good. Changes made are reflected correctly; either directly changing tab position in the NR editor or in the tab manager side bar works as expected.
Just need to understand how to publish on npm....maybe I should just upload zip's here with a readme to start?
Well, bear with me, my first attempt to use github this way, here the first version is anyway. I have tried it both with Node-RED v4 & v5, both works fine
Been away for a few days (long and painful story) but this looks good.
Now you just need the final step of publishing that to npmjs tagged with "node-red" then it can be picked up in the palette manager and the Flows site.
It may be because of the way you've set up your repo. You have a single repo for 2 packages. To publish to npm, you would need to do an npm publish --access public from each sub-folder. You will likely have to do npm login first in order to meet the publishing requirements of npm.
I can see it. But if I search for it, I cannot. I wonder if this is one of the new security features of npm - in fact, now I think about it, I think I did read about this - maybe I even posted about it. You will need to wait until it is searchable before it can be added to the Flows site and be useable in the Palette Manager.
In case it helps, the following are the release steps I use for UIBUILDER. Publishing is step 8.
Struggling a bit...think I managed. Now they at least can be found in search at npmjs.org. Added some files like LICENSE and README.md and some naming issues. Two versions, v4 for Node-RED version 4 and v5 for Node-RED version 5
(not sure but maybe v5 works for both NR 4 and NR 5)
EDIT: v5 also works for me if I install it for Node-RED 4 so maybe v4 could omitted
For some reason the Flows site hasn't picked up the current README that shows on npmjs but at least it is there. You could update your readme to show that it can be installed via the palette manager now.
I guess it is because several criterias like naming etc etc are not fulfilled. I'm not sure it should be in the palette either, I let management decide, this is just a suggestion for a useful tab organizer. To be used or not