JP2011238091A - Information processing device, image forming device, information processing method, program and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a device capable of easily and quickly performing a feature expansion of a web browser installed in the device without changing the web browser.SOLUTION: The device is an information processing device or an image forming device provided with a data processing section to process content data including document data written in a markup language. The device has one or more script execution sections additionally installed to execute one or more undefined scripts other than a defined script for which a data processing section can execute. The device also has a script execution management section. The script execution management section receives a script execution request from the data processing section when the script execution request generated by the data processing section to process a detected event is the script execution request for the undefined script. Then the script execution management section transmits the execution request to one or more of the script execution sections in series to inquire for practicability thereof and makes a practicable script execution section execute the undefined script.

Description

  The present invention relates to an information processing apparatus and an image forming apparatus that can easily and quickly cope with function expansion, an information processing method executed by the function expanded apparatus, a computer-readable program for executing the method, and a recording medium .

  Web pages, which are documents published on the Internet, are created using a markup language such as HTML (Hyper Text Markup Language), specify the structure of the HTML document using commands called tags, The image is displayed with different sizes and colors. The document described in HTML is an HTML document, and this HTML document is stored as an HTML file in a content server or the like for providing the HTML file.

  When browsing an HTML document, application software called a web browser is used to access the above-described server, acquire an HTML file from the server, and open the file. The Web browser is configured to interpret the tag of the HTML file and display it on the screen as specified by the tag.

  In addition to the display of the HTML document described above, the Web browser uses an object-oriented script language called JavaScript (registered trademark) to display a different message depending on the accessed time zone, which is a dynamic display. An alert (warning dialog box) can be displayed.

  Javascript (registered trademark) is a programming language that supports object-oriented programming that configures a program as a collection of objects composed of a collection of related data (attributes) and a procedure (method) for the collection of data. This JavaScript (registered trademark) is described using a script tag, and an attribute value can be specified to the tag, and an attribute can be added. By adding an attribute, a specific instruction can be added or a more detailed background can be added. You can specify effects such as color and character modification. In order to interpret and execute such Javascript (registered trademark), the web browser is implemented with code for interpreting and executing the Javascript (registered trademark).

  Application development in Javascript (registered trademark) is text-based, so it is easier to develop than using software development kits (SDK) for devices and Java (registered trademark) applets. be able to. Conventionally, hard coding has been adopted in order to implement a code for interpreting and executing the above-described Javascript (registered trademark) in a Web browser. Hard coding is a programming method for describing processing and data in a source code for the purpose of operating in a specific operating environment.

  In a Web browser mounted on a PC, an image forming apparatus, or the like, there is a case where it is desired to mount an original Javascript (registered trademark) and perform an operation specific to the apparatus. For example, the login user name or serial number of the apparatus is acquired from Javascript (registered trademark), and arbitrary processing is performed accordingly, or reading or printing is performed by Javascript (registered trademark). In order to realize this device-specific operation, a code for interpreting and executing a unique JavaScript (registered trademark) can be created, and the code can be implemented in a web browser by hard coding.

  For example, an HTML document acquired by a Web browser from a Web server is embedded in the HTML document acquired by the Web browser as a device that implements a code for interpreting and executing a unique JavaScript (registered trademark) in the Web browser. As a result, a device is proposed in which a document dynamically adapted to a specific embedded device in which the Web browser is embedded is generated and displayed by client-side processing. (See Patent Document 1).

  As described above, the Web browser of the embedded device provides a unique Javascript (registered trademark) execution function, so that dynamic contents corresponding to access from the embedded browser can be easily and flexibly expanded by the server side. It is possible to provide a control method in which privacy and security of client-side information can be protected.

  As described above, in the conventional apparatus or method, when a new unique JavaScript (registered trademark) attribute or method is added to the Web browser of the information processing apparatus or image forming apparatus, the JavaScript (registered) of the Web browser is registered. It is necessary to add or change code for analyzing and executing the trademark. This requires a man-hour (amount of work) for changing the Web browser itself and evaluating the range affected by the change, and the problem that it is not possible to flexibly cope with the addition of Javascript (registered trademark) functions. there were.

  In addition, Web browsers are upgraded every day in order to deal with defects, increase speed, realize a new architecture, and the like, and there is a case where it is desired to upgrade the Web browser installed in the apparatus. If the code for interpreting and executing Javascript (registered trademark) is re-implemented for the Web browser each time, the change of the Web browser cannot be quickly handled.

  Therefore, it has been desired to provide an apparatus that can easily and quickly cope with function expansion without changing the Web browser itself for a Web browser installed in such an apparatus.

  In view of the above problems, the present invention does not incorporate a unique script into a browser by hard coding, but implements the script with a plug-in and implements the plug-in as a COM (Component Object Model) interface. COM is a technical specification that is a basis for creating and using a componentized program, and the COM interface is a program component that can exchange data based on the COM. This COM interface has a feature that it can be used from any language and anywhere, regardless of the language or component used for development. For this reason, there is an advantage that the plug-in need not be corrected even if the environment for calling the plug-in changes without depending on the browser.

  When processing is requested from the plug-in side to the browser, for example, if the browser side is changed, such as a dialog display request or a script function execution request in a page, the plug-in side also changes the processing to perform the request. There must be. In order to solve this problem, an interface for requesting processing by the plug-in to the browser is provided to the plug-in as a library. As a result, differences in processing on the browser side can be absorbed by the library, so that even if the browser is changed due to version upgrade or the like, there is no need to modify the plug-in.

  Therefore, the above-described problems can be solved by providing an information processing apparatus and an image forming apparatus of the present invention that substantially employ these configurations.

  An information processing apparatus and an image forming apparatus that executes print processing in response to a print request include a data processing unit that processes content data including document data described in a markup language. These devices include one or more script execution units that are additionally implemented to execute one or more undefined scripts other than the predefined scripts that can be executed by the data processing unit, and a data processing unit, When an execution request for a script generated to process a detected event is an execution request for an undefined script, the execution request for the undefined script is accepted from the data processing unit, and one or more execution requests for the undefined script are received. The script execution unit is inquired as to whether or not the script execution unit can execute the script, and the executable script execution unit causes the undefined script to be executed.

  The above plug-ins can be easily added or deleted as script execution units managed by the script execution management unit, and even undefined scripts added for function expansion are executed by the implemented script execution unit can do.

  The one or more script execution units form a hierarchical structure, and the execution request for the undefined script can be executed in order from the upper script execution unit to the lower script execution unit in the hierarchical structure. It is configured to inquire whether or not there is, and to execute the undefined script in a subordinate executable script execution unit. Therefore, after execution, the lower-level script execution unit notifies the execution result to the higher-level script execution unit, the higher-level script execution unit to the script execution management unit, and the script execution management unit to the data processing unit.

  Further, an interface unit is provided that is called in response to a processing request from the script execution unit to the data processing unit and transmits an execution request that can be executed by the data processing unit in response to the processing request to the data processing unit. As a result, even if the data processing unit is updated due to version upgrade or the like, it is not necessary to update the script execution unit correspondingly, and labor can be saved.

  In the present invention, in addition to the information processing apparatus and the image forming apparatus, an information processing method executed by these apparatuses, a computer-readable program for executing the method, and a recording medium on which the program is recorded can be provided. Is possible.

1 is a diagram illustrating a network environment including an information processing apparatus and an image forming apparatus according to the present invention. 1 is a component configuration diagram of an information processing apparatus and an image forming apparatus of the present invention. The sequence diagram which showed the flow of the process at the time of executing an original script. The sequence diagram which showed the flow of the process which displays a confirmation alert. The sequence diagram which showed the flow of the process when the state change of an apparatus occurred. The flowchart which showed the flow of the process performed with a script parser. The flowchart which showed the flow of the process performed with a plug-in manager. Class configuration diagram including a plug-in manager and plug-in classes. The figure which illustrated the hierarchical structure of the object. The figure which showed the example of a description by the programming language of the process which receives the notification from the process request to a web browser which a utility performs, and a web browser.

  FIG. 1 is a diagram illustrating a network environment including an information processing apparatus and an image forming apparatus according to the present invention. The information processing apparatus shown in FIG. 1 is a PC 100, and the image forming apparatus is an MFP (Multi Function Peripheral) 110. In addition to these, external servers 130 and 140 are connected to a network 120.

  The PC 100 includes a CPU that executes an OS and various applications, and controls the entire apparatus and performs various arithmetic processes. For example, the CPU performs communication via the network 120, receives input from the user, outputs calculation results and the like to the display device, reproduces content, rips, stores data to the storage device, data from the storage device, and the like Reading, data management, etc.

  The PC 100 includes a communication interface for performing the above-described communication, and also includes an input device for receiving input from the user. The communication interface can include a LAN terminal, a modem, an antenna for realizing a wireless LAN, and a transceiver. Input devices include a keyboard for inputting letters and numbers, movement of the cursor displayed on the screen, selection of windows, icons, etc., mouse for realizing button pressing, fingers, stylus, etc. It is possible to employ a touch panel that realizes movement of the cursor on the screen, selection of icons, and the like. Moreover, a liquid crystal display, CRT, etc. are employable as a display apparatus mentioned above. Furthermore, as a storage device, ROM, RAM, HDD, etc. can be provided and stored in an SD card, CD-R, CD-RW, DVD-R, DVD-RW, DVD-RAM, etc. as an external storage device. SD card slot, CD drive, DVD drive, and the like.

  In addition, the PC 100 can include a speaker for outputting sound, an IEEE 1394 device, a USB device, and the like for connecting AV equipment and other equipment.

  Similar to the PC 100, the MFP 110 includes a CPU, a ROM as a storage device, a RAM, an HDD, a display device, an input device, a communication interface, a speaker, an IEEE 1394 device, a USB device, an SD card slot, and the like. The MFP 110 includes an operation panel as a display device and an input device, and includes a plurality of keys as the input device.

  Further, the MFP 110 includes an image reading device and a printer in order to realize printing, FAX transmission / reception, copying, and image reading. The image reading apparatus irradiates light from a cover for shielding external light, a transparent plastic or glass platen for placing a document under the cover, and a document platen from below the platen. A light source, an image sensor that receives light reflected from the document and converts it into an electrical signal, and an AD converter for converting the analog signal into a digital signal because the converted electrical signal is an analog signal. Yes.

  Here, the configuration of the reflection type image reading apparatus has been described. However, the image reading apparatus may be a transmissive type. In the case of the transmissive type, a light source is provided on the cover, and light is irradiated from the cover side, and the document and The light transmitted through the document table can be received by the image sensor. Note that a CCD image sensor, a CMOS image sensor, or the like can be used as the image sensor, and the light that has passed through the document table is not directly received by the image sensor but also reflected by one or more mirrors. Further, it may be configured to be incident on the image sensor.

  The printer employed in the MFP 110 can be a laser printer, and print image data sent from the PC 100 is developed on a memory by a CPU provided in the MFP 110, and the image is formed using a laser. That is, this printer includes an exposure device that irradiates a laser as writing light based on print image data, a photoconductor on which a latent image similar to the image is formed on the surface by irradiating the laser, and the photosensitive A charging unit that charges the body before the laser is irradiated, a developing unit that attaches toner to the photosensitive member on which the latent image is formed and develops, a paper feeding unit that feeds paper, and rotation of the photosensitive member The toner image formed on the surface by the transfer unit for transferring the toner image transferred onto the fed paper, the fixing unit for fixing the toner image transferred on the paper to the paper by applying heat and pressure, and the toner image fixed. And a paper discharge unit for discharging the printed paper.

  In addition, the printer can include a cleaning unit for removing toner remaining on the photosensitive member, a plurality of rollers for conveying paper in a predetermined direction, and the like.

  Since the MFP 110 requires an automatic document feeder (ADF) and high-speed image processing to automatically convey the document onto the document table, the MFP 110 can further include an ASIC that is a dedicated circuit for image processing.

  When reading the document, the MFP 110 can read the document using the image reading apparatus described above. In the case of printing, it is possible to print by forming a latent image on the surface of the photoconductor with a laser based on the sent print data, developing it, and transferring and fixing it on paper. it can. In the case of copying, an original can be read using an image reading device, and printed out by a printer based on the read data.

  In the case of FAX transmission, an original can be decomposed and read into two-dimensional information lines or points by an image reading device, digitally modulated using a modem, and sent to a communication line such as a telephone network. On the other hand, in the case of FAX reception, a signal transmitted via a communication line can be demodulated using a modem to restore a document.

  The data read by the image reading device, the data after the data is compressed and converted, and the data received by FAX can be stored in a storage device such as a memory.

  Examples of the network 120 include an intranet constructed within a limited range such as in-house, and the Internet where the range is not limited. As with the PC 100 described above, the external servers 130 and 140 are configured to include a CPU, a storage device, and a communication interface, and may include a display device and an input device.

  The external servers 130 and 140 provide content data including document data described in a markup language. Here, the markup language is a description language in which text paragraphs and font sizes are specified, and links to images and other documents are described using character strings called tags. As this markup language, HTML (Hyper Text Markup Language) or the like is used. There is a Web page in the content data including the HTML file described in HTML. The external servers 130 and 140 can provide this Web page in response to a request from the PC 100 or the MFP 110. The PC 100 and MFP 110 request the external servers 130 and 140 to browse the Web page, and a Web browser is installed to receive the Web page.

  The PC 100 and the MFP 110 request a web page from the web browser to the external servers 130 and 140, interpret the HTML file of the web page transmitted from the external server 130 and 140, and display the content of the web page on the browser screen. Can do. The external servers 130 and 140 implement a web server as application software in order to respond to a request from the web browser.

  Communication between the Web browser installed on the PC 100 and the MFP 110 and the Web server installed on the external servers 130 and 140 uses HTTP (Hypertext Transfer Protocol) as a communication protocol, and transmits / receives content data including an HTML file. Is called.

  The PC 100 and the MFP 110 provide basic functions commonly used by application software, such as input / output functions and memory management, in order to operate a Web browser as application software, and manage the entire apparatus. OS (Operating System) which is basic software is installed.

  In addition to the application software, the MFP 110 includes a printer application that executes a print job, a copy application that executes a copy job, a fax application that executes a fax transmission / reception job, and a scanner application that executes a scan job. As an interface between these applications and the OS, an API (Application Programming Interface), a Java (registered trademark) virtual machine (JVM), or the like can be provided. The API is an interface for calling an OS function when an application program such as a printer application is described. The JVM converts a Java (registered trademark) byte code into a native code operable on the OS and executes it. Is. For this reason, when the JVM is implemented, the application software can be implemented by a Java (registered trademark) bytecode.

  FIG. 2 is a component configuration diagram of the information processing apparatus and the image forming apparatus shown in FIG. These apparatuses include a Web browser 200, a plug-in manager 210, a plug-in 220, a utility 230, and a device SDK 240 as components. The Web browser 200 includes an event process 201, a UI 202, and a script parser 203.

  The web browser 200 is executed by the CPU and performs data processing such as requesting content data from the web server and displaying the content data provided from the web server. Function as. Similarly, the plug-in manager 210, the plug-in 220, the utility 230, and the device SDK 240 are also executed by the CPU and perform the respective processes, so that they are executed by the CPU and executed by the script execution management unit, script execution unit, interface unit, Each functions as a device control unit. The actual processing is executed by the data processing unit, script execution management unit, script execution unit, interface unit, and device control unit. In order to facilitate the explanation and make it easier to understand the contents, the Web browser 200 will be described below. , Plug-in manager 210, plug-in 220, utility 230, and device SDK 240 will be used for explanation.

  The Web browser 200 communicates with a Web server mounted on the external servers 130 and 140 based on URI (Uniform Resource Identifier) that is an identifier indicating content data in a certain format and HTTP, and acquires target content data. The acquired content data is analyzed according to the type, and based on the analysis result, text, an image, etc. are arranged at an appropriate position, a character size is adjusted, a color is added, and the like are displayed.

  In the Web browser 200, the UI 202 accepts a data acquisition instruction from the user as an input, and arranges characters, images, and the like included in the acquired content data at appropriate positions, and displays characters adjusted and the like. . The Web browser 200 can include an HTML parser (not shown) in order to analyze an HTML document included in the content data and to issue a layout instruction to the UI 202.

  The event process 201 processes an event generated by a user input or the like. Further, the event process 201 is executed when a predefined script, for example, an arbitrary input key is pressed in the Web browser 200 described by hard coding for function expansion of the Web browser 200 is pressed. In addition to scripts and the like, scripts that are not pre-defined in the Web browser 200, such as scripts for acquiring values set in the apparatus and setting values, scripts relating to security and important processing, ie, for function expansion An execution request for a script that is uniquely created and added to the apparatus or a modified script is generated to process the detected event, and is sent to the script parser 203.

  The script includes an attribute as additional information related to the properties and settings of the object to be operated, and a method that defines an operation on the object. For this reason, examples of undefined scripts that are not defined in the Web browser 200 include those in which these attributes and methods are added or changed. In order to execute an undefined script, a code for interpreting and executing the script is required. The code is provided as a plug-in 220 that is a program for adding a function, and is provided as a plug-in 220 to the apparatus. Implemented.

  When the event process 201 receives a value acquisition, setting, key input, or the like from the user, or when it is necessary to display a confirmation alert (warning or caution) according to the type of security or processing, the event process 201 Is generated, a script execution request corresponding to the event is generated and sent to the script parser 203. For example, if the user sets an arbitrary value, an event is generated by the input of the value by the user, a setting request including the value is generated in response to the event occurrence, and is sent to the script parser 203.

  When a script execution request is received from the event process 201, the script parser 203 determines whether the script execution request is defined in the Web browser 200 or undefined. If the processing requested by the execution request is hard-coded in the script language and is already defined, the script parser 203 interprets the request as requiring the processing and executes the processing. can do. However, if the request is an execution request for an undefined script, the script parser 203 interprets it and cannot execute it because there is no code to execute, and requests the plug-in manager 210 to execute the script. To do.

  The plug-in manager 210 manages a plurality of plug-ins 220 for executing undefined scripts. Based on the script execution request received from the script parser 203, the plug-in manager 210 executes the plug-in corresponding to the script, that is, the script. Search for a plug-in that can do that and request that corresponding plug-in to execute the script.

  The plug-in 220 is implemented as a COM (Component Object Model) interface so that the plug-in 220 does not depend on the plug-in development language and can be used even when the environment for calling the plug-in changes. As a result, it is not necessary to modify the plug-in, and the plug-in can be developed in various programming languages. Further, identification information for identifying the plug-in 220 is registered in the plug-in manager 210 so as to be managed by the plug-in manager 210 at the time of mounting.

  Plug-in 220 calls device SDK 240 to access device resources. Note that the device SDK 240 performs acquisition of values stored in the memory, setting of the values, detection of pressing of an input key, and the like.

  The plug-in 220 calls the utility 230 provided from the Web browser 200 in order to request the Web browser 200 to perform processing such as screen display. The utility 230 is an interface for the plug-in 220 to request processing from the Web browser 200, and is implemented as a library. Since this interface is a library made up of a plurality of program parts that are divided into parts that can be used from various programs, it can be used from a plurality of plug-ins. As a result, the utility 230 requested from the plug-in 220 can appropriately notify the requested processing to the updated web browser 200 even if the requested processing is updated and updated. .

  In the Web browser 200, the event process 201 accepts the notification, and can instruct the UI 202 to perform a desired display.

  In some cases, a user wants to perform a device-specific operation on a PC or MFP owned or managed by the user. For example, as described above, the login user name or serial number of the apparatus is acquired from Javascript (registered trademark) as a script, and arbitrary processing is performed according to the acquired user name or serial number, or reading or printing is performed by executing JavaScript (registered trademark). For example. In the apparatus of the present invention, an undefined script can be easily added and implemented in the form of a plug-in 220, so there is no need to re-implement code for interpreting and executing the undefined script for the Web browser 200. It is possible to respond quickly to changes such as version upgrades of the web browser 200.

  When a script attribute or method is added to the Web browser 200, an undefined script that is not defined in the added Web browser 200 is implemented as the plug-in 220. However, a component for use by a plurality of application software in common. It can be implemented as a structured DLL (Dynamic Link Library) file.

  Hereinafter, processing performed by the information processing apparatus or image forming apparatus in which the undefined script is mounted as a plug-in will be described in detail with reference to the drawings. FIG. 3 is a sequence diagram showing a basic flow of processing for acquiring or setting a certain value for the apparatus. Examples of the value to be acquired include each value and parameter as system information and status information. Moreover, about the setting of the value to an apparatus, the setting of those values and parameters can be mentioned. It may be a setting of a script function to be executed. Note that the process of acquiring or setting this value is a process realized by executing an undefined script.

  First, when the event process 201 of the Web browser 200 receives a value acquisition or setting request from a user, the event process 201 generates an undefined script execution request in order to realize the processing, and sends the execution request to the script parser 203. . When the script parser 203 receives it, the script parser 203 determines whether or not the script is defined in the Web browser 200. Here, since this script is not defined in the Web browser 200, the script parser 203 determines that the script is an undefined script and requests the plug-in manager 210 to execute the script. The plug-in manager 210 searches for the plug-in 220 corresponding to the script and requests the plug-in 220 to execute it. When the plug-in 220 accepts the execution request, the plug-in 220 requests the device SDK 240 to acquire or set a value requested by the script.

  FIG. 4 is a sequence diagram showing a flow of a process for executing a process for displaying a confirmation alert as an example of a process for executing an undefined script. This confirmation alert (warning or attention) can be displayed, for example, before executing a script related to security or important processing.

  In response to receiving a request for execution of security or important processing, the event process 201 generates a script execution request for realizing the processing, and sends the execution request to the script parser 203. The script parser 203 determines whether or not an execution target script is defined in the Web browser 200 from the received execution request. Since this script is not defined, the script parser 203 determines that it is an undefined script and requests the plug-in manager 210 to execute it. The plug-in manager 210 searches for the plug-in 220 corresponding to the script and requests the plug-in 220 to execute.

  Since this script first executes a process of displaying a confirmation alert in the Web browser 200, the plug-in 220 requests the utility 230 to display a confirmation alert. The utility 230 receives this request, converts it into an execution request that can be executed by the Web browser 200, transmits the execution request to the event process 201 of the Web browser 200, and requests display of a confirmation alert. The event process 201 receives the execution request, instructs the UI 202 to display a confirmation alert, and displays the confirmation alert.

  In accordance with the instruction, the UI 202 displays a character string including a message such as “Warning” or “Caution”, “OK” and “Cancel” buttons, and the like. This prompts the user to press a button. When the UI 202 detects that the user has pressed the “OK” button or the “Cancel” button, the UI 202 notifies the event process 201 of the type of the pressed button. The event process 201 receives the information and notifies the utility 230 of the button type, and the utility 230 notifies the plug-in 220 of the button type.

  Upon receiving this notification, the plug-in 220 requests the utility 230 to end the process of displaying the confirmation alert. Then, if the pressed button is a “cancel” button, the plug-in 220 stops the process, and if it is an “OK” button, the plug-in 220 starts executing the script related to the above-described security and important processes. Requests the device SDK 240 for processing.

  FIG. 5 is a sequence diagram showing a flow of processing for executing a script according to a change in the state of the apparatus as another example of processing for executing an undefined script. For example, it is a case where a user executes an arbitrary script by pressing a key.

  In this case, in order for the device SDK 240 to execute an arbitrary script function depending on the state change of the device, the device state change (here, a key is pressed) to the plug-in 220 that requests the Web browser 200 to perform the process. Notify that. The process of notifying the state change can be realized by requesting the plug-in 220 to notify the device SDK 240 in advance when a key is operated. The script function to be executed can be set based on the sequence shown in FIG. 3 by executing the undefined script.

  Upon receiving the notification, the plug-in 220 requests the utility 230 to execute an arbitrary script function. The utility 230 converts it into an execution request that can be executed by the Web browser 200, and sends the execution request to the event process 201. The event process 201 accepts the execution request and requests the script parser 203 to execute the script function.

  The script parser 203 interprets the execution request, and since the arbitrary script function is set based on the sequence shown in FIG. 3, it is a defined script and can execute the defined script. . The processing result can be displayed on the UI 202 via the event process 201.

  FIG. 6 is a flowchart showing the flow of processing performed by the script parser 203. This process starts from step 600. First, the script parser 203 accepts a script execution request from the event process 201 in step 610. Next, in step 620, the script parser 203 determines whether or not the script requested to be executed is a script defined in the Web browser 200. More specifically, the script parser 203 determines whether the script can be interpreted and executed. If it is a defined script, the process proceeds to step 630 to execute the script, and then proceeds to step 660 to set a return value to be returned as a processing result to the event process 201 that requested the execution. This process ends. In this case, the return value can include a value indicating that the processing has been completed correctly in addition to the processing result.

  On the other hand, if it is determined that it is not defined, the process proceeds to step 640, and the script parser 203 requests the plug-in manager 210 to execute the undefined script. After sending the execution request, the script parser 203 receives some value as a return value from the plug-in manager 210 in step 650. The plug-in manager 210 searches for the plug-in 220 corresponding to the script. If the corresponding plug-in 220 is not found, the plug-in manager 210 returns an undefined response, and otherwise returns an arbitrary value as an execution response. Therefore, the script parser 203 receives one of the values and determines which one it is.

  If the value is an arbitrary value, the process proceeds to step 660 and a return value to be returned to the event process 201 is set. If the return value is an undefined response, the process proceeds to step 670 and “undefined” returned as an undefined response. ”Is set, and in both cases, this processing is terminated at step 680.

  FIG. 7 is a flowchart showing a flow of processing performed by the plug-in manager 210. This process starts from step 700. In step 710, the plug-in manager 210 receives a script execution request from the script parser 203, and until the plug-in manager 210 corresponding to the requested script is found, the plug-in manager 210. Script execution is requested to each of a plurality of plug-ins managed by. The plug-in manager 210 sends an execution request to each of the plurality of plug-ins 220 and receives a response to the execution request from the plug-in 220. In step 720, the plug-in manager 210 determines whether or not the response is an execution response. If the response is an execution response, the plug-in manager 210 proceeds to step 740 and ends this processing. This is because the subsequent processing is performed by the plug-in 220.

  If it is not an execution response, the process proceeds to step 730 to indicate that it is not the corresponding plug-in 220, and it is determined whether the next plug-in 220 exists. That is, it is determined whether script execution is requested for all plug-ins 220 managed by the self. If there is a plug-in 220 that has not yet been requested, the process returns to step 710 to request the plug-in.

  On the other hand, if all plug-ins 220 have been requested, the next requested plug-in 220 does not exist, so the process proceeds to step 740 and this process is terminated. A specific method of searching for the corresponding plug-in 220 will be described later.

  FIG. 8 shows an example of a class configuration diagram of the plug-in manager 210 and the plug-in 220. “PluginManager” shown in FIG. 8 is the plug-in manager 210, and “Device”, “Scan”, and “Print” are provided by the plug-in 220 and correspond to the objects of the undefined script shown in FIG. is there. This object is a COM object.

  The classes corresponding to the plug-in manager 210 and the plug-in 220 all inherit the IDispach interface designed to be able to call any COM interface, and can be accessed by COM. Here, a class is a model that defines an object, and inheritance means that the definition of a class is inherited by another class. Therefore, as indicated by the arrows in FIG. 8, any of the objects “PluginManager”, “Device”, “Scan”, and “Print” can access the ID dispatch interface indicated by “IDispatch”. It is possible to call the COM interface.

  The above-mentioned object corresponding to the object of the undefined script is called by a method called IDispatch :: invoke () from a higher-level object as shown in FIG. 9, and requested processing (method of the called object). (Or attribute access) result is returned to the caller. This IDispatch :: invoke () is configured to designate information for identifying a method to be called and information to be passed to the calling method, and sends the designated information to the COM interface via the IDispatch interface. . The COM interface holds a pointer that designates an address on a memory in which a plurality of methods for providing a single function of the COM object are stored as program code. For this reason, the COM interface can call a method based on information for identifying a method to be called out of the specified information, and send and process information to be passed to the method. The processing result can be returned to the caller via the COM interface.

  Here, a case where aggregate printing is performed as execution of an undefined script will be described. The script is described as, for example, “device.print.layout = 2up”, and this device processes this script as follows.

  When the script parser 203 receives an execution request for a script including this script from the event process 201, the script parser 203 interprets this script and determines that it is an undefined script. Request to set “2up” in “device.print.layout” for PluginManager class. The PluginManager class is indicated as “window” in the embodiment shown in FIG. This PluginManager class actually accesses the COM interface via the ID dispatch interface by IDispatch :: invoke () as described above, and the COM interface accesses the object of the class belonging to the lower level. A description of the process is omitted. Therefore, the PluginManager class searches for the Device class from the subordinate classes, and requests the Device class object to set “2up” in “print.layout”.

  Next, the Device class object searches for the Print class from the classes belonging to the lower level of “Device” shown in FIG. 9 and requests the Print class object to set “2up” to “layout”. .

  In order for the PluginManager class to refer to the Device class, identification information for identifying the object is required, but a program ID is given as identification information, and when installing, updating, or uninstalling the plug-in 220, such as HDD By recording this program ID in the setting file stored in the storage device, the plug-in manager 210 and the plug-in 220 can be associated with each other.

  In order to facilitate the management of the plurality of plug-ins 220 as described above, a hierarchical structure is formed as an object to which the plurality of plug-ins 220 correspond, and undefined scripts are sequentially arranged from an upper object to a lower object in the hierarchical structure. The execution request can be transmitted to inquire whether or not execution is possible, and an undefined script can be executed on a subordinate object that can be executed. After the execution, the lower object sends the execution result to the higher object, the higher object sends the plug-in manager 210, and the plug-in manager 210 notifies the Web browser 200, thereby the Web browser 200. Can know that the execution request of the script has been processed.

  FIG. 10 is a diagram illustrating an example in which an interface between the Web browser 200 and the plug-in 220 implemented by the utility 230 is described in a programming language. FIG. 10A is an example in which a processing request to the Web browser 200 is described. “//” indicates that the subsequent line is treated as a comment, and this processing is a request to the Web browser. Show. In addition, “command” indicates the type of request such as a dialog display request, and “args” indicates an argument that is different for each request such as a message displayed in the dialog or a character string of a button. Here, the argument is a value passed to the function or method when the function or method is called.

  In the example of FIG. 10A, an event is immediately transmitted to display a dialog including a predetermined message and button, and “true” is returned as a return value when the event is processed, and “false” when the event is not processed. Is returned. Since this is executed when a SendEvent request is sent, the plug-in 220 displays this dialog for the Web browser 200 regardless of whether the Web browser 200 has been updated by sending this request. Can be performed.

  FIG. 10B is a diagram illustrating a process for receiving a notification from the Web browser 200. In FIG. 10B, in order to cooperate with the Web browser 200, a callback function to be called is defined using a function pointer type name (CALLBACK_FUNC) and an argument (ID). In the example shown in FIG. 10B, an event ID when the left button is pressed and an event ID when the right button is pressed are passed as arguments, and notification of which button is pressed is received. It is possible.

  In order to receive the notification, it is necessary to register a callback function to be called in advance. Registration processing for that purpose is described. In this registration process, a callback function pointer is added, and when the process is performed, “true” is returned as a return value, and when the process is not performed, “false” is returned.

  After receiving the notification that the button has been pressed, no further notification is required. Therefore, a process for deleting the callback function pointer in order to stop the notification is described. In this process, after receiving the above notification, the pointer of the callback function used for the notification is deleted. When the process is performed, "true" is returned as the return value, and when it is not performed, "false" Is returned.

  Again, the callback function can be registered / released regardless of whether the Web browser 200 has been updated by a request from the plug-in 220.

  The processing performed by the information processing apparatus and the image forming apparatus described so far is summarized as follows. These apparatuses are equipped with a Web browser 200 for processing content data including document data described in a markup language. The Web browser 200 generates a script execution request to process the detected event, and determines whether the execution request is a predefined script execution request.

  If it is a predefined script, it is executed by the script parser 203. If it is determined that the script is not a predefined script, an execution request for the undefined script is transmitted to the plug-in manager 210.

  The plug-in manager 210 sequentially sends the execution request for the undefined script to one or more plug-ins 220 that are added and mounted for function expansion, and inquires whether or not the execution is possible. Then, a plug-in 220 that can execute the undefined script is found from the plug-ins 220, and the plug-in 220 is caused to execute the undefined script.

  The plug-in 220 forms a hierarchical structure, and sends an undefined script execution request in order from the upper plug-in to the lower plug-in in the hierarchical structure to inquire whether or not it can be executed. Plug-in can execute the undefined script.

  The utility 230 called upon receiving a processing request from the plug-in 220 to the Web browser 200 sends an execution request that can be executed by the Web browser 200 in response to the processing request to the Web browser 200. Can be processed.

  In the present invention, an information processing method including each of these processing steps can be provided, a computer-readable program for executing the method, and an FD, CD, DVD, SD card in which the program is recorded. It is also possible to provide such a recording medium. The present invention has been described with the above-described embodiments, but the present invention is not limited to the above-described embodiments, and those skilled in the art will conceive other embodiments, additions, changes, deletions, and the like. It can be changed within the range that can be performed, and any embodiment is included in the scope of the present invention as long as the operation and effect of the present invention are exhibited.

DESCRIPTION OF SYMBOLS 100 ... PC, 110 ... MFP, 120 ... Network, 130, 140 ... External server, 200 ... Web browser, 201 ... Event process, 202 ... UI, 203 ... Script parser, 210 ... Plug-in manager, 220 ... Plug-in, 230 ... Utility, 240 ... Device SDK

JP 2009-009597 A

Claims (11)

An information processing apparatus including a data processing unit that processes content data including document data described in a markup language,
One or more script execution units additionally implemented to execute one or more undefined scripts other than the predefined scripts executable by the data processing unit;
When the execution request of the script generated to process the event detected by the data processing unit is the execution request of the undefined script, the execution request of the undefined script is accepted from the data processing unit, and the undefined A script execution management unit that sends an execution request of a script to the one or more script execution units in order to inquire whether the execution is possible, and causes the executable script execution unit to execute the undefined script. Information processing device.   Whether the one or more script execution units form a hierarchical structure, and can execute an execution request of the undefined script in order from an upper script execution unit to a lower script execution unit in the hierarchical structure. The information processing apparatus according to claim 1, wherein the undefined script is executed by the subordinate script execution unit that can execute the query.   An interface unit that is called in response to a processing request from the script execution unit to the data processing unit, and that transmits an execution request that can be executed by the data processing unit in response to the processing request, to the data processing unit; The information processing apparatus according to claim 1 or 2. An image forming apparatus that includes a data processing unit that processes content data including document data described in a markup language, and that executes print processing in response to a print request,
One or more script execution units additionally implemented to execute one or more undefined scripts other than the predefined scripts executable by the data processing unit;
When the execution request of the script generated to process the event detected by the data processing unit is the execution request of the undefined script, the execution request of the undefined script is accepted from the data processing unit, and the undefined A script execution management unit that sends an execution request of a script to the one or more script execution units in order to inquire whether the execution is possible, and causes the executable script execution unit to execute the undefined script. Image forming apparatus.   Whether the one or more script execution units form a hierarchical structure, and can the execution request for the undefined script be transmitted in order from the upper script execution unit to the lower script execution unit in the hierarchical structure and executed? The image forming apparatus according to claim 4, inquiring whether or not, and causing the executable script execution unit to execute the undefined script.   An interface unit that is called in response to a processing request from the script execution unit to the data processing unit, and that transmits an execution request that can be executed by the data processing unit in response to the processing request, to the data processing unit; The image forming apparatus according to claim 4 or 5. An information processing method executed by an information processing apparatus or an image forming apparatus including a data processing unit that processes content data including document data described in a markup language,
Determining whether the execution request of the script generated to process the detected event by the data processing unit is an execution request of a defined script that can be executed;
Transmitting an execution request for an undefined script that is not the defined script to a script execution management unit included in the information processing apparatus or the image forming apparatus when it is determined that the script is not the defined script;
Whether or not the script execution management unit can sequentially execute the execution request for the undefined script by adding the execution request to the one or more script execution units that are added and executed to execute the one or more undefined scripts. And causing the executable script execution unit to execute the undefined script.   Whether the one or more script execution units form a hierarchical structure, and can the execution request for the undefined script be transmitted in order from the upper script execution unit to the lower script execution unit in the hierarchical structure and executed? The information processing method according to claim 7, inquiring whether or not, and causing the subordinate script execution unit to execute the undefined script.   A step in which an interface unit that is called in response to a processing request from the script execution unit to the data processing unit transmits an execution request that can be executed by the data processing unit in response to the processing request to the data processing unit; An information processing method according to claim 7 or 8, further comprising:   The computer-readable program for performing the information processing method of any one of Claims 7-9.   A recording medium on which the program according to claim 10 is recorded.