Mozilla applications come with integrated add-on managers that, similar to package managers, install, update and manage extensions. Extensions comprise a subtype, albeit the most common and the most powerful one. "Add-on" can refer to anything that extends the functions of a Mozilla application. In Mozilla Foundation definitions, the words "add-on", " extension" and "plug-in" are not synonyms. Mozilla definition Main page: Software:Add-on (Mozilla) Programs may also implement plug-ins by loading a directory of simple script files written in a scripting language like Python or Lua. 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. HyperCard supported a similar facility, but more commonly included the plug-in code in the HyperCard documents (called stacks) themselves. Programmers typically implement plug-ins as shared libraries, which get dynamically loaded at run time. 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. Plug-ins depend on the services provided by the host application and do not usually work by themselves. 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. ( Browser extensions, which are a separate type of installable module, are still widely in use.) Examples include the Adobe Flash Player, a Java virtual machine (for Java applets), QuickTime, Microsoft Silverlight and the Unity Web Player.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |