node-red-dashboard icon indicating copy to clipboard operation
node-red-dashboard copied to clipboard

Nested lists/menu

Open mreis1986 opened this issue 1 year ago • 7 comments

Description

I would like to have a way to use recursive functions to create nested lists/menu

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

mreis1986 avatar Jan 26 '24 13:01 mreis1986

Do you have any examples of what you're after? Would you want this to be a widget?

joepavitt avatar Jan 26 '24 20:01 joepavitt

Collaborator

I would like to use this vue nested tree, but it's needed to do "npm install -S vue-tree-dnd@latest" and then use "import VueTreeDnd from 'vue-tree-dnd'" on node-red template node. P

https://www.npmjs.com/package/vue-tree-dnd

mreis1986 avatar Jan 31 '24 16:01 mreis1986

@joepavitt

mreis1986 avatar Feb 05 '24 10:02 mreis1986

Thanks for the additional detail, was away last week (and yesterday) on vacation, hence the delay in responding. I have hesitation in including this as a core widget to Dashboard 2.0 due to the additional dependencies that would come with it.

We therefore have two options:

  1. A standalone third-party widget - https://dashboard.flowfuse.com/contributing/widgets/third-party.html
    • This would be the best option, as it makes it easily accessible to others, handles the dependencies, etc.
  2. Work out a way to get the dependency available in the client-side javascript that VueJS runs. @Steve-Mcl any quick thoughts on how we could do this? I'd covered external dependencies in the documentation but this would be a Vue component, which consequently, VueJS would need to parse and render at runtime, so I'm not sure the example with BabylonJS applies here.

joepavitt avatar Feb 06 '24 11:02 joepavitt

@Steve-Mcl any thoughts about this ?

mreis1986 avatar Mar 04 '24 15:03 mreis1986

I think this is an ideal candidate for a 3rd part contrib node as @joepavitt states in option 1.

As for my thoughts on Option 2: This should definitely be a long term goal (to be able to support external vue components) but it is a lot harder achieve and not something I have time to look into right now. Of course if this issue ends up on my plate, i will look at implementation.

Also open to contributions from the community.

Steve-Mcl avatar Mar 04 '24 15:03 Steve-Mcl

I think this is an ideal candidate for a 3rd part contrib node as @joepavitt states in option 1.

As for my thoughts on Option 2: This should definitely be a long term goal (to be able to support external vue components) but it is a lot harder achieve and not something I have time to look into right now. Of course if this issue ends up on my plate, i will look at implementation.

Also open to contributions from the community.

Thanks! Will try my best

mreis1986 avatar Mar 04 '24 16:03 mreis1986