Sound naming spec: problems with prefixes
mzkqt at 0pointer.de
Thu Jul 17 07:32:24 PDT 2008
On Thu, 17.07.08 14:29, Bastien Nocera (hadess at hadess.net) wrote:
> I feel some of the names for the sounds are the wrong way around.
> For example:
> To me, network-connectivity-error should be error-network-connectivity.
> So that we could have a generic error sound.
But having a generic sound to alert the user about network
connectivity changes might make sense too?
I think people can always see this both ways. When Marc-Andre and I
discussed this we came to the conclusion that we have to pick *one*
order, regardless if there might be a use case for the opposite order
Maybe to fix this properly we should allow both prefixing and
postfixing sounds? i.e. when we look for a sound "a-b-c" we should
look for the power set of it i.e. for "a-b-c", "a-b", "b-c", "a", "b",
"c". This would be a significant departure from the icon naming logic
however. Sounds like overkill on first sight, but actually I don't
think it would be that bad. Or maybe instead of the power set we pick
the set of all prefixes in union with all suffixes? i.e. "a-b-c",
"a-b", "b-c", "a", "c" -- but no "b".
> The problem I see is that for some sounds, it's good to be able to match
> to a prefix, but sometimes it's not good enough. So to set a generic
> "error" sound, I'd need to modify:
For dialog-error some people might prefer to have a single sound for
all dialogs popping up, instead of having a single sound for all
errors that happen. Hence again, the order of these names is very much
> I've targetted 30-odd sounds (including the bell) to be user modifiable
> in the preferences:
> * Battery warning:
> * Long action completed:
> * Bells:
> * Button clicked:
What do you want to do with menu-replace?
> * Button toggled:
> * Login:
> * Logout:
> * Error:
> * Information or question (have a better idea?)
Hmm, sounds for opening dialogs but no sounds for opening/closing
> * Warning:
> * New email:
No IM sounds? Maybe collapse IM and email to "message-new"?
> * Empty trash:
> * Window maximised:
> * Window unmaximised:
> * Window minimised:
> What do you think?
Dunno. I'd properly start the otherway round: i.e. take the full list
and remove the items I think are unnecessary to show or can be
merged into a single prefix. So, take the full list and subtract:
all with "trash"
I am not sure to what this boils down however, and where it differs
from your list.
Then, I'd probably have in the code but commented all sounds that we
do not generate any sound for at the moment. Since libcanberra-gtk-module is the
only code that currently generates sounds this would leave these
OTOH: all of these are input feedback sounds. We have a checkbox for
that anyway. Maybe these are the ones which should not be displayed at all?
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
More information about the xdg