Re: lynx-dev Javascript

[dickey]

> On Mar 01, Larry W. Virden decided to present us with: 
> >  
> > One word of advice - the development version of Lynx tends to be updated 
> > once 
> > every week or two.  It probably would benefit you to figure out how to add 
> > the smallest amount of JavaScript you need to, and get that into the 
> > development version, so as to not fall too far behind.  Integrating small 
> > pieces frequently is probably going to be easier than taking several weeks 
> > and falling so far behind that it becomes difficult to integrate in the 
> > changes (didn't that happen with some MIT changes at one point in the 
> > past year or two?) 
>  
> Who is responsible for integrating patches? I'd like to hear 
> from this person, is there interest in integrating the libjs 
> stuff, as experimental as it is? 

it's debatable if anyone's "responsible".  but I'm the person who's been
integrating patches.  (it runs about 10 days apart because I work on other
programs - and work during the daytime; recently a little strained because
I was working on a project with some students).

I'm interested - sure.  If it looks (or sounds) too "experimental",
it'll have to be ifdef'd so that people don't get burned.
  
> I'm planning to keep up with the lynx development version. As 
> soon as I can distribute the patches, I will be releasing them 
> as often as possible (in practice: as soon as a given batch of 
> change works, make it into a patch). But for the next few days I 
> can't distribute anything, till there is a libjs released under 
> GPL (nobody outside Mozilla knows how long; 2 weeks? One month?) 

it sounds like we may integrate this early in the 2.8.3 cycle -- there's
some good reasons to put out a release before moving to other stuff
(the gettext integration and buffer-overflow fixes).

-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey