[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] javascript engine specification

From: Klaus-Peter Wegge
Subject: Re: [Lynx-dev] javascript engine specification
Date: Sat, 29 Sep 2012 12:29:14 +0200 (CEST)
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)

Henry and all,

may I also ask for a copy of the BarryScript package to my PM?
May be there are some good ideas in it even if it might be outdated.
I think that lynx can benefit from a partial JavaScript support in the
following situations which are at the moment hurting limits of lynx:
- javascript links
- Check of formfields by javascript functions
- HTML-text created by javascripts

for these and may be some more text-output based Javacript functions
no major changes in the lynx rendering is required.
But the problem will be to create a javascript engine which is reduced
to text-based output without all this graphic rubbish.

Moreover, it is the question how to plug-in such a piece of software
best into lynx. Such a plug-in may be used also for other purposes.

One of my students has created a proxy server which modifies
specified (very often used) web sites by applying user defined rules.
We are using this approach to make often used web-sites like
dictionaries, search engines, intranet services etc. more accessible
and easier to use by persons with disabilities. E.g. we insert
so called bypass links to the main parts of the site which allow a more
efficient use for blind users or we create missing alt-tags by applying
rules or remove redundant information etc.
I know, it would be much better to increase accessibility of the web site directly but the above strategy is very flexible.
Because the implementation of the described html-modifier into a proxy
is not the best way (security, personalization, administration) I was
thinking to plug-in this piece of existing software into lynx.
But due to time constrains, I have not figured out yet, how to do it
best in lynx.
Any initial hints are welcome, so one of my new students can try.

Many thanks


On Sat, 29 Sep 2012, Henry Nelson wrote:

On Fri, Sep 28, 2012 at 04:18:51PM +0200, Ákos Sülyi wrote:
I just really dont't like to miss those dynamically loaded stuff using
lynx. On the other hand these scripts mostly just annoying.

I don't want to change lynx's renderer, it's cool as it is. Maybe it
is a sick idea having js without dom.

You are not the first.  Some 15 years ago there was a project
called " BarryScript."  It didn't last very long, but if you
are interested I'll send you the original package.  Below my
sig I've included the README file.


 "Using Lynx is like wearing a really good pair of shades: cuts out
  the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
                                        -- me, March 1999

README included in "" (36kB)

Welcome to BarryScript, version 0.0.1.

Last updated:  November 17, 1997.

This is a standalone (read:  no hooks to lynx yet) BarryScript interpreter.
BarryScript is a fair portion of the "core" of a mishmash of the preliminary
draft of JavaScript 1.1 and the language description provided by David Flanagan
in his O'Rielly & Assoc. book, plus a bit of the new ECMA standard just to
keep things unclear.

What does "core" mean?  No objects.  No "document.write", no "Element.onfocus",
nothing that would make this really useful to lynx in the here and now, or
even in the here and later tomorrow afternoon.

Not all of the core is implemented, either.  While a standard FOR statement
exists, FOR ... IN does not.  Arrays have yet to be worked up.  I'm programming
the function calls this evening, actually.

Why distribute this to the world?  The framework is here for full language
implementation and hookup with lynx.  Consider this a request for comment and
a call for volunteers.  Or if someone is inspired to start from scratch and
come up with a better solution, I'll be more than happy to help or just cheer
you on.

Here's what to do:

1.  Be sure you have flex and bison installed.  [3 lines snipped H.N.]

2.  Type

3.  Link "" to a file containing JavaScript-like code.  (I've provided a
few examples with the extention "bs" -- no smart remarks, please.)

4.  Run the executable "x".  (ok, ok, it ain't descriptive, but it sure is
easy to type...)

5.  Watch and enjoy the resulting display that makes the old DOS debug screen
look positively meaningful....

6.  Read my project-defense-in-progress thesis.txt for more information.  At
this point, it hasn't even been put through the spell-checker yet, so please
bear with me.

Lynx-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]