<?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: Firefox.next Mockup: Sidebar, Workspaces and Vertical Tabs</title>
	<atom:link href="http://www.macstories.net/stories/firefoxnext-mockup-sidebar-workspaces-and-vertical-tabs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.macstories.net/stories/firefoxnext-mockup-sidebar-workspaces-and-vertical-tabs/</link>
	<description></description>
	<lastBuildDate>Thu, 13 Jan 2011 22:11:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Roundup: The Ultimate Mac Browsers List of 2009</title>
		<link>http://www.macstories.net/stories/firefoxnext-mockup-sidebar-workspaces-and-vertical-tabs/#comment-3207</link>
		<dc:creator>Roundup: The Ultimate Mac Browsers List of 2009</dc:creator>
		<pubDate>Fri, 30 Oct 2009 17:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.macstories.net/?p=220#comment-3207</guid>
		<description>[...] Very useful, but still too far from what I wrote about in my previuos article about a Workspaces feature in Firefox.next. [...]</description>
		<content:encoded><![CDATA[<p>[...] Very useful, but still too far from what I wrote about in my previuos article about a Workspaces feature in Firefox.next. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ticci</title>
		<link>http://www.macstories.net/stories/firefoxnext-mockup-sidebar-workspaces-and-vertical-tabs/#comment-133</link>
		<dc:creator>Ticci</dc:creator>
		<pubDate>Wed, 20 May 2009 21:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.macstories.net/?p=220#comment-133</guid>
		<description>sorry, this is the right graph:

http://i43.tinypic.com/17qur9.jpg</description>
		<content:encoded><![CDATA[<p>sorry, this is the right graph:</p>
<p><a href="http://i43.tinypic.com/17qur9.jpg" rel="nofollow">http://i43.tinypic.com/17qur9.jpg</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ticci</title>
		<link>http://www.macstories.net/stories/firefoxnext-mockup-sidebar-workspaces-and-vertical-tabs/#comment-132</link>
		<dc:creator>Ticci</dc:creator>
		<pubDate>Wed, 20 May 2009 21:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.macstories.net/?p=220#comment-132</guid>
		<description>&lt;b&gt;@ David Lee&lt;/b&gt;:

Thank you, first of all.
Well, in regards to site specific browsers (see Prism or Fluid.app) I think they really work only in some cases: for example, I&#039;ve got Google Analytics and this blog dashboard on Fluid.app, and it&#039;s way too useful. Basically, they&#039;ve become native apps. 
So, as you say, these are &quot;Websites like real apps&quot; or &quot;websites that we use everyday,everytime and we can put into a single app&quot;.
Then, we have less-visited sites (blogs,for example) and &quot;casual sites&quot; (sites you&#039;ve just discovered).
My mockup solves all of these 3 problems:

-Workspaces: you can create &quot;groups&quot; of sites you usually visit together (eBay/Paypal/UPS) and create spaces to better organize your web habits;

- Tabs: casual navigation;

- Webapps: organization and single web-apps;

You can also see it this way:



Workspaces                 WebApps                  Tabs

      &#124;                                  &#124;                             &#124;
      &#124;                                  &#124;                         CASUAL
      &#124;                                  &#124;

              ORGANIZATION  

                                         &#124;
                                         &#124;
                                         &#124;
                                  SINGLE APPS


As you can see, my mockup&#039;s three main features can handle all the 3 problems I mentioned before (everyday sites, less visited, casual)  mixing them through &quot;Organization&quot; and then sub-dividing them again giving us the option &quot;webapps&quot;.

Then, we could talk about bookmarks sorting, but I think I&#039;ll write another article about it, with another mockup.

What do you think?</description>
		<content:encoded><![CDATA[<p><b>@ David Lee</b>:</p>
<p>Thank you, first of all.<br />
Well, in regards to site specific browsers (see Prism or Fluid.app) I think they really work only in some cases: for example, I&#8217;ve got Google Analytics and this blog dashboard on Fluid.app, and it&#8217;s way too useful. Basically, they&#8217;ve become native apps.<br />
So, as you say, these are &#8220;Websites like real apps&#8221; or &#8220;websites that we use everyday,everytime and we can put into a single app&#8221;.<br />
Then, we have less-visited sites (blogs,for example) and &#8220;casual sites&#8221; (sites you&#8217;ve just discovered).<br />
My mockup solves all of these 3 problems:</p>
<p>-Workspaces: you can create &#8220;groups&#8221; of sites you usually visit together (eBay/Paypal/UPS) and create spaces to better organize your web habits;</p>
<p>- Tabs: casual navigation;</p>
<p>- Webapps: organization and single web-apps;</p>
<p>You can also see it this way:</p>
<p>Workspaces                 WebApps                  Tabs</p>
<p>      |                                  |                             |<br />
      |                                  |                         CASUAL<br />
      |                                  |</p>
<p>              ORGANIZATION  </p>
<p>                                         |<br />
                                         |<br />
                                         |<br />
                                  SINGLE APPS</p>
<p>As you can see, my mockup&#8217;s three main features can handle all the 3 problems I mentioned before (everyday sites, less visited, casual)  mixing them through &#8220;Organization&#8221; and then sub-dividing them again giving us the option &#8220;webapps&#8221;.</p>
<p>Then, we could talk about bookmarks sorting, but I think I&#8217;ll write another article about it, with another mockup.</p>
<p>What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Lee</title>
		<link>http://www.macstories.net/stories/firefoxnext-mockup-sidebar-workspaces-and-vertical-tabs/#comment-130</link>
		<dc:creator>David Lee</dc:creator>
		<pubDate>Wed, 20 May 2009 20:03:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.macstories.net/?p=220#comment-130</guid>
		<description>Nice concept! This is a very good followup to your first article. I&#039;m personally not fan of workspaces because none of them have worked well for me. But that may be more of an implementation problem than a conceptual problem. 

I&#039;m a big fan of single site browsers, they really makes sense for stuff that historically have been desktop apps (mail, calendar, etc). But you&#039;re brought a good point that this model may not make sense for the UPS site or paypal.

Seems like we need three different type of organization systems: (1) First class apps for websites that are like real apps, (2) a non-bookmark way to organize the websites used to quickly lookup stuff, and (3) then a third mechanism for dealing with websites that are mostly for reading.

What do you think? Are there another other common use cases for the web that might need another organization system? And how does that hook in best with the OS&#039;s user interface model?</description>
		<content:encoded><![CDATA[<p>Nice concept! This is a very good followup to your first article. I&#8217;m personally not fan of workspaces because none of them have worked well for me. But that may be more of an implementation problem than a conceptual problem. </p>
<p>I&#8217;m a big fan of single site browsers, they really makes sense for stuff that historically have been desktop apps (mail, calendar, etc). But you&#8217;re brought a good point that this model may not make sense for the UPS site or paypal.</p>
<p>Seems like we need three different type of organization systems: (1) First class apps for websites that are like real apps, (2) a non-bookmark way to organize the websites used to quickly lookup stuff, and (3) then a third mechanism for dealing with websites that are mostly for reading.</p>
<p>What do you think? Are there another other common use cases for the web that might need another organization system? And how does that hook in best with the OS&#8217;s user interface model?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

