Feat dynamic buttons

[justparking]

Covers issue /issues/252.

@mcartmel - please review naming, etc.

@scroix - do you have any opinion on the naming given it's based on the <dynamicselect> element; <dynamicselectbuttons> has been chosen for now.

I was thinking maybe just <dynamicbuttons> or <dynamicbuttongroup>?

[scroix]

I tried having a go documenting the types back in the Mk1 recipe.
https://github.com/museumsvictoria/nodel-recipes/tree/master/Frontend/Mk1
(There are some screenshots there as well)

Back then, the names were:

• DynamicSelect
• Select
• PartialSwitch
• Switch
• Pill
• Range
• Button

I'd happily support anything which remained sensibly consistent. Sticking "Dynamic" at the front of an otherwise static widget-type seems reasonable to me.

As for the suffix. It looks like /issues/252 is most similar to Button from Mk1. So, I would say, DynamicButton, not unlike Select -> DynamicSelect.

edit* DynamicButtonGroup is even better.

Here is a static ButtonGroup.

<buttongroup>
<button action='PresetChromecast' class='btn-default'>Chromecast</button>
<button action='PresetTV' class='btn-default'>TV</button>
<button action='PresetButler' class='btn-default'>Signage</button>
<button action='PresetSpare1' class='btn-default'>HDMI 1<badge event="Status2"/></button>
<button action='PresetSpare2' class='btn-default'>HDMI 2<badge event="Status2"/></button>
</buttongroup>

[mcartmel]

Late to the party here I know, sorry.

The other option is to add a type attribute, e.g. <dynamicselect type="buttons"/>. It's a convention already since we have <buttongroup type="vertical"/>.

[justparking]

Hey @morimoriysmoon,

Yeah, I've been thinking that I'm not comfortable with the name<dynamicselectbuttons> ❌.

<dynamicbuttongroup>✅ better indicates it's a dynamic form of a button group.

In this UI framework the select refers to the appearance of a selection box which is not relevant here.

dynamic is the key concept we're adding here.

This is all wishy-washy but <dynamicbuttongroup> does seems the clearest to me.

Can you please update the code accordingly and let's finally put this to bed.