Using Plugins

Difference (from prior major revision)

Changed: 1c1

< All plugin modules require that the core module be loaded in order to work. These modules can't be used with earlier versions of overlib. In all cases, the core module is loaded first, followed by the modules a user wishes to include on his/her web page, as shown in this code fragment:

to

> All plugins require that the core is loaded in order to work. These plugins can't be used with earlier versions of overlib. In all cases, the core is loaded first, followed by the plugins a user wishes to include on his/her web page, as shown in this code fragment:

Changed: 4c4

< (NOTE: PLUGIN_NAME should be replaced by the name of the appropriate plugin.) Unless otherwise noted below, these additional modules can be loaded in any order.

to

> NOTE: PLUGIN_NAME should be replaced by the name of the appropriate plugin. Unless otherwise noted below, these additional plugins can be loaded in any order.


All plugins require that the core is loaded in order to work. These plugins can't be used with earlier versions of overlib. In all cases, the core is loaded first, followed by the plugins a user wishes to include on his/her web page, as shown in this code fragment:

  <script type="text/javascript" src="overlib.js"></script>
  <script type="text/javascript" src="overlib_PLUGIN_NAME.js></script>

NOTE: PLUGIN_NAME should be replaced by the name of the appropriate plugin. Unless otherwise noted below, these additional plugins can be loaded in any order.



contents
home
manual
support
license
download
plugins