Application management device, multifunction printer, application management method, and program

Abstract

To avoid degrading user experience when browser functions are used by multiple applications. [Solution] A program for causing a computer to function as a management device for managing multiple applications, wherein the program provides means to prohibit the second application from using the browser function when the second application, which is capable of using the browser function, comes into the foreground while the first application, which is capable of using the browser function, is running, and means to allow the first application to use the browser function from the state it was in before the second application came into the foreground when the application running in the foreground returns from the second application to the first application.

Description

Technical Field

[0001] The present disclosure relates to an application management device for managing the use of browser functions by an application, a multifunction device including the application management device, an application management method, and a program.

Background Art

[0002] In information processing devices such as personal computers (also referred to as "PCs") and smartphones, network content can be displayed using the browser function of a web browser. Also, in information processing devices such as PCs and smartphones, network content can be displayed using an application (also referred to as a "WebView application") that can utilize the browser function of WebView. Note that an application is an application program executed by a computer and is also referred to as an "app".

[0003] A web browser transmits an information request for a web application based on an operation to a web server on the network. Also, the web browser has a function of analyzing rendering information included in a response from the web server by a web browser engine and displaying the screen obtained by the analysis on a display unit provided in the operation unit 211. Such a function is called a browser function. WebView is a component that provides a browser function that can be called on the application side, and can display the content of a web application for each WebView application.

[0004] Furthermore, some image forming machines are equipped with a web browser or WebView application. Some multifunction printers (also called "MFPs (Multi Function Peripherals)") are also equipped with a web browser or WebView application. Here, a multifunction printer is an image forming machine (image forming function unit) with other function units (for example, an image reading function unit, a copying function unit, an image saving function unit, an image input / output function unit, and an image transmission function unit) added to it. In the following, when we refer to an MFP, we will also include the image forming machine.

[0005] Embedded devices such as MFPs tend to have fewer resources, such as memory, compared to PCs and smartphones, and simultaneous use of WebView by multiple applications can lead to a decrease in usability. Therefore, it is known that embedded devices can ensure proper operation by limiting the number of applications that use WebView simultaneously and restricting certain WebView functions used by each application, thereby limiting the use of browser functions.

[0006] In this case, if the resources requested by the application at startup conflict, there is a method to strip the resources of the application not selected by the user and allow the other application to use them (Patent Document 1). [Prior art documents] [Patent Documents]

[0007] [Patent Document 1] Japanese Patent Publication No. 2009-146206 [Overview of the project] [Problems that the invention aims to solve]

[0008] However, conventional methods have the drawback of requiring user interaction to maintain or deplete resources such as browser functions. In environments where resource contention occurs frequently, user interaction is required each time a resource contention occurs, which degrades usability.

[0009] This disclosure is made in light of the above-mentioned issues and aims to avoid degrading the user experience of browser functions used by multiple applications. [Means for solving the problem]

[0010] One embodiment of the present disclosure is a program for causing a computer to function as a management device for managing multiple applications, the program comprising: means for prohibiting a second application capable of using a browser function from using the browser function if the second application, capable of using a browser function, comes into the foreground while the first application capable of using a browser function is running; and means for allowing the first application to use the browser function from the state it was in before the second application came into the foreground when the application running in the foreground returns from the second application to the first application. [Effects of the Invention]

[0011] This disclosure addresses the above-mentioned issues and ensures that the user experience of browser functions used by multiple applications is not diminished. [Brief explanation of the drawing]

[0012] [Figure 1] Overall system configuration diagram including the MFP and web application server according to the embodiment. [Figure 2] Functional block diagram showing the hardware configuration of the MFP according to this embodiment. [Figure 3] Block diagram showing the hardware configuration of a web server according to an embodiment [Figure 4] Diagram showing each software module provided in the MFP according to an embodiment and the relationships between them [Figure 5] Flowchart for explaining a method of managing a plurality of applications according to the first embodiment [Figure 6] Another flowchart for explaining a method of managing a plurality of applications according to the first and second embodiments [Figure 7] Correlation diagram between screens displayed on the operation unit of the MFP [Figure 8] Diagram showing an example of an application selection screen displayed on the operation unit of the MFP [Figure 9] Diagram showing an example of a status confirmation screen displayed on the operation unit of the MFP [Figure 10] Diagram showing an example of a print count history screen displayed on the operation unit of the MFP [Figure 11] Diagram showing an example of a web application screen displayed on the operation unit of the MFP [Figure 12] Transition diagram between screens displayed on the operation unit of the MFP [Figure 13] Transition diagram between screens displayed on the operation unit of the MFP [Figure 14] Diagram showing an example of an order form screen displayed on the operation unit of the MFP [Figure 15] Transition diagram between screens displayed on the operation unit of the MFP [Figure 16] Diagram showing an example of a status confirmation screen displayed on the operation unit of the MFP [Figure 17] Flowchart for explaining a method of managing a plurality of applications according to the second embodiment [Figure 18] Correlation diagram between screens displayed on the operation unit of the MFP [Figure 19] Transition diagram between screens displayed on the operation unit of the MFP [Figure 20] Transition diagram between screens displayed on the operation unit of the MFP [Figure 21]Flowchart for explaining a method of managing a plurality of applications according to the third embodiment [Figure 22] Flowchart for explaining a method of managing a plurality of applications according to the fourth embodiment

Best Mode for Carrying Out the Invention

[0013] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the disclosure according to the claims. Although a plurality of features are described in the embodiments, not all of these plurality of features are essential for the disclosure, and the plurality of features may be arbitrarily combined. Further, in the accompanying drawings, the same or similar configurations may be given the same reference numerals, and redundant descriptions may be omitted.

[0014] <First Embodiment> FIG. 1 is a diagram showing the overall configuration of a system including an MFP and a Web application server according to the first embodiment.

[0015] In this system, the MFP 110 and the Web application server 120 are interconnected via the LAN 100 and the Internet 130. The Web application server 120 is a server that executes a Web application. The MFP 110 is equipped with a Web browser and a WebView application. Therefore, the MFP 110 also functions as a Web client terminal that displays an operation screen of the Web application and receives operations by a user on the operation screen.

[0016] Figure 2 is a functional block diagram showing the hardware configuration of the MFP110. The control unit 200 includes a processor 201 such as a CPU, ROM 202, RAM 203, HDD 204, an operation interface (also called "operation interface") 205, and a network interface (also called "network interface") 206. The control unit 200 also includes a scanner interface (also called "scanner interface") 207, an image processing unit 208, and a printer interface (also called "printer interface") 209. These parts included in the control unit 200 are interconnected via a system bus 210.

[0017] When the MFP110 is powered on, processor 201 reads and executes the boot program stored in ROM 202. Processor 201 also uses the executed boot program to load the OS and control programs stored in HDD 204 into RAM 203. Then, processor 201 controls the MFP110 by reading and executing these programs from RAM 203. This control includes a control method described later using a flowchart.

[0018] ROM202 stores the boot program and various data mentioned above. RAM203 is used as work memory for the processor 201 to operate, and also as image memory for temporarily storing image data.

[0019] HDD204 stores the OS (Operating System) and various programs. It is also used to store image data. These programs include the applications described later.

[0020] The operation unit I / F 205 is an interface between the control unit 200 and the operation unit 211. It is used by the control unit 200 to display an operation screen on the display unit included in the operation unit 211, and for the control unit 200 to input user operations on the operation screen.

[0021] Network I / F 206 is an interface between the control unit 200 and the LAN 100, and is used by the control unit 200 to output information to the LAN 100 and to input information from the LAN 100.

[0022] The scanner I / F 207 is an interface between the control unit 200 and the scanner unit 212, and is used by the control unit 200 to control the scanner unit 212 and to input image data of the document scanned by the scanner unit 212.

[0023] The image processing unit 208 performs image processing on the image data input from the scanner unit 212 and the image data to be output to the printer unit 213.

[0024] The printer I / F 209 is an interface between the control unit 200 and the printer unit 213, and is used by the control unit 200 to cause the printer unit 213 to perform printing based on image data.

[0025] The operation unit 211 has a display unit with touch panel functionality and hard keys, and is used to display an operation screen according to data from the control unit 200 and to accept user input on the operation screen. The scanner unit 212 reads an image from a document, generates image data representing that image, and supplies it to the control unit 200. The printer unit 213 prints the image onto paper based on the image data input from the control unit 200.

[0026] Figure 3 is a block diagram showing the hardware configuration of the Web application server 120 according to the first embodiment.

[0027] The web application server 120 has a processor 301, RAM 302, ROM 303, HDD 304, and network I / F 305, which are interconnected via a system bus 306.

[0028] When the power to the web application server 120 is turned on, processor 301 reads and executes the boot program stored in ROM 303. Processor 301 also uses the executed boot program to load the OS and control programs stored in HDD 304 into RAM 302. Then, processor 201 reads and executes these programs from RAM 302, thereby realizing the functions of the web application server 120. Furthermore, processor 301 communicates with other devices on the internet 130, which is connected via network I / F 305.

[0029] The following explanation will use the terms "app identification information," "WebView app identification information," "permitted app identification information," and "currently operating app identification information." These terms will be explained below.

[0030] The MFP110 comes equipped with multiple applications that display on the screen, and these are identified by application identification information. This application identification information is a unique string of characters for each application, consisting of alphanumeric characters and some symbols.

[0031] Multiple applications are classified into WebView apps and non-WebView apps. The app identification information of a WebView app is used directly as the WebView app identification information.

[0032] According to this embodiment, only one WebView application is permitted to use WebView at a time. The identification information of the only WebView application currently permitted to use WebView (i.e., WebView application identification information) is used as is as the permitted application identification information. If there are no WebView applications currently permitted to use WebView, the permitted application identification information is NULL. NULL indicates that the permitted application identification information has been deleted or is invalid, for example, zero.

[0033] Only one application can display a screen on the control unit 211 at a time. The identification information of the currently displayed application is used directly as the current application identification information.

[0034] Figure 4 shows the multiple software modules installed in the MFP110 according to the first embodiment and their relationships. These software modules are stored in the HDD204 of the MFP110, loaded into RAM203, and executed by processor201, thereby realizing the functions of these software modules.

[0035] The WebView management unit 410 comprises a browser function execution unit 411, an application information acquisition unit 412, a WebView usage management unit 413, and a WebView conflict determination unit 414. The WebView management unit 410 functions as an application management device or application management unit.

[0036] The browser function execution unit 411 requests rendering information from the Web application server 120 based on requests related to browser functions from the WebView application. The browser function execution unit 411 then displays the screen obtained by the browser engine 420 analyzing the rendering information sent from the Web application server 120 on the display unit provided in the operation unit 211.

[0037] When the application displayed on the operation unit 211 changes, the application information acquisition unit 412 acquires application identification information, which is the identification information of the switched application, from the window management unit 430.

[0038] The WebView usage management unit 413 registers WebView application identification information. The WebView usage management unit 413 is also used to determine whether each application is a WebView application or not. The WebView application identification information is dynamically registered in the WebView usage management unit 413 at predetermined times, such as when an application instance is created.

[0039] Furthermore, the WebView usage management unit 413 updates the WebView applications that are currently permitted to use WebView. The WebView usage management unit 413 then stores the identification information of the WebView applications that are currently permitted to use WebView as the authorized application identification information. As mentioned above, if there are no WebView applications currently permitted to use WebView, the authorized application identification information is NULL.

[0040] The WebView conflict determination unit 414 determines whether or not there is currently a WebView application that is permitted to use browser functions, based on the execution permission application identification information stored in the WebView usage management unit 413.

[0041] The browser engine 420 analyzes the rendering information received from the web application server 120 and provides the screen data obtained through the analysis to the browser function execution unit 411.

[0042] The window management unit 430 manages applications that can display screens on the operation unit 211 based on screen data generated from drawing information and accept user operations. The window management unit 430 also manages all applications installed on the MFP110 in association with application identification information.

[0043] Figure 5 is a flowchart illustrating a method for managing multiple programs according to the first embodiment. This method manages whether to allow or deny the use of browser functions by the WebView application after the switch when the application displaying the screen is switched. This program management method is mainly executed by the WebView management unit, which functions as one of the various program management devices or program management units described above.

[0044] In S501, the window management unit 430 waits until the application that should display the screen switches. That is, it waits until the screen displayed by one application is about to switch to the screen displayed by another application. Here, the application running in the foreground displays the screen. The screen of the application running in the background is not displayed. Therefore, when the screen displayed by one application is about to switch to the screen displayed by another application, it is equivalent to the application running in the foreground switching from one application to another. Also, the other application that was waiting in the background becomes the foreground application.

[0045] Furthermore, when the "Home" button 906 (see Figure 9) located on the screen is pressed, the application that was displaying that screen closes. Then, the display of the application selection screen A1, which is typically one of several non-WebView applications, begins by another non-WebView application.

[0046] App selection screen A1 is positioned as the home screen. Alternatively, a screen displayed by another non-WebView app may also be designated as the home screen.

[0047] If any application is started, the window management unit 430 determines that it is YES, and the process proceeds to S502.

[0048] In S502, the application information acquisition unit 412 acquires identification information of the application whose screen has been newly displayed on the operation unit 211 by user operation from the window management unit 430. In other words, in S502, the application information acquisition unit 412 acquires the current operation application identification information of the new current operation application from the window management unit 430.

[0049] In S503, the WebView usage management unit 413 determines whether the current operation application identification information acquired by the application information acquisition unit 412 in S502 is registered as WebView application identification information. In other words, the WebView usage management unit 413 determines whether the current operation application is registered as a WebView application. If the current operation application is registered as a WebView application, the determination in S503 is YES, and the process proceeds to S504. If the current operation application is not registered as a WebView application, the determination in S503 is NO, and the process proceeds to S509.

[0050] In S504, the WebView conflict determination unit 414 determines whether the WebView usage management unit 413 stores execution permission application identification information that is different from the current application identification information. If the execution permission application information is NULL, it effectively means that no execution permission application information is stored, so the result of this determination is NO.

[0051] If the identification information of the current application differs from the execution permission application identification information stored in the WebView usage management unit 413, the determination in S504 becomes YES, and the process proceeds to S509.

[0052] In S509, the WebView usage management unit 413 sets the stored execution permission application identification information to NULL. Then, the process shown in Figure 5 is completed.

[0053] If the identification information of the current application is the same as the execution permission application identification information stored in the WebView usage management unit 413, the determination in S504 will be NO, and the process will proceed to S505.

[0054] In S505, the WebView usage management unit 413 changes the settings so that WebView applications other than the currently operating application are prohibited from using the browser function. At this point, in S503, it has already been determined that the currently operating application is a WebView application.

[0055] In S506, the WebView usage management unit 413 changes the settings so that the current application is allowed to use the browser function.

[0056] In S507, the WebView usage management unit 413 stores the current operation application identification information as the authorized application identification information.

[0057] In S508, the WebView usage management unit 413 notifies the current operating application that it has been granted permission to use the browser function. Then, the process shown in Figure 5 is completed.

[0058] Figure 6 is another flowchart illustrating how to manage multiple different programs.

[0059] In S601, the window management unit 430 waits until any application is terminated. Note that screens A2 through A4, for example, have a "Home" button 906, as shown in the diagram. When the "Home" button 906 is pressed, the application displaying that screen terminates.

[0060] If any application terminates, the window management unit 430 determines that it is YES, and the process proceeds to S602.

[0061] In S602, the application information acquisition unit 412 acquires the identification information (application identification information) of the terminated application from the window management unit 430.

[0062] In S603, the WebView conflict determination unit 414 determines whether the application identification information of the terminated application is stored in the WebView usage management unit 413 as the application identification information for which execution is permitted.

[0063] If the application identification information of the terminated application is stored as the authorized application identification information in the WebView usage management unit 413, the process proceeds to S604. Otherwise, the process in S604 is omitted, and the process in Figure 6 ends.

[0064] In S604, the WebView usage management unit 413 sets the execution permission application identification information to NULL. In other words, by deleting the execution permission application identification information, the WebView usage management unit 413 removes the registration of the WebView application that was determined to terminate in S601 as the only application permitted to run WebView. Then, the process shown in Figure 6 ends.

[0065] Next, we will explain specific operational examples using the screen displayed on the MFP110's control panel.

[0066] Figure 7 shows the four screens displayed on the operation unit 211 in the first embodiment and the correlation between them. The four screens are the application selection screen A1, also shown in Figure 8; the status confirmation screen A2, also shown in Figure 9; the print count history screen A3, also shown in Figure 10; and the Web application screen A4, also shown in Figure 11.

[0067] The app selection screen A1 is a screen created by a non-WebView app. The status confirmation screen A2 is a screen created by a WebView app. The print count history screen A3 is a screen created by WebView. The web app screen A4 is a screen created by both a WebView app and a WebView app.

[0068] Figure 8 shows an example of an application selection screen displayed on the control unit 211 by the operation application. Application selection screen A1 has a "Status Check" button 801, a "Web App" button 802, and a "Status Check" button 803. The screen of another application installed on the MFP110 corresponding to the pressed button can be displayed. When the "Status Check" button 801 or the "Status Check" button 803 is pressed, the application selection screen A1 transitions to the status check screen A2 (see Figure 9) by the other application that has moved from the background to the foreground (S711 in Figure 7). Also, when the "Web App" button 802 is pressed, the application selection screen A1 transitions to the Web App screen A4 (see Figure 11) by the other application that has moved from the background to the foreground (S712 in Figure 7). Application selection screen A1 is positioned as the home screen.

[0069] Figure 9 shows the status confirmation screen A2 displayed on the operation unit 211. The status confirmation screen A2 has a table 901, which allows users to check the print content requested by each application to the MFP 110. When the "Details" button 903 is pressed while any row in the table 901 is selected, the user can transition to a screen to check the detailed information of the print request displayed in that row, and the print request can be canceled by pressing the "Cancel" button 902. The status confirmation screen A2 also has a "Page Count History" button 904 and a "Back" button 905. When the "Page Count History" button 904 is pressed, the history information of the number of pages printed by the MFP 110 stored on the server is retrieved using the browser function, and the user can transition to the print count history screen A3, which includes the graph 1002 in Figure 10 (S713 in Figure 7). Therefore, the print count history screen A3 is a WebView screen displayed using WebView. The application that displays the status confirmation screen A2 shown in Figure 9 is a WebView application. Pressing the "Back" button 905 will return you to the previous screen.

[0070] Furthermore, the status confirmation screen A2 has a "Home" button 906. When the "Home" button 906 is pressed, the screen transitions to the home screen, which is the app selection screen A1. At this time, the application displaying the status confirmation screen A2 also closes. If the "Home" button 906 is pressed on any other screen, the application displaying that other screen also closes, and the screen transitions to the app selection screen A1. In addition, the application that displays the app selection screen A1 is started for this purpose.

[0071] The print count history screen A3 shown in Figure 10 has a "Back" button 1001 and a "Status Check" button 1003. When the "Status Check" button 1003 is pressed, the screen can be transitioned to the status check screen A2 shown in Figure 9 (S714 in Figure 7).

[0072] Figure 11 shows an example of a screen (Web application screen) displayed by a Web application shown on the operation unit 211. Web application screen A4 is based on drawing information obtained from the Web application server 120. Web application screen A4 has a "Status Check" button 1103 and a "Print" button 1102. When the "Print" button 1102 is pressed, the image data selected in table 1101 can be obtained from the storage on the Web application server 120 and printed by the MFP 110. When the "Status Check" button 1103 is pressed, another application moves from the background to the foreground, and Web application screen A4 transitions to status check screen A2 (see Figure 9) (S715 in Figure 7).

[0073] The status of printing in response to a print request made using the web application screen A4 in Figure 11 can be checked in Table 901 on the status confirmation screen A2 (Figure 9) until printing is complete. Printing in response to a print request can be canceled by pressing the "Cancel" button 902 while the relevant row is selected in Table 901.

[0074] Using Figure 12, we will explain a specific example of transitioning from the application selection screen A1 to the status confirmation screen A2, and then to the print count history screen A3.

[0075] When the display screen transitions from another screen to the app selection screen A1 (S1201), the identification information of the current operating app, which is the application that displays the app selection screen A1, is obtained in S502.

[0076] In this case, the current operating application, which displays the application selection screen A1, is a non-WebView application. Therefore, the identification information of the application that displays the application selection screen A1 is not registered in the WebView usage management unit 413 as WebView application identification information.

[0077] Therefore, in S503, it is determined that the currently operating application displaying the application selection screen A1 is not registered as a WebView application (NO).

[0078] Therefore, in S509, the method shown in Figure 5 for screen A1 is terminated by setting the execution permission application identification information stored in the WebView usage management unit 413 to NULL (i.e., deleting it).

[0079] When the "Status Check" button 801 or "Status Check" button 803 on the app selection screen A1 is pressed, the app selection screen A1 transitions to the status check screen A2 (S1202). Simultaneously, in S502, the identification information of the application to display the status check screen A2 is obtained.

[0080] Since the application that displays the status confirmation screen A2 is a WebView application, the identification information of the application that displays the status confirmation screen A2 is registered in the WebView usage management unit 413 as WebView application identification information.

[0081] Therefore, in S503, it is determined that the application that displays the status confirmation screen A2 is registered as a WebView application (YES), and the process proceeds to S504.

[0082] In this instance, during the period when app selection screen A1 was displayed, the execution permission app identification information was set to NULL in the 509 execution.

[0083] Therefore, the determination in S504 is NO, and the process proceeds to S505.

[0084] On the S505, the settings are changed so that the WebView application, which displays an A4 web application screen, is disabled from using browser functionality.

[0085] In S506, the settings are changed so that the WebView app that displays the status confirmation screen A2 is allowed to use browser functionality.

[0086] In S507, the identification information of the WebView application that displays the status confirmation screen A2 is stored as the execution permission application identification information.

[0087] S508 notifies that permission has been granted to use the browser function for the WebView application displaying the status confirmation screen A2.

[0088] Subsequently, when the "Page Count History" button 904 on the status confirmation screen A2 is pressed, the screen transitions to the print page count history screen A3, which is generated using the browser function (S1203).

[0089] As shown in the example using Figure 12, the application running immediately before the WebView application for displaying the status confirmation screen A2 moved from the background to the foreground was the application for displaying the application selection screen A1, which is a non-WebView application. In other words, no WebView application was running immediately before the WebView application for displaying the status confirmation screen A2 moved from the background to the foreground. Therefore, the WebView application for displaying the status confirmation screen A2 can use WebView to display the print count history screen A3.

[0090] Using Figure 13, we will explain a specific example of transitioning from the application selection screen A1 to the web application screen A4, then to the status confirmation screen A2, and finally back to the web application screen A4.

[0091] When the display screen transitions from another screen to the app selection screen A1 (S1301), the identification information of the current operating app, which is the application that displays the app selection screen A1, is obtained in S502.

[0092] In this case, the application that displays the application selection screen A1, the operation application, is a non-WebView application. Therefore, the identification information of the application that displays the application selection screen A1 is not registered in the WebView usage management unit 413 as WebView application identification information.

[0093] Therefore, in S503, it is determined that the currently operating application displaying the application selection screen A1 is not registered as a WebView application (NO).

[0094] Therefore, in S509, the method shown in Figure 5 for screen A1 is terminated by setting the execution permission application identification information stored in the WebView usage management unit 413 to NULL (i.e., deleting it).

[0095] When the "Web App" button 802 on the app selection screen A1 is pressed, the app selection screen A1 transitions to the Web App screen A4 (S1302). Simultaneously, in S502, the identification information of the application that will display the Web App screen A4 is obtained. In S1302, the WebView application for displaying the Web App screen A4 is the first to move from the background to the foreground, so the result in S501 is YES. Also, the WebView application for displaying the Web App screen A4 becomes active. Here, being active means being able to display the screen and accept input.

[0096] Since the application that displays the A4 web application screen is a WebView application, the identification information of the application that displays the A4 web application screen is registered in the WebView usage management unit 413 as WebView application identification information.

[0097] Therefore, in S503, it is determined that the application displaying the Web application screen A4 is registered as a WebView application (YES), and the process proceeds to S504.

[0098] In this instance, during the period when app selection screen A1 was displayed, the execution permission app identification information for S509 was set to NULL.

[0099] Therefore, the determination of NO is made in S504, and the process proceeds to S505.

[0100] On the S505, the WebView application that displays the status confirmation screen A2 will be configured to disable the use of browser functionality.

[0101] In S506, the settings are changed so that the WebView application that displays the A4 web application screen is allowed to use browser functionality.

[0102] In S507, the identification information of the WebView application that displays the A4 web application screen is stored as the execution permission application identification information.

[0103] S508 notifies that permission has been granted to use browser functionality for the WebView application that displays the A4 web application screen.

[0104] Subsequently, when the "Status Check" button 1103 on Web application screen A4 is pressed, the screen transitions to status check screen A2 (S1303). In S1303, the WebView application for displaying status check screen A2 first moves from the background to the foreground, so the S501 response is YES. The WebView application for displaying status check screen A2 also becomes active. The WebView application for displaying Web application screen A4 becomes inactive but does not terminate.

[0105] At this point, the WebView displaying the A4 web application screen stops operating while maintaining the state it was in immediately before the transition.

[0106] When the WebView application displaying the status confirmation screen A2 moves from the background to the foreground, the judgment in S501 becomes YES, S502 is executed, and the judgment in S503 becomes YES. Then, the judgment in S504 is performed.

[0107] Here, as mentioned above, in S507, which is executed when the application displaying the web application screen A4 moves from the background to the foreground, the identification information of the application displaying the status confirmation screen A2 is stored as the execution permission application identification information.

[0108] Therefore, the judgment in S504 is YES. Consequently, S505 to S508 are not executed, and the settings configured in S505 to S507, which were executed when the WebView application displaying the Web application screen A4 was moved from the background to the foreground, are maintained. In particular, in S505, the use of WebView by the WebView application displaying the status confirmation screen A2 is prohibited.

[0109] Therefore, even if the "Page Count History" button 904 on the status confirmation screen A2 is pressed, WebView is not used, and the print page count history screen A3 is not displayed (S1399).

[0110] Subsequently, when the "Back" button 905 on the status confirmation screen A2 is pressed, the screen transitions to the web application screen A4 (S1304). In other words, execution returns from the WebView application displaying the status confirmation screen A2 to the WebView application displaying the web application screen A4, and the screen transitions from the status confirmation screen A2 to the web application screen A4. In S1304, the WebView application for displaying the status confirmation screen A2 becomes inactive, and the WebView application for displaying the web application screen A4 becomes active. Thus, there is at most one active application.

[0111] In this case, since WebView is not used between S1301 and S1304, the WebView displaying Web application screen A4 can resume operation from the state immediately before the transition in S1303. If WebView were used between S1301 and S1304 due to the call in S1399, the WebView displaying Web application screen A4 would resume operation from its initial state.

[0112] As shown in the example using Figure 13, another WebView application is running that displays the Web application screen A4 before the WebView application displays the status confirmation screen A2. Therefore, the WebView application that displays the status confirmation screen A2 does not use WebView to display the print count history screen A3.

[0113] Furthermore, focusing on the WebView application that displays the Web application screen A4, the WebView application that displays the status confirmation screen A2, which transitioned from background to foreground after this application, does not use WebView to display the print count history screen A3. Therefore, when returning to the WebView application that displays the Web application screen A4, it is possible to display the Web application screen A4 from the state just before the WebView application that displays the status confirmation screen A2 transitioned from background to foreground.

[0114] Figure 14 shows an example of the order form screen A5 displayed on the operation unit 211. Figure 14(a) shows the order form screen A5 in its initial state, and Figure 14(b) shows the order form screen A5 in a completed state with handwritten or printed characters added by the user. The order form screen A5 has a "Status Check" button 1401. When the "Status Check" button 1401 is pressed, another application moves from the background to the foreground, and the order form screen A5 transitions to the status check screen A2 (see Figure 9). The order form screen A5 has a "Print" button 1402. When the "Print" button 1402 is pressed, printing is performed.

[0115] Using Figure 15, we will explain a specific example of transitioning from the app selection screen A1 to the order form screen A5, then to the status confirmation screen A2, and finally back to the order form screen A5.

[0116] When the display screen transitions from another screen to the app selection screen A1 (S1501), the identification information of the current operating app, which is the application that displays the app selection screen A1, is obtained in S502.

[0117] In this case, the current operating application, which displays the application selection screen A1, is a non-WebView application. Therefore, the identification information of the application that displays the application selection screen A1 is not registered in the WebView usage management unit 413 as WebView application identification information.

[0118] Therefore, in S503, it is determined that the currently operating application displaying the application selection screen A1 is not registered as a WebView application (NO).

[0119] After that, the method shown in Figure 5 for the application that displays the application selection screen A1 by setting the execution permission application identification information stored in the WebView usage management unit 413 to NULL (i.e., deleting it) in S509 is completed.

[0120] When the "Order Form App" button 1511 on the app selection screen A1 is pressed, the app selection screen A1 transitions to the order form screen A5 (S1502). Simultaneously, in S502, the identification information of the application that will display the order form screen A5 is obtained.

[0121] Since the application that displays the order form screen A5 is a WebView application, the identification information of the application that displays the order form screen A5 is registered in the WebView usage management unit 413 as WebView application identification information.

[0122] Therefore, in S503, it is determined that the application that displays the order form screen A5 is registered as a WebView application (YES), and the process proceeds to S504.

[0123] In this instance, during the period when app selection screen A1 was displayed, the execution permission app identification information for S509 was set to NULL.

[0124] Therefore, the program transitions from S504 to S505.

[0125] On the S505, the application that displays the status confirmation screen A2 will have its settings changed to a state where the use of the browser function is disabled.

[0126] In S506, the settings are changed so that the application displaying the order form screen A5 is allowed to use the browser function.

[0127] In S507, the identification information of the application that displays the order form screen A5 is stored as the authorized application identification information.

[0128] S508 notifies that permission has been granted to use the browser function for the application displaying the order form screen A5.

[0129] The order form screen A5 initially appears in the initial state shown in Figure 14(a). The user then enters order data into the order form screen A5. This order data includes, for example, part number, part name, quantity, unit price, and total amount. With this input, the order form screen A5 becomes filled out as shown in Figure 14(b) (S1503).

[0130] Subsequently, when the user presses the "Print" button 1402, printing is initiated. In this example, the user notices missing or incorrect data in the order form during printing. Therefore, when the user presses the "Status Check" button 1401 on the order form screen A5, the screen transitions to the status check screen A2 (S1504). The user selects the row currently being printed from table 901 on the status check screen A2 and presses the "Cancel" button 902, thereby interrupting the printing process.

[0131] As mentioned above, in S505, which is executed when the application displaying the order form screen A5 moves from the background to the foreground, the application displaying the status confirmation screen A2 is changed to a state where the use of browser functionality is prohibited, and this state is maintained. Therefore, even if the "Page Count History" button 904 on the status confirmation screen A2 is pressed, WebView is not used, and the print count history screen A3 is not displayed (S1599).

[0132] Subsequently, when the "Back" button 905 on the status confirmation screen A2 is pressed, the screen transitions to the order form screen A5 (S1505).

[0133] At this time, since the application displaying the status confirmation screen A2 is not using WebView, the order form screen A5 does not revert to its initial state and remains in a completed state. Therefore, the user can modify the completed order form.

[0134] As shown in the example using Figure 15, another WebView application for displaying the order form screen A5 is running before the WebView application for displaying the status confirmation screen A2. Therefore, the WebView application for displaying the status confirmation screen A2 cannot use WebView to further display the print count history screen A3.

[0135] Furthermore, focusing on the WebView application used to display the order form screen A5, the WebView application used to display the status confirmation screen A2, which later transitioned from background to foreground, does not display the print count history screen A3 because it is prohibited from using WebView. Therefore, when returning to the WebView application used to display the order form screen A5, this WebView application can display the order form screen A5 from the state it was in just before the WebView application used to display the status confirmation screen A2 transitioned from background to foreground.

[0136] According to the first embodiment, if the second WebView application moves from the background to the foreground immediately after the first WebView application, the first WebView application can use the WebView, but the second WebView application cannot. Therefore, when the second WebView application returns to the first WebView application, the first WebView application can resume the WebView from its suspended state. Here, the suspended state is the state immediately before the second WebView application moves from the background to the foreground.

[0137] However, when the first WebView app, a non-WebView app, and the second WebView app move from the background to the foreground, both the first and second WebView apps can utilize the WebView. Therefore, when switching back from the second WebView app to the first WebView app, the first WebView app will restart the WebView from its initial state.

[0138] <Second Embodiment> The second embodiment is a modification of the first embodiment.

[0139] In the second embodiment, the status confirmation screen A2 shown in Figure 9 is changed to the status confirmation screen A6 shown in Figure 16 by adding a "Web app" button 1601 to it. The "Web app" button 1601 is intended to allow direct transition from the status confirmation screen A6 to the Web app screen A4 shown in Figure 11.

[0140] Here, the web application screen A4 can be displayed using WebView. Therefore, in the first embodiment, when attempting to transition from the status confirmation screen A6 to the web application screen A4, the WebView application for displaying the web application screen A4 cannot display the web application screen A4 using WebView. In the second embodiment, this is made possible as follows. In other words, in the second embodiment, WebView applications are given priority. Then, when the second WebView application moves from background to foreground after the first WebView application, if the latter has a higher priority, the latter is allowed to use WebView. In the example above, the priority of the WebView application for displaying the web application screen A4 is set higher than the priority of the WebView application for displaying the status confirmation screen A6.

[0141] Figure 17 is a flowchart illustrating a method for managing multiple programs according to the second embodiment.

[0142] Compared to the method according to the first embodiment shown in Figure 5, the method according to the second embodiment shown in Figure 17 differs in that S1701 is added. Note that the method shown in Figure 6 is also performed in the second embodiment.

[0143] If the answer in S504 is YES, the process proceeds to S1701. In S1701, the WebView conflict determination unit 414 determines whether the current operating application has a higher priority than the WebView application that has the execution permission application identification information as its identification information. In other words, the WebView conflict determination unit 414 determines whether the current application, which is a WebView application, has a higher priority than the WebView application that is permitted to use WebView immediately before the current application moves from the background to the foreground.

[0144] If the current application has a higher priority than the application that is permitted to run WebView, the system checks YES in S1701 and proceeds to S505. This prevents the current application from being prohibited from using the WebView browser function if it has a higher priority than the application that is permitted to run WebView. In other words, if the current application has a higher priority than the application that is permitted to run WebView, the current application is allowed to use the WebView browser function.

[0145] If the current application has a lower priority than the application that is permitted to run, S1701 determines NO and proceeds to S509. In this case, as in the first embodiment, the current application is prohibited from using the WebView's browser function.

[0146] Figure 18 shows the four screens displayed on the operation unit 211 in the second embodiment and the correlation between them. The four screens are the application selection screen A1, also shown in Figure 8; the status confirmation screen A6, also shown in Figure 16; the print count history screen A3, also shown in Figure 10; and the Web application screen A4, also shown in Figure 11. Compared to the first embodiment, the difference is that the status confirmation screen A2 has been replaced by the status confirmation screen A6. In addition, a transition from the status confirmation screen A6 to the Web application screen A4 (S1801) has been added.

[0147] Using Figure 19, we will explain a specific example of transitioning from the application selection screen A1 to the status confirmation screen A6, and then to the web application screen A4.

[0148] The behavior when the display screen transitions from another screen to the app selection screen A1 (S1901) has already been explained, so we will omit any redundant explanation.

[0149] Furthermore, the behavior when the app selection screen A1 transitions to the status confirmation screen A6 is the same as the behavior when the app selection screen A1 transitions to the status confirmation screen A2, so redundant explanations will be omitted.

[0150] The following is how the process works when the status confirmation screen A6 transitions to the web application screen A4 according to the method shown in Figure 17.

[0151] The identification information of the currently operating application, which is the application displaying the A4 web application screen, is obtained by S502.

[0152] Here, the application displaying the A4 web application screen is a WebView application. Therefore, the identification information for the application displaying the A4 web application screen is registered in the WebView application identification information as WebView application identification information in the WebView usage management unit 413.

[0153] Therefore, in S503, it is determined that the application displaying WebView screen A4 is registered as a WebView app (YES), and the process proceeds to S504.

[0154] In S507 of the method shown in Figure 17, which was executed when the status confirmation screen A6 was displayed, the application identification information for displaying the status confirmation screen A6 was stored as the authorized application identification information, and this information is still stored.

[0155] Therefore, in S504, a YES determination is made, and the process proceeds to S1701.

[0156] In S1701, the WebView conflict determination unit 414 determines whether the current application has a higher priority than the application that is permitted to run. Here, the current application is the application that displays the Web application screen A4, and the application that is permitted to run is the application that displayed the status confirmation screen A6. Also, as mentioned above, the priority of the WebView application that displays the Web application screen A4 is higher than the priority of the WebView application that displays the status confirmation screen A6. Therefore, a YES determination is made in S1701 and the process proceeds to S505.

[0157] On the S505, the settings will be changed so that the application displaying the status confirmation screen A6 is disabled from using its browser function.

[0158] On S506, the settings are changed so that applications displaying A4 web application screens are allowed to use browser functionality.

[0159] In S507, the identification information of the application displaying the A4 web application screen is stored as the authorized application identification information.

[0160] S508 notifies that the application displaying the A4 web application screen has been granted permission to use the browser function.

[0161] Therefore, in the example shown in Figure 19, it becomes possible to transition directly from the status confirmation screen A6 to the web application screen A4. The web application screen A4 is then displayed correctly using WebView.

[0162] Applying the method according to the first embodiment makes such a transition impossible. Therefore, the user needs to use a transition as shown in Figure 20. In other words, the user needs to transition from the status confirmation screen A2 to the application selection screen A1 (S2001) and then to the web application screen A4 (S2002). That is, by transitioning from the status confirmation screen A2 to the application selection screen A1, it becomes necessary to set the execution permission application identification information to NULL in S509 before transitioning to the web application screen A4.

[0163] Therefore, according to the second embodiment, the number of unnecessary operations performed by the user can be reduced compared to the first embodiment.

[0164] Furthermore, even when using the method according to the second embodiment, if the priority is set as described above, the screen transitions shown in Figure 13 and Figure 15 can be successfully achieved, just as in the first embodiment.

[0165] According to the second embodiment, if the priority of the second WebView application is set higher than that of the first WebView application, the following becomes possible: Even if the second WebView application moves from the background to the foreground immediately after the first WebView application, both the first and second WebView applications will be able to use WebView.

[0166] Furthermore, according to the second embodiment, if the priority of the second WebView application is set lower than that of the first WebView application, the result will be the same as in the first embodiment. In other words, if the second WebView application moves from the background to the foreground immediately after the first WebView application, the first WebView application may be able to use WebView, but the second WebView application will not be able to use WebView.

[0167] <Third Embodiment> In the second embodiment, if permission is granted for a WebView application to use the WebView, other WebView applications are prohibited from using the WebView until that WebView application is terminated. Furthermore, in the second embodiment, even before the WebView application is terminated, if the application selection screen is displayed, other WebView applications may be permitted to use the WebView from that point onward.

[0168] Figure 21 is a flowchart illustrating a method for managing multiple programs according to the third embodiment.

[0169] In S501, the window management unit 430 waits until any application is started.

[0170] If any application is started, the window management unit 430 determines that it is YES, and the process proceeds to S502.

[0171] In S502, the application information acquisition unit 412 acquires identification information of the application whose screen has been newly displayed on the operation unit 211 by user operation from the window management unit 430. In other words, in S502, the application information acquisition unit 412 acquires the current operation application identification information of the new current operation application from the window management unit 430.

[0172] In S2101, the application information acquisition unit 412 determines whether the application identification information acquired in S502 is the identification information for the application to display the application selection screen A1. Here, it is assumed that the application identification information for the application to display the application selection screen A1 is stored in advance. Through this determination, the application information acquisition unit 412 can determine whether the application started this time is the application to display the application selection screen A1.

[0173] If the result in S2101 is YES, then in S509, the WebView usage management unit 413 sets the execution permission application identification information to NULL. In other words, the WebView usage management unit 413 deletes the execution permission application identification information. Then, the process shown in Figure 5 ends.

[0174] If the result in S2101 is NO, the process proceeds to S503. In S503, the WebView usage management unit 413 determines whether the current operation application identification information acquired by the application information acquisition unit 412 in S502 is registered as WebView application identification information. In other words, the WebView usage management unit 413 determines whether the current operation application is registered as a WebView application. If the current operation application is registered as a WebView application, the result in S503 is YES, and the process proceeds to S2103. If the current operation application is not registered as a WebView application, the result in S503 is NO, and the process in Figure 5 ends.

[0175] In S2103, the WebView conflict determination unit 414 determines whether or not there is a WebView application that is currently permitted to use browser functions, based on the execution permission application identification information stored in the WebView usage management unit 413.

[0176] Specifically, the WebView conflict determination unit 414 determines that if the execution permission application identification information stored in the WebView usage management unit 413 is NULL, there are currently no WebView applications that are permitted to use the browser function. In this case, in order to make the current operating application, the WebView application, the only WebView application permitted to use the browser function, the determination in S2103 becomes NO, and the process transitions from S2103 to S505.

[0177] The WebView conflict determination unit 414 determines that if the execution permission application identification information stored in the WebView usage management unit 413 is not NULL, there is currently only one WebView application that is permitted to use the browser function. In this case, the determination in S2103 becomes YES, and processing terminates.

[0178] In S505, the WebView usage management unit 413 changes the settings so that WebView applications other than the currently operating application are prohibited from using the browser function. At this point, in S503, it has already been determined that the currently operating application is a WebView application.

[0179] In S506, the WebView usage management unit 413 changes the settings so that the current application is allowed to use the browser function.

[0180] In S507, the WebView usage management unit 413 stores the current operation application identification information as the authorized application identification information.

[0181] In S508, the WebView usage management unit 413 notifies the current operating application that it has been granted permission to use the browser function. Then, the process shown in Figure 5 is completed.

[0182] According to the third embodiment, the method shown in Figure 6 is also performed.

[0183] Furthermore, even if the app selection screen appears before a WebView app that is permitted to use WebView terminates, it is acceptable to keep other WebView apps prohibited from using WebView thereafter. To achieve this, steps S2101 and S509 should be omitted, and the process should proceed directly from S502 to S503.

[0184] <Fourth Embodiment> The fourth embodiment is constructed based on the third embodiment, similar to how the second embodiment was constructed based on the first embodiment.

[0185] Figure 22 is a flowchart illustrating a method for managing multiple programs according to the fourth embodiment.

[0186] Compared to the method according to the third embodiment shown in Figure 21, the method according to the fourth embodiment shown in Figure 22 differs in that S1701 is added. Note that the method shown in Figure 6 is also performed in the fourth embodiment. The method according to the fourth embodiment shown in Figure 22 is different from the method according to the third embodiment shown in Figure 21 in that S1701 is added.

[0187] If the answer to S2103 is YES, the process proceeds to S1701. In S1701, the WebView conflict determination unit 414 determines whether the current application has a higher priority than the WebView application that has the execution permission application identification information as its identification information. In other words, the WebView conflict determination unit 414 determines whether the current application has a higher priority than the WebView application that is already permitted to use WebView at the time the current application, which is a WebView application, moves from the background to the foreground.

[0188] If the current application has a higher priority than the application that is permitted to run WebView, the system checks YES in S1701 and proceeds to S505. This prevents the current application from being prohibited from using the WebView browser function if it has a higher priority than the application that is permitted to run WebView. In other words, if the current application has a higher priority than the application that is permitted to run WebView, the current application is allowed to use the WebView browser function.

[0189] If the current application has a lower priority than the application that is permitted to run, S1701 determines NO and terminates the process. In this case, as in the third embodiment, the current application is prohibited from using the WebView's browser function.

[0190] <Other Embodiments> S509 is provided for the following reason: If a non-WebView application moves from the background to the foreground after the first WebView application has been authorized to use browser functionality, then the second WebView application will be authorized to use browser functionality. Therefore, if it is not necessary to make the second WebView application authorized to use browser functionality in such a case, S509 may be bypassed if the answer to S503 is NO.

[0191] In the above embodiment, each WebView application switches whether or not to use WebView based on whether or not it has received a notification from S508. However, this is not always the case.

[0192] For example, in the first embodiment, if the answer in S504 is YES, the WebView usage management unit 413 may notify the current operating application that the use of the browser function is prohibited. In the second embodiment, if the answer in S1701 is NO, the WebView usage management unit 413 may notify the current operating application that the use of the browser function is prohibited. In the third embodiment, if the answer in S2103 is YES, the WebView usage management unit 413 may notify the current operating application that the use of the browser function is prohibited. In the fourth embodiment, if the answer in S1701 is NO, the WebView usage management unit 413 may notify the current operating application that the use of the browser function is prohibited. Each application may then switch whether or not to use WebView based on whether it has received a permission notification or a prohibition notification from the WebView usage management unit 413.

[0193] Furthermore, for example, the WebView usage management unit 413 may maintain settings for information indicating whether each WebView application is permitted or prohibited from using WebView. Each WebView application may then refer to these settings for example, after a series of initialization processes following an application switch are completed, or when it becomes necessary to use WebView.

[0194] The embodiments described above can also be realized by performing the following process: supplying software (programs) that realize the functions of the embodiments described above to a system or device via a network or various storage media, and having the computer (CPU, MPU, etc.) of that system or device read and execute the program. The program may be executed by a single computer or by multiple computers working together. Furthermore, it is not necessary to implement all of the above processes in software; some or all of the processes may be implemented by hardware such as an ASIC. Also, the CPU is not limited to a single CPU that performs all the processing; multiple CPUs may work together as appropriate to perform the processing. Moreover, the functions of the embodiments described above are not only realized by the execution of the program code read by the computer. It is also possible that the OS running on the computer performs some or all of the actual processing based on the instructions of the program code, and the functions of the embodiments described above are realized through that processing.

[0195] <Technical Features of This Disclosure> This disclosure includes the following programs, configurations, and methods.

[0196] [Program 1] A program that allows a computer to function as a management device for managing multiple applications, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, means for prohibiting the second application from using the browser functionality, Means for allowing the first application to use the browser functionality from the state before the second application came into the foreground when the application running in the foreground returns from the second application to the first application, A program that makes a computer function.

[0197] [Program 2] If, during the period in which the first application is running, a third application that does not utilize the browser function is run in the foreground before the second application comes into the foreground, the computer is further configured to allow the second application to utilize the browser function. The program described in Program 1.

[0198] [Program 3] If, during the period in which the first application is running, the third application runs in the foreground, then the second application runs in the foreground, and further, when the first application returns to running in the foreground, the computer is further configured to allow the first application to use the browser functionality from its initial state. The program described in Program 2.

[0199] [Program 4] Even if the second application comes into the foreground while the first application is running, if the second application has a higher priority than the first application, the computer will further function as a means to allow the second application to use the browser functionality. The program described in any one of Programs 1 through 3.

[0200] [Program 5] If the second application comes into the foreground while the first application is running, and the second application has a lower priority than the first application, the computer may further function as a means to prevent the second application from using the browser functionality. The program described in any one of Programs 1 through 4.

[0201] [Program 6] If, during the period in which the first application is running, a third application capable of using the browser function comes into the foreground after the second application has come into the foreground, a prohibition means for prohibiting the third application from using the browser function, When the application running in the foreground returns from the third application to the first application, means for allowing the first application to use the browser functionality from the state before the second application came into the foreground, To make computers function even better, The program described in any one of Programs 1 through 5.

[0202] [Program 7] Even if the third application comes into the foreground after the second application has come into the foreground during the period when the first application is running, if the third application has a higher priority than the first application, the computer will further function as a means to allow the third application to use the browser functionality. The program described in Program 6.

[0203] [Program 8] If, during the period in which the first application is running, the second application comes into the foreground and then the third application comes into the foreground, and the third application has a lower priority than the first application, the computer may further function as a means to prevent the third application from using the browser functionality. The program described in Program 6 or 7.

[0204] [Configuration 1] A management device for managing multiple applications, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, means for prohibiting the second application from using the browser functionality, Means for allowing the first application to use the browser functionality from the state before the second application came into the foreground when the application running in the foreground returns from the second application to the first application, An application management device equipped with the following features.

[0205] [Configuration 2] The application management unit manages multiple applications, An image forming function unit for forming an image, A multifunction printer equipped with, The aforementioned application management unit, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, means for prohibiting the second application from using the browser functionality, Means for allowing the first application to use the browser functionality from the state before the second application came into the foreground when the application running in the foreground returns from the second application to the first application, A multifunction printer equipped with the following features.

[0206] [method] A management method for managing multiple applications, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, the second application is prohibited from using the browser functionality. If the application running in the foreground switches back from the second application to the first application, the first application is allowed to use the browser functionality from the state it was in before the second application came into the foreground. An application management method having

Claims

1. A program that allows a computer to function as a management device for managing multiple applications, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, means for prohibiting the second application from using the browser functionality, When the application running in the foreground switches back from the second application to the first application, means for allowing the first application to use the browser function from the state before the second application came into the foreground, A program that makes a computer function.

2. If, during the period in which the first application is running, a third application that does not utilize the browser function is run in the foreground before the second application comes into the foreground, the computer is further configured to allow the second application to utilize the browser function. The program according to claim 1.

3. During the period in which the first application is running, if the third application runs in the foreground, then the second application runs in the foreground, and further if the first application returns to running in the foreground, the computer is further configured to allow the first application to use the browser functionality from its initial state. The program according to claim 2.

4. Even if the second application comes into the foreground while the first application is running, if the second application has a higher priority than the first application, the computer will further function as a means to allow the second application to use the browser functionality. The program according to claim 1.

5. If the second application comes into the foreground while the first application is running, and the second application has a lower priority than the first application, the computer may further function as a means to prevent the second application from using the browser function. The program according to claim 1.

6. If, during the period in which the first application is running, a third application capable of using the browser function comes into the foreground after the second application has come into the foreground, a prohibition means for prohibiting the third application from using the browser function, When the application running in the foreground returns from the third application to the first application, means for allowing the first application to use the browser function from the state before the second application came into the foreground, To make computers function even better, The program according to claim 1.

7. Even if the third application comes into foreground after the second application has come into foreground during the period in which the first application is running, if the third application has a higher priority than the first application, the computer will further function as a means to allow the third application to use the browser functionality. The program according to claim 6.

8. If, during the period in which the first application is running, the second application comes into foreground execution, and then the third application comes into foreground execution, and the third application has a lower priority than the first application, the computer may further function as a means to prevent the third application from using the browser functionality. The program according to claim 6.

9. A management device for managing multiple applications, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, means for prohibiting the second application from using the browser functionality, When the application running in the foreground switches back from the second application to the first application, means for allowing the first application to use the browser function from the state before the second application came into the foreground, An application management device equipped with the following features.

10. The application management unit manages multiple applications, An image forming function unit for forming an image, A multifunction printer equipped with, The aforementioned application management unit, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, means for prohibiting the second application from using the browser functionality, When the application running in the foreground switches back from the second application to the first application, means for allowing the first application to use the browser function from the state before the second application came into the foreground, A multifunction printer equipped with the following features.

11. A management method for managing multiple applications, If a second application capable of using browser functionality comes into the foreground while a first application capable of using browser functionality is running, the second application is prohibited from using the browser functionality. When the application running in the foreground switches back from the second application to the first application, the first application is allowed to use the browser functionality from the state it was in before the second application came into the foreground. An application management method having

Images