https://bugs.kde.org/show_bug.cgi?id=396140

Michał Dybczak <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #5 from Michał Dybczak <[email protected]> ---
I applaud this proposal.
There is really no problem with many progress bars when we see pacman or apt
output in terminal - they nicely show what is being done. We could always go
with spinning circle... but that's not a thing that would satisfy a Linux user
if there is a way to show it better.

There is something hypnotizing and satisfying in seeing an update info and that
is being done right. Currently Discover's update behavior is everything
opposite: unsatisfying and confusing. Clicking on "Update" does not show any
graphical, immediate response, like: changing UI for update info: preparing,
initializing, checking, downloading, etc. It invokes feeling of being stuck,
frozen, like something bad had happened so this proposal is important and can
lead to only better result.

- Having bar cleared out and filled up again on next update phase feels quite
ok - many programs or systems follow that step by step progress bar pattern.
- Having multiple progress bars that are filled to the end after each phase is
completed feels also ok, although a bit busy and this could take more space.
- Having a single progress bar for all operation is not great IMO. Each phase
can take different time, it's hard to have accurate % info (maybe I'm wrong),
such progress bar moves much slower (less satisfying), has more opportunities
to stuck on certain level (again: not good). Linux users tend to want more info
what is happening, even on GUI programs. Single progress bar is ok for single
program/package installation but for the system update this feels like too
simplistic approach which don't take into account user's intelligence and need
to know what is happening.

There is a reason why most people end up using Synaptics, Muon, terminals or
other less graphically pleasing but more accurate and informative programs.

It would be cool if Discover was ahead of normal software centers and presented
seemingly simple, nice for newbie and yet, had more "juice" in it. Clear info
on package source (and other options timed to it) is a move toward this
direction. Improving update experience would be another step. Sure, it won't be
ideal at first but once the step will be done, it can be improved.

So in the end Discover would be "simple by default, powerful when needed" ;).

Another thing is: how package managers questions re handled by Discover? Is it
already implemented when we need to delete/replace some packages or there might
be info on unresolved dependencies (which can point to manual solution on what
to do to fix the update)? So far GUI programs are not always showing enough
info so on rolling systems terminal is the advised method of updates.
Or maybe allowing users to use terminal for update can be a thing? Octopi does
that nicely, I always shows an option to use terminal and I always agree as
it's right thing to do on Arch based system. This is ideal, because I either
confirm update in GUI program or click to open terminal. There is no additional
prompt that would annoy users.

Just a bunch of thoughts. Thanks for making PLasma better and better every day?
:D

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to