In the "Actions" branch I have done the initial development for notifs with actions. But there is a problem: the callback to the original script.

It is asynchronous to the creation of the notif, so simply returning the text is a no-go.
The second idea is to return an object:

{
notification: <notification_element>
actions:
    [
        <action_element_one>,
        <action_element_two>
    ]
}

The creating script can then add eventlisteners to the whole notification or actions at will. Even for instance using hover to show extra info. That is open to the dev to work on.

One problem: return does not work.
The callback function of CommandManager.execute is never called.

Please advise..

Add an accent colour that will be shown in the notif in a dot or border.

Developers could use this to identify their extension or specific notifs like red for a warning.

Register every notification in the settings.json so the user has a history of it's notifications.

Maybe we can limit the number of notifications to 100.

Related to commit: ff283f8

Need to complete #11 first

Brackets has it's own server running, but on a random port

This could also be done by simply adding an image tag with a base64 encoded image in the title.

How can we create support (a userbase) for this extension? It is dependent on use by other extensions.

We can create our own extensions that implement it, or for instance create issues or pull-requests for other extensions. The last seems a bit spammy, but when it means a genuine improvement I think it's okay.

The callback will be called when the notification has been created, with as parameter the element of the notif.

CommandManager.execute("notifications.notification",
{
    title: "Message title",
    message: "Message body"
    callback:function(element){  /* do stuff */  }
});

This can be used by the firing script to manipulate the notification afterwards. Like updating information or adding customized interaction.

Started a document describing different notification types: Wiki page