search

Sian-Lee-SA / honeycomb-menu

Honeycomb menu is a Home Assistant module (not a card) that can be applied to any lovelace card. When activated by the defined action on said card, the module will display a 'rounded' list of honeycomb buttons with an optional XY pad to make interfacing with lovelace more fluent
Other
203 stars 11 forks source link

Feature request/ ideas #51

Closed wernerhp closed 1 year ago

wernerhp commented 1 year ago

Thanks for this module. It's really great!

Here's a video to showcase how I used this and hopefully aid in explaining some ideas that I think would be really useful.

https://github.com/Sian-Lee-SA/honeycomb-menu/assets/2578772/fec57dd9-7577-46c3-b99f-f36bb40b5bea

  1. I added another honeycomb service call to a honeycomb button. This opens a new menu, but closes the first one even with autoclose false. Would be nice if only leaf nodes could be set to autoclose.
  2. It would be really cool if one could expand to more than 6 buttons, e.g. start a second row of clockwise buttons around the first and cascade out up to 12.
  3. 1 + 2 combined to expand the menu into different directions. i.e. dont dismiss the first menu, but when I build the second one I only add buttons in certain positions so I can infinite expand submenus - perhaps dimming the previous layer a slightly.
  4. It would be nice if one could specify the button label with and without a icon. Currently it shows the name of the entity. I would like to show an icon and state/attribute value for Temperature, Humidity and Pressure in the leaf node after hitting more-info.
Sian-Lee-SA commented 1 year ago
  1. Not sure what you mean by leaf nodes, but each button can be manually set with autoclose or using templates.
  2. 12 + 6 = 18 buttons which imo is too many for any average use. even using just 1 or 2 buttons extra still leaves an empty 10 hexagons. I find 6 fits my needs perfectly which can be expanded upon using sub menus. This also involves extra unnecessary calcualtions on position but also determining if it's one set of menus or 2 aswell as making sure the extra menu isn't clipped from the visible view etc.
  3. This design goes against the UX intended for this module, the menu is not designed to act like a dialog or a sub system of other menu items. It's primary focus is just quick toggles for touch screens.
  4. You can customise the button anyway you wish. Head over to Custom Button Card to see their options or just use a completely different card via - type. This will most likely involve adding extra styles to suit.

Having said that, feel free to fork and edit as you please to fit your needs. As stated in other threads, this menu is purely a self purpose made module which I made available to the public ue to requests from other sources when showing my Floorplan. I won't be added anything new to the module and is technically in a feature freeze state, but I will update from time to time to fix issues that may arrise.

wernerhp commented 1 year ago
  1. Leaf nodes - meaning the button that don't open another honeycomb-menu. The button that calls the service to open another honeycomb-menu would not be a leaf node. I did set autoclose to false on individual buttons and on the main config, but the initial menu always closes when the second one opens.
  2. I don't mean 6+12. I just mean, 6+6, i.e. 2 rows and only if more than 6 buttons exist. default 6, but allow adding more than 6 buttons that will then be added in a second row. Basically have all be show: false except when they are set to something.

Ok, thanks