[Edbrowse-dev] eb$master

[Karl Dahlke <eklhad@comcast.net>]

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]

As per my last post, I now give each window access to the master window through eb$master.
This window is always there, behind the scenes.
Even if you unbrowse every file, so it looks like there is no js anywhere in edbrowse, the master window persists.
If functions have been compiled in the master window then eb$master.compiled will be true.
We can, in *.js, test for this, and if it is false we can compile a large static function in the master window,
then link to it from our window.
I have done this for dumptree(), showscripts(), and the console object.
These functions are compiled once but available from every window.
If things don't blow up I'll do the same for most of the other functions,
especially the monster functions in third.js.
This makes it a little less cut&paste to put in an updated snapshot of one of these functions however.
If it says function foo() we have to change that to eb$master.foo = function()
but other than that it isn't hard, just something we maintainers have to remember to do.
Check it out, and if you don't object I will gradually transform the other static functions into a compile-once mode.
I don't bother doing this for the little one or two line functions,
and certainly no point for the native methods, since a pointer to C takes up less space than a pointer to eb$master.whatever.

Karl Dahlke