9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "matt heath" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Future of Plan9
Date: Sun, 24 Dec 2000 15:46:55 +0000	[thread overview]
Message-ID: <003e01c06dc0$be98b080$0301a8c0@freeze> (raw)
In-Reply-To: <00a401c06d4f$c020e880$35d76ccb@coma>

There's always the w3c standards compliant browser which is open source and
written in c not c++

http://www.w3.org/Amaya/

plan9's graphical shell would also promote something like XML term

http://xmlterm.com

which renders xml/html interactively from the command line (xcat)

To bring it in to the plan9 world I suppose one would mount the page as a
file system exposing the DOM, links, images etc. in directories.
Use xcat to render the html and echo to manipulate the DOM in the language
of choice. Javascript would need to be implemented but I've used python,
perl and vbscript to do the job with IE. So build a native script language
and a javascript2native converter.

plan9 would then have great xml tools esp. with distributed execution

plan9 and Inferno are going to have to cope with xhtml and xhtml basic if
they want to continue to penetrate the embedded device scene.
I think the move to xhtml is a good thing for web design.
It would be a mistake to do an html 4 implementation and then watch it all
go down the pan.


so there's an anwer - email me when it's finished :-)






  reply	other threads:[~2000-12-24 15:46 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-24  2:11 Russ Cox
2000-12-24  2:18 ` Boyd Roberts
2000-12-24 15:46   ` matt heath [this message]
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
  -- 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  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-21 17:46 anothy
2000-12-23 13:21 ` Steve Kilbane
2000-12-24  1:21   ` Boyd Roberts
2001-01-02 17:52     ` Chris Locke
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='003e01c06dc0$be98b080$0301a8c0@freeze' \
    --to=matt@proweb.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).