[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ayatana] progress window chrome



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

frederik.nnaji@xxxxxxxxx wrote on 08/12/10 21:24:
>
> On Wed, Dec 8, 2010 at 20:57, Roth Robert <evfool@xxxxxxxxx
>...
>> On Wed, Dec 8, 2010 at 2:22 PM, Matthew Paul Thomas
>...
>>> Yes. It is a bug in the HIG that it recommends repeating title bar
>>> text as primary text in progress windows.
>>
>> The sentence that recommended repeating the title bar text as
>> primary text in progress windows was removed since 2.30... you can
>> still see it in 2.28, but it does not appear since 2.30 anymore. I
>> guess that the screenshot was not updated.
> 
> whow, such historical detail ;)

Oh, it's even worse than that. The person who removed it was ... me.
<http://mail.gnome.org/archives/usability/2010-March/msg00021.html>

I just forgot yesterday that I'd done it.

> Now let's hope that the 3.0 will rid us of the necessity of talking
> about how many titles a progress window needs..

Or, if hoping isn't your style, you could report bugs and make patches
for the programs (like Synaptic) that currently repeat titles.

> In reality, even the current stable HIG recommends against using
> windows for the indication of progress,

That's a misleading summary. The guidelines recommend against using
progress windows in specific cases -- where the task prevents you from
doing anything in an existing window (in which case you should show
progress in that existing window), or where the task will take only a
few seconds. There are still many cases where progress windows are
appropriate.

>                                         which itself leads to the
> conclusion that displaying progress within an extra window is an
> improper way of presenting that kind of data.

It doesn't really.

- -- 
Matthew Paul Thomas
http://mpt.net.nz/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0A2GoACgkQ6PUxNfU6ecpOaACeNvKjsqv3OOJbvWoMhEdKiPBS
C7IAoKBxJsSX4yGZoNDWBmwwkQrKRryv
=1wLe
-----END PGP SIGNATURE-----