Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature parity between CLI and GUI #99

Open
Neurrone opened this issue May 9, 2021 · 2 comments
Open

Feature parity between CLI and GUI #99

Neurrone opened this issue May 9, 2021 · 2 comments

Comments

@Neurrone
Copy link

Neurrone commented May 9, 2021

Hi,

I'm visually impaired and rely on a screen reader to use a computer.

It does not work with the Bleachbit Gui and making it compatible would take some effort. It does work well with the command line interface as it just outputs text directly to stdout.

There are a few places where using the CLI interface is less convenient than using the gui, so having feature parity would be really useful for me.

  1. Using bleachbit -l to list cleaners only shows individual cleaners and their options, but not help text about what they do, I'm pretty sure that gui does provide that info. I've had to resort to reading through the source XMLs for the cleaners to figure out what some of the options does. It would be great if through a -v flag, that help info could be printed out as well.
  2. Using --preview to check how much space was freed or using the clean option does print out the size of every file, but that isn't human friendly - what I'd love to see for example is a list which summarizes this information. For example, a list of applications / cleaners and how much space was freed for each.
@az0
Copy link
Member

az0 commented May 11, 2021

I would like to help with the screen reader compatibility for the GUI, but I haven't found a good way to do it yet.

For the verbose list of cleaners, the GUI shows a label and a description, and currently the CLI shows neither. I am wondering whether you want to see both.

Would the following work? This is an example for Adobe Reader

adobe_reader.cache: Cache: Delete the cache
adobe_reader.mru: Most recently used: Delete the list of recently used documents

For the second case (how much space was freed), what do you think of this format in addition to the long list of files?

Zoom: Cache: 5.3MB
Zoom: Logs: 201.1MB
Zoom: Recordings: 30.5MB

Would it be OK to show these summaries mixed in with the file names, or is there a big advantage to showing all the summaries after all the files are listed?

@Neurrone
Copy link
Author

Thanks @az0 for the quick response.

I agree that having it work natively with the gui would be good, but technically implementing this is much harder, hence why this issue focuses for now on making it work better with a CLI (feature parity). The CLI would be a very good alternative.

For the verbose list of cleaners, the GUI shows a label and a description, and currently the CLI shows neither. I am wondering whether you want to see both.

The CLI does show the label when you do -l but without descriptions, since I can't use the gui, I wanted some way of viewing it with the cli.

Would the following work? This is an example for Adobe Reader

Perfect, this is exactly what I had in mind. I'd suggest only showing this if you have an additional flag passed to the list command like -v to preserve existing behaviour.

Would it be OK to show these summaries mixed in with the file names, or is there a big advantage to showing all the summaries after all the files are listed?

The latter. Its much easier to read if it were all at the bottom, you could just scroll up after executing the command to get a good overview of how much space each type / application was using that was now freed.

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

No branches or pull requests

2 participants