In Nexista there are currently two types of plugins, and I'm going to rename one of them to extensions. Here's an explanation of the new distinction:
Plugins
These are application specific actions. Simply put. They are called the same way as actions but are shipped with applications rather than the default Nexista set. One example would be a plugin that create a thumbnail of an image. Plugins allow Nexista to do more, but don't change how Nexista runs.Extensions
Extensions are more substantial changes to the behavior of Nexista. They can be located anywhere, and are defined in the configuration process. They register handlers for altering the initialization and processing of the Nexista pipeline. Extensions change they way Nexista works. One example is the development buffer which allows the user to view the flow XML document above the page output, or another to rewrite request variables prior to insertion into the flow document.What does this change affect?
* foundry.php - I'm retaining the plugins code for a few months* configuration files - I'm now in the process of changing the plugins sections to extensions* The build/prepend directive will be deprecatedSpeaking of foundry.php, I'd still very much like to leverage phing more in Nexista, but I just haven't found the time.