We're moving their physical location into a new Indigo plugin bundle that will be much more user friendly when it comes to installing additional functionality (plugins, scripts, images, etc). IWS Plugins will still continue to use the same basic directory structure, cherrypy and the cheetah template engine (we might upgrade those to newer versions). We haven't yet determined if we're going to require them to use the new python object model or whether we'll support the older-style object access as described by the current plugins.
So, bottom line - if your plugin doesn't rely heavily on access to Indigo objects, then the change (if any) will be small. An example of this would be the
LWC Indigo Web Server Plugin. If we require switching to the new object model from the current access methods, it would only have to have one line changed. This is what the current plugin uses to update the variable value:
- Code: Select all
cherrypy.server.indigoDb.VariableSetValue(cherrypy.server.indigoConn, "VariableName", "Value")
This is what it would look like using the new object model:
- Code: Select all
indigo.variable.setValue(varReference, "Value")
Don't want to get into any details yet, but that gives you a sense of how things will change. If, however, you're extensively asking Indigo for data, then the changes might be more substantial. Still probably not huge, but more than just a line or two.