OK, good news/bad new.
The good news is I figured out how to manually read the snapper metadata so even when I boot off a snapshot I can do this now:
The bad news is that I don't think a snapshot number is enough information to restore a subvolume so I am probably have to completely change the way I load and store that data.
EDIT: I don't think I can go in the opposite direction either. I may have to make a special snapshot restore tab.
btw I was thinking, canât these snapper tabs be âsub tabsâ of the btrfs tab? since snapper doesnât work without btrfs
They could be but I would probably need to make the UI bigger to support that. It might be a problem if you were booted off the ISO and you were stuck in a low resolution.
After looking at this more I came up with three options.
I think that option 2 or 3 are probably the best options. Option 1 is the hardest to implement and also somewhat strange from a UI perspective. Between the other two options I am not sure which is more intuitive. Having to go to a different tab to restore snapshots or having a UI that changes dynamically.
Hmm 3rd option seems good to me
As we don't have to change tabs
OK, just pushed the changes.
This is going to need some testing.
Now that I have seen it. I think the 3rd option was the way to go.
I think I would go with 2, if I am understanding correctly.
The "enriched info" might be handy even on "non recovery mode" and "checkboxes to change state of tabs" is not very common
too late⊠
I posted a few seconds before you. It is done.
I am noticing this, its happening very often in this forum ⊠I am always late !
I was worried about this but it seems OK in practice now that I have used it. The tab actually doesnât change much. Here is the unchecked version of the same screen.
yeah, seems nice and not tooo crowded.
If anything, you can always take the snapper list command as reference.
two ideas:
.. in the config settings, can you expose more options? like number{cleanup,limit,limit_important} ?
also ... had this idea ... a button ... that ... would .... delete .... all ... snapshots .... 
I am actually running snapper list to populate the data.
I could. The reason I didnât was the idea was to create an easy to use interface similar to what timeshift has.
I suppose I could hide those options behind an advanced checkbox or something. I feel like the interface is becoming a sea of checkboxes that hide and show things though.
yeah, i totally understand you. I just thought of adding the number configs, because then one could control the amount of snapshots created without going into snapper command line
EDIT: ( better explanation ) the number of snapshots, I mean, it creates by timeline and number. with those configs, all snapshot cleanups and retention settings are exposed in the GUI.
but maybe, if too crowded, just the NUMBER_LIMIT would be enough
btw ... sorry for constantly being annoying.
as far as my experience went, no problem in creating, changing settings and creating and deleting snapshots. recovery also went well, but I only tested it a little.
I still haven't tested home, because I have to move a folder out of it into a subvolume or else i will be out of space in no time ( but will right now )
ok... so I am having trouble creating the home config.
I set the name to home, and I set the backup to /home, but the button stays on "cancel", not save !
You arenât being annoying. The feedback that you and others have provided has been very helpful in making the application better. Just look at how much better it is since the topic was first opened a few days ago.
I am not sure I understand what you mean. You click the save button and it doesnât work?
ohhh I see ⊠its the save button next to the âroot configâ ⊠and not the button next to the new configuration.
that seems âtrickyâ
There used to not be a cancel button which perhaps is what it throwing you off. Since the buttons were all at the top it was more obvious.
yeah, it seems like those operations are all about the root config.
I was thinking that when config name was set and backup path also set the cancel would turn into save.
can you put a save config in the same row as the cancel one, even if does the same as the one at the top ? ( or in the save config button, make the label "save new config" ) ( or put the name of the new config in the "select config tab" and when clicking cancel it would go back to previous one ? )
maybe the most efficient is to "clone" the save config next to the cancel one, you agree ?
OHH but btw, most important, I check the snapper configs ( list-configs ) and the files directly in etc , and it was properly created. nice ! 
Also there is one thing missing
The storage occupied by a snapshot is not shown
And the shared unshared storage also
