Mark-up language implementation of graphical or non-graphical user interfaces

• US 7,219,305 B2
• Filed: 09/18/2003
• Issued: 05/15/2007
• Est. Priority Date: 09/12/2000
• Status: Expired due to Term

• Current Assignee: Avaya Incorporated
• Original Assignee: Avaya Technology Corporation Miami Lakes FLA US
• Inventors: Jennings, Terry D.
• Primary Examiner(s): Nguyen, Cao (Kevin)
• Application Number:
  US10/666,910
• Publication Number:
  US 20040061713A1
• Time in Patent Office: 1,335 Days
• Field of Search: 715/762, 715/763, 715/765, 715/513, 715/760, 715/734, 715/738, 715/743, 715/744, 715/733, 715/761, 715/736, 715/749, 715/742, 715/853, 715/854
• US Class Current: 715/761
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A user interface (132)—be it graphical (GUI) or telephony (TUI) to an application (120) is defined by stored interface and feature description documents (122,124) written in XML and JavaScript, so that the user interface and changes thereto can be effected without access to source code. Interface description documents define the appearance and the behavior of the user interface toward the user, while feature description documents define the interaction of the user interface with the interfaced-to application, both in conformity with a user-interface object model (310). Stored connector object plug-ins (126) define connector objects for rendering elements of feature description documents, and stored layout object plug-ins (128) define layout objects for rendering elements of interface description documents of one or more interfaces.

Claims

1. A method of implementing a user interface comprising:

storing one or more description documents defining a plurality of types of at least one user interface and comprising definitions of elements of the at least one user interface;

storing a plurality of objects each comprising a renderer for rendering a different one of the elements;

forming a first renderer of a selected user interface of a selected any one type of the plurality of the types by loading into an interface-implementation engine (interactor) objects of the plurality of objects that correspond to the elements of at least one description document of the stored description documents that defines the selected user interface of the selected any one type;

rendering the selected user interface of the selected any one type by executing the first renderer;

forming a second renderer of a selected user interface of a selected any other type of the plurality of the types which is different from said any one type by loading into same said interactor objects of the plurality of objects that correspond to the elements of at least one description document of the stored description documents that defines the selected user interface of the selected any other type; and

rendering the selected user interface of the selected any other type by executing the second renderer.

2. The method of claim 1 wherein:

the one type of interface is a telephony user interface (TUI); and

the other type of interface is a graphical user interface (GUI).

3. The method of claim 1 wherein:

each step of forming comprises

reflecting the definitions of the elements from the at least one description document that defines the selected user interface of the selected type into an object model to create an instance of the object model that defines the selected user interface of the selected type; and

each step of rendering comprises

executing the objects that correspond to the reflected element definitions.

4. The method of claim 1 wherein:

each step of rendering comprises

passing each element definition from the at least one description document that defines the selected user interface of the selected type to the corresponding object and executing said object to render the element.

5. The method of claim 1 wherein:

storing one or more description documents comprises

storing one or more description documents defining the at least one user interface and comprising one or more definition elements, and

storing one or more description documents defining interactions of the at least one user interface with at least one application and comprising one or more interaction elements;

storing a plurality of objects comprises

storing a plurality of layout objects each comprising a renderer for rendering a different one of the definition elements, and

storing a plurality of connector objects each comprising a renderer for rendering a different one of the interaction elements;

each step of forming a renderer comprises

forming a layout engine for the selected user interface from layout objects that correspond to the definition elements of at least one description document that defines the selected user interface, and

forming a connector engine for the selected user interface from layout objects that correspond to the interaction elements of at least one description document that defines interaction of the selected user interface with a selected application; and

each step of rendering the selected user interface comprises

rendering the selected interface to the selected application by executing the layout engine and the connector engine.

6. The method of claim 5 wherein:

rendering the selected interface to the selected application by executing the layout engine and the connector engine comprises

passing each element of the description documents that define the selected user interface and its interaction with the selected application to the corresponding object and executing said object to render said element.

7. An apparatus that effects the method of one of the claims 1–

6.

8. A computer-readable medium containing instructions which, when executed in a computer, cause the computer to perform the method of one of the claims 1–

6.

9. An apparatus for implementing a user interface, comprising:

storage for storing (a) one or more description documents defining a plurality of types of at least one user interface and comprising definitions of elements of at least one user interface, and (b) a plurality of objects each comprising a renderer for rendering a different one of the elements; and

a processor for connecting to the storage and (c) forming a first renderer of a selected user interface of a selected any one type of the plurality of the types by loading into an interface implementation engine (interactor) objects of the plurality of objects that correspond to the elements of at least one description document of the stored description documents that defines the selected user interface of the selected any one type, (d) rendering the selected user interface of the selected any one type by executing the renderer, (e) forming a second renderer of a selected user interface of a selected any other type of the plurality of the types which is different from said any one type by loading into same said interactor objects of the plurality of objects that correspond to the elements of at least one description document of the stored description documents that defines the selected user interface of the selected any other type, and (f) rendering the selected user interface of the selected any other type by executing the second renderer.

10. The apparatus of claim 9 wherein:

the processor renders the selected user interface of the selected type by passing each element definition from the at least one description document that defines the selected user interface of the selected type to the corresponding object and executes said object to render the element.

11. The apparatus of claim 9 wherein:

the one type of interface is a telephony user interface (TUI); and

the other type of interface is a graphical user interface (GUI).

12. The apparatus of claim 9 wherein:

the processor forms each renderer by reflecting the definitions of the elements from the at least one description document that defines the selected user interface of the selected type into an object model to create an instance of the object model that defines the selected user interface of the selected type; and

the processor renders each selected user interface by executing the objects that correspond to the reflected element definitions.

13. The apparatus of claim 9 wherein:

the storage stores (a)(i) one or more description documents defining at least one user interface and comprising one or more definition elements, (a)(ii) one or more description documents defining interactions of the at least one user interface with at least one application and comprising one or more interaction elements, (b)(i) a plurality of layout objects each comprising a renderer for rendering a different one of the definition elements, and (b)(ii) a plurality of connector objects each comprising a renderer for rendering a different one of the interaction elements; and

the processor forms (c)(i) a layout engine for the selected user interface of the selected type from layout objects that correspond to the definition elements of at least one description document that defines the selected user interface of the selected type and (c)(ii) a connector engine for the selected user interface of the selected type from layout objects that correspond to the interaction elements of at least one description document that defines interaction of the selected user interface of the selected type with a selected application, and (d) renders the selected interface of the selected type to the selected application by executing the layout engine and the connector engine.

14. The apparatus of claim 13 wherein:

the processor renders the selected user interface of the selected type to the selected application by passing each element of the description documents that define the selected user interface of the selected type and its interactions with the selected application to the corresponding object and executing said object to render said element.

15. An apparatus for implementing a user interface comprising:

means for storing one or more description documents defining a plurality of types of at least one user interface and comprising definitions of elements of the at least one user interface;

means for storing a plurality of objects each comprising a renderer for rendering a different one of the elements;

means for forming a first renderer of a selected user interface of a selected any one type of the plurality of the types by loading into an interface-implementation engine (interactor) objects of the plurality of objects that correspond to the elements of at least one description document of the stored description documents that defines the selected user interface of the selected any one type;

means for rendering the selected user interface of the selected any one type by executing the first renderer;

means for forming a second renderer of a selected user interface of a selected any other type of the plurality of the types which is different from said any one type by loading into same said interactor objects of the plurality of objects that correspond to the elements of at least one description document of the stored description documents that defines the selected user interface of the selected any other type, and

means for rendering the selected user interface of the selected any other type by executing the second renderer.

16. The apparatus of claim 15 wherein:

the one type of interface is a telephony user interface (TUI); and

the other type of interface is a graphical user interface (GUI).

17. The apparatus of claim 15 wherein:

each means for forming comprises means for reflecting the definitions of the elements from the at least one description document that defines the selected user interface of the selected type into an object model to create an instance of the object model that defines the selected user interface of the selected type; and

each means for rendering comprises means for executing the objects that correspond to the reflected element definitions.

18. The apparatus of claim 15 wherein:

means for rendering comprise

means for passing each element definition from the at least one description document that defines the selected user interface to the corresponding object; and

means for executing said object to render the element.

19. A method comprising:

storing description documents that define a user interface, comprised of interface elements, in terms of an object model, some of the description documents defining a first type of the user interface and others of the description documents defining a second type of the user interface;

storing renderers each for rendering a different one of the interface elements, some of the renderers for rendering the first type of the user interface and others of the renderers for rendering the second type of the user interface;

parsing the description documents of a selected either type of the user interface by an interface implementation engine (interactor) to identify the elements of the selected type of user interface;

reflecting the identified elements into the object model by the interactor to generate an instance of the object model that represents the selected type of the user interface;

downloading the renderers corresponding to the reflected elements into the interactor to create a renderer for the selected type of the user interface; and

executing the renderer by the interactor to create the selected type of the user interface.

20. The method of claim 19 wherein:

the first type of the interface is a telephony user interface (TUI); and

the second type of the interface is a graphical user interface (GUI).

21. The method of claim 19 wherein:

the description documents are expressed in a mark-up language.

22. The method of claim 19 wherein:

the description documents define the object model.

23. The method of claim 19 wherein:

each renderer is an object whose execution renders the corresponding interface element.

24. The method of claim 23 wherein:

executing the renderer comprises

invoking execution of each loaded renderer with the corresponding reflected element of the object model to render the corresponding interface element.

25. The method of claim 19 wherein:

each renderer is for rendering the different interface element in a different interface of a different type for a different device and a different application.

26. An arrangement comprising:

description documents, stored in a computer readable-medium, that define a user interface, comprised of interface elements, in the terms of an object model, some of the description documents defining a first type of the user interface and others of the description documents defining a second type of the user interface;

renderers, implemented in a computer, each for rendering a different one of the interface elements, some of the renderers for rendering the first type of the user interface and others of the renderers for rendering the second type of the user interface; and

an interface implementation engine (interactor), implemented in a computer, for parsing the description documents of a selected either type of the user interface to identify the elements of the selected type of user interface, for reflecting the identified elements into the object model to generate an instance of the object model that represents the selected type of the user interface, for loading the renderers corresponding to the reflected elements into the interactor to create a renderer of the selected type of the user interface, and for executing the renderer to create the selected type of the user interface.

27. The arrangement of claim 26 wherein:

the first type of the interface is a telephony user interface (TUI); and

the second type of the interface is a graphical user interface (GUI).

28. The arrangement of claim 26 wherein:

the description documents are expressed in a mark-up language.

29. The arrangement of claim 26 wherein:

the description documents define the object model.

30. The arrangement of claim 26 wherein:

each renderer is an object whose execution renders the corresponding interface element.

31. The arrangement of claim 30 wherein:

the interactor executes the renderer by invoking execution of each loaded renderer with the corresponding reflected element of the object model to render the corresponding interface element.

32. The arrangement of claim 26 wherein:

each renderer is for rendering the different interface element in a different interface of a different type for a different device and a different application.

33. The arrangement of claim 26 further comprising:

storage for the description documents;

storage for the renderers; and

a processor for forming the interactor.