[Livin]

@Livin: I'm not quite sure I understand what you mean by 'user extensible'. Is there a way you can give me an example of what you mean?

Definitely

Most HA/event systems have some method of bi-direction communications, which is perfect for true integration.

... connection type like EventGhost (great back-end automation tool for complex HTPC/HA) has:
TCPEvents : A better Network Event Receiver/Sender plugin
WebSockets

OR

... connection-less ability like simply sending/receiving commands over HTTP using web servers, then parsing the payload for the needed data.


As basis for the example, lets use the screenshot you posted on Post #1, the Dashboard view.
- it is broken into sections. The user would have the ability to add one or more custom sections specific to their needs.
- each section would be defined by a set of XML files or whatever you deem best for your app - this is to define any static text, buttons, notifications, item ordering, etc) and then can be dynamically defined based on notifications/communications from external systems (other apps like: EventGhost, HomeSeer, or whatever.

External systems would send your app the notification via a formatted and/or defined payload (you define and publish) - your app would then parse the payload and turn it into status text, buttons, commands, images, etc based on what was parsed - and place it in the user defined sections on the dashboard.

payload examples for Home Alarm System...

Simple Status Text and Image

button type = status
button background = "C:\images\backgrounds\alarm"
text string = "Armed"
status image = "C:\images\alarm_red.jpg",32x32

... this will simply show the status of the alarm system


Control Button with Text, Status Image, and Command back to Alarm System

button type = toggle
button command = "http://homeserver:8080/device=alarm&command=disarm"
button background = "C:\images\backgrounds\alarm"
text string = "Armed"
status image = "C:\images\alarm_red.jpg",32x32

... this will create a button that shows the Alarm as 'armed' but when the button is pushed will send the command to the alarm system (HA system) to 'disarm'
... then, once the alarm is disarmed, the HA system would send another notification and the button would change to suit the new status, and new command needed to 'arm' it.


Does this help explain - there are tons of possibilities for use cases here.