lynx-dev Lynx and Javascript: how-to

[Ilya Zakharevich]

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

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden