In message <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] writes:
> Someone "just" needs to write the code to implement JavaScript support.. but
> JavaScript's impression of how pages are layed out is different from the
> way Lynx does it.
It's definitely possible - I have a very, very, very alpha Lynx+JS.
Unfortunately, about all it can do is validate *some* form fields and
*sometimes* follow Javascripted links.
Lynx and it's internal structure weren't designed for Javascript, and
that makes it a whole magnitude more difficult to bolt it on after
the fact. If there is to be a Javascripted Lynx, the internals need
either a radical redesign or something extraordinarily clever. I think
it's possible to replace Lynx's internal idea of the page with Javascript
objects that represent the page. It's a lot of work, but you get almost
trivial Javascript support afterwards. You also get a Lynx that has to
be linked with Javascript (although you could disable it on the pages),
and which would be effectively a fork (unless it was well supported).
Is there enough support for Javascript in Lynx to make it worthwhile?
(I haven't looked at links and w3m in any great depth so far, but from
what I've read and seen, they don't look like they have a much better
internal design than Lynx).
--
rob partington % [EMAIL PROTECTED] % http://lynx.browser.org/
