<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Back/forward buttons in browsers: why not use graphs for them?</title>
	<link>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/</link>
	<description>Lobet den Herrn</description>
	<pubDate>Thu, 09 Sep 2010 11:34:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Back/forward buttons in browsers: why not use graphs for them? by: Tjaard</title>
		<link>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-286</link>
		<pubDate>Mon, 03 Apr 2006 13:09:03 +0000</pubDate>
		<guid>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-286</guid>
					<description>Hmm, here on Linux it doesn't appear to work... I fear what'd happen on Firefox 1.5 :P... I think it'd be nice if it were compatible with Tab Mix Plus' session saving abilities, as this includes saving each tab's history as well. August 14th is an awful long time ago, so perhaps mailing to the list can put back some life into it :) .</description>
		<content:encoded><![CDATA[	<p>Hmm, here on Linux it doesn&#8217;t appear to work&#8230; I fear what&#8217;d happen on Firefox 1.5 :P&#8230; I think it&#8217;d be nice if it were compatible with Tab Mix Plus&#8217; session saving abilities, as this includes saving each tab&#8217;s history as well. August 14th is an awful long time ago, so perhaps mailing to the list can put back some life into it :) .
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Back/forward buttons in browsers: why not use graphs for them? by: Paul Dicker</title>
		<link>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-283</link>
		<pubDate>Sat, 01 Apr 2006 14:39:14 +0000</pubDate>
		<guid>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-283</guid>
					<description>Currently, ForwardFork tries to accomplish somthing like that. Maybe you want to have a look at it</description>
		<content:encoded><![CDATA[	<p>Currently, ForwardFork tries to accomplish somthing like that. Maybe you want to have a look at it
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Back/forward buttons in browsers: why not use graphs for them? by: Tjaard</title>
		<link>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-123</link>
		<pubDate>Sat, 20 Aug 2005 13:53:40 +0000</pubDate>
		<guid>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-123</guid>
					<description>Meta-information for links on pages would be a good idea indeed. It'd be possible to use the forward button (or the associated mouse gesture ;) ) to go to the next page without ever having visited it before; a thing that's totally natural for any web site with some kind of ordering on its pages. The meta-data needed would consist of two properties: a unique identification of the ordering used and of course the property stating whether the link points forward or backward. This would allow for multiple orderings to exist on a single page, something that I think could be quite useful in certain situations.

The sad thing about introducing new elements is that they need to be standardized and that that process is quite... slow (not to mention certain companies don't care much about standards). I'd be happy if the Mozilla people would consider just implementing graphs/trees, but introducing meta-elements for navigation in the process won't hurt, I guess...</description>
		<content:encoded><![CDATA[	<p>Meta-information for links on pages would be a good idea indeed. It&#8217;d be possible to use the forward button (or the associated mouse gesture ;) ) to go to the next page without ever having visited it before; a thing that&#8217;s totally natural for any web site with some kind of ordering on its pages. The meta-data needed would consist of two properties: a unique identification of the ordering used and of course the property stating whether the link points forward or backward. This would allow for multiple orderings to exist on a single page, something that I think could be quite useful in certain situations.</p>
	<p>The sad thing about introducing new elements is that they need to be standardized and that that process is quite&#8230; slow (not to mention certain companies don&#8217;t care much about standards). I&#8217;d be happy if the Mozilla people would consider just implementing graphs/trees, but introducing meta-elements for navigation in the process won&#8217;t hurt, I guess&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Back/forward buttons in browsers: why not use graphs for them? by: Georg Muntingh</title>
		<link>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-122</link>
		<pubDate>Sat, 20 Aug 2005 12:53:25 +0000</pubDate>
		<guid>http://tjaard.nl/2005/08/15/backforward-buttons-in-browsers-why-not-use-graphs-for-them/#comment-122</guid>
					<description>Now that is an interesting idea! Maybe it would be especially interesting to use it for a website on itself. Some websites lack any form of transparency. When combined with meta-information of the links, I think it would be a great tool for me to grasp the structure of the website in just a glance. Ofcourse in particular the non-transparent websites will lack meta-information for the links, but in that case maybe one could just display the filenames?

On a first thought, I think in a lot of cases displaying just a tree structure would be the most transparent. Who cares that you can reach a page in several different ways? What matters, is how you get there from the mainpage. In case of a non-hierarchical site as Wikipedia, one ofcourse would need the graph structure.

This could also help not to overlook any pages. For these reasons, I would really use a button to `switch to graph-mode'. I want it, now!</description>
		<content:encoded><![CDATA[	<p>Now that is an interesting idea! Maybe it would be especially interesting to use it for a website on itself. Some websites lack any form of transparency. When combined with meta-information of the links, I think it would be a great tool for me to grasp the structure of the website in just a glance. Ofcourse in particular the non-transparent websites will lack meta-information for the links, but in that case maybe one could just display the filenames?</p>
	<p>On a first thought, I think in a lot of cases displaying just a tree structure would be the most transparent. Who cares that you can reach a page in several different ways? What matters, is how you get there from the mainpage. In case of a non-hierarchical site as Wikipedia, one ofcourse would need the graph structure.</p>
	<p>This could also help not to overlook any pages. For these reasons, I would really use a button to `switch to graph-mode&#8217;. I want it, now!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
