Composable events for dynamic user interface composition

• US 10,466,872 B1
• Filed: 12/20/2013
• Issued: 11/05/2019
• Est. Priority Date: 12/20/2013
• Status: Active Grant

• Current Assignee: Open Text Corporation
• Original Assignee: Open Text Corporation
• Inventors: Totale, Sachin G., Suliman, Marwan, Vidyananda, Naveen, Salvi, Roshan Prakash, Taj, Mohamed
• Primary Examiner(s): Spratt, Beau D
• Application Number:
  US14/136,232
• Time in Patent Office: 2,146 Days
• Field of Search: None
• CPC Class Codes: G06F 3/0484 for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
• CPC Class Codes: G06F 40/186 Templates
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

Composable events to provide a dynamic user interface are disclosed. In various embodiments, a definition of a custom user interface event is received. The definition includes an identification of a data value to be associated with the event, a scope of the event within which the event will be consumed, and an event trigger in response to which an instance of the custom user interface event is to be published. Application user interface code configured to provide one or more application user interface elements configured to publish or subscribe to the custom user interface event is generated programmatically, based at least in part on the definition.

Claims

1. A method of providing a user interface, comprising:

prior to a runtime of an application, receiving an indication of a selection associated with a custom user interface event;

in response to the indication, providing a template to assist defining the custom user interface event in a structured manner;

prior to the runtime of the application, receiving at least in part via the template a definition of the custom user interface event, the definition including an identification of a data value to be associated with the custom user interface event, an indication of a scope of the custom user interface event, wherein the custom user interface event is consumed only within the indicated scope by other page elements outside of a first application user interface element selected to publish the custom user interface event, and one or more event triggers in response to which an instance of the custom user interface event is to be published;

prior to the runtime of the application, receiving an indication of the first application user interface element to publish the custom user interface event and associating the first application user interface element with the custom user interface event; and

generating programmatically, based at least in part on the definition, an application user interface code configured to provide, during the runtime of the application, an application user interface page to a client, the application user interface page comprising one or more application user interface elements including the first application user interface element, wherein the first application user interface element is configured to publish, upon occurrence of at least one of the one or more event triggers, for consumption by one or more elements of the application user interface page within the scope, the instance of the custom user interface event with an associated data value according to the identification of the data value and wherein the application user interface code is configured to cause the associated data value to be stored in a content cache from which the data value is read by the one or more elements of the application user interface page within the scope until another instance of the custom user interface event is published.

2. The method of claim 1, wherein the definition is received via a software development tool interface.

3. The method of claim 1, wherein the identification of the data value comprises an indication of a payload to be associated with the custom user interface event.

4. The method of claim 3, wherein the payload comprises a set of one or more parameters.

5. The method of claim 3, wherein the associated data value is stored in a structure associated with an event bus via which the instance of the custom user interface event is published.

6. The method of claim 1, further comprising receiving a definition of the first application user interface element configured to publish the custom user interface event.

7. The method of claim 1, further comprising, receiving a definition of a second application user interface element of the one or more application user interface elements, the second application user interface element configured to subscribe to the custom user interface event.

8. The method of claim 1, further receiving an expression to be evaluated in connection with consumption of the custom user interface event.

9. The method of claim 8, wherein the expression includes the associated data value as an argument.

10. The method of claim 9, wherein the associated data value is included in a payload associated with the instance of the custom user interface event.

11. The method of claim 10, wherein at least one application user interface element is configured to use the expression to consume the instance of the custom user interface event and to perform a dynamic user interface action determined based at least in part on a result of evaluation of the expression.

12. The method of claim 1, wherein the scope is fragment-wide, page-wide, or application-wide.

13. A system, comprising:

a data storage device; and

a processor coupled to the data storage device and configured to;

prior to a runtime of an application, receive an indication of a selection associated with a custom user interface event;

in response to the indication, provide a template to assist defining the custom user interface event in a structured manner;

prior to the runtime of the application, receive, at least in part via the template and store in the data storage device, a definition of the custom user interface event, the definition including an identification of a data value to be associated with the custom user interface event, an indication of a scope of the custom user interface event, wherein the custom user interface event is consumed only within the indicated scope by page elements outside of a first application user interface element selected to publish the custom user interface event, and one or more event triggers in response to which an instance of the custom user interface event is to be published;

prior to the runtime of the application, receive an indication of the first application user interface element to publish the custom user interface event and associate the first application user interface element with the custom user interface event; and

generate programmatically, based at least in part on the definition, an application user interface code configured to provide, during the runtime of the application, an application user interface page to a client, the application user interface page comprising one or more application user interface elements, wherein the one or more application user interface elements include the first application user interface element configured to publish, upon occurrence of at least one of the one or more event triggers, for consumption by one or more elements of the application user interface page within the scope, the instance of the custom user interface event with an associated data value according to the identification of the data value, wherein the application user interface code is configured to cause the associated data value to be stored in a content cache from which the data value is read by the one or more elements of the application user interface page within the scope until another instance of the custom user interface event is to be published.

14. The system of claim 13, wherein the data storage device comprises a memory.

15. The system of claim 13, wherein the identification of the data value comprises an indication of a payload to be associated with the custom user interface event.

16. The system of claim 15, wherein the application user interface code is configured to store the associated data value in a structure associated with an event bus via which the instance of the custom user interface event is published.

17. The system of claim 13, wherein the processor is further configured to receive a definition of the first application user interface element configured to publish the custom user interface event.

18. The system of claim 13, wherein the scope is fragment-wide, page-wide, or application-wide.

19. A computer program product to provide a user interface, the computer program product being embodied in a non-transitory computer-readable storage medium and comprising computer instructions for:

prior to a runtime of an application, receiving an indication of a selection associated with a custom user interface event;

in response to the indication, providing a template to assist defining the custom user interface event in a structured manner;

prior to the runtime of the application, receiving at least in part via the template a definition of the custom user interface event, the definition including an identification of a data value to be associated with the custom user interface event, an indication of a scope of the custom user interface event, wherein which the custom user interface event is consumed only within the indicated scope by page elements outside of a first application user interface element selected to publish the custom user interface event, and one or more event triggers in response to which an instance of the custom user interface event is to be published;

prior to the runtime of the application, receiving a selection of the first application user interface element to publish the custom user interface event and associating the first application user interface element with the custom user interface event; and

generating programmatically, based at least in part on the definition, an application user interface code configured to provide, during the runtime of the application, an application user interface page to a client, the application user interface page comprising one or more application user interface elements, wherein the one or more application user interface elements include the first application user interface element configured to publish, upon occurrence of at least one of the one or more event triggers, for consumption by one or more elements of the application user interface page within the scope, the instance of the custom user interface event with an associated data value according to the indication of the data value, wherein the application user interface code is configured to cause the associated to be stored in a content cache from which the data value is read by the one or more elements of the application user interface page within the scope until another instance of the custom user interface event is to be published.