Difference between revisions of "Plugin"
(Added topic about plugins in Gecko) |
|||
| Line 1: | Line 1: | ||
=Short description= | =Short description= | ||
Plugin is a program that interacts and extends functionality of your browser. | Plugin is a program that interacts and extends functionality of your browser. | ||
| + | |||
=Long Description= | =Long Description= | ||
Uses for plugin: | Uses for plugin: | ||
| Line 18: | Line 19: | ||
* Plugins rely on main application to achive set of actions. | * Plugins rely on main application to achive set of actions. | ||
** | ** | ||
| + | |||
| + | ==Plugins in Gecko== | ||
| + | * Plugins increases functionality of Gecko-based browsers. Examples of this includes embedded viewers for Flash/Shockwave and Adobe Acrobat PDFs. | ||
| + | |||
| + | * Plugins are dynamically loaded. | ||
| + | |||
| + | * There are limitationts to plugins (as compared to extensions): they are platform specific so they have to be ported to every OS and processor that you wish to use the plugin on. | ||
| + | |||
| + | * In order to develop plugins for the Gecko engine, you'll need the plugin SDK, which is located in the Mozilla source under mozilla/modules/plugin/tools/sdk. Samples and source code can be viewed via LXR: http://lxr.mozilla.org/seamonkey/source/modules/plugin/tools/sdk/ | ||
=Resources= | =Resources= | ||
| + | http://developer.mozilla.org/en/docs/Gecko_Plugin_API_Reference | ||
http://www.herts.ac.uk/ltdu/technology/what_is_a_plugin.html | http://www.herts.ac.uk/ltdu/technology/what_is_a_plugin.html | ||
| − | |||
http://en.wikipedia.org/wiki/Plugin | http://en.wikipedia.org/wiki/Plugin | ||
Revision as of 10:57, 6 October 2006
Short description
Plugin is a program that interacts and extends functionality of your browser.
Long Description
Uses for plugin:
- read certain types of files eg audio/video
To install a plugin in mozilla, usually the package is extracted in a plugin sub directory When the package is installed the browser has to be restared to activate the plugin. eg. in Linux its located in ~/.mozilla/plugins/
Plugin is an addon to the main application that provides the service. Plugins depand on the core application and do not work by themselves.
The advantage of plugins is that it allows to add/update functionality without changing the main application.
- Plugins are different from Extensions:
- Extensions modify existing functionality and can work independent of main application
- Extensions offered to decrease the size of main application and offer optional functions
- In mozilla, extensions reduce feature creap
- Plugins rely on main application to achive set of actions.
Plugins in Gecko
- Plugins increases functionality of Gecko-based browsers. Examples of this includes embedded viewers for Flash/Shockwave and Adobe Acrobat PDFs.
- Plugins are dynamically loaded.
- There are limitationts to plugins (as compared to extensions): they are platform specific so they have to be ported to every OS and processor that you wish to use the plugin on.
- In order to develop plugins for the Gecko engine, you'll need the plugin SDK, which is located in the Mozilla source under mozilla/modules/plugin/tools/sdk. Samples and source code can be viewed via LXR: http://lxr.mozilla.org/seamonkey/source/modules/plugin/tools/sdk/
Resources
http://developer.mozilla.org/en/docs/Gecko_Plugin_API_Reference http://www.herts.ac.uk/ltdu/technology/what_is_a_plugin.html http://en.wikipedia.org/wiki/Plugin
