From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <002101c00f43$c21ed580$02a7b6c3@lucid.proweb.net>
From: "Matt Lawless" <alf@proweb.co.uk>
To: <9fans@cse.psu.edu>
References: <e_n_d_e_r@hotmail.com>, <200008231529.LAA29928@cse.psu.edu> <39A43650.E22AB1A2@null.net> <000701c00ee2$590d1040$02a7b6c3@lucid.proweb.net> <05da01c00eed$606147c0$03c684c3@psychobasketcase.org>
Subject: Re: [9fans] browser again
Date: Sat, 26 Aug 2000 10:55:20 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: ffc55870-eac8-11e9-9e20-41e7f4b1d025

> > it's an "inline" browser
> > it can render html and execute javascript AND give you an interactive
shell
> > at the same time

> to quote rob, i'm going to 'do a boyd' here.  are you out of your
> mind?  javascript?  i'd prefer RSTS basic.

well to quote myself "it can"

notice not "it should"

:-)

javascript is not, of course, a requirement. Any language with ECMA bindings
could work.
For instance I use python as my client side scripting language in internet
explorer

the point of xmlterm is that it renders html interactively in your shell
which is a different approach from the monolithic browser model.

I thought people might be interested in different approaches

Matt