Places:Controller: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 7: | Line 7: | ||
The Places Controller is implemented in the <code>PlacesController</code> object, which lives in <code>browser/components/places/content/controller.js</code> and is included by <code>chrome://browser/content/places/places.js</code> | The Places Controller is implemented in the <code>PlacesController</code> object, which lives in <code>browser/components/places/content/controller.js</code> and is included by <code>chrome://browser/content/places/places.js</code> | ||
The controller is the one constant factor about any Places instantiation. The <code>PlacesController</code> object is required by the views. You must include this script file for | The controller is the one constant factor about any Places instantiation. The <code>PlacesController</code> object is required by the views. You must include this script file for things to work. | ||
= Functionality = | = Functionality = | ||
Revision as of 01:33, 31 March 2006
Background
The controller is part of the Places System's MVC architecture. The controller is responsible for enabling, disabling and performing commands based on the state of a PlacesView.
Code Location
The Places Controller is implemented in the PlacesController object, which lives in browser/components/places/content/controller.js and is included by chrome://browser/content/places/places.js
The controller is the one constant factor about any Places instantiation. The PlacesController object is required by the views. You must include this script file for things to work.