MODELED USER INTERFACE CONTROLLERS

• US 20130167110A1
• Filed: 12/27/2011
• Published: 06/27/2013
• Est. Priority Date: 12/27/2011
• Status: Abandoned Application

• Current Assignee: SAP SE
• Original Assignee: Rene Gross
• Inventors: Gross, Ren, Stumpf, Dirk, Kornmann, Tim, Ritter, Gerd M.
• Application Number:
  US13/337,645
• Publication Number:
  US 20130167110A1
• Time in Patent Office: Days
• US Class Current: 717/105
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A computer-implemented system may receive and store first metadata defining a view of a user interface component, the first metadata conforming to a user interface view model, receive and store second metadata defining a controller of the user interface component, the second metadata conforming to a user interface controller model, receive and store third metadata defining data of the user interface component, the third metadata conforming to a user interface data model, and execute a framework to provide the user interface component to a client based on the first metadata, the second metadata and the third metadata.

Claims

1. A method implemented by a computing system in response to execution of program code by a processor of the computing system, the method comprising:

receiving and storing first metadata defining a view of a user interface component, the first metadata conforming to a user interface view model;

receiving and storing second metadata defining a controller of the user interface component, the second metadata conforming to a user interface controller model;

receiving and storing third metadata defining data of the user interface component, the third metadata conforming to a user interface data model; and

executing a framework to provide the user interface component to a client based on the first metadata, the second metadata and the third metadata.

2. A method according to claim 1,

wherein the third metadata defines a binding between a field of the data and a node attribute of a business object conforming to a business object model;

wherein the second metadata defines a transformation between the node attribute and the data field, and

wherein executing the framework comprises executing the framework to transform node attribute to the data field based on the second metadata.

3. A method according to claim 2,

wherein the first metadata defines a user interface control of the user interface component;

wherein the second metadata defines an event handler associated with the user interface control, and

wherein executing the framework comprises executing the framework to detect an event associated with the user interface control and to execute the event handler in response to the detection based on the second metadata.

4. A method according to claim 3,

wherein the second metadata defines a message mapping associated with the node attribute, and

wherein executing the framework comprises executing the framework to detect a message associated with the node attribute and mapping the message based on the second metadata.

5. A method according to claim 1,

wherein the first metadata defines a user interface control of the user interface component;

wherein the second metadata defines an event handler associated with the user interface control, and

wherein executing the framework comprises executing the framework to detect an event associated with the user interface control and to execute the event handler in response to the detection based on the second metadata.

6. A method according to claim 1,

wherein the third metadata defines a binding between a field of the data and a node attribute of a business object conforming to a business object model;

wherein the second metadata defines a message mapping associated with the node attribute, and

wherein executing the framework comprises executing the framework to detect a message associated with the node attribute and mapping the message based on the second metadata.

7. A non-transitory computer-readable medium storing program code executable by a computing system to:

receive and store first metadata defining a view of a user interface component, the first metadata conforming to a user interface view model;

receive and store second metadata defining a controller of the user interface component, the second metadata conforming to a user interface controller model;

receive and store third metadata defining data of the user interface component, the third metadata conforming to a user interface data model; and

execute a framework to provide the user interface component to a client based on the first metadata, the second metadata and the third metadata.

8. A medium according to claim 7,

wherein the third metadata defines a binding between a field of the data and a node attribute of a business object conforming to a business object model;

wherein the second metadata defines a transformation between the node attribute and the data field, and

wherein execution of the framework comprises execution of the framework to transform node attribute to the data field based on the second metadata.

9. A medium according to claim 8,

wherein the first metadata defines a user interface control of the user interface component;

wherein the second metadata defines an event handler associated with the user interface control, and

wherein execution of the framework comprises execution of the framework to detect an event associated with the user interface control and to execute the event handler in response to the detection based on the second metadata.

10. A medium according to claim 9,

wherein the second metadata defines a message mapping associated with the node attribute, and

wherein execution of the framework comprises execution of the framework to detect a message associated with the node attribute and mapping the message based on the second metadata.

11. A medium according to claim 7,

wherein the first metadata defines a user interface control of the user interface component;

wherein the second metadata defines an event handler associated with the user interface control, and

wherein execution of the framework comprises execution of the framework to detect an event associated with the user interface control and to execute the event handler in response to the detection based on the second metadata.

12. A medium according to claim 7,

wherein the third metadata defines a binding between a field of the data and a node attribute of a business object conforming to a business object model;

wherein the second metadata defines a message mapping associated with the node attribute, and

wherein execution of the framework comprises execution of the framework to detect a message associated with the node attribute and mapping the message based on the second metadata.

13. A computing system comprising:

a memory storing processor-executable program code; and

a processor to execute the processor-executable program code to cause the system to;

receive and store first metadata defining a view of a user interface component, the first metadata conforming to a user interface view model;

receive and store second metadata defining a controller of the user interface component, the second metadata conforming to a user interface controller model;

receive and store third metadata defining data of the user interface component, the third metadata conforming to a user interface data model; and

execute a framework to provide the user interface component to a client based on the first metadata, the second metadata and the third metadata.

14. A medium according to claim 13,

wherein the third metadata defines a binding between a field of the data and a node attribute of a business object conforming to a business object model;

wherein the second metadata defines a transformation between the node attribute and the data field, and

wherein execution of the framework comprises execution of the framework to transform node attribute to the data field based on the second metadata.

15. A medium according to claim 14,

wherein the first metadata defines a user interface control of the user interface component;

wherein the second metadata defines an event handler associated with the user interface control, and

wherein execution of the framework comprises execution of the framework to detect an event associated with the user interface control and to execute the event handler in response to the detection based on the second metadata.

16. A medium according to claim 15,

wherein the second metadata defines a message mapping associated with the node attribute, and

wherein execution of the framework comprises execution of the framework to detect a message associated with the node attribute and mapping the message based on the second metadata.

17. A medium according to claim 13,

wherein the first metadata defines a user interface control of the user interface component;

wherein the second metadata defines an event handler associated with the user interface control, and

wherein execution of the framework comprises execution of the framework to detect an event associated with the user interface control and to execute the event handler in response to the detection based on the second metadata.

18. A medium according to claim 13,

wherein the third metadata defines a binding between a field of the data and a node attribute of a business object conforming to a business object model;

wherein the second metadata defines a message mapping associated with the node attribute, and

wherein execution of the framework comprises execution of the framework to detect a message associated with the node attribute and mapping the message based on the second metadata.