From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <200012231321.NAA02607@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Future of Plan9 
In-reply-to: Your message of "Thu, 21 Dec 2000 12:46:36 EST."
             <20001221174641.5B116199E4@mail.cse.psu.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: Steve Kilbane <steve@whitecrow.demon.co.uk>
Date: Sat, 23 Dec 2000 13:21:05 +0000
Topicbox-Message-UUID: 3cdcdcb0-eac9-11e9-9e20-41e7f4b1d025

> i can easialy imagine controlls for a web browser in the
> acme structure.

Having played with the concept for Wily a fair few years
back, the trickiest part, for me, was representing the
URLs. I wanted to have the normal text available, and
B3 on the text would follow to the URL's destination.

But how to show that the text is a link? Best thing I
could come up with was to stick it in [...]. Having a
window type that supported more than one font would
help (possible in Wily, which already has file and
directory windows as different types).

The spirit of Unicode could be subverted by using
a different portion of the font to render the text, etc.
but that's pretty gross.

IIRC, I opted for the simple approach: the HTML parser
rewrote text so that it came out as:

	blah blah [yadda yadda][unique] blah blah
	....
	[unique][geturlcmd http://www.example.com/]

So you can see a link, and B3 on the unique key takes
you to the end of the doc, where there's a command
available for double-click B1, B2. Yuck.

steve