#Extremely clumsy Element Image edit interface

1 messages · Page 1 of 1 (latest)

crystal tangle
#

I'm trying to find a way to edit an Element Image in a more efficient way. In the current iteration, The old YAML edit is still more useful than the new graphical interface, because, as you can see in the screenshot that i posted here, we still have a discrepancy from the preview and the correct image that is shown when i finish to update.
In bigger picture as i made in this case, the user still need to open and close the tab to continuously update the page because we have no feedback in the edit.
It still more useful now to open the developer mode in firefox an edit directly the style css in a second page and to report the value inside the YAML file.

Possible solution:
Add a fullscreen edit page as we have implemented in the code version in the last update (this will help to speed up the edit process as a stop gap solution), or add the possibility to drag and drop the element inside the image (but this require a major code rework).
Thanks for the help to everyone who want to help, for me is a quite a significant improvement because I realize some very big map for our client and it will speed up my worload.

clear pike
#

it is the same thing but you create an image in inkscape and select where you want things.. then you write yaml in homeassistant

#

it takes some time to figure it out but then it goes quckly

crystal tangle
#

well, for my problem, this solution still not resolve it. our client usually give us a jpg or a pdf files, so if. ihave to manually edit every file to swg it's not viable.
What i need is a graphic interface to see directly what i was doing in real time or something similar, but I think coding something like that is not easy, so for now i stick with the old system