System and method for metadata-driven user interface

• US 20030221165A1
• Filed: 05/22/2002
• Published: 11/27/2003
• Est. Priority Date: 05/22/2002
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Young, Jeffrey Scott, Griggs, Shane Lee, Plaisted, Patrick Edwin, Carlson, Craig Lane, Gibson, Patrick Jude, Brookins, Timothy James
• Application Number:
  US10/153,036
• Publication Number:
  US 20030221165A1
• Time in Patent Office: Days
• US Class Current: 715/505
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

A user interface comprising one or more fields can be generated based on metadata in program logic. The field can be provided in a smart object through object oriented programming. Smart object metadata indicating an attribute of the field can be embedded in the smart object. Logical form metadata identifies a data type associated with the field, and layout metadata identifies a location of the field on the user interface. Physical control metadata identifies a physical control to represent the field on the user interface, and physical settings metadata identifies presentation characteristics of the physical control. The field can be generated on the user interface by displaying the physical control identified by the physical control metadata in the location identified by the layout metadata, with the attribute identified in the smart object metadata, and having the characteristics identified in the physical settings metadata.

Claims

1. A computer-implemented method for generating a form on a user interface, the user interface displaying a field of the form, said method comprising the steps of:

developing logical form metadata for the field that identifies a data type associated with the field;

developing layout metadata for the field that identifies a location of the field on the user interface;

assigning physical control metadata to the field that identifies a physical control to represent the field on the user interface, the physical control being of the data type indicated by the logical form metadata; and

generating the field on the user interface by rendering the physical control identified by the physical control metadata in the location identified by the layout metadata.

2. The method according to claim 1, wherein said step of developing logical form metadata comprises the steps of:

selecting a logical type identifier for the data type associated with the field; and

mapping the logical type identifier to the field.

3. The method according to claim 2, further comprising the step of creating a field identifier for the field,

wherein said mapping step comprises associating the logical type identifier with the field identifier.

4. The method according to claim 1, wherein said step of developing layout metadata comprises the steps of:

selecting a layout geometry used to display the form on the user interface; and

creating layout metadata for the field in the format of the selected geometry.

5. The method according to claim 4, wherein the selected geometry comprises one of absolute positioning and table flow.

6. The method according to claim 5, wherein the selected geometry comprises absolute positioning, and

wherein said creating step comprises creating coordinates that indicate the location of the field on the user interface.

7. The method according to claim 5, wherein the selected geometry comprises table flow, and

wherein said creating step comprises creating location information based on the relative position of the field to another field on the user interface.

8. The method according to claim 1, wherein said step of assigning physical control metadata comprises the steps of:

selecting a physical control to represent the field; and

mapping the physical control to the logical form metadata of the field.

9. The method according to claim 8, further comprising the step of creating a field identifier for the field,

wherein said mapping step comprises associating the physical control with the field identifier.

10. The method according to claim 1, further comprising the step of embedding state metadata for the field in a smart object, the state metadata indicating an attribute of the field,

wherein said generating step comprises rendering the field based on the state metadata.

11. The method according to claim 10, wherein the attribute of the field comprises one of “

must write,”

“

read/write,” and

“

read only.”

12. The method according to claim 10, wherein the attribute comprises “

must write” and

indicates that a value associated with the field is required and not currently entered.

13. The method according to claim 10, wherein the attribute comprises “

read/write” and

indicates enabled control of the field.

14. The method according to claim 10, wherein the attribute comprises “

read only” and

indicates disabled control of the field.

15. The method according to claim 1, further comprising the step of assigning physical settings metadata to the physical control that identifies presentation characteristics of the physical control,

wherein said generating step comprises rendering the physical control on the user interface based on the physical settings metadata.

16. A computer-readable medium having computer-executable instructions for performing the method of claim 15.

17. A system for generating a form, comprising:

a user interface that displays the form; and

a processor running a program module, the program module comprising;

state metadata that identifies an attribute of the field,

layout metadata that identifies a location of the field on the user interface, and

physical control metadata that identifies a physical control to represent the field on the user interface, and

a renderer that generates the field on the user interface by displaying the physical control identified by the physical control metadata in the location identified by the layout metadata and with the attribute identified by the state metadata.

18. The system according to claim 17, wherein the attribute of the field comprises one of “

must write,”

“

read/write,” and

“

read only.”

19. The system according to claim 17, wherein the program module further comprises physical settings metadata that identifies a presentation characteristic of the physical control, and

wherein said renderer generates the physical control on the user interface based on the physical settings metadata.

20. The system according to claim 17, wherein the program module further comprises logical form metadata that identifies a data type associated with the field, and

wherein the physical control metadata identifies a physical control of the data type identified by the logical form metadata.

21. The system according to claim 20, wherein the program module further comprises a field identifier for the field, and

wherein the logical form metadata is associated with the field identifier.

22. The system according to claim 20, wherein the program module further comprises a field identifier for the field, and

wherein the logical form metadata and the physical control are associated with the field identifier.

23. The system according to claim 17, wherein the layout metadata comprises location information in the format of a specified layout geometry.

24. The system according to claim 23, wherein the specified geometry comprises one of absolute positioning and table flow.

25. The system according to claim 24, wherein the specified geometry comprises absolute positioning, and

wherein the location information comprises coordinates that indicate the location of the field on the user interface.

26. The system according to claim 24, wherein the specified geometry comprises table flow, and

wherein the location information indicates the relative position of the field to another field on the user interface.

27. A computer-readable medium having computer-executable instructions for performing a method for generating a form on a user interface, the user interface displaying a field of the form, said method comprising the steps of:

embedding state metadata for the field in a smart object, the state metadata indicating an attribute of the field;

developing logical form metadata for the field that identifies a data type associated with the field;

developing layout metadata for the field that identifies a location of the field on the user interface;

assigning physical control metadata to the field that identifies a physical control to represent the field on the user interface, the physical control being of the data type indicated by the logical form metadata; and

generating the field on the user interface by rendering the physical control identified by the physical control metadata in the location identified by the layout metadata and having the attribute identified by the state metadata.

28. The computer-readable medium according to claim 27, wherein said step of developing logical form metadata comprises the steps of:

selecting a logical type identifier for the data type associated with the field; and

mapping the logical type identifier to the field.

29. The computer-readable medium according to claim 28, wherein said method further comprises the step of creating a field identifier for the field, and

wherein said mapping step comprises associating the logical type identifier with the field identifier.

30. The computer-readable medium according to claim 27, wherein said step of developing layout metadata comprises the steps of:

selecting a layout geometry used to display the form on the user interface; and

creating layout metadata for the field in the format of the selected geometry.

31. The computer-readable medium according to claim 30, wherein the selected geometry comprises one of absolute positioning and table flow.

32. The computer-readable medium according to claim 31, wherein the selected geometry comprises absolute positioning, and

wherein said creating step comprises creating coordinates that indicate the location of the field on the user interface.

33. The computer-readable medium according to claim 31, wherein the selected geometry comprises table flow, and

wherein said creating step comprises creating location information based on the relative position of the field to another field on the user interface.

34. The computer-readable medium according to claim 27, wherein said step of assigning physical control metadata comprises the steps of:

selecting a physical control to represent the field; and

mapping the physical control to the logical form metadata of the field.

35. The computer-readable medium according to claim 34, wherein said method further comprises the step of creating a field identifier for the field, and

wherein said mapping step comprises associating the physical control with the field identifier.

36. The computer-readable medium according to claim 27, wherein the attribute of the field comprises one of “

must write,”

“

read/write,” and

“

read only.”

37. The computer-readable medium according to claim 27, wherein the attribute comprises “

must write” and

indicates that a value associated with the field is required and not currently entered.

38. The computer-readable medium according to claim 27, wherein the attribute comprises “

read/write” and

indicates enabled control of the field.

39. The computer-readable medium according to claim 27, wherein the attribute comprises “

read only” and

indicates disabled control of the field.

40. The computer-readable medium according to claim 27, wherein said method further comprises the step of assigning physical settings metadata to the physical control that identifies presentation characteristics of the physical control, and

wherein said generating step comprises rendering the physical control on the user interface based on the physical settings metadata.

41. A computer-implemented method for generating a form on a user interface, the user interface displaying a field of the form, said method comprising the steps of:

developing logical form metadata for the field that identifies a data type associated with the field;

assigning physical control metadata to the field that identifies a physical control to represent the field on the user interface, the physical control being of the data type indicated by the logical form metadata; and

generating the field on the user interface by rendering the physical control identified by the physical control metadata.

42. The method according to claim 41, wherein said step of developing logical form metadata comprises the steps of:

selecting a logical type identifier for the data type associated with the field; and

mapping the logical type identifier to the field.

43. The method according to claim 42, further comprising the step of creating a field identifier for the field,

wherein said mapping step comprises associating the logical type identifier with the field identifier.

44. The method according to claim 41, wherein said step of assigning physical control metadata comprises the steps of:

selecting a physical control to represent the field; and

mapping the physical control to the logical form metadata of the field.

45. The method according to claim 44, further comprising the step of creating a field identifier for the field,

wherein said mapping step comprises associating the physical control with the field identifier.

46. The method according to claim 41, further comprising the step of embedding state metadata for the field in a smart object, the state metadata indicating an attribute of the field,

wherein said generating step comprises rendering the field based on the state metadata.