Skip to content
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.

feature request - total size of the layer would help prioritizing layers #42

Open
grooverdan opened this issue Feb 17, 2022 · 5 comments

Comments

@grooverdan
Copy link

Its a little hard to focus on 12 layers when its not immediately obvious which is the largest.

A total image size would be useful too.

@dcermak
Copy link
Owner

dcermak commented Feb 17, 2022

This certainly sounds like a good idea.

I am currently thinking about revamping the UI quite a bit, especially wrt how the image & layers are displayed.

Would you have an idea what else you'd like to see for each layer? And I am thinking about give the layers more descriptive names, but I honestly don't really have a great idea what to use else here.

@grooverdan
Copy link
Author

Layer hashes seem to correspond to History (if you exclude the those created with a "empty_layer": true). So the layer hash and the created_by from the history at least is enough to identify what needs to change back in the generation stage. Some UI technique to minimize the size of `created_by' in the menu (big generation lines are possible), but still display the full element when looking at the graph of the layer.

I'm not sure if it is there currently, but keeping layers in their ordering helps. I don't have a great preference for top down or bottom up.

@dcermak
Copy link
Owner

dcermak commented Mar 18, 2022

Hey @grooverdan, sorry for the long radio silence. What do you think of the following UI: https://twitter.com/DefolosDC/status/1504848530132934660

@grooverdan
Copy link
Author

🍰 Thanks looking amazing. Great improvement.

@dcermak
Copy link
Owner

dcermak commented Apr 29, 2022

This updated UI is now in the main branch, feel free to give this a try @grooverdan.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants