<?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"
	>
<channel>
	<title>Comments on: Ubiquity in Firefox: Round 1</title>
	<atom:link href="http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/</link>
	<description>-- aza &#124; ɐzɐ --</description>
	<pubDate>Thu, 11 Mar 2010 03:48:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Matěj Cepl</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-6546</link>
		<dc:creator>Matěj Cepl</dc:creator>
		<pubDate>Fri, 27 Nov 2009 22:44:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-6546</guid>
		<description>Search bar must die!!! I have already switched it of and use Search keywords only (search keywords are kind of forgotten and yet they are doing essentially the same what Ubiquity does now).</description>
		<content:encoded><![CDATA[<p>Search bar must die!!! I have already switched it of and use Search keywords only (search keywords are kind of forgotten and yet they are doing essentially the same what Ubiquity does now).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maxx69</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-6034</link>
		<dc:creator>Maxx69</dc:creator>
		<pubDate>Thu, 22 Oct 2009 20:05:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-6034</guid>
		<description>Briefly, they are find, identify, select, and obtain. ,</description>
		<content:encoded><![CDATA[<p>Briefly, they are find, identify, select, and obtain. ,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-5067</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 30 Mar 2009 20:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-5067</guid>
		<description>Well, since it seems quite natural to use / to get to a seach maybe the text interface should start #!</description>
		<content:encoded><![CDATA[<p>Well, since it seems quite natural to use / to get to a seach maybe the text interface should start #!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: david</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-3794</link>
		<dc:creator>david</dc:creator>
		<pubDate>Tue, 03 Feb 2009 12:56:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-3794</guid>
		<description>Slightly off-topic I think if ubiquity moves to awesomebar/searchbar the adding of the selected text preview needs to come with. 
So the new design would be the command with the selected text, followed by the command without the selected text.

I would also prefer to have a unified location bar instead of locationbar-searchbar duo.</description>
		<content:encoded><![CDATA[<p>Slightly off-topic I think if ubiquity moves to awesomebar/searchbar the adding of the selected text preview needs to come with.<br />
So the new design would be the command with the selected text, followed by the command without the selected text.</p>
<p>I would also prefer to have a unified location bar instead of locationbar-searchbar duo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-3773</link>
		<dc:creator>Henrik</dc:creator>
		<pubDate>Sat, 31 Jan 2009 16:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-3773</guid>
		<description>Aza, as what you always say: Let's reduce the UI. Personally I like design #1. No additional elements or pop-ups which will irritate users. Only the wanted output is visible. All together a good reuse of the awesome bar.</description>
		<content:encoded><![CDATA[<p>Aza, as what you always say: Let&#8217;s reduce the UI. Personally I like design #1. No additional elements or pop-ups which will irritate users. Only the wanted output is visible. All together a good reuse of the awesome bar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-3722</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Wed, 28 Jan 2009 11:52:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-3722</guid>
		<description>Mouse and Keyboard interface should ideally be the same. In your words "Fewer choices means fewer worries"</description>
		<content:encoded><![CDATA[<p>Mouse and Keyboard interface should ideally be the same. In your words &#8220;Fewer choices means fewer worries&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ChrisJF</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-3677</link>
		<dc:creator>ChrisJF</dc:creator>
		<pubDate>Tue, 27 Jan 2009 02:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-3677</guid>
		<description>I'm actually a little surprised that this hasn't been brought up already but I think #1 needs to be tweaked a bit.

Design #1 mixes metaphors too much with the identity button. The identity button is a place for *website* identity and *security* information. Ubiquity does not have anything to do with website identity and security. Obviously, #1 looks better than the rest because it is more polished. However, I think #2 (with more polish, and maybe #1's drop-down menu) would be the best choice.

Also, just a thought, you might want to consider renaming the Location Bar to the Action Bar if the Location bar and Ubiquity are combined.

Keep up the good work, guys!</description>
		<content:encoded><![CDATA[<p>I&#8217;m actually a little surprised that this hasn&#8217;t been brought up already but I think #1 needs to be tweaked a bit.</p>
<p>Design #1 mixes metaphors too much with the identity button. The identity button is a place for *website* identity and *security* information. Ubiquity does not have anything to do with website identity and security. Obviously, #1 looks better than the rest because it is more polished. However, I think #2 (with more polish, and maybe #1&#8217;s drop-down menu) would be the best choice.</p>
<p>Also, just a thought, you might want to consider renaming the Location Bar to the Action Bar if the Location bar and Ubiquity are combined.</p>
<p>Keep up the good work, guys!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean S</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-3661</link>
		<dc:creator>Sean S</dc:creator>
		<pubDate>Mon, 26 Jan 2009 22:24:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-3661</guid>
		<description>I like the design for # 1 best, but I think that the points made about combining the various bars are valid and need to be addressed. 

Since the Awesome Bar + Ubiquity replicates the functionality of the search bar, I suggest that the search bar be replaces with a Ubiquity Commands dropdown. 

I think it is important to be able to use the commands with only the keyboard, but that no user should be forced to give up the mouse to use these features. I like how # 1 places the command as another option in the Awesome Bar, and I think that backspace is appropriate for elilminating it, at least for our keyboard-only types. 

For those that prefer the mouse, the search bar can be replaced with commands instead - perhaps featuring only the top 10 or 5, or open a pane like History for searching for some command you have that isn't displayed. For users that have a lot of commands, having one place to find all of them would be useful. Selecting one would populate the Awesome Bar with that command and make it look like # 1. If the wrong one is selected, they can clear it from that dropdown or choose another. 

I think the average user doesn't want to lose their search bar, so having the same dropdown functionality as before would make it easy for the average user to mentally adjust from two bars to one. Naturally there would have to be some tutorial about "commands" being introduced, but the average user should be able to make the connection since the basics don't change much.</description>
		<content:encoded><![CDATA[<p>I like the design for # 1 best, but I think that the points made about combining the various bars are valid and need to be addressed. </p>
<p>Since the Awesome Bar + Ubiquity replicates the functionality of the search bar, I suggest that the search bar be replaces with a Ubiquity Commands dropdown. </p>
<p>I think it is important to be able to use the commands with only the keyboard, but that no user should be forced to give up the mouse to use these features. I like how # 1 places the command as another option in the Awesome Bar, and I think that backspace is appropriate for elilminating it, at least for our keyboard-only types. </p>
<p>For those that prefer the mouse, the search bar can be replaced with commands instead - perhaps featuring only the top 10 or 5, or open a pane like History for searching for some command you have that isn&#8217;t displayed. For users that have a lot of commands, having one place to find all of them would be useful. Selecting one would populate the Awesome Bar with that command and make it look like # 1. If the wrong one is selected, they can clear it from that dropdown or choose another. </p>
<p>I think the average user doesn&#8217;t want to lose their search bar, so having the same dropdown functionality as before would make it easy for the average user to mentally adjust from two bars to one. Naturally there would have to be some tutorial about &#8220;commands&#8221; being introduced, but the average user should be able to make the connection since the basics don&#8217;t change much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sander D</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-3635</link>
		<dc:creator>Sander D</dc:creator>
		<pubDate>Mon, 26 Jan 2009 17:42:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-3635</guid>
		<description>Of these designs, I think #1 looks best as doesn't add extra buttons and has a colour that looks 'dynamic'.

But it doesn't look like you can use natural language there: the Map command is heavily separated from the address argument. What was wrong with your original mockup?
http://www.azarask.in/gfx/future_ubiquity.png

Also, is it really neccessary to introduce a new mode to the AwesomeBar? As you noted, this design requires a way to get back to the URL-going state. Most screens are large enough to put the preview box inside the list with other (URL) suggestions.</description>
		<content:encoded><![CDATA[<p>Of these designs, I think #1 looks best as doesn&#8217;t add extra buttons and has a colour that looks &#8216;dynamic&#8217;.</p>
<p>But it doesn&#8217;t look like you can use natural language there: the Map command is heavily separated from the address argument. What was wrong with your original mockup?<br />
<a href="http://www.azarask.in/gfx/future_ubiquity.png" rel="nofollow">http://www.azarask.in/gfx/future_ubiquity.png</a></p>
<p>Also, is it really neccessary to introduce a new mode to the AwesomeBar? As you noted, this design requires a way to get back to the URL-going state. Most screens are large enough to put the preview box inside the list with other (URL) suggestions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: egroeg</title>
		<link>http://www.azarask.in/blog/post/ubiquity-in-firefox-round-1/#comment-3623</link>
		<dc:creator>egroeg</dc:creator>
		<pubDate>Sat, 24 Jan 2009 12:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.azarask.in/blog/?p=272#comment-3623</guid>
		<description>i think you should pulse the address bar when text is selected and turn the address bar into a button you could click that would pull up a grey translucent like terminal window (tilda?)  from the bottom that gives suggestions on what you could do w/ it. 

also an icon by the back/forward buttons could work.

or web2.0y have a fold of the page peal back on a corner?</description>
		<content:encoded><![CDATA[<p>i think you should pulse the address bar when text is selected and turn the address bar into a button you could click that would pull up a grey translucent like terminal window (tilda?)  from the bottom that gives suggestions on what you could do w/ it. </p>
<p>also an icon by the back/forward buttons could work.</p>
<p>or web2.0y have a fold of the page peal back on a corner?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
