REMOVE INDIGO 7 PLUGIN INSTALL
REMOVE INDIGO 7 PLUGIN FULL

It creates and manages C++ objects (and bridges them to native Python objects) that represent the Indigo Object Model ( IOM), deals with communication with the IndigoServer, and makes sure that the IOM is kept in sync with the IndigoServer. But, fear not, the IPH hides all this complexity from you. The IPH communicates with the IndigoServer through the XML interface the IndigoServer provides. Each plugin will have it’s own instance of an IPH as well, so one plugin isn’t likely to bring down another or the IndigoServer. Each Server Plugin will be launched in a special application called the Indigo Plugin Host (IPH). The keys in this file will help Indigo understand what functionality your plugin provides, what it’s name and version number are, etc.Įditing a plist file isn’t difficult since it's just a text XML file that looks like this:Ĭom.yourorgidentifier.yourpluginidentifierīefore we get to the specifics, let’s describe the process by which your plugin will get executed. The ist file is a standard XML property list file that contains several important key/value pairs. There’s only one file that’s directly inside the Contents folder and it’s required (read very important). So, why did we go to the trouble of using the bundle format when there's just a file and a couple of folders? Because in future versions, we're going to add capabilities to the plugin bundle. This is the standard macOS bundle construction, so we decided to follow the pattern. All other files/folders are inside that folder. Let’s go through each folder/file and discuss what it does.įirst, though, you can see that there is only one top-level folder in the bundle - Contents. In this window, you can create the folder structure above to have the elements that your plugin will need. To get to the contents, right click on it and select Show Package Contents and it will open a separate window that is, in fact, just a new Finder window just like any other. Click “Add”, and now your folder appears as a file. The Finder will prompt you about adding the extension.

REMOVE INDIGO 7 PLUGIN INSTALL

It’s moved around and treated as a single file, and all the user has to do to install your solution is to double-click it in the Finder and Indigo will install and enable it for you.Ĭreating a bundle is really easy: just create a folder in the Finder and end the name with. The first thing you’ll notice is that this is actually a real Finder bundle - so it appears to be a single file called Example.indigoPlugin. indigoPlugin), which has a very specific structure to encapsulate everything that a plugin needs to perform it's functions: We created a macOS Finder bundle type, the Indigo plugin bundle (. If any of the API tables in the documentation don't have a version number you can assume that the feature is available in API version 1.0 and later.īack to Top Indigo Support Folder Structure See the API version chart to see which API versions were released in which Indigo version.

The major number (X.0) will only be incremented when we do something that will break backwards compatibility. As of Indigo 5 v 5.1.2, we've begun incrementing the API minor version number (1.X) whenever we add new features. Up until Indigo 5 v5.1.1, the API remained 1.0 and the documents were just updated with new features (which could lead to incompatible features if using an older release of Indigo). Let’s start by first looking at the Application Support folder structure which the Indigo installer creates.Ī note about version numbers: As we've revised the API and added features, we've incremented the API version number. To deliver this additional functionality, we created the Indigo plugin bundle. Someone with sufficient skills can implement support for any kind of device and have them integrated into the Indigo UI as first-class citizens.

REMOVE INDIGO 7 PLUGIN FULL

This server API allows users and 3rd party vendors to implement their own functionality in Python with full access to all the objects and events that Indigo understands (referred to as the Indigo Object Model, or IOM). With Indigo 5.0, we added a new server plugin API that allows 3rd party developers to more natively add devices, triggers, and actions to Indigo. Later, the Indigo Web Server was added along with the IWS plugin and the ability to add custom images. Indigo has a long history of extensibility - AppleScript Attachment scripts were available from the start (which will be deprecated in Indigo 7.2 and later).

Remove indigo 7 plugin