From f6c489879127a87d9a77041a0c3b93e359088d0e Mon Sep 17 00:00:00 2001 From: Neil Dorin Date: Wed, 12 Feb 2020 16:50:43 -0700 Subject: [PATCH] Adds link to plugin diagram --- Plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Plugins.md b/Plugins.md index aadbee3..fe9abcc 100644 --- a/Plugins.md +++ b/Plugins.md @@ -10,7 +10,7 @@ Essentials is meant to be a lightweight framework and an extensible basis for de ## How do Plugins Work? One or more plugins can be loaded to the /user/ProgramX/plugins as .dlls or .cplz packages. When the Essentials Application starts, it looks for any .cplz files, unzips them and then iterates any .dll assemblies in that folder and loads them. Once the plugin assemblies are loaded the Essentials Application will then attempt to load a configuration file and construct items as defined in the file. Those items can be defined in either the Essentials Framework or in any of the loaded plugin assemblies. - -- INSERT PLUGIN DIAGRAM -- +![Architecture drawing](https://pepperdash.github.io/Essentials/Plugin%20Load%20Sequence.png) ## What Must be Implemented in a Plugin for it to Work? All plugin assemblies must contain a static method called LoadPlugin():