Developers.

Allows you to add messages to the games notification area.

Register the library in your code file:

Lua Code:

local libNotification = LibNotification

After your addon is initialized call the libraries CreateProvider() function.

Lua Code:

local provider = libNotification:CreateProvider()

The provider will have a notifications table. This is where you put your messages.

Lua Code:

provider.notifications

Messages need to be written in a certain format, the following is an example:

Warning: Spoiler

Lua Code:

local msg = {
    dataType             = NOTIFICATIONS_ALERT_DATA,
    secsSinceRequest     = ZO_NormalizeSecondsSince(0),
    note     = "Use it wisely",
    message = "Add custom notification messages",
    heading = "LibNotifications",
    texture = "/esoui/art/miscellaneous/eso_icon_warning.dds",
    shortDisplayText         = "Custom Notification",
    controlsOwnSounds         = true,
    keyboardAcceptCallback     = OnKeyboardAccept,
    keyboardDeclineCallback    = OnKeyboardDecline,
    gamepadAcceptCallback     = OnGamepadAccept,
    gamepadDeclineCallback    = OnGamepadDecline,
    data = {}, -- Place any custom data you want to store here
}

So what do all of those keys do?

dataType's and what buttons are available with them:
NOTIFICATIONS_REQUEST_DATA -- note, accept (checkmark), & decline (x) buttons
NOTIFICATIONS_WAITING_DATA -- shows a spinning wheel (no message text, note, accept, or decline)
NOTIFICATIONS_ALERT_DATA -- note & delete (x) buttons

secsSinceRequest: Is used for sorting the notifications (in descending order). You should use ZO_NormalizeSecondsSince(0), which is the seconds since login. This will keep the notifications in order, newest notifications on top. Note since it sorts in descending order the keyName is misleading. Its not really the seconds since request, ZOS named it, not me.

note: In keyboard mode this is the tooltip text for the note button. If you leave out the note, the note button will be hidden automatically. In gamepad mode it is just displayed as text after the message. See gamepad picture for an example.

message: The message text to be displayed.

heading: In keyboard mode this is the heading text to be displayed (next to the icon). In gamepad mode this is used as a category header for all messages displayed by your provider. See gamepad picture for an example. *Warning: You can NOT display more than one heading/category at a time in gamepad mode (without creating multiple providers). In gamepad mode the category heading will be named after this key/value from the FIRST msg in your list. Changing the heading name on other messages in your notifications table will do nothing, unless you delete the first message and some other message becomes the first in the list. Then that heading will be used. This is not my doing, this is the way ZOS wrote the gamepad notification system.

texture: The texture to be displayed. In keyboard mode it is 32 x 32.

shortDisplayText: Only used in gamepad mode. This is the text that is displayed under the category/heading, next to the texture, for your message. See gamepad picture for an example.

controlsOwnSounds: When false the game will automatically play the SOUNDS.ACCEPT, SOUNDS.DECLINE sounds when the buttons are clicked. When set to true no sounds will be played so that you can play your own click sounds.

The reason for separate keyboard/gamepad callbacks is because sometimes different code needs to be run for keyboard/gamepad mode. If your code can use the same callback for both just set the keyboard/gamepad callbacks to the same callback function.
keyboardAcceptCallback: Accept callback function for keyboard mode.
keyboardDeclineCallback: Decline callback function for keyboard mode.
gamepadAcceptCallback: Accept callback function for gamepad mode.
gamepadDeclineCallback: Decline callback function for gamepad mode.

data = {} There are other key/value pairs that are used by the game inside the message table. To avoid interfering with key names used by the game place any custom data you want to store with your message in this table.

Create your messages and add them to your provider notifications table:

Lua Code:

table.insert(provider.notifications, msg)

It is up to you to add & remove your messages from the notifications table when you are done with them.
WARNING:
The table must be numerically indexed & there can be no missing indices. I recommend using table.insert() & table.remove() for adding/removing messages

After you are done making changes Adding/Removing messages, call the update function:

Lua Code:

provider:UpdateNotifications()

Try not to call this anymore than necessary.
It fires off ALL of the BuildNotificationList functions for every notification provider in the game!

Just In case anyone needs to know for creating/selecting icons. The icon on the keyboard rowControl is 32 x 32.

The code can be found on github: https://github.com/sirinsidiator/ESO-LibNotification.