On Mon, 4 Feb 2002, Luke Davis wrote:
> and, unfortunately, very standard, and becoming more so every day.
>
> This problem needs to be rectified, and quickly.
>
> I fail to understand why it has not yet been done? I came up with a few
> easy solutions for getting around a couple small script problems in lynx,
> and I do not understand why the developers have not fixed these things.
> For example: there are ways to handle those javascript URLs, that just use
> a function to grab the URL
> ("javascript::openwindow('http://www...com/.../...');"), and other such
> solutions could be made workable, with very slight modification to the
> source, such as permitting lynx to pass the base href to an external
> program for processing, and so on.
>
> What is holding this up at the development end?
You know, all you have to do is to develop such functionality yourself,
produce a patch against the standard lynx source tree and make that patch
available on a website and let everybody here benefit from your work.
Eventually someone will add some improvements to your patch, someone will do
likewise, etc. That's how open source works. If you need something then
don't wait after someone else but do it yourself. If it's useful to other
people they'll join your development efforts.
Nicolas