Support multiple elements of the same type on a single node about pyaiot

[aabadie]

Your idea sounds interesting but I'm wondering how it can work with the actual state of the vuejs application.

Each resource (endpoint) is linked to only one specific widget via a global data model in the web interface. If we want to have the same widget type for different endpoints in the same node, the vuejs data model and the view will have to be updated. I see this workflow:

• when receiving an update message, split the endpoint based on _ (as you suggested) and get a data type (led, temperature, etc) and a data name/id (could be numbers or strings)
• then instead of storing the data value directly in the model (see this line, we could use a more complex structure containing the type (led, temperature) and the value.
• on the view, wrap the whole body container in a HTML element with a v-for loop attribute, (around here).

It's not very nice, but it should work.

Maybe @bformet has good advices for this.

[bergzand]

I was afraid it would be somewhat more complicated than simply splitting and iterating. Thats why I opened an issue for this :)
Thanks for the pointers, I'm going to play around a bit, see if I can get something working.

[aabadie]

I'm going to play around a bit, see if I can get something working.

Keep us posted of any progress or problem.

By the way, there's also a need for a major refactoring of the dashboard html page: it would be great to take profit of vuejs components mecanism and webpack for generating smaller js code (among other things for the developper).

[bformet]

Interesting feature and the proposed workflow looks good to me, can't see why it wouldn't work.

[astralien3000]

Maybe it's not the main topic here, but I would rather do:

/outside/temp
/inside/temp

than:

/temp_inside
/temp_outside

At least it's what the URLs are for, in my opinion.

[aabadie]

Maybe it's not the main topic here, but I would rather do

+1 for the sub-url but then I would use them the other way around:

/temperature/outside
/temperature/inside

It should be easier for parsing them on the application side.

What do you think ?

[bergzand]

I'll make sure to build a separate function for the path/identifier parsing, should be easy to adapt to different use cases if necessary :)