Re: lynx-dev Lynx and Javascript: how-to

[edmondrod]

There is a working javascript processor that can be used.  NJS.  Even
if it is out of date, it could be replaced with another script at a later
time, or simply turned off completely.  Coupling the lynx calls to the
script processor with an intermediate function should make the script
easily replaceable.    Does the outline below adress the <script> tags
as well?  That seems to be a good place to start.  If the javascript
processor fails, a blank string would be returned, and perhaps some sort 
of warning message. 

I tried a few scripts from the Internet that I found on NJS.  Sometimes the 
scripts have functions that are not defined, so I figure that the big
2 must have some kind of library defining some common functions.   

Edmond Rodriguez 




> From address@hidden  Thu Jul  5 16:31:26 2001
> 
> 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
> 


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