Semi-Dynamically create pages aka "HMI feature"

[JeremyTheocharis]

Semi-Dynamically create pages aka "HMI feature"

[joepavitt]

@Steve-Mcl can link to his in-progress update on this. It's not something we can do at the moment as it requires core changes to how subflows work, but Steve is making great progress here.

[joepavitt]

The content of the webinar would be really interesting for us as a team, but I cant participate. Could you provide me with a recording or notes or something?

It'll be uploaded to our YouTube, and website after the session has finished.

[JeremyTheocharis]

• what is missing is there the multi-user view (that multiple users can interact with the dashboard)

[joepavitt]

what is missing is there the multi-user view (that multiple users can interact with the dashboard)

Could you expand on what you mean by this please?

[JeremyTheocharis]

what is missing is there the multi-user view (that multiple users can interact with the dashboard)

Could you expand on what you mean by this please?

I think you got it already with "requires core changes to how subflows work". a typical workaround is to have a single page, and then the user selects the machine in a dropdown. but if multiple users work with it, they overwrite each others "dropdown".

Do you have anything that comes near to what we are trying to achieve? Maybe with a little more copy and paste?

[joepavitt]

Do you have anything that comes near to what we are trying to achieve? Maybe with a little more copy and paste?

If you're using FlowFuse, we have the Shared Team Library which allows you to store flow .json and recall them across any of your instances, would give you the raw flow each time, rather than a nested SubFlow, but is definitely better than a lot of copy/paste?

but if multiple users work with it, they overwrite each others "dropdown".

With this though, you're also after Multi User Dashboards, which is another FlowFuse feature, and actually I'm doing a Webinar about it on Thursday this week.

Also did a short write-up about it here. You no longer have the "Centralized Store" of data that you have with Node-RED Dashboard, instead, everything is client-side only, and it's up to you to architect which pieces are persisted, in a database for example.

[joepavitt]

Also, just to link to the discussion thread where Steve has shown some early demos of the subflow workflow: node-red/designs#77

[JeremyTheocharis]

Thank you! The content of the webinar would be really interesting for us as a team, but I cant participate. Could you provide me with a recording or notes or something?