Comment 90 for bug 390508
Revision history for this message
| Holger Berndt (berndth) wrote Re: notify-send ignores the expire timeout parameter | #90 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> Totally wrong
No, it's not. Denying reality may be fun, but it's not helpful. I was not talking about what you'd like, but about what notify-osd is aiming at. It is part of project Ayatana, and here's a statement about configurability in that project:
http://<email address hidden>
> Oh really? That's strange, because it fits perfectly my needs
Obviously, it doesn't, because otherwise, there wouldn't be any need to complain.
> BTW, I'm not a "luser", I'm a computer engineer (and developer as well),
I didn't say anything about "lusers". And I don't really care for your engineering background, but thanks for telling me. It's got nothing to do with the discussion at hand, though.
> so I think I'm able to evaluate that by myself, thanks.
So just go ahead, and evaluate if notify-osd fits your needs. Because in fact, it doesn't seem like you did that yet. You're evaluating how notify-osd should change it's design to fit your needs. That's not the same thing.
> Oh well, finally we discovered the problem: the others
Yes, if you rely on notification daemon specialities, you're doing something wrong. For comparison: Here's what the KDE notification daemon developer (completely unrelated to notify-osd) has to say about how and where Galago notifications may end up in KDE:
http://
http://
How does a developer know how his notification is going to look or behave? If it's not in-house code, he can't. Thus, he can't rely on presentation, or, in other words, if he needs to rely on presentation, it's not the right infrastructure to use.