XML-based graphical user interface application development toolkit

• US 6,990,654 B2
• Filed: 09/14/2001
• Issued: 01/24/2006
• Est. Priority Date: 09/14/2000
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Carroll, Thomas J. Jr.
• Primary Examiner(s): NGUYEN BA, HOANG VU A
• Application Number:
  US09/953,050
• Publication Number:
  US 20020085020A1
• Time in Patent Office: 1,593 Days
• Field of Search: 717/109, 717/104, 717/105, 717/113, 717/114, 717/116, 717/123, 717/143, 715/500, 715/513, 715/760, 715/762, 715/763
• US Class Current: 717/109
• CPC Class Codes: G06F 8/38 for implementing user interfaces

Abstract

The invention as disclosed herein relates to a system and a method for creating user interfaces for software applications. Particularly, the invention allows a developer to segregate the development of the user interface from the development of the underlying application logic. In one embodiment of the invention, an applications graphical user interface is specified using an XML document as an application interface file. At application compile time this application interface file is parsed, and the specifications therein used to retrieve graphical screen components from an interface library to create the user interface. A grammar file can be used to further specify the parsing of the application interface file, and impose consistency upon the interface development process.

Claims

1. A computer implemented system for generating an application graphical user interface, comprising:

a parser, for parsing an application source code file, application interface file, interface grammar file, and interface library, to dynamically generate an application graphical user interface;

an application source code file for an application, specifying an application logic that is executed by actions generated by a plurality of graphical elements displayed for said application graphical user interface;

an application interface file specifying said plurality of graphical elements within an interface library to be displayed for said application graphical user interface;

an interface grammar file specifying rules to be used in parsing said application interface file; and

an interface library comprising a plurality of graphical elements to be retrieved by said parser in accordance with the specifications of said application interface file and said interface grammar file.

2. The system of claim 1, further comprising:

an interface propertyfile specifying a set of graphical elements within said interface library to be used by said application interface file.

3. The system of claim 1 wherein said application interface file is chosen from a plurality of available application interface files when a user logs in to the system.

4. The method of claim 3 wherein the application interface file to be used is selected dependent on the type of device used by the user.

5. The system of claim 1 wherein said interface library comprises a library of object oriented classes.

6. The system of claim 1 wherein said parser comprises means for:

determining within said application source code file a reference to said application interface file;

determining by reference to said interface grammar file whether a function call specified by said application source code file is allowed; and

communicating said function call to said interface library.

7. The system of claim 1 wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes.

8. The system of claim 7 wherein said interface grammar file is a document type description file which specifies the dependencies of the application screen component function calls to one another.

9. The system of claim 1 wherein said interface library comprises a set of screen component classes.

10. The system of claim 9 wherein said application source code file comprises function calls to at least one of said screen component classes.

11. A computer implemented system for development of an application graphical user interface, comprising:

means for creating an application source code file specifying an application logic;

means for creating an application interface file specifying a plurality of graphical elements within an interface library to be displayed for said application graphical user interface;

means for creating an interface grammar file specifying rules to be used in parsing said application interface file;

an interface library comprising a plurality of graphical elements to be retrieved in accordance with the specification of said application interface file and said interface grammar file; and

a parser, for parsing said application source code file, said application interface file, and said interface grammar file, retrieving said plurality of graphical elements from said interface library, and dynamically generating an application graphical user interface,

wherein said parser comprises means for

determining within said application source code file a reference to said application interface file,

determining by reference to said interface grammar file whether a function call specified by said application source code file is allowed, and

communicating said function call to said interface library.

12. The system of claim 11, further comprising:

an interface property file specifying a set of graphical elements within said interface library to be used by said application interface file.

13. The system of claim 11 wherein said application interface file to be used is chosen from a plurality of available application interface files when a user logs in to the system.

14. The method of claim 13 wherein the application interface file to be used is selected dependent on the type of device used by the user.

15. The system of claim 11 wherein said interface library comprises a library of object oriented classes.

16. The system of claim 11 wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes.

17. The system of claim 16 wherein said interface grammar file is a document type description file which specifies the dependencies of the application screen component function calls to one another.

18. The system of claim 11 wherein said interface library comprises a set of screen component classes.

19. The system of claim 18 wherein said application source code file comprises function calls to at least one of said screen component classes.

20. A computer implemented system for allowing consistency verification of an application user interface for an application in a graphical user interface development system, comprising:

an interface library comprising a plurality of graphical elements;

means for parsing an application interface file, said application interface file specifying a plurality of graphical elements within said interface library to be displayed for said application;

means for parsing an interface grammar file, said interface grammar file specifying rules to be used in parsing said application interface file and retrieving said pluralityof graphical elements; and

means for retrieving from said interface library a plurality of graphical elements, in accordance with the rules applied by said interface grammar file during parsing;

wherein said means for parsing further comprises means for

determining within an application source code file a reference to said application interface file,

determining by reference to said interface grammar file whether a function call specified by said application source code file is allowed, and

communicating said function call to said interface library.

21. The system of claim 20, further comprising:

an interface property file specifying a set of graphical elements within said interface library to be used by said application interface file.

22. The system of claim 20 wherein said application interface file to be used is chosen from a plurality of available application interface files when a user logs in to the system.

23. The method of claim 22 wherein the application interface file to be used is selected dependent on the type of device used by the user.

24. The system of claim 20 wherein said interface library comprises a library of object oriented classes.

25. The system of claim 20 wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes.

26. The system of claim 25 wherein said interface grammar file is a document type description file which specifies the dependencies of the application screen component function calls to one another.

27. The system of claim 20 wherein said interface library comprises a set of screen component classes.

28. The system of claim 27 wherein said application source code file comprises function calls to at least one of said screen component classes.

29. A computer implemented method of developing a graphical user interface application, comprising the steps of:

parsing an application interface file, application source code file, interface grammar file, and interface library, wherein

said application interface file specifies a plurality of graphical elements within an interface library to be displayed for said graphical user interface application,

said application source code file specifies an application logic that is executed by actions generated by said plurality of graphical elements displayed for said graphical user interface application, and

said interface grammar file specifies rules to be used in parsing said application interface file; and

retrieving from said interface library said plurality of graphical elements in accordance with the specifications of said application interface file and said interface grammar file.

30. The method of claim 29, further comprising:

using an interface property file to specify a set of graphical elements within said interface library to be used by said application interface file.

31. The method of claim 29 wherein said application interface file to be used is chosen from a plurality of available application interface files when a user logs in to a system.

32. The method of claim 31 wherein the application interface file to be used is selected dependent on the type of device used by the user.

33. The method of claim 29 wherein said interface library comprises a library of object oriented classes.

34. The method of claim 29 further comprising:

determining within said application source code file a reference to said application interface file;

determining by reference to said interface grammar file whether the function call specified by said application source code file is allowed; and

communicating said function call to said interface library.

35. The method of claim 29 wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes.

36. The method of claim 35 wherein said interface grammar file is a document type description file which specifies the dependencies of the application screen component function calls to one another.

37. The method of claim 29 wherein said interface library comprises a set of screen component classes.

38. The method of claim 37 wherein said application source code file comprises function calls to at least one of said screen component classes.

39. A computer implemented method of development of an application graphical user interface, comprising the steps of:

creating an application interface file specifying a plurality of graphical elements within an interface library to be displayed for said application graphical user interface;

creating an application source code file specifying an application logic that is executed by actions generated by said plurality of graphical elements displayed for said graphical user interface application;

creating an interface grammar file specifying rules to be used in parsing said application interface file;

providing an interface library comprising said plurality of graphical elements to be retrieved in accordance with the specification of said application interface file and said interface grammar file;

parsing said application source code file, said application interface file, and said interface grammar file to determine a plurality of graphical elements to be retrieved from said interface library; and

retrieving said plurality of graphical elements from said interface library, and dynamically generating an application graphical user interface.

40. The method of claim 39, further comprising:

specifying via an interface property file a set of graphical elements within said interface library to be used by said application interface file.

41. The method of claim 39 wherein said application interface file to be used is chosen from a plurality of available application interface files when a user logs in to a system.

42. The method of claim 41 wherein the application interface file to be used is selected dependent on the type of device used by the user.

43. The method of claim 39 wherein said interface library comprises a library of object oriented classes.

44. The method of claim 39 further comprising:

determining within said application source code file a reference to said application interface file;

determining by reference to said interface grammar file whether a function call specified by said application source code file is allowed; and

communicating said function call to said interface library.

45. The method of claim 39 wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes.

46. The method of claim 45 wherein said interface grammar file is a document type description file which specifies the dependencies of the application screen component function calls to one another.

47. The method of claim 39 wherein said interface library comprises a set of screen component classes.

48. The method of claim 47 wherein said application source code file comprises function calls to at least one of said screen component classes.

49. A computer implemented method for allowing consistency verification of an application user interface in a graphical user interface development system, comprising the steps of:

providing an interface library comprising a plurality of graphical elements;

providing means for parsing an application interface file, said application interface file specifying said plurality of graphical elements within said interface library to be displayed for said application user interface;

providing means for parsing an interface grammar file, said interface grammar file specifying rules to be used in parsing said application interface file and retrieving said plurality of graphical elements;

providing means for retrieving from said interface library said plurality of graphical elements, in accordance with the rules specified by said interface grammar file;

determining within an application source code file a reference to said application interface file;

determining by reference to said interface grammar file whether a function call specified by said application source code file is allowed; and

communicating said function call to said interface library.

50. The method of claim 49, further comprising:

an interface property file specifying a set of graphical elements within said interface library to be used by said application interface file.

51. The method of claim 49 wherein said application interface file to be used is chosen from a plurality of available application interface files when a user logs in to a system.

52. The method of claim 51 wherein the application interface file to be used is selected dependent on the type of device used by the user.

53. The method of claim 49 wherein said interface library comprises a library of object oriented classes.

54. The method of claim 49 wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes.

55. The method of claim 54 wherein said interface grammar file is a document type description file which specifies the dependencies of the application screen component function calls to one another.

56. The method of claim 49 wherein said interface library comprises a set of screen component classes.

57. The method of claim 56 wherein said application source code file comprises function calls to at least one of said screen component classes.

58. A computer implemented method of creating an application graphical user interface, comprising:

using an application source code file specifying an application logic;

using an application interface file to specify a plurality of graphical elements within an interface library to be displayed for said application graphical user interface;

using an interface grammar file to specify rules to be used in parsing said application interface file;

accessing an interface library comprising said plurality of graphical elements to be retrieved in accordance with the specification of said application interface file and said interface grammar file;

parsing said application source code file, said application interface file, and said interface grammar file to determine a plurality of graphical elements to be retrieved from said interface library; and

locating said plurality of graphical elements within said interface library, and using said plurality of graphical elements to generate said application graphical user interface;

determining within said application source code file a reference to said application interface file;

determining by reference to said interface grammar file whether a function call specified by said application source code file is allowed; and

communicating said function call to said interface library.

59. The method of claim 58, further comprising:

specifying via an interface property file a set of graphical elements within said interface library to be used by said application interface file.

60. The method of claim 58 wherein said application interface file to be used is chosen from a plurality of available application interface files when a user logs in to a system.

61. The method of claim 60 wherein the application interface file to be used is selected dependent on the type of device used by the user.

62. The method of claim 58 wherein said interface library comprises a library of object oriented classes.

63. The method of claim 58 wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes.

64. The method of claim 63 wherein said interface grammar file is a document type description file which specifies the dependencies of the application screen component function calls to one another.

65. The method of claim 58 wherein said interface library comprises a set of Java screen component classes.

66. The method of claim 65 wherein said application source code file comprises function calls to at least one of said screen component classes.

67. A computer implemented system for developing an application graphical user interface, comprising:

a parser, for parsing an application source code file, application interface file, interface grammar file, and interface library, to generate an application graphical user interface, wherein said parser comprises means for determining within said application source code file a reference to said application interface file, determining by reference to said interface grammar file whether a function call specified by said source code file is allowed, and passing said function call to said interface library;

an application source code file specifying an application logic wherein said application source code file comprises function calls to at least one of a plurality of Java screen component classes;

an application interface file specifying a plurality of graphical elements within an interface library to be displayed for said application graphical user interface, wherein said application interface file is chosen from a plurality of available application interface files, wherein said application interface file is an extended markup language file which maps application screen component function calls to screen component classes;

an interface grammar file specifying rules to be used in parsing said application interface file wherein said interface grammar file is a document type description file which specifies rules and dependencies of the application screen component function calls to one another; and

an interface library comprising a plurality of graphical elements to be retrieved by said parser in accordance with the specification of said application interface file and said interface grammar file, wherein said interface library comprises a library of screen component classes.