Plugin
Encyclopedia : P : PL : PLU : Plugin
A plugin (or plug-in) is a computer program that interacts with a main application (a web browser or an email program, for example) to provide a certain, usually very specific, function.
Typical examples are plugins that
- read or edit specific types of files (for instance, multimedia files)
- encrypt or decrypt email (for instance, PGP)
- filter images in graphic programs
Plugins are slightly different from extensions, which modify or add to existing functionality. The main difference is that plugins generally rely on the main application's user interface and have a well-defined boundary to their possible set of actions. Extensions generally have fewer restrictions on their actions, and may provide their own user interfaces. They sometimes are used to decrease the size of the main application and offer optional functions. Mozilla Firefox uses a well-developed extension system to reduce the feature creep that plagued the Mozilla Application Suite.
Perhaps the first software applications to include a plugin function were HyperCard and QuarkXPress on the Macintosh, both released in 1987. In 1988, Silicon Beach Software included plugin functionality in Digital Darkroom and SuperPaint, and the term plug-in was coined by Ed Bomke. These days, plugins are typically implemented as shared libraries that must be installed in a place prescribed by the main application. HyperCard supported a similar facility, but it was more common for the plugin code to be included in the HyperCard documents (called stacks) themselves. This way, the HyperCard stack became a self-contained application in its own right, which could be distributed as a single entity that could be run by the user without the need for additional installation steps.
Open Application programming interfaces (APIs) provide a standard interface, allowing third parties to create plugins that interact with the main application. A stable API allows third-party plugins to function as the original version changes and to extend the lifecycle of obsolete applications. The Adobe Photoshop and After Effects plugin APIs have become a standard and been adopted to some extent by competing applications. Other examples of such APIs include Audio Units and VST.
Implementation
Examples
Many professional software packages offer plugin APIs to developers, in order to increase the utility of the base product. Examples of these include:- Eclipse
- GStreamer multimedia pipe handler
- jEdit Program Editor
- NetBeans plug-in modules
- Winamp, foobar2000 and XMMS
See also
Shared libraryExternal links
- [Browser Plugin Penetration Stats (According to Macromedia)]
- [Browser Plugin For Delivery of Software Applications]
- [PluginsWorld.com - Directory of plugins]
- [Toolfarm.com - Resource for visual effects plugins]
- [Java Plugin Framework (JPF)]
From Wikipedia, the Free Encyclopedia. Original article here. Support Wikipedia by contributing or donating.
All text is available under the terms of the GNU Free Documentation License See Wikipedia Copyrights for details.