On 11/5/21 13:34, Imobach Gonzalez Sosa wrote:
El vie, 05-11-2021 a las 13:31 +0100, josef Reidinger escribió:
On Fri, 5 Nov 2021 11:41:27 +0000
José Iván López González <[email protected]> wrote:
On 11/5/21 11:37, Imobach Gonzalez Sosa wrote:
El vie, 05-11-2021 a las 11:13 +0000, David Díaz escribió:
Althought I like more how it is presented in elementary OS
[1][2]
[1] https://paste.opensuse.org/2dfde486
[2] https://paste.opensuse.org/ea0a54b9
In our case, I would say that our logs are not ready to be shown
to the
end user. They contain a lot of unneeded stuff, there are typos,
and so
on. It is maybe time to think about cleaning up our logs? 🙂
Instead of logs, maybe we can show the list of actions we have now:
- creating partitions
- downloading yast2-sound
- installing yast2-sound
As said, it is against our goal to provide better experience with
parallel download/install. It is hard to write something to user if
there are multiple things doing currently.
So it can be at max someething like "start download of yast2-sound",
"finish download of yast2-sound", ...
Josef
In my opinion, that's too much. For now, I would not show the logs, but
just the main steps, and that's it.
In general, I would stick to Josef's original proposal and I would
consider merging the "finish clients" screen too. But step by step 🙂
Agreed. Just showing some general information about what's going on
(like the number of pending packages), together with the release notes
is the perfect solution in my opinion. We always complain users don't
read the release notes, so let's put them before their eyes with no
other option.
I don't like the ideas of "show details" or "display logs". I don't
think there is any real value in having logs scrolling through the
screen. It's just placebo for those who want to feel they are in control
of the internal details. ;-)
Don't get me wrong, I'm one of those addicts to scrolling geeky messages
and I hated when Linux distributions adopted splash screens during
booting. But being realistic there is probably not a real use case for
them in the installation process. Even if the process freezes (something
that I have never seen personally or in a report), I don't think having
those visible logs would make any difference in that case.
Running logs are just pr0n for geeks. :-)
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Software Solutions
