-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
since naughty does not support all of the specs[1] I'm trying to close
the gaps. Next thing to add would be Categories[2], which i would map to
presets but there is the issue: I already mapped urgency levels[3] to
presets. Now there are different approaches to solve this problem:
a) one or two table(s): one for catching urgency levels and one more
catching categories (could be combined in one). If two presets apply
this way, the urgency level one should be applied last in order to get
priority.
b) More generic, there should be like filters:
[ { urgency = "low", category = "device.added" }, { preset_data } ]
This way we could set up more precise rules. We could setup
naughty.config.mapping containing this rules pointing to presets.
Additionally we could also filter by application name of sender.
I'd like to hear your feedback.
Regards,
Leon Winter
[1] http://www.galago-project.org/specs/notification/0.9/index.html
[2] http://www.galago-project.org/specs/notification/0.9/x211.html
[3] http://www.galago-project.org/specs/notification/0.9/x320.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkk7pvgACgkQ3qn9m9SfDYeNKgCgt0VrqdLSweCXESzF4dyzVHE5
uhYAniokVr02CEOz8pKoN4Q01nvAwalI
=eQJy
-----END PGP SIGNATURE-----
--
To unsubscribe, send mail to [EMAIL PROTECTED]
