<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: Interactive notifications mockup</title> <atom:link href="http://www.stefanoforenza.com/interactive-notifications-mockup/feed/" rel="self" type="application/rss+xml" /><link>http://www.stefanoforenza.com/interactive-notifications-mockup/</link> <description>Stefano Forenza - Personal Blog</description> <lastBuildDate>Tue, 24 Jan 2012 22:15:59 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: dranorter</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-35725</link> <dc:creator>dranorter</dc:creator> <pubDate>Thu, 02 Jul 2009 18:56:06 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-35725</guid> <description>... I really think this, or something like it, would be much more intuitive. My tendency with notifications is to put my mouse over them when I&#039;m reading them, which (jarringly) makes them disappear (rather than keeping them longer), and I often want to click them to raise the origin application.
I&#039;m not sure I like the coloured strip idea; I think the title text or icon could remain instead, but, whatever works.
Also, @Prior, as a hobbyist developer I would love to know about a notification system which allows interactions while letting the user ignore them too. (Then I would make a script which worked off a two-column file pairing messages with shell commands, a sort of to do list, randomly displaying one every half-hour, launching the task if I click.) Is there such a system?
I will go google alternative notification systems I guess.</description> <content:encoded><![CDATA[<p>&#8230; I really think this, or something like it, would be much more intuitive. My tendency with notifications is to put my mouse over them when I&#8217;m reading them, which (jarringly) makes them disappear (rather than keeping them longer), and I often want to click them to raise the origin application.</p><p>I&#8217;m not sure I like the coloured strip idea; I think the title text or icon could remain instead, but, whatever works.</p><p>Also, @Prior, as a hobbyist developer I would love to know about a notification system which allows interactions while letting the user ignore them too. (Then I would make a script which worked off a two-column file pairing messages with shell commands, a sort of to do list, randomly displaying one every half-hour, launching the task if I click.) Is there such a system?</p><p>I will go google alternative notification systems I guess.</p> ]]></content:encoded> </item> <item><title>By: jackflap</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34953</link> <dc:creator>jackflap</dc:creator> <pubDate>Sat, 13 Jun 2009 19:53:41 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34953</guid> <description>i really like the way the new notifications currently work in jaunty and see no need for them to change</description> <content:encoded><![CDATA[<p>i really like the way the new notifications currently work in jaunty and see no need for them to change</p> ]]></content:encoded> </item> <item><title>By: Ryan Prior</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34870</link> <dc:creator>Ryan Prior</dc:creator> <pubDate>Thu, 11 Jun 2009 04:43:22 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34870</guid> <description>The idea is that notifications shouldn&#039;t have any features other than to send a short message that is ignorable by the user, but might be helpful. Another system may be developed to deal with situations where you do need interaction from the user, but we&#039;ve decided that notifications should not try to fill that need.</description> <content:encoded><![CDATA[<p>The idea is that notifications shouldn&#8217;t have any features other than to send a short message that is ignorable by the user, but might be helpful. Another system may be developed to deal with situations where you do need interaction from the user, but we&#8217;ve decided that notifications should not try to fill that need.</p> ]]></content:encoded> </item> <item><title>By: Stefano Forenza</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34869</link> <dc:creator>Stefano Forenza</dc:creator> <pubDate>Thu, 11 Jun 2009 03:47:03 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34869</guid> <description>@Nick HS: I made the proposal because my interpretation of &#039;lack of disruptiveness&#039; was to still allow the click-through.
Clearly, if the notion is &quot;knowing you won&#039;t *ever* be able to do anything with those black things&quot; then that&#039;s another thing.
But, then, what&#039;s the point of having &lt;a href=&quot;https://wiki.ubuntu.com/NotificationDesignGuidelines#Morphing%20window&quot; rel=&quot;nofollow&quot;&gt;morphing windows&lt;/a&gt; ?
Since I thought the screen edge principle had not been considered, I tried to propose it.
That said, to be honest, I don&#039;t even expect a reply from the team, but I think the matter is worth trying.</description> <content:encoded><![CDATA[<p>@Nick HS: I made the proposal because my interpretation of &#8216;lack of disruptiveness&#8217; was to still allow the click-through.</p><p>Clearly, if the notion is &#8220;knowing you won&#8217;t *ever* be able to do anything with those black things&#8221; then that&#8217;s another thing.</p><p>But, then, what&#8217;s the point of having <a
href="https://wiki.ubuntu.com/NotificationDesignGuidelines#Morphing%20window" rel="nofollow">morphing windows</a> ?</p><p>Since I thought the screen edge principle had not been considered, I tried to propose it.</p><p>That said, to be honest, I don&#8217;t even expect a reply from the team, but I think the matter is worth trying.</p> ]]></content:encoded> </item> <item><title>By: Nick HS</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34868</link> <dc:creator>Nick HS</dc:creator> <pubDate>Thu, 11 Jun 2009 03:33:41 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34868</guid> <description>That idea was kicked to death when notify-osd first came out, its been decided (whether true or not) that notifications should not be disruptive and therefore have no actions. Personally I prefer it</description> <content:encoded><![CDATA[<p>That idea was kicked to death when notify-osd first came out, its been decided (whether true or not) that notifications should not be disruptive and therefore have no actions. Personally I prefer it</p> ]]></content:encoded> </item> <item><title>By: Stefano Forenza</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34861</link> <dc:creator>Stefano Forenza</dc:creator> <pubDate>Wed, 10 Jun 2009 21:44:35 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34861</guid> <description>@dim: would you elaborate ?</description> <content:encoded><![CDATA[<p>@dim: would you elaborate ?</p> ]]></content:encoded> </item> <item><title>By: Dim</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34859</link> <dc:creator>Dim</dc:creator> <pubDate>Wed, 10 Jun 2009 21:34:01 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34859</guid> <description>No, thanks. We had interactive notifications before. Too much stress when you couldn&#039;t click that button in time.</description> <content:encoded><![CDATA[<p>No, thanks. We had interactive notifications before. Too much stress when you couldn&#8217;t click that button in time.</p> ]]></content:encoded> </item> <item><title>By: Stefano Forenza</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34856</link> <dc:creator>Stefano Forenza</dc:creator> <pubDate>Wed, 10 Jun 2009 19:18:17 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34856</guid> <description>@all: is no secret that notifications are controversial and the indicator applet makes thing convoluted.
From a @G perspective, also, should the the &lt;em&gt;morphing windows&lt;/em&gt; be seen as “make it the way it used to be.” ??
https://wiki.ubuntu.com/NotificationDesignGuidelines
My proposal brings consistency to the whole, avoiding different look, feel and behaviour between interactive and non interactive notifications.
It brings an easy and intuitive way to interact with a notification that the indicator applet fails to obtain.
It lessens a lot the risk of accidental clicks. Is much less intrusive than morphing windows as well.
If you&#039;re creating something different, do that to obtain something, not because it&#039;s just different.</description> <content:encoded><![CDATA[<p>@all: is no secret that notifications are controversial and the indicator applet makes thing convoluted.</p><p>From a @G perspective, also, should the the <em>morphing windows</em> be seen as “make it the way it used to be.” ??<br
/> <a
href="https://wiki.ubuntu.com/NotificationDesignGuidelines" rel="nofollow">https://wiki.ubuntu.com/NotificationDesignGuidelines</a></p><p>My proposal brings consistency to the whole, avoiding different look, feel and behaviour between interactive and non interactive notifications.<br
/> It brings an easy and intuitive way to interact with a notification that the indicator applet fails to obtain.<br
/> It lessens a lot the risk of accidental clicks. Is much less intrusive than morphing windows as well.</p><p>If you&#8217;re creating something different, do that to obtain something, not because it&#8217;s just different.</p> ]]></content:encoded> </item> <item><title>By: G</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34855</link> <dc:creator>G</dc:creator> <pubDate>Wed, 10 Jun 2009 19:11:32 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34855</guid> <description>Your proposal is essentially &quot;make it the way it used to be.&quot;
Way to go!</description> <content:encoded><![CDATA[<p>Your proposal is essentially &#8220;make it the way it used to be.&#8221;</p><p>Way to go!</p> ]]></content:encoded> </item> <item><title>By: daniel</title><link>http://www.stefanoforenza.com/interactive-notifications-mockup/comment-page-1/#comment-34854</link> <dc:creator>daniel</dc:creator> <pubDate>Wed, 10 Jun 2009 18:53:35 +0000</pubDate> <guid
isPermaLink="false">http://www.stefanoforenza.com/?p=1787#comment-34854</guid> <description>I thought the main notify-osd idea is to remove all interaction from notifications.</description> <content:encoded><![CDATA[<p>I thought the main notify-osd idea is to remove all interaction from notifications.</p> ]]></content:encoded> </item> </channel> </rss>
