[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Tue, 4 Jul 2000 00:25:26 -0400
000703 Larry W. Virden wrote:
>> From: David Woolley <address@hidden>
>> but also the browser object model. Netscape's is probably best documented,
>> but Microsoft's is more extensive. The browser object model is the feature
>> possibly to an extent where it is easier to start from scratch,
>>or from the Mozilla source code base.
if that is correct, we may have to accept Lynx has no long-term future:
eg i have recently run into JS roadblocks using the Internet
to inquire re local inter-city bus fares & our public-library catalog
(yes, i protested, with a good response from the library,
but so far nothing from the publicly-owned bus co).
> somewhere in the Lynx distribution there used to be a note
i have two sources: (1) a JS package which i believe LV recommended,
which was part of something larger & which i downloaded & archived:
the README is signed by Brendan Eich 960917; (2) www.ngs.fi/js/ ,
which seems quite detailed, but was last updated 981217.
> Right now all the configure does is set up some Makefile info
> for linking the library. But at least you wouldn't have to worry
> about what commands to implement at first...
Lynx might start by creating a link in place of a JS `onclick':
that would avoid a lot of problems, similarly to Lynx handling of frames.
> There are incompatibilities between Netscape vs IE vs ECMAScript--
> at least the first two -- that are going to be a pain to accomodate.
NGS too ... (smile).
SUPPORT ___________//___, Philip Webb : address@hidden
ELECTRIC /]     | Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden