Matthew Cruickshank wrote in message
<[EMAIL PROTECTED]>...
>When I foolishly suggested a definitions list
>(http://access-mozilla.sourceforge.net/article.php?sid=10)
>there were a few people agreeing with the idea. I
>think it's a good one. ...for newbies who might not
>know they're using a [browser] that renders [HTML] or
>what [XHTML] or a [screenreader] is. It's purpose is
>to have a short one or two paragraphs on some word
>that which many projects assume the reader knows
>(Netscape, Mozilla, Rhino, CSS). I don't mind taking
>responsibility for this if it's wanted.
>
>My ideal hierarchy would be,
>
>/define/[word]
>
>(I would also be wanting to use a variable that shows
>which (if any) node the person came from so I might
>build two-way links. /define/html then
>/define/markup language?from=[ID#])
>
>Buh-bye!
What about links to everything2.com? It works quite well for /., and I use
it quite often when I need to know what something is. It is kind of
inkeeping with the ethos of mozilla too. Afterall, why duplicate someone
elses work?
--
psr
->8O)
[from address in headers munged, reply to address should be ok]
