[FEATURE REQUEST] Can we give extensions and scripts 'save preset' and 'load preset' functionality?

[vis223]

I spend all my time using A1111 but the more I try to experiment with extensions I realize a great deal of my time is spent inputting values repeatedly after a reset. It's maddening to fill out a ton of parameters then have them zeroed by some unexpected event. To my knowledge, only Deforum has 'save' and 'load settings' but shouldn't it be standard with all the add-ons? Even the simplest AE plugin has preset management. .A 'Save All state' at the very least but a preset protocol s is surely more future-proof?

Also, could there be a way to access 'read_me' or 'help' files direct from the extension? It's another time-suck going back and forth to github or a downloads folder. Some of these extensions require constant referral to be understood clearly.

And one last suggestion. Could the 'arrow-heads' be applied more consistently to every section currently 'living on the left'. If we could fold-up sections used less frequently it brings oft-used parts nearer to the top.

I see lots off scroll-fatigue on here and a simple solution is to fold up sections we use less often. They'd still be enabled if needed but remain folded until being tweaked.

For instance, Conditioning Highres.fix strength takes up real-estate. I don't want to disable it but want to fold it up when not in use. As I would also the latent mirror mode..

The 'samplers' could be closed in a box with the 'currently used' on display and an arrow-head for more if required. We don't need to see them all the time it becomes a drag scrolling past them when we could hide them instead. I know you can hide them in settings but I can never decide what to turn off so I still need access but there's no reason for it take up so much space constantly.

Most of the 'original' settings can stay unchanged for an entire session. Let's face it, the big boys here are Steps, CFG, Denoise and Seeds so we want them near the top with quickest access. They'd appear a damn site nearer the top if we could fold-up many of the settings above them.

The input intensive sections, like random and randomize, x/y/z , dynamic prompts etc, are currently a really long scroll from the top. So to experiment requires so much back and forth up and down my hands go numb. Especially as I can't save any of these settings - as per my first suggestion

If fixes exist already then I'm not aware and sorry for possibly ranting. I'm interested in these CSS alternatives I hear rumour but have no idea where to look or how to use them. I'd greatly appreciate any tips and workarounds. But changing the default config values is not really the advice I'm looking for.

I suggest before completely redesigning the gui we should be trying to 'compact' what exists already.

Thank you for taking the time. This is my first post

[some9000]

I am by no means an expert, barely made StylePile. But it seems like the UI library being used here - gradio - isn't really made for things of this scale. By default it has all this padding and margins everywhere. Everything is like a children's book instead of a proper UI. So a relatively simple array of choices takes up the whole screen vertically. One way to fight this is changing browser scale, but that's also a little messy.

Do agree that everything to do with sampling could live below other options. Batch count and Batch size may as well be the more important ones. In general there is some room for improvements. Now that most functions seem to be done and things have slowed down with massive additions looking at the UI might be a good idea. I have tried to change things using the user.css option, but that is basically locked to block sizes and such. Could not change margins and appearance of elements so it stays that way.

As for saving settings of most things - that sounds like a mess to implement, since it would mean some way to get all that data from specific extensions (control/variable names and values), saving to some file. Then, when loading adding all those checks if that extension is currently present/active and then, on top of that you would need to restore all those settings for each UI element.

[Gerschel]

https://github.com/Gerschel/sd_web_ui_preset_utils