Am 11.06.2014 12:20, schrieb Lars Uebernickel:
>> I disagree. The "x-canonical-snap-decisions-timeout" is intentionally used in
>> favour of the Freedesktop timeout feature, to indicate very clearly, that is
>> is only applicable to snap-decisions notifications.
> I think that's unnecessary for the same reason I thought introducing hints for
> snap decision actions was unnecessary.
The hint "x-canonical-snap-decisions" is an indicating hint, e.g.
like the standard "body" hint, and used to point out that there are
certain rules enforced upon the use of actions, put forth by UX-design,
which deviate from the FDO-standard. Therefore I do not regard
"x-canonical-snap-decisions" as being unnecessary.
Furthermore hints are the designated means to introduce new features (or
different behaviour).
> It's unlikely that developers have a
> problem understanding that the timeout only applies to a specific kind of
> notification.
Being explicit rather than implicit avoids misunderstanding and
possible "false-positive" bug-reports due to that.
> Adding additional hints only increases the complexity of the API and makes it
> harder to switch between different kinds of notifications.
By design every introduced notification-type serves a very specific
purpose, that differs in behaviour, visuals and interaction. Thus
switching between different notification-types is not a common thing to
do for a developer, unless UX-requirements change later on.
Am 11.06.2014 12:20, schrieb Lars Uebernickel: snap-decisions- timeout" is intentionally used in snap-decisions" is an indicating hint, e.g. snap-decisions" as being unnecessary.
>> I disagree. The "x-canonical-
>> favour of the Freedesktop timeout feature, to indicate very clearly, that is
>> is only applicable to snap-decisions notifications.
> I think that's unnecessary for the same reason I thought introducing hints for
> snap decision actions was unnecessary.
The hint "x-canonical-
like the standard "body" hint, and used to point out that there are
certain rules enforced upon the use of actions, put forth by UX-design,
which deviate from the FDO-standard. Therefore I do not regard
"x-canonical-
Furthermore hints are the designated means to introduce new features (or
different behaviour).
> It's unlikely that developers have a
> problem understanding that the timeout only applies to a specific kind of
> notification.
Being explicit rather than implicit avoids misunderstanding and
possible "false-positive" bug-reports due to that.
> Adding additional hints only increases the complexity of the API and makes it
> harder to switch between different kinds of notifications.
By design every introduced notification-type serves a very specific
purpose, that differs in behaviour, visuals and interaction. Thus
switching between different notification-types is not a common thing to
do for a developer, unless UX-requirements change later on.