<?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: Queues: A Browsing Paradigm for Power Surfers</title>
	<atom:link href="http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/feed/" rel="self" type="application/rss+xml" />
	<link>http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/</link>
	<description>Hacker, Engineer, Dancer, Gentleman</description>
	<lastBuildDate>Sun, 25 Jul 2010 11:00:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam Richard</title>
		<link>http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/comment-page-1/#comment-15413</link>
		<dc:creator>Adam Richard</dc:creator>
		<pubDate>Thu, 19 Jul 2007 00:18:14 +0000</pubDate>
		<guid isPermaLink="false">http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/#comment-15413</guid>
		<description>&lt;p&gt;I really like this idea.  I&#039;m wondering whether tabs are really the best interface for a tree traversal of your web-pages, though.  That is, if my browsing history is a tree, why not just have the little down arrow on the back and forward buttons bring up a graph of the web pages connected to the current one?  It&#039;s very often that I go to a web page (call it A), then go &quot;back&quot; a web page or two, then click another link, and now neither the back or forward buttons can get me back to A.  With a tree, I would be able to.  Since I&#039;d be able to find all the webpages I&#039;ve just been to, I would be able to stop worrying about starting new tabs for new threads of browsing.  Tabs might still be useful for working with multiple web pages at once, but since that can already be done with separate windows, I&#039;d almost wonder if they&#039;re worthwhile at all in the long run.&lt;/p&gt;

&lt;p&gt;Further, it may happen that I&#039;m on a webpage and want to remember to visit a bundle of links in the future.  So there should be a feature to Ctrl-click or Alt-click or something on a link to add it further along in the graph of the forward/backward buttons.  (I think you kind of discussed this in relation to tabs though.)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I really like this idea.  I&#8217;m wondering whether tabs are really the best interface for a tree traversal of your web-pages, though.  That is, if my browsing history is a tree, why not just have the little down arrow on the back and forward buttons bring up a graph of the web pages connected to the current one?  It&#8217;s very often that I go to a web page (call it A), then go &#8220;back&#8221; a web page or two, then click another link, and now neither the back or forward buttons can get me back to A.  With a tree, I would be able to.  Since I&#8217;d be able to find all the webpages I&#8217;ve just been to, I would be able to stop worrying about starting new tabs for new threads of browsing.  Tabs might still be useful for working with multiple web pages at once, but since that can already be done with separate windows, I&#8217;d almost wonder if they&#8217;re worthwhile at all in the long run.</p>
<p>Further, it may happen that I&#8217;m on a webpage and want to remember to visit a bundle of links in the future.  So there should be a feature to Ctrl-click or Alt-click or something on a link to add it further along in the graph of the forward/backward buttons.  (I think you kind of discussed this in relation to tabs though.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Purvis</title>
		<link>http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/comment-page-1/#comment-14812</link>
		<dc:creator>Mike Purvis</dc:creator>
		<pubDate>Wed, 11 Jul 2007 22:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/#comment-14812</guid>
		<description>&lt;p&gt;Terrill: I&#039;ve wondering about similar things as well, but always with more of an emphasis on the present, rather than on historical data... it&#039;s the present that concerns me in the everyday. But as you say, the real problem is finding a way of elegantly collapsing the stretches of linear browsing so as to emphasize the interesting bits. Perhaps you could simply throw the whole thing on a logarithmic time scale, so that the farther in the past you go, the less long the node connection lines become.&lt;/p&gt;

&lt;p&gt;Anyhow, the other issue is that SVG and Canvas are both ridiculously slow for doing serious graph stuff. I used Canvas for the &lt;a href=&quot;http://sandbox.mikepurvis.com/js/clock/&quot; rel=&quot;nofollow&quot;&gt;clock&lt;/a&gt; and SVG for the &lt;a href=&quot;http://sandbox.mikepurvis.com/design/engine.svg&quot; rel=&quot;nofollow&quot;&gt;six-stroke wankel&lt;/a&gt;, and in both cases I found the performance pretty disappointing. So you could always experiment, but if you mean to package it as a Firefox plugin, expect to waste time getting it up to speed.&lt;/p&gt;

&lt;p&gt;Cam: Really? I think the tabs as implemented are the &lt;em&gt;least surprising&lt;/em&gt; approach. Most of the features I&#039;m describing here would catch a user off guard if they weren&#039;t expecting them. Also, this is heavily optimized for a very specific kind of browsing strategy. I&#039;d still like to try implementing these ideas as a plugin, but I don&#039;t they&#039;d ever make sense in a browser core.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Terrill: I&#8217;ve wondering about similar things as well, but always with more of an emphasis on the present, rather than on historical data&#8230; it&#8217;s the present that concerns me in the everyday. But as you say, the real problem is finding a way of elegantly collapsing the stretches of linear browsing so as to emphasize the interesting bits. Perhaps you could simply throw the whole thing on a logarithmic time scale, so that the farther in the past you go, the less long the node connection lines become.</p>
<p>Anyhow, the other issue is that <acronym title="Scalable Vector Graphics">SVG</acronym> and Canvas are both ridiculously slow for doing serious graph stuff. I used Canvas for the <a href="http://sandbox.mikepurvis.com/js/clock/" rel="nofollow">clock</a> and <acronym title="Scalable Vector Graphics">SVG</acronym> for the <a href="http://sandbox.mikepurvis.com/design/engine.svg" rel="nofollow">six-stroke wankel</a>, and in both cases I found the performance pretty disappointing. So you could always experiment, but if you mean to package it as a Firefox plugin, expect to waste time getting it up to speed.</p>
<p>Cam: Really? I think the tabs as implemented are the <em>least surprising</em> approach. Most of the features I&#8217;m describing here would catch a user off guard if they weren&#8217;t expecting them. Also, this is heavily optimized for a very specific kind of browsing strategy. I&#8217;d still like to try implementing these ideas as a plugin, but I don&#8217;t they&#8217;d ever make sense in a browser core.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cam Turner</title>
		<link>http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/comment-page-1/#comment-14794</link>
		<dc:creator>Cam Turner</dc:creator>
		<pubDate>Wed, 11 Jul 2007 17:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/#comment-14794</guid>
		<description>&lt;p&gt;This is an awesome idea. I know many people (who are not power users) who simply assume that this is the way tabs should work and I agree. have you submitted this to the mozilla team? They should at least read this article.&lt;/p&gt;

&lt;p&gt;As for Terrill&#039;s idea, personal browsing statistics would be really cool, but I&#039;d expect that this kind of feature would be released by some sort of spyware company because that data would be really useful to them too... or a search engine company even. I&#039;d be weary of anything that already does what you suggest as there is a good chance there are alternative motives.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is an awesome idea. I know many people (who are not power users) who simply assume that this is the way tabs should work and I agree. have you submitted this to the mozilla team? They should at least read this article.</p>
<p>As for Terrill&#8217;s idea, personal browsing statistics would be really cool, but I&#8217;d expect that this kind of feature would be released by some sort of spyware company because that data would be really useful to them too&#8230; or a search engine company even. I&#8217;d be weary of anything that already does what you suggest as there is a good chance there are alternative motives.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terrill</title>
		<link>http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/comment-page-1/#comment-14784</link>
		<dc:creator>Terrill</dc:creator>
		<pubDate>Wed, 11 Jul 2007 14:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://uwmike.com/articles/2007/07/01/queue-browsing-paradigm/#comment-14784</guid>
		<description>&lt;p&gt;This is slightly off topic, but anyway...&lt;/p&gt;

&lt;p&gt;Seeing your hint at trees above I have always wanted a visual tree view of my browsing.  Even though it would be more like a forest with lots of root nodes, and very tall trees, it would still be very interesting.&lt;/p&gt;

&lt;p&gt;Also, I would really like to see a different view of my browsing over the day/week/month. Something more web like, showing only unique nodes (pages) and the connections I&#039;ve made between them. The line weight of the connections would denote the number of times I had made that connection.  The size of the node would denote the number of times I viewed the page (that would be a good indicator of importance).&lt;/p&gt;

&lt;p&gt;Since the web would be a real mess when viewed (lines crossing each other, going under nodes, etc) when you click on a node it would &#039;organize&#039; the web around it, to provide at least a bit of clarity to that specific spot.   I&#039;m kind of envisioning Digg Swarm, but personalized, and persistant over sessions. http://labs.digg.com/swarm/&lt;/p&gt;

&lt;p&gt;Do you know if anything like this exists?  I am very tempted to try making something.  Use some of these data structures and algorithms I&#039;ve been learning this term.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is slightly off topic, but anyway&#8230;</p>
<p>Seeing your hint at trees above I have always wanted a visual tree view of my browsing.  Even though it would be more like a forest with lots of root nodes, and very tall trees, it would still be very interesting.</p>
<p>Also, I would really like to see a different view of my browsing over the day/week/month. Something more web like, showing only unique nodes (pages) and the connections I&#8217;ve made between them. The line weight of the connections would denote the number of times I had made that connection.  The size of the node would denote the number of times I viewed the page (that would be a good indicator of importance).</p>
<p>Since the web would be a real mess when viewed (lines crossing each other, going under nodes, etc) when you click on a node it would &#8216;organize&#8217; the web around it, to provide at least a bit of clarity to that specific spot.   I&#8217;m kind of envisioning Digg Swarm, but personalized, and persistant over sessions. <a href="http://labs.digg.com/swarm/" rel="nofollow">http://labs.digg.com/swarm/</a></p>
<p>Do you know if anything like this exists?  I am very tempted to try making something.  Use some of these data structures and algorithms I&#8217;ve been learning this term.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- uwMike.com will return...-->
