[Edbrowse-dev] getters and setters in straight javascript

[Karl Dahlke <eklhad@comcast.net>]

It is certainly possible that some of startwindow.js will eventually
have to return to native C,
appendChild and insertBefore in particular, but only if it must.
The advantages of keeping support routines in js are so many and so substantial
I don't even have to list them.
A 4 to 1 code reduction is just one example.

You speak of the day when "we have determined which js engine to use",
as though we will know that the js engine will not need to change again.
I don't have a lot of confidence that day will ever come.
Such things are supported and then not supported.
Even if we do settle on one brand,
mozilla as an example, the next version might
have a completely different api. We've seen that before.
All other things being equal, we would want to minimize
the code that interacts with the js engine.
Call it insurance if you will.

As per the URL setters, these had a lot of c++ strings in them,
which is why I ran into them in the first place.
We were going to have to convert this code back to C strings
if it remained native, so I did an easier conversion,
that may stand or may not.

Yes I agree there isn't much point in moving the document.cookie setter,
it's not that much code, it is straight C, it works,
and some of it has to be native anyways.
The other setters are equally straightforward, and can remain native.

So ok, having removed over 1,000 lines from jseng-moz.cpp,
and having converted the remaining c++ strings to c,
Adam I think we are finally go for launch.
Create jseng-duk.c, and I hope it works, and works well, and works cleanly.
After a small amount of research, Chris is pretty optimistic.
It looks a lot easier to work with than the mozilla beast
we've been wrangling with thus far. But only time will tell.

Karl Dahlke