JP2011204139A - Operation recording program and device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily and appropriately generate data for repeatedly performing operations partially different but substantially similar to one another.SOLUTION: In the operation recording method: input by a key except a predetermined key is prohibited in response to an instruction of an operation recording start; script data to reproduce the operation of clicking are generated in response to the clicking; a text input screen is displayed in response to pressing on a test input key or clicking on a text input button to receive text input; script data to reproduce the text input are generated; an input and the like of a character string and a value associated with the character string are received in response to pressing of a definition reference input key or clicking on a definition reference input button; a value associated with the input character string is read from a definition file storing defined character strings and values associated with the defined character strings; and script data to input the value are generated.

Description

  The present invention relates to a technique for recording operation of a computer.

  For example, Japanese Unexamined Patent Application Publication No. 2007-4734 discloses a technique for reproducing an operation previously performed by a user or repeatedly executing a series of operations performed from a certain point in the past. Specifically, the information processing apparatus has a function of automatically recording operation histories in order of time series, and a function of automatically reproducing and storing operations retroactively to locations designated by the user on the time series. Then, the operations that can be performed by the user from the application are classified for each function in the contents of the operation history. In this function classification, contents are divided into those that allow the user to change contents at the time of reproduction, and those that allow the change are changed and reproduced as required by the user at the time of reproduction. However, it is not possible to devise a device that assumes the case where the same operation is repeatedly performed while changing only a part in different information processing apparatuses.

  Japanese Patent Application Laid-Open No. 2004-78268 discloses a technique for preventing operational errors and reducing labor and time required for operations in a system that is required to repeat the same or similar operation procedures. It is disclosed. Specifically, a script file, a setting file that defines parameter values for the script file, and a script engine that reads the script file and the setting file and executes processing specified in the script are prepared. A script is stored in the script file, and the script is a set of information including a command analyzed by the script engine and control information for controlling the interpretation of the script. The configuration file is a file that defines parameter values used by the script. While the script is fixed information that cannot be changed, the setting file information is changeable information. The script engine controls programs other than the script engine according to the script file and the setting file. However, it has not been considered how to generate the script file and the setting file.

JP 2007-4734 A JP 2004-78268 A

  As described above, when different operations are performed on different computers in a similar manner, but the same operation is repeated, for example, when setting up a network of multiple servers of the same company, it is easier and more appropriate. A method for generating data to be used is not disclosed.

  Accordingly, an object of the present invention is to provide a technique for more easily and appropriately generating data for repeatedly performing a partially different but substantially similar operation on different computers.

  An operation recording program according to one aspect of the present invention provides a computer with (A) a step of prohibiting key input other than a predetermined key after an operation recording start instruction or after activation, and (B) a click. Generating script data for reproducing the click operation and storing the script data in the data storage unit; (C) pressing a text input key included in a predetermined key or a text input button prepared separately; A text input screen is displayed in response to clicking of the button, a step of receiving the text input, generating script data for reproducing the text input, and storing the script data in the data storage unit; and (D) included in a predetermined key When a definition reference input key is pressed or a separately provided definition reference input button is clicked, the character string and the character string are associated. The input or selection of the defined value is accepted, and it is associated with the input or selected character string from the definition file storing the defined character string and the value associated with the defined character string. Generating a script data for reading out the input value and inputting the value, and storing it in the data storage unit; and (E) script data stored in the data storage unit after the operation recording is completed. And a step of outputting a file including a computer.

  In this way, after making the user specially aware of the key input during operation recording, script data that is input using the definition file is generated for the key input portion that differs for each device. Yes. In this way, script data can be easily generated for the user just by clicking, and for the key input, the script data can be appropriately generated while separating the normal key input and the key input portion that is different for each device. Can be generated.

  It should be noted that the definition reference script generation step described above receives the specific character string and the specific character string in the definition file in response to the input of the specific character string and the value associated with the specific character string. The method may include a step of storing a value associated with.

  As described above, the script data may be generated while the definition file is generated. The definition file may be customized for each device that is edited by the user and that executes the file including the script data.

  The program described above is stored in a computer-readable storage medium or storage device such as a flexible disk, a CD-ROM, a magneto-optical disk, a semiconductor memory, or a hard disk. Note that data being processed is temporarily stored in a storage device such as a computer memory.

  According to the present invention, it is possible to more easily and appropriately generate data for repeatedly performing a partially different but substantially similar operation on different computers.

FIG. 1 is a system outline diagram according to the embodiment. FIG. 2 is a diagram illustrating a window example of the operation recording program. FIG. 3 is a diagram showing a main processing flow in the embodiment. FIG. 4 is a diagram illustrating a window example of the operation recording program. FIG. 5 is a diagram showing a processing flow of key input related processing. FIG. 6 is a diagram showing a processing flow of the program activation processing. FIG. 7 is a diagram illustrating an example of an operation target window. FIG. 8 is a diagram illustrating an example of script data. FIG. 9 is a diagram illustrating a processing flow of the click process. FIG. 10 is a diagram illustrating an example of script data. FIG. 11 is a diagram illustrating the correspondence between classes and scripts. FIG. 12 is a diagram illustrating the correspondence between classes and scripts. FIG. 13 is a diagram illustrating an operation example on the operation target window. FIG. 14 is a diagram illustrating an example of script data. FIG. 15 is a diagram illustrating an operation example on the operation target window. FIG. 16 is a diagram illustrating an example of script data. FIG. 17 is a diagram illustrating an operation example on the operation target window. FIG. 18 is a diagram illustrating an example of script data. FIG. 19 is a diagram illustrating an operation example on the operation target window. FIG. 20 is a diagram illustrating an example of script data. FIG. 21 is a diagram illustrating an operation example on the operation target window. FIG. 22 is a diagram illustrating an example of script data. FIG. 23 is a diagram illustrating an operation example on the operation target window. FIG. 24 is a diagram illustrating an example of script data. FIG. 25 is a diagram illustrating an operation example on the operation target window. FIG. 26 is a diagram illustrating an example of script data. FIG. 27 is a diagram illustrating an operation example on the operation target window. FIG. 28 is a diagram illustrating an example of script data. FIG. 29 is a diagram illustrating an operation example on the operation target window. FIG. 30 is a diagram illustrating an example of script data. FIG. 31 is a diagram illustrating an operation example on the operation target window. FIG. 32 is a diagram illustrating an example of script data. FIG. 33 is a diagram illustrating an operation example on the operation target window. FIG. 34 is a diagram illustrating an example of script data. FIG. 35 is a diagram illustrating an example of a text input window. FIG. 36 is a diagram illustrating an example of script data. FIG. 37A is a diagram illustrating an operation example on the operation target window. FIG. 37B is a diagram showing an input window for definition names and definition values. FIG. 38 is a diagram illustrating an example of a definition file. FIG. 39 is a diagram showing an example of a definition name and definition value selection window. FIG. 40 is a diagram illustrating an example of script data. FIG. 41 is a diagram illustrating an operation example on the operation target window. FIG. 42 is a diagram illustrating an operation example on the operation target window. FIG. 43 is a diagram illustrating an example of script data. FIG. 44 is a diagram showing a processing flow of control input processing. FIG. 45 is a diagram showing a window configuration example after the recording is stopped. FIG. 46 is a diagram showing another example of the definition file. FIG. 47 is a functional block diagram when using a script file and a definition file. FIG. 48 is a functional block diagram of a computer.

  FIG. 1 shows an outline of a system according to an embodiment of the present invention. A display device 1 such as a liquid crystal display device or a CRT (Cathode Ray Tube) display, a keyboard 5, and a mouse 7 are connected to a computer 3 that performs operation recording. Although there are cases where it is connected to a LAN (Local Area Network) or the like, the description is omitted because it is not related to the following description.

  The computer 3 is installed with various programs (hereinafter referred to as a general program 39) including an operating system (OS), business application programs, and the like, and an operation recording program 31 according to the present embodiment. Will be executed accordingly. The computer 3 also has a data storage unit 33 such as a hard disk drive, which stores data of the general program 39 and the operation recording program 31, and also includes a script file 331 and a definition file 333 generated by the operation recording program 31. Is stored.

  The operation recording program 31 according to the present embodiment includes a click processing unit 311, a text input processing unit 312, a definition reference processing unit 313, a key input restriction unit 314, and an extended function processing unit 315. It is what is realized.

  Next, processing contents by the operation recording program 31 will be described with reference to FIGS. First, the user instructs the computer 3 to start the operation recording program 31. When the operation recording program 31 is activated, the operation recording program 31 prompts the user to specify a save destination directory and file name of the script file 331, for example. The operation recording program 31 receives designation of the save destination directory and file name of the script file 331 from the user, and opens the script file 331 having the designated file name in the data storage unit 33 in the designated save destination directory. Then, for example, a window as shown in FIG. 2 is displayed on the display device 1. In the example of FIG. 2, a recording start button, a script generation button, and a setting button are included. The script generation button cannot be clicked unless the operation record is completed. The setting button is a button for performing various settings and is not related to the present embodiment so that detailed description thereof is omitted. Here, it is assumed that the user clicks a recording start button.

  Then, the operation recording program 31 receives an instruction to start recording from the user (FIG. 3: step S1), and displays, for example, a window as shown in FIG. Since the recording start button shown in FIG. 2 is clicked, the recording start button is changed to a recording stop button. The script generation button and setting button do not change. Then, according to the recording start instruction, a text input button, a virtual key input button, a definition selection button, a program start button, a partial image collection button, a snapshot button, a reboot button, a TAG button, A target window designation button, a comment input button, an echo input button, a log input button, a free input button, a sleep input button, and a maximize button are displayed. Since the buttons below the partial image collection button are not related to the gist of the present embodiment, the description thereof is omitted. The virtual key input button is a button for inputting special keys such as Alt, Ctrl, Shift, and cursor movement. This virtual key input button is not related to the main point of the present embodiment and will not be described further.

  The symbol shown on the left side of each button is a hot key display, and can be instructed by pressing a key on the keyboard 5 instead of clicking the button.

  Further, the key input restricting unit 314 of the operation recording program 31 prohibits keyboard input other than the hot key after the recording start instruction (step S3). In this way, the user can be made aware of what key input is necessary. Specifically, whether it is normal text input, definition selection that must be changed for each computer that executes the script, or key input that must be input with a virtual key input button Let

  Then, the operation recording program 31 starts accepting an input from the user, and when accepting any input, performs the following processing (step S5).

  When this input is a hot key input or a click of a button corresponding to the hot key (step S7: Yes route), key input related processing is performed (step S9). When the key input related process ends, the process proceeds to step S19. The key input related process will be described with reference to FIGS.

  If the input accepted in step S5 is a click on the program start button or a press of the hot key “X” (FIG. 5: step S21), a program start process is performed (step S23). When this program activation process ends, the process returns to the original process via the terminal C. The program activation process will be described with reference to FIGS.

  For example, the text input processing unit 312 displays an input window such as an executable file name on the display device 1 (step S61). For example, a window as shown in FIG. 7 is displayed. Key input to this window is allowed. In the example of FIG. 7, a list of programs to be executed is further displayed and a radio button for selecting a program, a radio button for displaying a start menu and selecting a program, and one of those radio buttons. A program selection section including a button for confirming the selection, an input field for inputting an execution file name, a reference button for specifying the execution file name from the directory display, and an argument to be passed to the program to be executed , An input field for a work directory name of a program to be executed, a reference button for designating the work directory name from the directory display, an OK button for registering a setting input, and a setting input And a cancel button for canceling. The result of selecting the operation in the program selection field is reflected in the execution file name input field. The user performs input according to such a window and clicks the OK button.

  Then, for example, the text input processing unit 312 receives an input such as an execution file name from the user (step S63), generates a script including the execution file name and stores the script in the script file 331 (step S65). A script as shown in FIG. 8 is stored in the script file 331. The script shown in FIG. 8 is a script for executing a program having a designated execution file name. Then, for example, the text input processing unit 312 instructs the OS to activate the actually designated program among the general programs 39 (step S67).

  Note that the case where the program is not activated in FIG. 5 (step S21: No route) will be described below in a necessary scene.

  Returning to the description of the processing in FIG. 3, when step S9 ends, the operation recording program 31 determines whether the processing ends (step S19). If the processing is not ended, the operation recording program 31 returns to step S5 via the terminal B. On the other hand, when the end of the process is instructed, the process ends. Note that if the recording end button is not clicked and the end is instructed, or if the script generation button is not clicked and the end is instructed, the process is terminated with a warning to the user.

  On the other hand, if the input in step S5 is not a click of a hot key or a button corresponding to the hot key (step S7: No route) but a click with the mouse 7 (step S11: Yes route), the click processing unit 311 A click process is performed (step S13). This click process will be described with reference to FIGS. After the click process, the process proceeds to step S19.

  Click processing will be described with reference to FIG. It is assumed that the user first clicked on a window of a program to be operated in order to select the window.

  That is, the click processing unit 311 determines whether a window is selected, that is, whether a specific class (for example, Static) in the window for the activated program has been clicked (FIG. 9: Step S71), and the window is selected. In step S73, a script including the selected window name is generated and stored in the script file 331. For example, script data as shown in FIG. 10 is stored in the script file 331 at this stage. A portion surrounded by a dotted line in FIG. 10 is added in step S73. Here, the window name is “SwitchBtnTest”. After step S73, the process returns to the original process.

  Note that in the case of a click on a class “ComboLbox” other than the class shown in FIGS. 11 and 12 described below and the specific class, a script “SelectItem (“ text ”)” is generated and stored. Here, “text” is the text selected in the list box of the combo box.

  On the other hand, if it is not the selection of the window, the click processing unit 311 determines whether the button is clicked (step S75). More specifically, it is determined whether the click is for a class as shown in FIG. 11 in the click target window. That is, it is determined whether or not the list box and button class listed here are applicable. The table shown in FIG. 11 shows an example of a class name and a script to be generated correspondingly. In the case of the classes listed in FIG. 11, the click processing unit 311 has information about the selected button (selected text, clicked button, etc.) as shown in association with the table in FIG. And the click result is turned on or off), a script including the information is generated and stored in the script file 331 (step S77). Then, the process returns to the original process.

  On the other hand, when the class is not the class shown in FIG. 11 but the class shown in FIG. 12, the click processing unit 311 displays the coordinate value and the clicked coordinate value as shown in the table of FIG. The necessary information is acquired, a script including the click coordinate value and the acquired information is generated, and stored in the script file 331 (step S79). Then, the process returns to the original process.

  For example, it is assumed that a window as shown in FIG. 13 is an operation target window. The title of the window in FIG. 13 is “SwitchBtnTest” described above. Here, it is assumed that the user operates the mouse 7 and clicks the check box “Check 1” in the upper left to change from the unchecked state to the checked state. In such a case, the process proceeds to step S77 to generate a script as shown within the dotted line in FIG. With the class on the second line in FIG. 11, a script including the window title and information on the clicked check box is generated. Here, the style is “Check 1”, the caption is “1”, and the state is “true”. The state “true” means waiting for processing of the pressed button, and the state “false” means keeping the button closed.

  Next, assume that a mouse operation as shown in FIG. 15 is performed, for example. That is, it is assumed that the check state “Check2” is clicked to change the check state to the unchecked state. In such a case, the process proceeds to step S77 to generate a script as shown in the dotted line in FIG. With the class on the second line in FIG. 11, a script including the window title and information on the clicked check box is generated. Here, the style is “Check 2”, the caption is “0”, and the state is “true”.

  Next, assume that a mouse operation as shown in FIG. 17 is performed, for example. That is, it is assumed that the check box “¥” is clicked to change the unchecked state to the checked state. In such a case, the process proceeds to step S77 to generate a script as shown in the dotted line in FIG. With the class on the second line in FIG. 11, a script including the window title and information on the clicked check box is generated. Here, the style is “¥¥¥” for representing “¥”, the caption is “1”, and the state is “true”.

  Further, for example, it is assumed that a mouse operation as shown in FIG. 19 is performed. That is, it is assumed that the option “Radio 2” in the center of the three radio buttons at the lower left is clicked. The selection for the option “Radio1” is canceled. In such a case, the process proceeds to step S77 to generate a script as shown in the dotted line in FIG. With the class on the second line in FIG. 11, a script including the window title and information on the clicked radio button is generated. Here, the style is “Radio2”, the caption is “1”, and the state is “false”.

  Further, assume that a mouse operation as shown in FIG. 21 is performed, for example. That is, it is assumed that the option “Radio3” is clicked under the three radio buttons on the lower left. The selection for the option “Radio 2” is canceled. In such a case, the process proceeds to step S77, and a script as shown within the dotted line in FIG. 22 is generated. With the class on the second line in FIG. 11, a script including the window title and information on the clicked radio button is generated. Here, the style is “Radio3”, the caption is “1”, and the state is “false”.

  Further, assume that a mouse operation as shown in FIG. 23 is performed, for example. In other words, it is assumed that the selected state is changed to the non-selected state by clicking the button in the upper center. In such a case, the process proceeds to step S77, and a script as shown within the dotted line in FIG. 24 is generated. With the class on the second line in FIG. 11, a script including the window title and information on the clicked button is generated. Here, the style is “Push Btn”, the caption is “0”, and the state is “true”.

  Further, assume that a mouse operation as shown in FIG. 25 is performed, for example. In other words, it is assumed that the selected state is transitioned to the non-selected state by clicking the check box at the upper center. In such a case, the process proceeds to step S77 to generate a script as shown in the dotted line in FIG. With the class on the second line in FIG. 11, a script including the window title and information on the clicked check box is generated. Here, the style is “3-state”, the caption is “0”, and the state is “true”.

  Further, assume that a mouse operation as shown in FIG. 27 is performed, for example. In other words, it is assumed that the button “Radio5” is clicked among the buttons “Radio4” and “Radio5” of the exclusive buttons in the lower center, and the button “Radio5” is changed to the selected state. In such a case, the process proceeds to step S77 to generate a script as shown in the dotted line in FIG. With the class on the second line in FIG. 11, a script including the window title and information on the clicked check box is generated. Here, the style is “Radio 5”, the caption is “1”, and the state is “false”.

  Further, assume that a mouse operation as shown in FIG. 29 is performed, for example. That is, it is assumed that the list view box “ListView Item 1” (not the check box) in the upper right column is clicked to change the non-selected state to the selected state. In such a case, the process moves to step S79, and a script as shown within the dotted line in FIG. 30 is generated. With the class on the first line in FIG. 12, a script including the window title, the click coordinate value, and the information to be clicked is generated. “295, 65” in the second line of the script is a click coordinate value. Further, the first argument “0” of ctlMouseEventR represents a left click, “1” represents a right click, and “2” represents a double click. Also, “ListView Item 1” in the third line of the script is the text to be clicked.

  Further, for example, it is assumed that a mouse operation as shown in FIG. 31 is performed. In other words, it is assumed that the list state box “ListView Item 2” (not the check box) in the upper right column is clicked to change the selected state to the non-selected state. In such a case, the process proceeds to step S79, and a script as shown within the dotted line in FIG. 32 is generated. With the class on the first line in FIG. 12, a script including the window title, the click coordinate value, and the information to be clicked is generated. “295, 81” in the second line of the script is a click coordinate value. In addition, “ListView Item 2” in the third line of the script is text to be clicked.

  Further, assume that a mouse operation as shown in FIG. 33 is performed, for example. That is, it is assumed that the text input column 3310 in the middle right column is clicked. Next, preparations are made for inputting text. In such a case, the process proceeds to step S79, and a script as shown within the dotted line in FIG. 34 is generated. Because of the class on the sixth line in FIG. 12, a script including the window title and the click coordinate value is generated. “323, 180” in the second line of the script is a click coordinate value.

  Thereafter, the user performs text input. However, as shown in step S3, keyboard input other than the hot key is prohibited, so the user clicks the text input button of the operation recording program 31 or the hot key. Press down “1”.

  Such a case will be described with reference to FIG. In step S5, an input is accepted, and it is determined that this input is a hot key input or a corresponding button click, and key input related processing is performed (step S9). Shifting to the description of the key input related process (FIG. 5), when it is determined in step S21 that it is not an instruction to start a program (step S21: No route), and it is determined that the input is text ( Step S25: Yes route), the text input processing unit 312 displays a text input window on the display device 1 (step S27). For example, a window as shown in FIG. 35 is displayed.

  As shown in FIG. 35, a window including a character string input field is displayed, and the key input restriction unit 314 permits key input. In the example of FIG. 35, the text “test” is input. If a line break is necessary, check the “Add line break” check box. Then click the send button. To cancel, click the cancel button.

  The text input processing unit 312 receives the input text (step S29), generates a script including the input text, and stores it in the script file 331 (step S31). For example, a script within a dotted line in FIG. 36 is generated. In this example, the window title and the input text “test” are included. Then, the process returns to the original process. Note that the input text is also transmitted to the operation recording target program, and as shown in FIG. 37A, the text “test” is entered in the text input field 3310.

  Here, it is assumed that the user has determined that it is necessary to input text having different contents depending on the computer that executes the script file 331. Such text is different from the following example, but is, for example, an IP address that is different for each device or other parameters. In such a case, the definition selection button in the window of FIG. 4 is clicked or the associated hot key “3” is pressed down.

  Such a case will be described with reference to FIG. In step S5, an input is accepted, and it is determined that this input is a hot key input or a corresponding button click, and key input related processing is performed (step S9). Shifting to the description of the key input related process (FIG. 5), it is determined that it is not an instruction to start a program in step S21 (step S21: No route) and is not an instruction to input text in step S25. When it is determined that the instruction is for selecting a definition (step S25: No route) (step S33: Yes route), the definition reference processing unit 313 checks whether the definition file 333 already exists in the data storage unit 33. (Step S37).

  If the definition file 333 does not exist, the definition reference processing unit 313 displays an input window for generating the definition file 333, and inputs a file name and the like, and the specified file name. The definition file 333 is generated in the data storage unit 33 (step S39). Then, the definition reference processing unit 313 causes the display device 1 to display a definition name and definition value setting window (step S41). For example, a window as shown in FIG. 37B is displayed. In the example of FIG. 37B, a definition name input field, a definition value input field, an OK button, and a cancel button are provided. In this example, the definition name “TESTDATA” is input, the definition value “10” is input, and the OK button is clicked.

  The definition reference processing unit 313 receives the definition name and the definition value, and stores the definition name and the definition value in the definition file 333 (step S43). For example, data as shown in FIG. 38 is stored in the definition file 333. Here, the definition name and the definition value are registered by connecting with “=”.

  When it is determined in step S37 that the definition file 333 exists or after step S43, the definition reference processing unit 313 displays a definition name and definition value selection window on the display device 1 (step S45). For example, a window as shown in FIG. 39 is displayed. In the example of FIG. 39, a field for displaying a plurality of pairs of definition names and definition values, an add button, an edit button, a delete button, a select button, and a cancel button are provided. In such a window, it is assumed here that the definition name and the definition value registered in steps S41 and S43 are selected. That is, after selecting the row 3910, the selection button is clicked.

  As described above, when any row is selected and the selection button is clicked (step S47: Yes route), the definition reference processing unit 313 receives a selection instruction from the user and recognizes that the selection instruction has been made. (Step S47: Yes route), a script for reading out the corresponding definition value including the selected definition name from the definition file 333 is generated and stored in the script file 331 (Step S49). For example, the script within the dotted line in FIG. 40 is generated. In the dotted line of FIG. 40, the first line includes the title of the operation target window, and the second line includes the selected definition name “TESTDATA”. Thus, when the script file 331 is executed, the corresponding definition value “10” is actually read. After step S49, the definition value “10” corresponding to the definition name selected this time is sent to the operation target window, and the definition value “10” is displayed in the input field 3310 as shown in FIG. After step S49, the process returns to the original process.

  In the window shown in FIG. 39, when an add button or a specific row is selected and a change button is clicked (step S51), the process returns to step S41. Here, the definition name and the definition value are added, or at least one of the definition name and the definition value is corrected and registered. On the other hand, when the user clicks the delete button after selecting a specific row instead of clicking the add button or the change button, the definition reference processing unit 313 defines the definition name and definition of the selected row in the definition file 333. The value pair is deleted (step S53). Then, the process proceeds to step S45 via the terminal D.

  Furthermore, when the definition selection hot key is not pressed in step S33, the extended function processing unit 315 performs processing corresponding to the pressed hot key or the clicked button (step S35). Then, the process returns to the original process via the terminal C.

  By carrying out the processing as described above, even if it is necessary to input different values on different computers, it is only necessary to change the definition file 333. Therefore, it is possible to make an error rather than generating the script file 331 for each computer. It can be reduced and dealt with efficiently.

  Next, it is assumed that the user clicks an OK button in the operation target window as shown in FIG. In such a case, the process proceeds to step S77, and a script as shown within the dotted line in FIG. 43 is generated. With the class on the second line in FIG. 11, a script including the window title and information on the clicked button is generated. Here, the style is “OK”, the caption is “1”, and the state is “false”.

  It is assumed that the operation recording has been completed so far. Then, the user clicks a recording end button in the operation recording program 31 window.

  The processing for this will be described with reference back to FIG. In step S5, an input is accepted, and it is determined that this input is not a hot key input or a corresponding button click (step S7: No route) but a click (step S11: No route). When a button such as recording stop in the window of the operation recording program 31 is clicked (step S15: Yes route), a control input process is performed (step S17). If it is not a control input, the process proceeds to step S19 via the terminal A. The control input process will be described with reference to FIGS. 44 and 45. When it is determined that the recording stop button has been clicked (step S81: Yes route), the key input restriction unit 314 cancels the prohibition of keyboard input (step S83). Here, the window of the operation recording program 31 is in a state as shown in FIG. 45, for example. Here, a recording start button, a script generation button, and a setting button can be clicked. In this state, the operation recording program 31 further accepts input from the user (step S84).

  If the script output button is clicked in step S84 (step S85: Yes route), the operation recording program 31 closes the script file 331 in the data storage unit 33 (step S87) and returns to the original process. . Further, the script output button is not clicked (step S85: No route), and when the recording start button is clicked (step S89: Yes route), the process returns to step S1 of FIG. When the recording restart button is not clicked (step S89: No route), and the setting button is clicked, the operation recording program 31 performs processing such as setting (step S91). Then, the process returns to the original process. Note that the processing such as setting is not the main part of the present embodiment, and thus description thereof is omitted.

  By performing the processing as described above, the user can easily generate a script file. Furthermore, for device-specific text input, by generating a script that can be read from the definition file, the parts that need to be changed are aggregated into the definition file, making it possible to easily handle individual devices while reducing errors. Yes.

  That is, a definition file 333 as shown in FIG. 38 is used for a certain apparatus, but it is used after changing to a definition file as shown in FIG. 46 for another apparatus. That is, TESTDATA = 10 is changed to TESTDATA = 30. In this way, the definition file 333 is prepared by changing each device.

  The operation recording program 31 has a function of reading the value of the corresponding data item from another file holding device-specific data such as an IP address and changing the definition value of the corresponding definition name in the definition file 333. You may make it provide. Such a function may be prepared as a tool in addition to the operation recording program 31.

  Further, as shown in FIG. 47, the script file 331 and the definition file 333 generated in this way are interpreted by the script engine 4100 to reproduce the operation performed on the operation recording target program 4200. , Input and other operations are performed. Since this technique is described in, for example, Japanese Patent Application Laid-Open No. 2004-78268, it will not be described further.

  Although one embodiment of the present invention has been described above, the present invention is not limited to this. For example, the functional block diagram described above is an example, and may not necessarily match the actual program module configuration. As for the processing flow, as long as the processing result does not change, the processing order may be changed or the processing flow may be executed in parallel.

  Furthermore, the window configuration of the operation recording program 31 is an example, and other configurations may be used. Also, hot keys may be assigned to all buttons so that window display itself is not performed.

  Further, the keyboard input is restricted after the operation recording is started, but the keyboard input may be restricted according to the activation of the operation recording program 31.

  As shown in FIG. 48, the computer 3 described above includes a memory 2501, a CPU 2503, a hard disk drive (HDD) 2505, a display control unit 2507 connected to the display device 2509, and a drive device for the removable disk 2511. 2513, an input device 2515, and a communication control unit 2517 for connecting to a network are connected by a bus 2519. An operating system (OS) and an application program for executing the processing in this embodiment are stored in the HDD 2505, and are read from the HDD 2505 to the memory 2501 when executed by the CPU 2503. If necessary, the CPU 2503 controls the display control unit 2507, the communication control unit 2517, and the drive device 2513 to perform necessary operations. Further, data in the middle of processing is stored in the memory 2501 and stored in the HDD 2505 if necessary. In an embodiment of the present technology, an application program for performing the above-described processing is stored in a computer-readable removable disk 2511 and distributed, and installed from the drive device 2513 to the HDD 2505. In some cases, the HDD 2505 may be installed via a network such as the Internet and the communication control unit 2517. Such a computer apparatus realizes various functions as described above by organically cooperating hardware such as the CPU 2503 and the memory 2501 described above, the OS, and necessary application programs.

DESCRIPTION OF SYMBOLS 1 Display apparatus 3 Computer 5 Keyboard 7 Mouse 31 Operation recording program 33 Data storage part 39 General program 311 Click process part 312 Text input process part 313 Definition reference process part 314 Key input restriction part 315 Extended function process part

Claims (3)

A step of prohibiting key input other than a predetermined key in response to an instruction to start operation recording or after activation;
Generating script data for reproducing the click operation in response to the click, and storing the script data in the data storage unit;
In response to pressing of a text input key included in the predetermined key or clicking on a separately provided text input button, a text input screen is displayed to accept the text input and reproduce the text input. Generating script data and storing it in the data storage unit;
In response to pressing of a definition reference input key included in the predetermined key or clicking on a separately provided definition reference input button, the input or selection of a character string and a value associated with the character string is accepted and defined. To read the value associated with the input or selected character string from the definition file storing the already associated character string and the value associated with the defined character string and to input the value Generating the script data and storing the definition reference script in the data storage unit;
Outputting a file containing the script data stored in the data storage unit after the operation recording is completed;
Is an operation recording program for causing a computer to execute. The definition reference script generation step includes:
The step of storing the specific character string and the value associated with the specific character string in the definition file in response to the input of the specific character string and the value associated with the specific character string The operation recording program according to claim 1, comprising: Means for prohibiting key input other than a predetermined key in response to an operation record start instruction or after activation;
In response to a click, means for generating script data for reproducing the click operation and storing it in a data storage unit;
In response to pressing of a text input key included in the predetermined key or clicking on a separately provided text input button, a text input screen is displayed to accept the text input and reproduce the text input. Means for generating script data and storing it in the data storage unit;
In response to pressing of a definition reference input key included in the predetermined key or clicking on a separately provided definition reference input button, the input or selection of a character string and a value associated with the character string is accepted and defined. To read the value associated with the input or selected character string from the definition file storing the already associated character string and the value associated with the defined character string and to input the value A script for generating a reference script for generating the script data and storing the script data in the data storage unit;
Means for outputting a file containing the script data stored in the data storage unit after the operation recording is completed;
An operation recording apparatus.

Images