As of now, the ColorizerPaletteIO visualization of the palette items used the item's paletteItemId in the interface, which is not really nice nor does it provide relevant information for the user.
Having a semantic name for the color would be the desired option, but this does require quite a lot of internal logic:
each item in the palette have a dedicated form for its label with an internal logic to update that label
for styling it would be great if there was a button to activate the form / input and keep it as plain text until then
clicking the activate button would make the form input writable, hide the button and replace it with a save button
clicking that save button would update the palette item in ColorizerPalette (and consequently in the database) and deactivate the form again, showing the activate button again
As of now, the
ColorizerPaletteIOvisualization of the palette items used the item'spaletteItemIdin the interface, which is not really nice nor does it provide relevant information for the user.Having a semantic name for the color would be the desired option, but this does require quite a lot of internal logic:
form/inputand keep it as plain text until theninputwritable, hide the button and replace it with a save buttonColorizerPalette(and consequently in the database) and deactivate the form again, showing the activate button again