Developers:

     The lindyFrame application comes with a pre-install plugin called HTMLViewer that serves as an example for developers in creating modules for the framework. The HTMLViewer plugin is a simple hyper-text browser that loads a HTML tutorial when lindyFrame first runs for review. That tutorial can be used for a basis of creating your own plugins for deployment with the framework. The docs directory of the lindyFrame installation also holds the tutorial files so that viewing can be accomplished locally with any desired web browser.

Deployment:

     The tutorial discusses the decision a developer should make when designing a plugin for the specification of resource loading. A local or network deployment requires no special treatment, but a HTTP repository will need a local document installed on the server to inform the lindyFrame framework of the available plugins for installation. That file must have the name, lindyframe_plugin_list.xml and be compressed in the .gz format. Again the docs directory of the installation contains an example HTTP repository structure for deployment of the HTMLViewer to a web server. The temp directory need not be included with the setup since it only serves to store the plugin list file before compression.

Plugin Management:

     All plugins are controlled through the Tools | Plugin Management interface of the framework. Local plugins are loaded via the install button. Network or HTTP plugins are loaded by first creating a repository, +. If successful then plugins will be listed in the new repository tab, highlight one then again use the install button. To remove a repository select its tab and use the - tab. The Manage tab displays current loaded plugins and may also be used to remove a selected plugin.