We'd like to get some feedback from the teeming masses about a topic we're discussing regarding allowing others to enhance Harmony.
One approach, which we call "coating", is to provide a 'sandbox' in which almost anyone could overlay any given Harmony screen with one or more buttons, and tie them to commands already present in our app.
If someone wants to add buttons for skip to and skip back to the "H" screen, they could, since the commands are there even if the screen doesn't have buttons for that.
For skip ahead, you'd define the screen, button location and size, a graphic file, and that it would emit command+n once when tapped.
If you want to cover buttons you don't want to see, or redefine one by covering it with a clear button, you could do that too.
You could also place a graphic image and display text retrieved from another application or the system. For example, get the temperature from hardware that has Applescript support in its sofware.
Coating isn't sufficient to add new features to Harmony, by design. For that you'll need to understand more about Harmony's design. We do have a longer term direction to make it extensible by developers using XML and Applescript.
But is coating something that's useful enough, and safe enough, that it would be a major value-add to Harmony? We'd like to get your feedback and suggestions.
A few details: The definitions would be in a text file, the format of which would be XML or possibly comma separated values (CSV). We don't plan to have a tool to help create the text file that holds the coating instructions. We'd provide an example and instructions.