Before we dive headlong into a redesign, it might be worth asking whether there is a better engine out there. After the 24 api, mozilla became very confusing, in my opinion. Not because of c++, but because of all those compartments etc. I think we got them right, but it is a house of cards. Blow on it the wrong way and it collapses. And I don't like its fixed js heap size, that's not very practical. I've heard chrome is public domain. Do they have a better, stand alone js engine, and might they, or someone else, offer some dom support that we could use, assuming it can be disentangled from the screen or other representations? Even if we have to take the code and mangle it, rather than using a clean library with a published api, it still might be worth it. A lot of code goes into a browser. But if our approach, mozjs24 with a hand crafted dom on top, turns out to be the best way, then I am willing to march on.
Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
