Jump to content

Plug-in (computing)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Laczkó Dávid (talk | contribs) at 10:08, 24 March 2019 (→Mechanism). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Mozilla Firefox displaying a list of installed plug-ins
Look up plug-in or add-on in Wiktionary, the free dictionary.

In computing, a plug-in (or plugin, add-in, addin, add-on, or addon) is a software component that adds a specific feature to an existing computer program. When a program supports plug-ins, it enables customization.

Web browsers have historically allowed executables as plug-ins, though they are now mostly deprecated. (These are a different type of software module than browser extensions.) Two plug-in examples are the Adobe Flash Player for playing videos and a Java virtual machine for running applets.

A theme or skin is a preset package containing additional or changed graphical appearance details, achieved by the use of a graphical user interface (GUI) that can be applied to specific software and websites to suit the purpose, topic, or tastes of different users to customize the look and feel of a piece of computer software or an operating system front-end GUI (and window managers).

Purpose and examples

Applications support plug-ins for many reasons. Some of the main reasons include:

Types of applications and why they use plug-ins:

Mechanism

Example Plug-In Framework

The host application provides services which the plug-in can use, including a way for plug-ins to register themselves with the host application and a protocol for the exchange of data with plug-ins. Plug-ins depend on the services provided by the host application and do not usually work by themselves. Conversely, the host application operates independently of the plug-ins, making it possible for end-users to add and update plug-ins dynamically without needing to make changes to the host application.[11][12]

Programmers typically implement plug-in functionality using shared libraries, which get dynamically loaded at run time, installed in a place prescribed by the host application. HyperCard supported a similar facility, but more commonly included the plug-in code in the HyperCard documents (called stacks) themselves. Thus the HyperCard stack became a self-contained application in its own right, distributable as a single entity that end-users could run without the need for additional installation-steps. Programs may also implement plugins by loading a directory of simple script files written in a scripting language like Python or Lua.

Mozilla definition

Main article: Add-on (Mozilla)

In Mozilla Foundation definitions, the words "add-on", "extension" and "plug-in" are not synonyms. "Add-on" can refer to anything that extends the functions of a Mozilla application. Extensions comprise a subtype, albeit the most common and the most powerful one. Mozilla applications come with integrated add-on managers that, similar to package managers, install, update and manage extensions. The term, "Plug-in", however, strictly refers to NPAPI-based web content renderers. Plug-ins are being deprecated.[13]

History

Plug-ins appeared as early as the mid 1970s, when the EDT text editor running on the Unisys VS/9 operating system using the UNIVAC Series 90 mainframe computers provided the ability to run a program from the editor and to allow such a program to access the editor buffer, thus allowing an external program to access an edit session in memory.[14] The plug-in program could make calls to the editor to have it perform text-editing services upon the buffer that the editor shared with the plug-in. The Waterloo Fortran compiler used this feature to allow interactive compilation of Fortran programs edited by EDT.

Very early PC software applications to incorporate plug-in functionality included HyperCard and QuarkXPress on the Macintosh, both released in 1987. In 1988, Silicon Beach Software included plug-in functionality in Digital Darkroom and SuperPaint, and Ed Bomke coined the term plug-in.[citation needed]

See also

References

  1. ^ "PCSX2 - The Playstation 2 emulator - Plugins". pcsx2.net. Retrieved 2018-06-10.
  2. ^ Bernert, Pete. "Pete's PSX GPU plugins". www.pbernert.com. Retrieved 2018-06-10.
  3. ^ Team, Demul. "DEMUL - Sega Dreamcast Emulator for Windows". demul.emulation64.com. Retrieved 2018-06-10.
  4. ^ "Android Emulator Plugin - Jenkins - Jenkins Wiki". wiki.jenkins.io. Retrieved 2018-06-10.
  5. ^ "KDE/dolphin-plugins". GitHub. Retrieved 2018-06-10.
  6. ^ "Cemu Plugin Loader Makes It Easy To Load In DLL Plugins". One Angry Gamer. 2017-07-14. Retrieved 2018-06-10.
  7. ^ "OpenEmu/SNES9x-Core". GitHub. Retrieved 2018-06-10.
  8. ^ "Recommended N64 Plugins". Emulation General Wiki. Retrieved 2018-06-10.
  9. ^ "Playstation plugins & utilities!". www.emulator-zone.com. Retrieved 2018-06-10.
  10. ^ "PS3 Homebrew Apps / Plugins / Emulators | PSX-Place". www.psx-place.com. Retrieved 2018-06-10.
  11. ^ Mozilla Firefox plugins – Description of the difference between Mozilla Firefox plugins and extensions under the general term add-on.
  12. ^ Wordpress Plug-in API – Description of the Wordpress Plug-in architecture.
  13. ^ Paul, Ian. "Firefox will stop supporting plugins by end of 2016, following Chrome's lead". PCWorld. IDG. Retrieved 20 October 2016.
  14. ^ EDT Text Editor Reference Manual, Cinnaminson, New Jersey: Unisys Corporation, 1975
Retrieved from "https://en.wikipedia.org/w/index.php?title=Plug-in_(computing)&oldid=889228766"