JPH06149526A - Window system - Google Patents

Abstract

PURPOSE:To efficiently reproduce an user operation by input event information. CONSTITUTION:The event information from a keyboard 12 and a mouse 3 is discriminated at a window server 11 and the event information for a window program 1 is stored in a storage part 17 along with time information. Also, the event information for the window program 2 is stored in the storage part 18 along with the time information. Based on the input event information, the event information in the storage part 17 or 18 is supplied to the window program 1 or 2 and is window displayed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a window system and is capable of reproducing an event according to event information input by a user.

[0002]

2. Description of the Related Art In recent years, window systems have been realized in workstations and personal computers.

In general, the window system means a system capable of switching and executing application programs assigned to each window one after another by multi-window display.

The function of organizing and displaying information according to the user's need is an important technique from the viewpoint of the user interface. As such a window system, there is X Window System (trademark of Massachusetts Institute of Technology, USA). Further, for example, MS-Wi applicable to a personal computer
Windows (trademark of Microsoft Corporation, USA) is also available.

For example, consider a case where there is a window A for drawing a picture on the display and a window B for displaying a sentence. In this case, whether to select the window A or the window B is selected by, for example, a marker. When a line is drawn in the window A, the window A is selected with a marker, and in this state, for example, a start point, an end point for drawing a line with a mouse or a keyboard, a line type, etc. are set. A line can be drawn in the window A by supplying event information and the like to the workstation body and the like and performing drawing processing.

On the other hand, when a sentence is displayed in the window B, the window B is selected by a marker, and in this state, character and symbol information is supplied as event information to a workstation or the like by using a keyboard or the like, so that the window B is displayed. Character information can be displayed on the.

Next, FIG. 2 shows an example of functional blocks when a window system is specifically applied to a workstation.

In FIG. 2, an event for the window system is generated from the keyboard 12, mouse 3, etc. by the user's window operation, and the window server 1
1 is supplied. Upon receiving this event, the window server 11 determines the window program that is the target of the event and notifies the corresponding window program 1 or 2 of the occurrence of the event.

The event is generally in the form of abstracted data sent from all input devices connected to the hardware. For example, it means information such as a key being pressed on the keyboard 12 or a button being pressed on the mouse 3.

The event log processing in the conventional window system has two methods: a method of instructing the window server 11 of the event log and a method of instructing the window programs 1 and 2.

Next, the above two methods will be described.

(A) Instructing the window server 11
Method FIG. 3 is an explanatory diagram of event log acquisition (No. 1).

In FIG. 3, all the events that occur on the window system are temporarily recorded in the event log acquisition unit 1.
The event recorded in No. 4 and recorded in the event log acquisition unit 14 is again given to the window server 11.

First, when the user specifies acquisition of an event log, logs of all events that occur on the window system by the window operation of the user thereafter are recorded in the event log acquisition unit 14.

FIG. 4 is an explanatory diagram of event reproduction (No. 1).

In FIG. 4, the acquired event can be reproduced by the window server 11 according to an instruction from the user.

(B) Event log acquisition is performed by window
What Gram Does FIG. 5 is an explanatory diagram of event log acquisition (No. 2).

In FIG. 5, each window program 1 or 2 individually records the event notified by the window server and reproduces it later. Each window program 1 and 2 records a log of events received from the window server 11.

FIG. 6 is an explanatory diagram of event reproduction (No. 2).

In FIG. 6, reproduction of the acquired event is independently performed for each of the programs 1 and 2 according to the acquired log.

[0021]

As described above, the user operation that can be reproduced by the conventional user operation acquisition and reproduction method is the method (a) of reproducing the user operation by the acquisition event for the entire window system, or The method is limited to either one of the user operation reproducing method (b) of the user operation by the event acquired by the window programs 1 and 2.

Therefore, in the above method (a), the window operations of all the events stored in the event log acquisition unit 14 can be reproduced at one time, but the individual window programs 1 or 2 It has the drawback that it is not possible to reproduce only the user operation for.

Further, in the above method (b), only the user operation for each of the window programs 1 and 2 can be reproduced individually, but the user operation cannot be reproduced for the entire window system at once. There is also a drawback that each existing window program must be rewritten so that the event log can be acquired.

Further, in any of the above methods, the reproduction of the individual user operation by the event log for the provided window programs 1 and 2 cannot be applied to another window program to reproduce the user operation. There is also.

Therefore, there has been a demand for realizing both the reproduction of the user operation on the entire window system and the reproduction of the user operation for each window program. Furthermore, it also supports the function to reproduce the operation to a certain window program to another arbitrary window program.

The present invention has been made in view of the above problems, and an object of the present invention is to provide a window system capable of efficiently reproducing a user operation by input event information.

[0027]

In order to achieve the above object, the window system of the present invention provides each window processing program corresponding to each window and event information from the input section to each window processing program. An event processing unit for performing processing for the above is provided, and the window system for displaying in a window using the window processing program based on the input event information is realized by including the following characteristic means.

That is, in the event information storage mode, the event processing section stores event information management means for storing and managing the input event information corresponding to each window processing program, and the event information reproduction mode. At the same time, an event information supply means for giving the managed event information to the corresponding window processing program or another window processing program is provided.

[0029]

According to the window system of the present invention, the event information management means can manage the input event information corresponding to each window processing program. Therefore, when the user operation for each window is reproduced, Can be reproduced for each.

Moreover, since the event information supply means can reproduce not only the window processing program corresponding to the input event information but also any other window processing program, the window having the same contents can be obtained. The display can be displayed in another window, and various window displays can be realized.

[0031]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT A preferred embodiment of the window system of the present invention will be described with reference to the drawings.

FIG. 1 is a functional block diagram for acquiring event information when the window system of this embodiment is applied to a workstation.

In FIG. 1, the window system of this embodiment stores the window programs 1 and 2, the window server 11, and the event log for the window program 1 managed by the window server 11 in the workstation body 4. It includes a unit 17, an event log storage unit 18 for the window program 2, and a time information generation unit 19.

Window server 11 to display 1
Display data is output to 22. The display 122 is composed of a window A for displaying the display data obtained by the window program 1 and a window B for displaying the display data obtained by the window program 2.

Further, a keyboard 12 for user operation and a mouse 3 are connected to the workstation body 4, and event information generated from these is supplied to the window server 11.

Then, the window server 11 discriminates the supplied event information and responds depending on whether the input event information is the event information for the window program 1 or the window program 2. It is stored in the storage unit 17 or 18.

That is, if the input event information is for the window program 1, the window server 1
1 is an event log storage unit 17 for window program 1
To be stored in. If the input event information is for the window program 2, the window server 1
1 is the event log storage unit 18 for the window program 2
To be stored in.

In addition, the event information is stored together with the time information from the time information generator 19.
This is done, for example, when the window program 1 or 2 is notified based on the event information stored in the event log storage unit 17 or 18, for example, in order of the stored time. , Event information is stored together with time information.

The above event acquisition process will be described with reference to the flowchart of FIG. 8 as an example.

In the flowchart of FIG. 8, when event information is supplied to the window server 11, the type of event information (whether a key is pressed by the keyboard 12 or a button is pressed by the mouse 3). , Etc.) is determined (S81). Next, the target window program of the supplied input event information is determined (S82).

Next, the window server 11 is supplied to and stored in the storage unit 17 or 18 for storing the input event information.

Next, reproduction of an event will be described with reference to FIG. 7 based on the stored event information.

FIG. 7 is a functional block diagram of a window system of one embodiment for event reproduction.

In FIG. 7, the event information stored in the event log storage unit 17 for the window program 1 is given to the window program 1, and drawing is performed based on the given event information.

Further, the event information stored in the event log storage section 18 for the window program 2 is given to the window program 2, and drawing is performed based on the given event information.

Reproduction of the above event will be described with reference to the flowchart of FIG. 9 as an example.

In the flowchart of FIG. 9, the window server 11 judges the log storage area for storing the event to be reproduced, that is, the storage unit 17 or 18 based on the input information from the user (S91). Then, a judgment is made and a log is stored in the storage unit 17 or 18 (history of event information)
It is confirmed whether or not is stored (S92).

Then, if any log is stored, it is determined whether the stored log is a reproduction target (S93). Here, if it is determined that the log is to be reproduced, this log (event information history)
This window information is notified to the window program 1 or 2 which is the target of (2) and the drawing processing is performed (S94).

As described above, the reproduction of the drawing based on the stored event information can be performed at once for the two windows.

FIG. 10 shows an example of an example program for event acquisition and event reproduction. In the program example of FIG. 10, this program includes a file information display portion 10a, a user information display portion 10b, a program (final) creation portion 10c, a program (final) execution portion 10d, and a logout portion. 1
0e and 0e.

Then, for example, the conventional X-Window
By configuring the window server of the system as in this embodiment, it is possible to reproduce a user operation for a terminal program such as xterm or kterm.

For example, by acquiring a log of event information generated from the keyboard for xterm and reproducing it, the user operation can be executed again and the result can be acquired.

In FIG. 10, the keyboard input from the user is "Is", "who", "cc-o".
final final. c-Isocket "," f
"inal", "logout" are reproduced in order, and x
It is passed to term and the result is displayed.

Then, the xterm displays the same processed result without being aware of the actual keyboard input from the user or the reproduced event.

FIG. 11 is a diagram showing an example of drawing in which the event reproduction as described above is performed.

In the drawing example diagram of FIG. 11, FIG.
This is an example in which event information is reproduced in the order of (a) → (b) → (c) and drawing is performed. The event information stored in this way can be given to the window program in order to reproduce the drawing in order.

FIG. 12 shows an example of a hardware configuration diagram for realizing the functional blocks of the window system shown in FIGS. 1 and 7.

In the hardware configuration diagram of FIG. 12, the window system includes a CPU 121, a keyboard 2, a mouse 3, a display 122, a main memory section 123, a window server program memory section 124, and a window program memory. And a part 125.

In the hardware configuration diagram of FIG. 12, the window server program memory unit 124
Is a memory unit that stores a program that realizes the function of the window server 11. Then, the window program memory unit 125 uses the window programs 1 and 2
Is a memory unit for storing.

Further, the main memory section 123 stores a basic program for controlling the entire window system by the CPU 121. The keyboard 2 and the mouse 3 generate event information by a user operation. The display 122 displays a window according to the event information.

According to the window system of the above embodiment, since the window server 11 acquires and manages event information (log) for each window program 1 and 2, reproduction of user operation for the entire window system. It is possible to realize both the individual operation of the user for each of the window programs 1 and 2 and the reproduction.

Further, according to the window system of this embodiment, there is an advantage that only the window server 11 needs to be rewritten and the existing window programs 1 and 2 need not be changed.

Furthermore, in order to enable automation of all window programs that require user operation, a benchmark test that simulates user operation (test for comparing and evaluating the performance of hardware and software)
Very effective for environment and batch processing. It is also useful for simplifying user operations for programs that require complicated window operations and for debugging new programs.

In the window system of the above embodiment, the event information in the event log storage unit 17 for the window program 1 is given to the window program 1 and the event log storage unit 18 for the window program 2 is provided.
The event information of is given to the window program 2 so that both can be drawn, but the present invention is not limited to this. For example, as shown in FIG. 13, only the event information in the event log storage unit 17 for the window program 1 may be given to the window program 1 by a user operation and reproduced.

Further, for example, as shown in FIG. 14, the event information in the event log storage unit 17 for the window program 1 can be given to the window program 2 by a user's operation and drawn. In other words, the window program 2 does not care whether the received event information is for the window program 1,
The same drawing process as that performed by the user for the window program 1 can be reproduced for the window program 2.

Furthermore, the functional block diagram of the window system of FIGS. 1 and 7 and the hardware configuration diagram of the window system of FIG. 12 of the above embodiment are examples.
It is not limited to these.

[0067]

As described above, according to the window system of the present invention, the event processing section is provided with the event information management section and the event information supply section, so that the event processing section has a function for each window processing program. Since the event information can be acquired and managed, it is possible to efficiently reproduce both the user operation for the entire window system and the user's individual operation for each window processing program.

Further, various window displays can be efficiently realized by reproducing the above-mentioned efficient user operation.

Furthermore, the reproduction of the above user operation is also effective when applied to program debugging, system performance evaluation, and the like.

[Brief description of drawings]

FIG. 1 is a functional block diagram of event log acquisition of an embodiment of a window system according to the present invention.

FIG. 2 is a functional block diagram of a conventional window system.

FIG. 3 is an explanatory diagram of event log acquisition (No. 1) of a conventional example.

FIG. 4 is an explanatory diagram of event reproduction (part 1) of a conventional example.

FIG. 5 is an explanatory diagram of event log acquisition (No. 2) of a conventional example.

FIG. 6 is an explanatory diagram of reproduction (No. 2) of an event of a conventional example.

FIG. 7 is a functional block diagram of event reproduction by the window system according to the embodiment.

FIG. 8 is a flowchart of an event acquisition process according to an embodiment.

FIG. 9 is a flowchart of event reproduction processing according to an embodiment.

FIG. 10 is a diagram of an example program for event acquisition and reproduction according to an embodiment.

FIG. 11 is a diagram of a drawing example by event reproduction according to an embodiment.

FIG. 12 is a hardware configuration diagram of a window system according to an embodiment.

FIG. 13 is a functional block diagram (No. 1) of event reproduction according to another embodiment.

FIG. 14 is a functional block diagram (No. 2) of event reproduction according to another embodiment.

[Explanation of symbols]

1, 2 ... Window program, 3 ... Mouse, 11 ... Window server, 12 ... Keyboard, 17 ... Window program 1 event log storage section, 18 ... Window program 2 event log storage section.

Claims (1)

[Claims] 1. A window processing program corresponding to each window and an event processing section for performing processing for giving event information from an input section to the window processing program are provided, and based on the input event information. In a window system for displaying in a window using the window processing program, the event processing unit, in the event information storage mode,
Event information management means for storing and managing the input event information corresponding to each window processing program, and the window processing program or the other corresponding to the managed event information in the event information reproduction mode. And an event information supply means for giving to the window processing program.