Recording user-driven events within a computing system

• US 8,448,138 B2
• Filed: 01/15/2008
• Issued: 05/21/2013
• Est. Priority Date: 01/15/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Chang, Wen-Chieh, Huang, Shu-Fang, Jiang, Yan-Mei, Huang, Ling-Ya, Wen, Li, Chen, Chih-Yung, Chang, Michael Jen-Chiung, King, Hung Ju, Huang, Yuli
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Luu, Cuong V
• Application Number:
  US12/014,756
• Publication Number:
  US 20090182753A1
• Time in Patent Office: 1,953 Days
• Field of Search: None
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence

Abstract

Technologies are described herein for recording user-driven events within a computing system. An interface is established between a recorder application and an input method editor (“IME”) executing on the computer system. Through the use of the interface, the recorder application can obtain and record data identifying user-driven events that are performed within the IME. An interface is also established between the recorder application and a UI control that does not expose data regarding user-driven events through standard system calls. Through the use of the interface, the recorder application can obtain and record data identifying user-driven events detected at the UI control. The recorder application can also provide data identifying the recorded user-driven events directly to a bug tracking application program for inclusion in a bug database.

Claims

1. A method for recording user-driven events within a computing system, the method comprising:

establishing

a first interface between a recorder application and an input method editor (IME) executing on the computing system, the first interface being configured to provide data identifying a first user-driven event detected at the IME to the recorder application,

a second interface between the recorder application and a user interface (UI) control that generates non-standard focus and event messages, the second interface being configured to provide data identifying a second user-driven event detected at the UI control to the recorder application, and

a third interface between the recorder application and an application program, the third interface being configured to provide data identifying a third user-driven event detected at the application program to the recorder application, wherein the UI control and the application program are different, and wherein the first, second, and third user-driven events are different;

receiving data identifying the first user-driven event detected at the IME on the first interface, the second user-driven event detected at the UI control on the second interface, and the third user-driven event detected at the application program on the third interface; and

recording the data identifying the first user-driven event, the second user-driven event, and the third user-driven event.

2. The method of claim 1, wherein the first interface comprises a text services framework.

3. The method of claim 1, wherein the second interface comprises an accessibility interface.

4. The method of claim 1, wherein the third interface comprises a system hook.

5. The method of claim 1, further comprising:

providing the data identifying the first user-driven event detected at the IME to a bug tracking application program;

providing the data identifying the second user-driven event detected at the UI control to the bug tracking application program; and

providing the data identifying the third user-driven event detected at the application program to the bug tracking application program.

6. The method of claim 5, wherein providing the data identifying the first user-driven event detected at the IME, the data identifying the second user-driven event detected at the UI control, and the data identifying the third user-driven event detected at the application program to the bug tracking application program comprises:

receiving a request to provide the data identifying the first user-driven event detected at the IME, the data identifying the second user-driven event detected at the UI control, and the data identifying the third user-driven event detected at the application program to the bug tracking application program;

causing the bug tracking application program to be executed in response to receiving the request;

providing the data identifying the first user-driven event detected at the IME, the data identifying the second user-driven event detected at the UI control, and the data identifying the third user-driven event detected at the application program to the bug tracking application program; and

causing the data provided to the bug tracking application program to be stored in a bug tracking database maintained by the bug tracking application program.

7. A computer storage medium having computer-executable instructions stored thereon which, when executed by a computer, cause the computer to:

establish

a first interface between the recorder application and a user interface (UI) control that generates non-standard focus and event messages, the first interface being configured to provide data identifying a first user-driven event detected at the UI control to the recorder application,

a second interface between a recorder application and an input method editor (IME) executing on the computing system, the second interface being configured to provide data identifying a second user-driven event detected at the IME to the recorder application, and

a third interface between the recorder application and an application program, the third interface being configured to provide data identifying a third user-driven event detected at the application program to the recorder application, wherein the UI control and the application program are different, and wherein the first, second, and third user-driven events are different;

receive data identifying the first user-driven event detected at the UI control on the first interface, the second user-driven event detected at the IME on the second interface, and the third user-driven event detected at the application program on the third interface; and

record the data identifying the first user-driven event, the second user-driven event, and the third user-driven event.

8. The computer storage medium of claim 7, comprising further computer-executable instructions stored thereon that, when executed by the computer, cause the computer to:

provide the data identifying the first user-driven event detected at the UI control to a bug tracking application program;

provide the data identifying the second user-driven event detected at the IME to the bug tracking application program;

and

provide the data identifying the third user-driven event detected at the application program to the bug tracking application program.

9. The computer storage medium of claim 8, wherein the second interface comprises a text services framework.

10. The computer storage medium of claim 9, wherein the first interface comprises an accessibility interface.

11. The computer storage medium of claim 10, wherein the third interface comprises a system hook.

12. A method for recording user-driven events within a computing system, the method comprising:

executing a recorder application on the computing system, the recorder application configured to record user-driven events occurring within the computing system;

establishing a text services framework between the recorder application and an input method editor (IME);

establishing an accessibility interface between the recorder application and a user interface (UI) control that generates non-standard focus and event messages;

establishing an interface between the recorder application and an application program;

providing data identifying a first user-driven event detected at the IME by way of the text services framework between the recorder application and the IME;

recording the data identifying the first user-driven event detected at the IME by way of the recorder application;

providing data identifying a second user-driven event detected at the UI control by way of the accessibility interface between the recorder application and the UI control;

recording the data identifying the second user-driven event detected at the UI control by way of the recorder application;

providing data identifying a third user-driven event detected at the application program on the interface between the recorder application and the application program, wherein the UI control and the application program are different, and wherein the first, second, and third user-driven events are different;

recording the data identifying the third user-driven event detected at the application program by way of the recorder application; and

providing the data identifying the first user-driven event detected at the IME, the data identifying the second user-driven event detected at the UI control, and the data identifying the third user-driven event detected at the application program to a bug tracking application program for storage in a bug database.

13. The method of claim 12, wherein the interface between the recorder application and the application program comprises a system hook.