github/atom
1
1
Fork 0
mirror of https://github.com/atom/atom.git synced 2026-04-06 03:02:13 -04:00
Code Issues Packages Projects Releases Wiki Activity

Fix docs

Browse Source
This commit is contained in:
Ben Ogle
2013-10-21 16:24:29 -07:00
parent 71a24ec49b
commit 8ac84359b1
1 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
src/package-manager.coffee
View File

@@ -11,13 +11,13 @@ Packages have a lifecycle
* Every package (except those in core.disabledPackages) is 'loaded', meaning
`Package` objects are created, and their metadata loaded. This includes themes,
as themes are packages
* Each non-theme package is 'activated', meaning its resources are loaded into the
* Packages and themes can be enabled and disabled, and
TODO:
* test that it doesnt activate all the theme packages
* originally disabled packages can be enabled, and loaded without reloading
* config.observe the core.disabledPackages
* The ThemeManager.activateThemes() is called 'activating' all the themes, meaning
their stylesheets are loaded into the window.
* The PackageManager.activatePackages() function is called 'activating' non-theme
package, meaning its resources -- keymaps, classes, etc. -- are loaded, and
the package's activate() method is called.
* Packages and themes can then be enabled and disabled via the public
.enablePackage(name) and .disablePackage(name) functions.
###
module.exports =
class PackageManager
@@ -39,11 +39,13 @@ class PackageManager
setPackageState: (name, state) ->
@packageStates[name] = state
# Public:
enablePackage: (name) ->
pack = @loadPackage(name)
pack?.enable()
pack
# Public:
disablePackage: (name) ->
pack = @loadPackage(name)
pack?.disable()