DaveGee wrote:This is just a rough idea but I think it's nice and clean and makes for pretty easy backup and installs with everything being self contained and located in the web servers 'home' directory in a subdirectory called /plugins or /plugs as in the example below.
This looks good. I need to think about how this applies to the bigger picture of future plugins that add custom hardware support and UI to Indigo itself. In those cases there might be AppleScript, .nib's, etc., that Indigo needs to load as well, which might make moving the plugin folder up a level (into Indigo 2 instead of IndigoWebServer) a good idea. For example, if someone wanted to add support for the Elk alarm system they could potentially want to:
- Add a new Device type and Device dialog NSView nib
- Add new Action types and Action panel NSView nib
- Add Control Page icons, new Control Page control types for the Control Page Editor along with NSView nib to edit its properties
- Add Control Page web handler function for rendering control HTML/JS
Regardless, this is exactly what I was thinking we need to do -- localize all of the plugins to a particular folder with a specific structure.
Matt