> Here is my JS console code. Wow! First of all, I don't undderstand that javascript at all, but I see that it works, so on we go. It is now included in startwindow.js as per the latest push. You don't have to type an extra command; the ok (object keys) function is there.
Type jex (javascript executions) from a running web page to enter this mode. I very much didn't want to type jex each and every time, so it's a mode, like a in the editor. Type . by itself to exit this mode. So now you can look at and change variables, and use the ok function for the members of any object. alert(ok(document.body)); But there are two major things to fix. 1. All the gc variables under document are damn annoying. These are artificial placeholders in edbrowse to protect certain things from garbage collection. They could all be members of the object document.gc$, instead of variables under document. That's not hard to do but not trivial, and must be done in both decorate.c and jseng-moz.cpp. 2. The real nuisance is having to type alert all the time. When you run a js shell, from mozilla or v8 or whomever, the result of your entered command is displayed if there is a result. You don't have to type alert all the time. This is obviously what we want. So javaParseExecute should return a string if the executed script has a result, a string we can print if not null, or perhaps a new function javaParseExecuteResult for this purpose. Then this feature won't be quite so painful to use. If you set db3 before you enter then you will see syntax errors etc, instead of just silence, assuming your entered command worked when maybe it didn't. this is not documented yet, because I don't think we have the final interface or all the details worked out. But we all wanted it, and it was so damn easy to do, especially since Kevin handed me the ok() function, so why not move forward on it. If someone wants to address either of the shortcomings above, or suggest improvements, let me know. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
