[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ayatana] unity and notifications
- To: Conscious User <conscioususer@xxxxxxx>
- Subject: Re: [Ayatana] unity and notifications
- From: Michael Jonker <citizen.jonker@xxxxxxxxx>
- Date: Thu, 16 Sep 2010 16:22:37 +0100
- Cc: ayatana@xxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=2guPkeiZ5XUWqWrYHkpGgRFjgM18teAadTE9W2B+kyI=; b=jVdc4ku514QSUQEQsV0Kuh0ra7YaWmmOj0uaXGHZqgruT4H1mj3F5f0HIe0fAq0aff Bm0hhgTNtVKkbatkx2kfApXiOqt2EgexDtnbDj3LK7No6HoURJF3tmZAEfcwnP8aqRyi X47cpYMqO5nPm0yHC8ljTFa5B0ro3LWSQ13Sw=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; b=eTUUc5iSsdMi/cUCqfA0V4LaGQwoAywu3atyK5nM0RBn8xgw7qI6Z+wzl8/YKQm/wM OZTti1aD3jUlTXXbNGOezG689iYuc3HHmZa49k1Da4FPPUvV3RjbaAzEl0e/tPmeeRxV 7R5/QzoVhe9i6+6FJfCIbNMBEjn2FO8ZhuAw4=
- In-reply-to: <1284637671.12920.29.camel@laptop>
- List-archive: <http://lists.launchpad.net/ayatana>
- List-help: <https://help.launchpad.net/ListHelp>
- List-id: <ayatana.lists.launchpad.net>
- List-owner: <https://launchpad.net/~ayatana>
- List-post: <mailto:ayatana@lists.launchpad.net>
- List-subscribe: <https://launchpad.net/~ayatana>
- List-unsubscribe: <https://launchpad.net/~ayatana>
- References: <1284564973.8854.1.camel@dani-desktop> <1284572153.2195.9.camel@michael-desktop> <1284577655.1858.2.camel@chronic> <1284635333.5265.21.camel@ubuntu-laptop> <1284637671.12920.29.camel@laptop>
- Reply-to: citizen.jonker@xxxxxxxxx
With specific reference to Unity and the notification:
We need to get ready for the touchscreen market. The present logic of
the notification is mouse-centric and will need to be overhauled for
touch screen.
In this situation, the mouse cursor causing the notification to fade
will not be available and the notification will simply take up real
estate for a length of time the user cannot control.
On Thu, 2010-09-16 at 13:47 +0200, Conscious User wrote:
> > My point is that a x (close) button would dismiss this
> > intrusion to my focussed work immediately - or - moving the notification
> > to a position I can accept will give me the best of both worlds.
>
> Best of both worlds for your particular use case, but the truth is:
> neither option is fully ideal. A close/respond button creates problems
> with accidental clicks (a bubble popping up exactly when you are
> clicking in something below it), and there is the fact that it feels
> wrong to get out of your workflow just to close a notification.
>
> The current NotifyOSD bubbles follow this principle quite well with
> respect to the case where you might need to interact with the mouse:
> it simply fades away smoothly when you approximate the cursor and
> gets out of the way. However, you are absolutely correct when you
> say that the bubbles get in the away when you need to *just see*
> what is below them, not interact with. Then you need to put the
> mouse over them to make them fade, which is almost the same thing
> as closing.
>
> So, the question to the Ayatana designers is: how to cover this case
> of "just wanting to see what is below" satisfactorily? I remember
> hearing that NotifyOSD will be getting some love for Natty, so I'm
> particularly curious about it.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ayatana
> Post to : ayatana@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ayatana
> More help : https://help.launchpad.net/ListHelp