9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steve Kilbane <steve@whitecrow.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Future of Plan9
Date: Sat, 23 Dec 2000 13:21:05 +0000	[thread overview]
Message-ID: <200012231321.NAA02607@whitecrow.demon.co.uk> (raw)
In-Reply-To: Your message of "Thu, 21 Dec 2000 12:46:36 EST." <20001221174641.5B116199E4@mail.cse.psu.edu>

> 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




  reply	other threads:[~2000-12-23 13:21 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-21 17:46 anothy
2000-12-23 13:21 ` Steve Kilbane [this message]
2000-12-24  1:21   ` Boyd Roberts
2001-01-02 17:52     ` Chris Locke
  -- strict thread matches above, loose matches on Subject: below --
2003-02-12 21:10 bwc
2003-02-12  0:42 okamoto
2003-02-11 15:01 bwc
2003-02-10 17:01 [9fans] " Jaytee
2003-02-11  9:30 ` [9fans] " Douglas A. Gwyn
2003-02-11 13:06   ` Jim Choate
2003-02-11 13:19     ` Russ Cox
2003-02-11 13:32       ` Jim Choate
2003-02-11 14:11     ` Fco.J.Ballesteros
2003-02-12  4:31       ` Jim Choate
2003-02-12  5:12         ` Andrew
2003-02-12 10:34         ` matt
2003-02-12 11:46           ` Digby Tarvin
2003-02-12 17:17         ` Sam
2003-02-12 20:58           ` adrian Damn it !
2003-02-12 21:00             ` Matt Keeler
2003-02-11 14:35     ` Ronald G. Minnich
2003-02-11 16:04     ` Dan Cross
2003-02-11 17:05       ` matt
2003-02-12  9:52     ` ozan s yigit
2003-02-12 18:23   ` north_
2001-01-03  1:19 William Staniewicz
2001-01-02 22:43 ` matt heath
2001-01-08  9:54 ` Ross Evans
2000-12-24  2:11 Russ Cox
2000-12-24  2:18 ` Boyd Roberts
2000-12-24 15:46   ` matt heath
2000-12-25  5:47 ` Anthony Starks
2001-01-02 17:36 ` Randolph Fritz
2001-01-02 17:36 ` cLIeNUX user
2001-01-02 17:42 ` Anssi Porttikivi
2000-12-24  1:51 Russ Cox
2000-12-24  1:55 ` Boyd Roberts
2000-12-24  2:03 ` Boyd Roberts
2001-01-02 16:51 ` Dan Cross
2000-12-23 14:40 rob pike
2000-12-22 14:00 forsyth
2000-12-22 22:13 ` Boyd Roberts
2000-12-22 11:32 forsyth
2001-01-02 17:24 ` cLIeNUX user
2000-12-21 19:21 forsyth
2000-12-21 20:48 ` matt
2000-12-21 19:20 forsyth
2000-12-22  9:20 ` cLIeNUX user
2000-12-21 18:30 Russ Cox
2000-12-21 18:33 ` matt
2000-12-21 18:25 forsyth
2000-12-19 10:48 forsyth
2000-12-13 10:49 [9fans] " Stephen Adam
2000-12-14  9:49 ` [9fans] " Deztroyer-a1
2000-12-14 12:05   ` Boyd Roberts
2000-12-19  9:57   ` Randolph Fritz
2000-12-19 16:07     ` vecera
2000-12-20  0:58       ` Steve Kilbane
2000-12-20 18:59         ` William Staniewicz
2000-12-21  9:44           ` Alexander C. Deztroyer
2000-12-21 18:27             ` Andrew Zubinski
2000-12-21  9:45         ` vecera
2000-12-22  0:04           ` Steve Kilbane
2000-12-20  9:59       ` Alexander C. Deztroyer
2000-12-20 10:00       ` Patrick R. Wade
2000-12-20  9:59     ` Alexander C. Deztroyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200012231321.NAA02607@whitecrow.demon.co.uk \
    --to=steve@whitecrow.demon.co.uk \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).