Debugger Architecture: Difference between revisions

Debugger Architecture (view source)

520 bytes added , 13 January 2012

no edit summary

Confirmed users

231

edits

Revision as of 16:28, 13 January 2012 (view source) Past (talk \| contribs) No edit summary ← Older edit		Revision as of 16:37, 13 January 2012 (view source) Past (talk \| contribs) No edit summary Newer edit →
Line 13:		Line 13:
	== The Debugger UI ==		== The Debugger UI ==

	The client part of the client-server architecture (modulo the dbg-client.jsm library) resides in browser/devtools/debugger. There we can find the DebuggerUI.jsm module that serves as the main entry point from the browser to the Script Debugger		The client part of the client-server architecture (modulo the dbg-client.jsm library) resides in browser/devtools/debugger. There we can find the DebuggerUI.jsm 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, debugger.xul loads two more scripts, debugger.js and debugger-view.js. debugger.js contains the controller functions, while debugger-view.js contains the view functions in a traditional MVC separation. In other words, debugger-view.js handles all things visual and debugger.js mediates between user actions and protocol messages to control the debugged script.