On Apr 6, 5:51 pm, Canny <[email protected]> wrote: > I have some ideas about creating new firebug debugging features. For > example, given a downloaded web page, beautify (www.jsbeautifier.org) > various contents (html/javascript/css) before the user is allowed to > debug the web application. This should be very useful to work with > very "ugly"-formatted third party contents. As another example, I want
To be successful you have to intercept the js code before firefox compiles it. You can get most cases by intercepting net traffic (see net.js and component/firebug-channel-listener.js or firebug-http- observer.js) but recognizing JS requires parsing HTML at least to some simple degree. > to develop an automated tool that produces traces (an example trace > could be the intermediate presentation of all of the executed > javascript bytecode instructions along with their parameter values) You can trace the function calls easily but producing a useful UI for a complex application is difficult. We have no access to the bytecodes. > while executing any Javascript code in the current page. This can be a > useful feature in terms of reverse engineering existing web > applications, (provided that some code is intentionally obfuscated to > hide something from the user). Many obscuring tools have decompilers, so integrating them with firebug might be an easier goal. > > Although I have been using Firebug for a long time, I am pretty much a > rookie with respect to Firebug development. Can anyone give some > suggestions or helpful pointers on how to implement the ideas above? I > am aware of the blog "Software is hard", that is definitely an > excellent source of information and I read relevant posts there. > However, to a newbie, the amount of knowledge available on browser > extension development sometimes seems very insufficient, whereas > sometimes seems overwhelming. See also http://getfirebug.com/wiki/index.php/Firebug_Internals > > Does it really sound like a daunting task too challenge to be > accomplished for a rookie developer? Or could you help to point out > the subset of things I should probably know immediately to implement > the simple ideas above? Deobscuring intentionally obscured code is rocket science. Uncompressing compressed code is probably doable to a limited level of satisfaction. You might look at the google project closure http://code.google.com/closure/compiler/ jjb > > Thank you very much! > > --Yan -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
