Comment 91 for bug 390508

@Holger on Ayatana

That's an interesting philosophy for a linux distribution, but bear in mind
that in that case, they did not delete all the other packages from the
repository. If you don't like the default application shipped with the
Ubuntu install CD, you can very well go ahead and install any others from
the repositories. Ignoring timeouts (enforcing the defaults) is similar to
removing all the applications that conflict with the defaults from the
repository. The problem is not with setting a default - that's fine; the
problem is with forcing people to use that default even if they don't want
to.

--
Support Wikipedia:
http://wikimediafoundation.org/wiki/Donate/en
http://volunteer.wikimedia.org/
--
DRM 'manages access' in the same way that jail 'manages freedom'.

On Tue, Mar 23, 2010 at 1:59 AM, Holger Berndt <email address hidden> wrote:

> > 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>/msg00747.html
>
> > 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://markmail.org/message/hxvahasqoemkuhp5#query:+page:1+mid:ij55nyqffhbf3gvs+state:results
>
> http://markmail.org/message/hxvahasqoemkuhp5#query:+page:1+mid:hgigaz6777qubzet+state:results
>
> 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.
>
> --
> notify-send ignores the expire timeout parameter
> https://bugs.launchpad.net/bugs/390508
> You received this bug notification because you are a direct subscriber
> of the bug.
>