Re: [Ayatana] Notify OSD: Talk about giving the user preferences

[Luke Benstead <kazade@xxxxxxxxx>]

I've just seen this:

"notify-osd (0.9.20-0ubuntu1) karmic; urgency=low

  * New upstream version:
    - added support for integer gconf-key "/apps/notify-osd/gravity"
    - supported values are 1 (NorthEast, top-right) and 2 (East,
vertically centered at right of screen)
    - switch back default positioning to NorthEast (top-right)"

Just wanted to say thank you to whoever is responsible for providing the choice.

Luke.

P.S A south-east option would be awesome ;)

2009/9/1 Luke Benstead <kazade@xxxxxxxxx>:
>> The main problem here, which Mark has hit upon in previous emails, is
>> that while more configuration sounds nice and simple in theory, it
>> creates buggy and inelegant applications. Each option added creates
>> another code path to develop, maintain, and test. Even a simple binary
>> checkbox theoretically doubles the the number of possible
>> configurations as you have all the possibilities you did before with
>> the option unchecked, and now that same number with the new option
>> checked. It can really be a drain on new features and overall quality,
>> which would be a disservice to users.
>
> I totally agree. However in this particular instance, the inability to
> configure the location, conflicts with GNOME's general ability to be
> configured (i.e. screen elements can be positioned to a users
> preference and the notifications may conflict with that). Also, my
> accessibility point stands, some users have better vision in certain
> portions of their view and would prefer the notifications where they
> can see them. I totally agree that the options should be limited, I
> don't think the size, colour, animation style, duration etc. of the
> notifications need to be configurable (font-size definitely so for
> accessibility, but I believe that's already the case) positioning is
> necessary though IMO.
>
>>
>> That said, users are different and some basic configuration options
>> can be beneficial. It is just a fine line on a slippery slope, and I
>> think there is a lot that can be done with good defaults and
>> intelligent behavior, instead of working around a lack thereof with
>> lots of configuration options.
>
> Yep, sane defaults make sense. But in some circumstances we should be
> able to change them. I'll give an example, the Pidgin developers
> decision to make the input box non-resizable was a sane change to
> make. It didn't really affect anyone, no-one suddenly couldn't see the
> box, it didn't interfere with any users daily work, it just may not
> have been their preference and I believe it was a good decision, it
> didn't take me long to get used to it and now I don't even think about
> it.
>
> However, right now on Jaunty, if I'm typing into the Firefox search
> box and a notification comes in, it interrupts me. As I've mentioned a
> few times, people with poor vision may not even see the notifications
> in the chosen position (I believe this is the most serious issue
> really). Users who arrange their desktop in a non-default way (e.g.
> have desktop widgets in that location, have an app with a sidebar
> there etc.) will be disrupted by the notifications. Yes they fade if
> you hover them, but that's still an action you must perform, and
> something that a slight configurability will remedy.
>
> Luke.
>