$ npm install microplugin$ bower install microplugin
Using the provided mixin, extend your function with the API for declaring and loading plugins:
That's it for integration! Now you can selectively load the plugins on an instance-by-instance basis.
var editor =plugins: 'links''images';
initializePlugins() method sets up the plugin system and loads a list of plugins (with options). It accepts the list in three styles, depending on your preference.
List (no options)
List (with options)
name: "plugin_a" options: /* ... */name: "plugin_b" options: /* ... */name: "plugin_c" options: /* ... */
Hash (with options)
"plugin_a": /* ... */"plugin_b": /* ... */"plugin_c": /* ... */
Plugins aren't extravagant—they are barebones by design. A plugin is simply a function that gets called when an instance of your object is being constructed. Within that function, you can manually override methods, set up event listeners, etc. The
this context will be the instance of your object.
Plugins can declare dependencies to other plugins (and use any exports they provide) through the
Sets up all methods on the function and its prototype for defining and loading plugins.
Declares a new plugin with the specified name.
Loads a plugin as a dependency and returns whatever it exports (if anything).
Initializes the plugin system and loads a list of plugins with the provided options. The "plugins" argument can be in a variety of formats.
Copyright © 2013 Brian Reavis & Contributors
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.