support for the visual card editor

[Ulrar]

Hi,

I don't know what it would involve to support the card editor, but since this card only has one option hopefully not much.

Right now I use the built in horizontal / vertical stack card to build my card and subcards, then I edit the code to replace the type with this card instead, it'd be nice not to have to do that on every edit.

Thanks !

[kauelima]

+1 on this as I do the same thing, I call it a donnor card hahaha

Pasting the docs here so I can try later to contribute to this:

"Custom Cards | Home Assistant Developer Docs" https://developers.home-assistant.io/docs/frontend/custom-ui/custom-card/

[j-loewen]

Yes, please

[SergiuToporjinschi]

plus another one

[kauelima]

Spoiler after almost one year from my last comment: I wasn't able to do it hahaha My simple hacky designer brain was unable to go that far into understanding what needed to be done to make it work in the visual editor hahaha

[ildar170975]

hahaha do not rely on visual editor to almost any custom card; even some conditional cards have UI editors with errors, use yaml instead as a 100% working solution.

[kauelima]

hahaha do not rely on visual editor to almost any custom card; even some conditional cards have UI editors with errors, use yaml instead as a 100% working solution.

We know that yaml is the best solution with all features, but basic usage should be available on the visual editor, no reason why not. It's all about ease of use

[ildar170975]

I do understand but in current circumstances the UI editor (imho) will be one of the last things to be added. But surely we need to keep this particular issue open.

Due to a complexity of many cards (especially custom ones) maintaining UI editor is not an easy task. Also, some options may be conflicting to each other - and UI should perform corresponding checks etc.

[Ulrar]

A lot of cards don't implement all the options, in this specific case the only one really needed is mode since that's likely the only option used by the vast majority of users, the rest can stay as advanced yaml only IMHO.

TBH it's not about the ability to configure the card using the UI, it's about being able to use it for other cards. Right now because this card sits at the top of the tree it disables the UI for all the child cards, most of which probably do support it which is unfortunate and makes using this card very frustrating.

As stated there is an easy work around, using the built in stack cards to edit the child cards then swapping back to this custom one, but it gets annoying really fast. It'd be really great to have a basic UI editor, even if it exposes no options, just as a pass through to the child card's editors

[kauelima]

That's totally it, even the most basic functionality would already be awesome, but I just saw that this plugin seems to be abandoned since 2020, so we may never get it :( I'll look for alternatives

[mvanlijden]

@RomRider any way you could give this card some love? I know many people use it, but the lack of a UI editor for underlaying cards is hindering a good usability for a lot of us. The vertical-stack-in-card implemented a UI editor a while back for this goal, maybe some dev can take that code as inspiration? https://github.com/ofekashery/vertical-stack-in-card/pull/128