Congratulations! You've just taken the first major step in writing a custom plugin for the Elgato Stream Deck.
Within the directory from which you are reading this file, there exist a few other necessary files. These are:
PhilipsHueSdPlugin.csproj: The C# project file used to build the pluginProgram.cs: The code for the application which will be called by the Stream Deck software when loading and running your plugin.DefaultPluginAction.cs: The file in which the functionality of the first (default) action for the plugin will be written. This file provides a basic implementation of an action for your plugin, following a pattern which can be repeated.
Due to the multi-platform target of the Stream Deck, when specifying filesystem paths which will be used at runtime (images, other assets), use the POSIX/Unix standard forward slash (/) as the directory separator.
Do this path/to/my/assets
Instead of path\to\my\assets
The manifest.json file (also referred to as the manifest or manifest file) is the mechanism used by the Stream Deck SDK to uniquely identify plugins, their actions and other parameters.
Your first step should set a value for both the Author and the URL values, representing you and your plugin.
The following are the base set of images/icons which are needed for the plugin. While defaults have been provided, they should be changed to help distinguish your plugin and its action(s) from others.
Unless otherwise noted, image assets should all be in the "Portable Network Graphics" (PNG) format.
Note: While all efforts have been made to ensure the correctness of this information, please refer to the official Style Guide and Manifest file definition for the latest and most up-to-date information.
Path to property in manifest.json file: Icon
The category icon, identified by the Icon property in the manifest, is the primary visual identifier for your plugin. It is also used to display information about your plugin in the More Actions... list, which displays the list of available plugins to download to uses, as well as the category (group) icon in the Actions list if your plugin supports more than a single action.
The Icon property in the manifest represents the base file name of the image, without a file extension. For example, if your icon's file name is myPluginIcon.png, you would set the value as myPluginIcon.
There are two of these files necessary. A default one for a regular, non-scaled (high-DPI) display, and another for scaled display. The default icon should be 28 pixels squared (28x28px), and named with the base file name and extension. i.e. _PluginName_.png.
The other file, for high-DPI displayes, must be 56 pixels squared (56x56px), and the value @2x appended to the file name, before the extension. i.e. [email protected]
Path to property in manifest.json file: Actions[x].Icon
The action image, for which there is one for each action available from the plugin, is the icon which helps identify the action item in the Actions list, within the category (group) defined by your plugin. Just as with the Category Icon, when setting its value in the manifest, do not specify an extension.
Each element in the Actions element of the manifest has an Icon property which must be set (which one possible exception - see below). While not strictly necessary, each action should have its own, distinct icon for its visual identity. Per the current specifications, the Action Image should be a single color -
#d8d8d8 (rgb(216,216,216)).
Again, just as with the Category Icon, two separate copies of this file are needed, with the same naming rules but different sizes; a default one for a regular, non-scaled (high-DPI) display, and another for scaled display. The default icon should be 20 pixels squared (20x20px), and preferably named in a manner in which it can be easily related to its action, such as actionIcon.png. When setting its value in the manifest, here too specify only the file name, and do not include the etension.
The other file, for high-DPI displayes, must be 40 pixels squared (40x40px), and the value @2x appended to the file name, before the extension. i.e. [email protected]
An Action item is not required to have an icon specified (but still can) if its VisibleInActionList property in the manifest is set to false.
Path to property in manifest.json file: Actions[x].States[y].Image
The Key Icon is the icon which is displayed on the key(s) to which is is assigned on the Stream Deck, as well as within the Stream Deck software during configuration. If your action supports multiple states, the Key Icon will be displayed when its assigned state is active. Each action hast as least one state, and as of this time, has at most two states.
Once again, just as with the Category Icon and Action Image, when setting its value in the manifest, do not specify an extension.
Again, just as with the Category Icon and the Action Image,two separate copies of this file are needed, with the same naming rules but different sizes; a default one for a regular, non-scaled (high-DPI) display, and another for scaled display. The default icon should be 72 pixels squared (72x72px). Again, it should preferably named in a manner in which it can be easily related to either the action or state is represents, such as actionIconButton.png or actionIconActive.png.
Of course! First, congratulations on getting your first action for your Stream Deck plugin working! To allow your plugin to do more, you will need to create (and implement) a new Action definition. Here is how you do this:
- Create a new class (in a new file or an existing one), and make sure it inherits from the
BaseStreamDeckActionclass e.g.:internal class MyNextPluginAction : BaseStreamDeckAction - Implement the required properties and methods, such as
UUID - Register it with the
ConnectionManagerinstance within theProgram.csfile. Look for the.RegisterAction(new DefaultPluginAction()code line, copy it, and change the typeDefaultPluginActionto your new class' name. From the example in step 1, this would look like.RegisterAction(new MyNextPluginAction()). - Add a definition for the new action in the
manifest.jsonfile, ensuring that the value for theUUIDfield in the manifest matches theUUIDproperty of your new class.
That's it! Repeat this process for any additional actions you wish to include and perform as part of your plugin.
Here are some helpful references for both this template and the Stream Deck: