Objects with run-time classes and methods of making them

• US 5,896,532 A
• Filed: 06/15/1992
• Issued: 04/20/1999
• Est. Priority Date: 06/15/1992
• Status: Expired due to Term

• Current Assignee: AT&T IPM Corp. (AT&T, Inc.)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Blewett, Charles Douglas
• Primary Examiner(s): Beausoliel, Jr., Robert W.
• Assistant Examiner(s): Elmore, Stephen C.
• Application Number:
  US07/898,251
• Time in Patent Office: 2,500 Days
• Field of Search: 395/157, 395/650, 395/700, 395/670, 395/682, 395/683, 395/685, 395/701, 395/704, 395/712, 364/280, 364/284, 364/286, 364/976, 364/977, 364/977.1
• US Class Current: 719/310
• CPC Class Codes: G06F 9/4488 Object-oriented
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

Techniques for defining object classes at run time which are indistinguishable from object classes compiled at compile time. The techniques are applied to widgets employed in X window systems. Further disclosed are new kinds of widgets. One of the new kinds is a widget which has monitor functions associated with specific resources. When the resource is accessed, the monitor function is executed. Another is a widget which has a callback tester function associated with a list of callback functions. The callback tester performs a test whenever any resource of the widget is modified, and if the test succeeds, the functions on the list of callback functions are invoked. Other kinds of widgets are adapted to representing servers and clients. In these widgets, resources represent interprocess communications and operations on the resources are related to the interprocess communication.

Claims

1. A widget (523) for use in an X window graphical user interface system, the widget being characterized in that:

the widget is a software object stored in a computer readable medium and represents a window which may be displayed on a display; and

the widget'"'"'s resources include a first resource (713) which is first defined at run time.

2. The widget set forth in claim 1, further characterized in that:

the widget'"'"'s resources include a set of further resources (720) which are defined at run time;

the first resource is a monitor function (719) which is associated with one further resource of the set of further resources and which is invoked when the one further resource is accessed.

3. The widget set forth in claim 2 further characterized in that:

there are a plurality of the monitor functions.

4. The widget set forth in any claims 2 or 3 further characterized in that:

the monitor function includes a first monitor function which is invoked when the one further resource is read and a second monitor function which is invoked when the one further resource is modified.

5. The widget set forth in claim 1 further characterized in that:

the widget'"'"'s resources further include

one or more callback functions and

a set of further resources which are defined at run time; and

the first resource is a callback tester function which performs a test whenever any of the set of further resources is modified and which is associated with a set of the callback functions, the callback functions in the set being invoked if the results of the test so indicate.

6. The widget set forth in claim 5 further characterized in that:

the test may be made on any value accessible to the callback tester function when the callback tester function performs the test.

7. The widget set forth in any of claims 5 or 6 and further characterized in that:

there are a plurality of the callback tester functions.

8. A method of making a widget for use in the X window system, the widget belonging to a first class which is a subclass of a second class and the method comprising performing the steps in a computer system at run time of:

receiving a definition of the second class;

receiving a definition of a set of resources;

making a definition of the first class from the definition of the second class and the definition of the set of resources; and

creating the widget according to the definition of the first class.

9. The method set forth in claim 8 further characterized in that:

the step of making a definition of the first class includes the steps of

putting the definition of the second class into a form such that an object of the second class may be created; and

making the definition of the first class from the form and the definition of the set of resources.

10. A widget (523) for use in an X window system which is characterized in that:

the widget is a software object stored in a computer readable medium; and

the widget includes among its resources (735) a monitor function (719) which is associated with a given one of the resources, the association being such that the monitor function is invoked when the given resource is accessed.

11. The widget set forth in claim 10 further characterized in that:

there are a plurality of the monitor functions.

12. The widget set forth in any of claims 10 or 11 further characterized in that:

the monitor function includes a first monitor function which is invoked when the given resource is read and a second monitor function which is invoked when the given resource is modified.

13. A widget (523) for use in an X window system which is characterized in that:

the widget is stored in a computer readable medium; and

the widget includes among its resource callback tester function(721) which performs a test whenever a resource belonging to a set thereof is modified and which is associated with a set of the callback functions, the association being such that the callback functions in the set are invoked if the test'"'"'s results so indicate.

14. The widget set forth in claim 13 further characterized in that:

the test may be made on any value accessible to the callback tester function when the callback tester function performs the test.

15. The widget set forth in any of claims 13 or 14 further characterized in that:

there is a plurality of the callback tester functions.

16. A widget for use in the X window system which is characterized in that:

the widget is stored in a computer readable medium; and

the widget includes resources (1214,

     1222) representing an interprocess communication and means (1211) for relating operations on the resources to the interprocess communication.

17. The widget set forth in claim 16 further characterized in that:

the resources representing the interprocess communication represent data contained in the interprocess communication; and

the means for relating operations on the resources to the interprocess communication include a callback function invoked in response to an XtSetValues operation which reads a portion of the data represented by the resources.

18. The widget set forth in claim 17 further characterized in that:

the resources representing the interprocess communication include first resources representing an incoming interprocess communication;

and second resources representing an outgoing interprocess communication.

19. The widget set forth in claim 18 further characterized in that:

the widget represents a server process which receives interprocess communications from and provides interprocess communications to client processes; and

the callback functions further include a first callback function which is invoked when the server gets a new client process and a second callback function which is invoked when a client process dies.

20. The widget set forth in claim 18 further characterized in that:

the widget represents a client process which receives interprocess communications from and provides interprocess communications to a server process;

and the callback functions further include a callback function which is invoked when the client process dies.

21. The widget set forth in claim 16 further characterized in that:

the widget'"'"'s resources further include a run-time resource which is defined at run time; and

the means for relating operations on the resources employs the run-time resource.

22. The widget set forth in claim 21 further characterized in that:

the run-time resource includes a first run-time resource which may be accessed and a second run-time resource which is a monitor function associated with the first run-time resource, the monitor function being invoked when the first run-time resource is accessed; and

the means for relating operations accesses the first run-time resource;

and

the monitor function responds thereto by sending an interprocess communication.