Managing toast notifications via a toast adapter and plugins
Toast notifications can be managed via a toast adapter and plugins. A toast adapter can function as an intermediary between a service and an application that interfaces with the Windows toast framework. The service can employ plugins that are configured to send toast requests to the toast adapter. The toast requests can include metadata from which the toast adapter can construct toast content. The toast adapter can then interface with the application to submit the toast content to the Windows toast framework to cause the toast notifications to be displayed. When a user interacts with a toast notification, the arguments that the Windows toast framework provides can be relayed by the application to the toast adapter. The toast adapter may then identify which plugin was the source of the toast notification and provide an indication of the user's interaction with the toast notification to the plugin.
1. A method for managing toast notifications via a toast adapter and plugins, the method comprising:
receiving, at a toast adapter, a first toast request from a first plugin that is integrated into a first service;
in response to the first toast request, generating, by the toast adapter, first toast content; and
providing, by the toast adapter, the first toast content to an application to cause the application to submit the first toast content to the Windows toast framework to thereby cause a first toast notification to be displayed;
in response to a user interacting with the first toast notification, receiving, by the toast adapter and from the Windows toast framework via the application, arguments representing how the user interacted with the first toast notification; and
in response to receiving the arguments, sending, by the toast adapter and to the first plugin, an indication of the user's interaction with the first toast notification.
2. The method of claim 1 , wherein the first toast request includes metadata, and wherein the toast adapter generates the first toast content from the metadata.
3. The method of claim 1 , further comprising:
in response to receiving the arguments, accessing, by the toast adapter, mappings to determine that the arguments pertain to the first plugin.
4. The method of claim 3 , wherein determining that the arguments pertain to the first plugin comprises determining that the mappings associate an identifier that is included in the arguments with an identifier of the first plugin.
5. The method of claim 4 , wherein the identifier that is included in the arguments comprises one of a launch string included in the first toast content or a content identifier of an action included in the first toast content.
6. The method of claim 1 , wherein the first toast request specifies a first context, the method further comprising:
including the first context in the indication of the user's interaction with the first toast notification.
7. The method of claim 1 , wherein the toast adapter generates the first toast content using a contract associated with the first plugin.
8. The method of claim 1 , further comprising:
receiving, at the toast adapter, a second toast request from a second plugin that is integrated into the first service;
in response to the second toast request, generating, by the toast adapter, second toast content; and
providing, by the toast adapter, the second toast content to the application to cause the application to submit the second toast content to the Windows toast framework to thereby cause a second toast notification to be displayed.
9. The method of claim 1 , further comprising:
receiving, at the toast adapter, a second toast request from a second plugin that is integrated into a second service;
in response to the second toast request, generating, by the toast adapter, second toast content; and
providing, by the toast adapter, the second toast content to the application to cause the application to submit the second toast content to the Windows toast framework to thereby cause a second toast notification to be displayed.
10. The method of claim 9 , wherein the first plugin and the second plugin are instances of the same plugin.
11. One or more computer storage media storing computer executable instructions which when executed on a computing device implement a method for managing toast notifications via a toast adapter and plugins, the method comprising:
receiving, at a toast adapter, toast requests from one or more plugins that are integrated into one or more services;
in response to each toast request, generating, by the toast adapter, toast content; and
providing, by the toast adapter, the toast content generated for each toast request to an application to cause the application to submit the toast content generated for each toast request to the Windows toast framework to thereby cause a toast notification to be displayed in response to each toast request;
in response to a user interacting with the toast notification that was displayed in response to a first toast request of the toast requests, receiving, by the toast adapter and from the Window s toast framework via the application, arguments representing how the user interacted with the toast notification;
processing, by the toast adapter, the arguments to identify which of the one or more plugins sent the first toast request; and
sending, by the toast adapter and to the identified plugin, an indication of the user's interaction with the toast notification.
12. The computer storage media of claim 11 , wherein the one or more plugins comprise multiple plugins that are integrated into a service.
13. The computer storage media of claim 11 , wherein the one or more plugins comprise multiple plugins that are integrated into multiple services.
14. The computer storage media of claim 11 , wherein processing the arguments to identify which of the one or more plugins sent the first toast request comprises determining that an identifier that is included in the arguments is associated with an identifier of the identified plugin.
15. The computer storage media of claim 11 , wherein the indication of the user's interaction with the toast notification includes context that the identified plugin included in the first toast request.
16. A computing device comprising:
one or more processors; and
computer storage media storing computer executable instructions which when executed by the one or more processors implement a method for managing toast notifications via a toast adapter and plugins, the method comprising:
in response to receiving toast requests from multiple plugins, generating, by a toast adapter, toast content for each of the toast requests;
causing, by the toast adapter, the toast content for each of the toast requests to be submitted to a toast framework to thereby cause a toast notification for each of the toast requests to be displayed including a first toast notification for a first toast request of the toast requests;
in response to a user interacting with the first toast notification that is displayed for the first toast request of the toast requests, receiving, by the toast adapter, arguments representing how the user interacted with the first toast notification;
in response to receiving the arguments, identifying, by the toast adapter, a first plugin of the multiple plugins that sent the first toast request; and
sending, by the toast adapter, an indication of the user's interaction with the first toast notification to the first plugin.
17. The computing device of claim 16 , wherein the multiple plugins are integrated into a single service.
18. The computing device of claim 16 , wherein the multiple plugins are integrated into multiple services.