lynx-dev
[Top][All Lists]
Advanced

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

lynx-dev Javascript how-to


From: Philip Webb
Subject: lynx-dev Javascript how-to
Date: Fri, 15 Mar 2002 17:00:11 -0500
User-agent: Mutt/1.3.25i

here are two items which may be of interest, if not assistance,
in current efforts to add JS support to Lynx.
the NJS site was last updated 010503.
IZ made some important additions to Lynx, but hasn't been active recently.

--- Item 1 ---

 http://www.bbassett.net/njs/  may help shorten the work somewhat.

--- Item 2 ---

Date: Thu, 5 Jul 2001 16:05:31 -0400
From: Ilya Zakharevich <address@hidden>
Subject: lynx-dev Lynx and Javascript: how-to

Let me repeat it again: given a working Javascript processor, it is
absolutely trivial to make Lynx understand Javascript.  Let me
reiterate a simple implementation.

I mark the functionality added to Javascript processor by [JS], added
to Lynx by [L].

Stage 1: [L]  Teach lynx a new type of HTML-flow source: JavaScript
              processor (this is in addition to file/news/http/etc);

         [JS] Teach JS to emit HTML for the static part of the document.

  [This stage covers a significant portion of documents already.]

Stage 2: [JS] Teach JS to mark the triggers-for-actions in the static
              HTML by <lynx-jsp:id> type anchors and unique identifiers.

         [L]  Teach lynx to call the processor back when lynx-jsp:id
              anchors are activated, and read back a new version of
              the document.  

         [L]  Support <lynx-immediate-url:URL> scheme to make lynx
              switch to a different document when reading this new
              version (for "active" hyperlinks).

              [Thus an active hyperlink is marked as <lynx-jsp:id>,
              when activated, lynx informs the processor which id was
              activated, the processor calculated the URL, imbeds it
              into HTML surrounded in <lynx-immediate-url:URL>
              wrapper, and writes the HTML back to lynx.]

  [Validation of fields should be negotiable - either on each
   keypress, or when field editing is done...]

Hope this helps, Ilya

--- End forwarded message ---

-- 
========================,,============================================
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

reply via email to

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