FlowFuse
Improved feedback of Node-RED editor status with integrates editor
As a Node-RED Developer, working through FlowFuse I want to have clear feedback on the status of the editor/instance So that I have a clear understanding on why I may not be able to edit on my instance directly
Conditions we need to consider for the Immersive Node-RED Experience include when an instance is in one of the following states:
- Suspended
- Error
- Crashed
- Starting
- Installing
These are currently covered by our status pill, and traditionally just disable the "Open Editor" button. Now though, the Editor will be available directly within FlowFuse, meaning that, if in one of these states, we need to consider some form of improved feedback as a lot of screen real estate will be "dead", where the editor will go once available.
Design Task: https://github.com/FlowFuse/flowfuse/issues/3659
### Tasks
- [ ] https://github.com/FlowFuse/flowfuse/issues/3659
Essentially, we need to fill out this red space when the editor is not available (for the different reasons details above)
but also, may want to (as per this screenshot) include the standard FlowFuse header when the Node-RED Editor (and header) is not available). May cause confusion with a switch out, but also, looks very strange without it
@Yndira-E not urgent - but want to put this on your radar for some ideas - would take inspiration from the new ident we have, with the edge glow? Want to create something that's SVG only, using Lottie Animations probably.
A "simpler" solution would be to have a placeholder Node-RED style grid in place, and somehow play with that as part of a "loading" state
@Yndira-E is there any plan in your schedule for this at all? Would like to have something in over the next couple of weeks
Hi @joepavitt yes, I have it planned for this week, but I'll probably won't be able to finish it until next week.
Hi @joepavitt yes, I have it planned for this week, but I'll probably won't be able to finish it until next week.
That's great Yndira - thanks, just helps with the planning of the dev work
@joepavitt , should I close this task and handle future animations in another task?
