Debugger Architecture: Difference between revisions

No edit summary
Line 13: Line 13:
== The Debugger UI ==
== The Debugger UI ==


The client part of the client-server architecture (modulo the <tt>dbg-client.jsm</tt> library) resides in <tt>browser/devtools/debugger</tt>. There we can find the <tt>DebuggerUI.jsm</tt> module that serves as the main entry point from the browser to the Script Debugger, as well as the home for supplementary functions that interface with the rest of the browser (storing preferences, loading files, etc.). The main UI document, <tt>debugger.xul</tt> loads two more scripts, <tt>debugger.js</tt> and <tt>debugger-view.js</tt>. <tt>debugger.js</tt> contains the controller functions, while <tt>debugger-view.js</tt> contains the view functions in a traditional MVC separation. In other words, <tt>debugger-view.js</tt> handles all things visual and <tt>debugger.js</tt> mediates between user actions and protocol messages to control the debugged script.
The client part of the client-server architecture (modulo the <tt>dbg-client.jsm</tt> library) resides in <tt>browser/devtools/debugger</tt>. There we can find the <tt>DebuggerUI.jsm</tt> module that serves as the main entry point from the browser to the Script Debugger, as well as the home for supplementary functions that interface with the rest of the browser (storing preferences, loading files, etc.). The main UI document, <tt>debugger.xul</tt> loads two more scripts, <tt>debugger.js</tt> and <tt>debugger-view.js</tt>: <tt>debugger.js</tt> contains the controller functions, while <tt>debugger-view.js</tt> contains the view functions in a traditional MVC separation. In other words, <tt>debugger-view.js</tt> handles all things visual and <tt>debugger.js</tt> mediates between user actions and protocol messages to control the debugged script.
Confirmed users
231

edits