JP2018014603A - Information processing apparatus, control method and program of information processing apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve such a problem that a font available in a region based on the HTML data of WebView and in other region may be different, when using a Web font in the WebView.SOLUTION: In an image formation device capable of representing the screen of whole application by multiple screen components of different lithography method, and font data used by multiple screen components, in common, the first screen component expands the font data used by itself, and notifies a second screen component that the font data has been expanded when the font data used was expanded, and upon receiving the notification that font data was expanded from the first screen component, the second screen component acquires the font data again and plots the screen of itself again.SELECTED DRAWING: Figure 3

Description

  The present invention relates to an information processing apparatus including a web browser that is connected to a web server and displays an operation screen provided by the web server, a control method for the information processing apparatus, and a program.

  It is known that an information processing apparatus such as a PC or a mobile phone is connected to a Web server on a network and an operation screen provided by a Web application on the Web server is displayed on a Web browser provided in the information processing apparatus. In this case, first, the Web browser of the information processing apparatus requests an operation screen from the Web application on the Web server. Information on Web contents (including HTML data, JavaScript (registered trademark), and extended font data used in the Web contents) for the Web application to display an operation screen on the Web browser in response to a request from the information processing apparatus Respond to the processing unit. The Web browser of the information processing apparatus analyzes the received Web content and displays a screen based on the description. When the user inputs an instruction via the operation screen displayed on the Web browser, the Web browser notifies the input instruction to the Web server. The Web application on the Web server that has received this notification executes processing in accordance with the input instruction.

  Furthermore, there is a GUI component called WebView that has a function equivalent to the Web browser function described above and can be used as an element constituting an application on the information processing apparatus. An application on the information processing apparatus can realize the same expression and function as a Web browser on the application screen using this WebView.

  Some Web browsers and Webviews have a function that can dynamically expand fonts used in Web content to be displayed. By using this font expansion function, the Web application can expand the expressive power of the screen and improve user operability. Further, for example, as a method of using fonts in a plurality of areas constituting an application screen, there is a method of determining and expressing a font used in each area based on user settings (Patent Document 1).

JP 2011-40093 A

  When the screen itself based on the HTML data displayed on the Web browser is divided into a plurality of areas as in the conventional method, it is possible to select and use a font corresponding to the contents expressed in each area. it can.

  However, considering the case where the screen of the application is configured using both WebView and other GUI components, there is a problem that the font extension function can be used only on the WebView area. For this reason, there is a demand for a method that can use the font expansion function in a screen area other than WebView on the application screen.

  The present invention has been made in view of the above conventional example, and an object thereof is to provide an information processing apparatus, method, and program that can use a font expansion function regardless of the type of GUI component used by an application.

  In order to achieve the above object, the present invention has the following configuration.

A first drawing unit and a second drawing unit, which provide a drawing function for an application and have different drawing methods;
Display means for displaying an image drawn by the first drawing means and the second drawing means;
The first drawing means is configured to add an extended font to the second drawing means when the extended font data acquired for drawing the first data by the first drawing means is newly registered. Notification of registration notification,
The second drawing means acquires the registered extended font data in response to the extended font registration notification, and uses the extended font data to obtain second data to be drawn by the second drawing means. It is characterized by drawing.

  According to the present invention, the font extension function can be used regardless of the type of GUI component used by the application. As a result, the expressive power of the application screen can be expanded and the operability of the application can be improved.

It is a figure which shows the structural example of the system using the image processing apparatus in embodiment of this invention. It is a figure which shows the hardware structural example of the image processing apparatus in embodiment of this invention. It is a figure which shows the software structural example of the image processing apparatus in embodiment of this invention. It is a figure which shows the information management table example of the font data in embodiment of this invention. It is a figure which shows the example of a screen in embodiment of this invention. It is a figure which shows the Java source code example which designates the utilization font in embodiment of this invention. It is a figure which shows the example of the HTML source code which designates the utilization font in embodiment of this invention. It is a figure which shows the example of a screen after execution of the flowchart of FIG. 10 in embodiment of this invention. It is a figure which shows the Java source code example which designates the font displayed in FIG. 8 in embodiment of this invention. It is a flowchart until it acquires extended font data in embodiment of this invention, and redraws an application. It is a flowchart until it deletes the extended font data which an application utilizes with the uninstallation process of the application in embodiment of this invention. It is a follow chart which expanded step S1007 in FIG. 10 in embodiment of this invention.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.

[Embodiment 1]
<System configuration>
FIG. 1 is a configuration example of a system using an image processing apparatus according to the present invention. This system includes an MFP 100 and a Web server 103 connected to the network 101 via the Internet 102. A network 101 is a base for communicating between devices, and is connected to the Internet 102. A multifunction peripheral device (MFP) 100 that is an image processing apparatus has a Web browser and a Webview function. The WebView function is provided by the operating system, and an application uses the function. Therefore, any device having a Web browser or WebView function can be used instead of the MFP, and is not limited to the MFP. Further, MFP 100 may be managed with a local IP address. In this case, a gateway (not shown) exists between the network 101 and the MFP 100, and the gateway performs address conversion. For example, a gateway includes a router. Further, the gateway or the MFP 100 may have a firewall function. Web server 103 has a function of distributing Web content via a network, and returns Web content in response to a request from MFP 100. Each device and network does not necessarily have to be connected to the Internet, and may exist on a local network.

<Hardware configuration of the device>
FIG. 2 shows an example of a hardware configuration in the MFP 100 and the Web server 103 of this embodiment. The components constituting these devices include a CPU 201 that executes a program to control the MFP 100 and the Web server 103, a RAM 202 that provides a work area to the CPU 201, and a storage device 203 that stores the program according to the present embodiment and various settings. (HDD, SSD, NVRAM, etc. may be included). Further, it includes a user input device 204 for a user to input commands, a UI display device 205 for screen display, a network device 206 for communicating with other devices via a network, and a main bus 200.

  In this embodiment, unless otherwise specified, in the MFP 100 and the Web server 103, the CPU 201 controls the RAM 202, the storage device 203, the user input device 204, the UI display device 205, and the network device 206 via the main bus 200. Further, the UI display device 205 may also serve as the user input device 204 like a touch panel display. However, the Web server 103 may not include the user input device 204 or the UI display device 205. In addition, the MFP 100 may include an image reading device and an image printing device connected to the main bus 200 as components other than the illustrated components.

<Software configuration>
FIG. 3 shows an example of a software module group installed in the MFP 100 according to this embodiment. The module group shown in FIG. 3 is executed as a program by the CPU 201 in the MFP 100.

  Modules that are actually operated by the user include an application 300 operating on the application platform 303, a Web browser 307 independent of the application platform 303, and the like. The application 300 and the web browser 307 can display a screen on the UI display device 205. In addition, the application platform 303 can install / uninstall the application 300 in accordance with a user operation. Note that there may be a plurality of applications operating on the application platform 303. In this case, the application 300 may have application identification information for identifying the application. These software modules have their resources managed by an operating system (not shown). The WebView function is also provided by the operating system.

  Examples of components used when the application 300 constructs a screen include a GUI control 301 and a WebView 302. The WebView 302 and the Web browser 307 described above can acquire and display the Web content to be displayed from the Web server 103 via the network device 206 as described above. The content of the Web content to be displayed is an operation screen displayed on the screen of MFP 100, for example. It is also possible to execute a device function (not shown) of the MFP based on input information from the user input via the operation screen. Since the GUI control 301 is executed by the Web engine 304 and the WebView 302 is executed by the application platform 303 to perform drawing, it can be said that the Web engine 304 and the application platform 303 provide a drawing function.

  When handling Web content, the WebView 302 and the Web browser 307 may render HTML included in the Web content by using the Web engine 304 and the font engine 305 that are common modules in the MFP 100, and execute JavaScript (registered trademark). it can. Note that if the Web content acquired from the Web server 103 includes extended font data, the Web engine 304 can additionally store the extended font data in the font data 306 using the font engine 305. The font data 306 includes a management table shown in FIG. 5 and a font file containing font data. In this example, the WebView 302 renders and displays data written in accordance with the HTML notation, but data written in other markup languages may be rendered.

  The data stored in the font data 306 can also be used by the GUI control 301 of the application 300 via the font engine 305 and the application platform 303. For this reason, when extended font data exists in the Web content acquired from the Web server 103, the extended font data is registered in the font data 306, and the Web engine 304 notifies the application platform 303 to that effect. . This notification is referred to as a font expansion notification here.

  Further, when the application platform 303 receives the above font extension notification from the Web engine 304, the application platform 303 redraws the GUI control 301 of the application 300 after receiving the font extension notification. Furthermore, the application platform 303 deletes the extended font data in the font data 306 as necessary when the application 300 is uninstalled from the application platform 303.

  Note that the Web content described above is not limited to that provided by the Web server 103. Similarly, the form of the Web server 103 is not limited to the Web server that transmits / receives a request / response according to the HTTP protocol. The language for mounting each software module group is not limited to a specific language such as Java or C.

<Font data information management table>
FIG. 4 is an example of an information management table for font data in the embodiment of the present invention. The information management table includes at least a font name, information on a path where a font file is arranged, and identification information of an application using the font. The types of fonts to be handled include default font data 400 that always exists in the MFP 100 and extended font data 401 that is acquired based on acquisition of Web content. As described above, the extended font data 401 is included in the Web content acquired from the Web server 103, and the Web engine 304 may additionally register with the font data 306 along with the application identification information via the font engine 305. it can. Also, when the application 300 is uninstalled, the extended font data 401 associated with the application to be deleted can be deleted by using the application identification information. The element group of the font management table shown here is an example. For example, other component elements may be included, or application identification information may not be included if the elements are not associated with an application.

<Display screen example and font specification (using different fonts)>
FIG. 5 shows an example of a screen displayed on the UI display device 205 by the application 300 according to the embodiment of the present invention. The screen example of the application 300 includes an area 500 displayed by the GUI control 301 and an area 501 displayed by the WebView 302. The fonts used to represent characters are different between the area 500 and the area 501. An example of an implementation method for using a font in each area will be described later with reference to FIGS.

  FIG. 6 is an example of Java (registered trademark) source code for designating a font to be displayed in the area 500 displayed by the GUI control 301 in FIG. The description content of the source code 600 is such that the GUI control 301 designates the Serif font in the default font 400 included in the font data 306. In FIG. 6, the character string “Aiueo” is specified in the third line, the Serif font is specified in the last line, and the font of the character displayed in the area 500 of FIG. 5 is specified in FIG. 6. Serif. The source code shown here is an example, and the language for implementing the application 300 and the GUI control 301 is not limited to Java (registered trademark).

  FIG. 7 is an example of HTML source code for designating a font displayed in the area 501 displayed by the WebView 302 in FIG. As the description content of the source code 700, the WebView 302 in FIG. 4 designates the CanPop font in the extended font data 401 included in the font data 306 (source code third line in FIG. 7). Although the description of the character string to be displayed is omitted, “Tatsutoto” and the like are designated as illustrated in FIG. The extended font data 401 is downloaded as Web contents together with the HTML code, and the WebView 302 can display the extended font specified by HTML as shown in the area 501 in FIG. In the procedure of FIG. 10 to be described later, if additional registration of extended font data is not performed, for example, the font name “Serif” at the end of the Java (registered trademark) source code in FIG. 6 is replaced with the HTML source code in FIG. Even if the designated font file name “CanPop” is rewritten, it is still displayed as shown in FIG. This is because, for example, if the application platform 303 that executes the application 300 described in Java (registered trademark) does not acquire the extended font data, even if the extended font is specified, for example, the font specified as the default This is because drawing is performed using.

<Display screen example and font specification (with font extension notification)>
FIG. 8 shows the application 3 after execution of the flowchart of FIG. 10 in this embodiment.
00 is an example of a screen displayed on the UI display device 205. The font data 306 in this example includes the management table and font file shown in FIG. 4, and uses the same font data as in the display example in FIG. This screen example includes an area 800 displayed by the GUI control 301 and an area 501 displayed by the WebView 302 as in FIG. It can be seen that the fonts used to represent characters are the same in the area 800 and the area 501 in the figure. In order to realize this, an example of a method for mounting the area 800 will be described later with reference to FIG. Note that the configuration of this screen is merely an example, and an application 801 having a region 802 or a region 803 using a plurality of WebViews 302 may be used. In this case, in order to use the same font in all areas, it is necessary to specify the same font in each area.

  FIG. 9 is an example of Java source code for designating a font to be displayed in the area 800 in FIG. 8 in the present embodiment. It is an example of source code for designating a font in Java when expressing a font on an application screen in the present embodiment. Unlike the source code 600, the source code 900 shows an example in which the CanPop font in the extended font data 401 included in the data 306 is specified as the font to be used in the same manner as the source code 700. In order to use the same extended font data in the area 800 and the area 501 described above, it is necessary to implement the same font as in this example. That is, it is necessary to describe the same font in the HTML data and application program read by WebView. Note that when there are a plurality of font data, a priority order may be set for loading the font data. Further, it is preferable that the extended font data is loaded with priority over the default font. In this case, if the extended font data specified by the source code 900 does not exist in the font data 306, the default font 400 is applied.

<Extended font registration process>
FIG. 10 is a flowchart from when the Web engine 304 according to the embodiment of the present invention acquires the extended font data 401 until the application platform 303 redraws (and redisplays) the GUI control 301. When the Web view 302 used in the application 300 on the MFP 100 downloads Web content from the Web server 103 via the Web engine 304, this flowchart starts. In this case, it is assumed that the application platform 303 performs drawing by the GUI control 301 before using the WebView 302.

In step S1000, the Web engine 304 confirms or determines whether or not the extended font data is included in the downloaded Web content. If it is determined that it is included, the process proceeds to step S1001. If it is determined that it is not included, the process proceeds to step S1007.
In step S1001, the Web engine 304 instructs the font engine 305 to register the acquired extended font data, and the process advances to step S1002.

  In step S1002, the font engine 305 registers and saves the extended font data in the font data 306, and the process advances to step S1003.

In step S1003, the Web engine 304 draws HTML content on the WebView 302 using the registered extended font data, and the process advances to step S1004. If there are a plurality of WebView areas, the same processing may be performed in all WebView areas.
In step S1004, the Web engine 304 notifies the application platform 303 that the extended font data has been registered (extended font registration notification), and the process advances to step S1005.

  In step S1005, in response to the extended font registration notification, the application platform 303 instructs the font engine 305 to acquire the registered extended font data, and the process advances to step S1006.

  In step S1006, the font engine 305 returns the extended font data corresponding to the acquisition command to the application platform 303, and proceeds to step S1007.

  In step S1007, the application platform 303 draws the GUI control 301 using the acquired extended font data, and the process ends. The GUI control 301 may be a group of program modules for drawing a GUI (graphical user interface), for example. In step S1007, the GUI control 301 is re-executed to draw a GUI including an extended font. If the GUI control 301 has already been executed by the application platform 303 before the execution of step S1007, the GUI has already been drawn. For example, even if an extended font is specified in the GUI, the extended font is not included in the drawn content. Cannot be used and is drawn with the default font. In S1007, it is redrawn.

  After execution of this flowchart, the screen display changes from the state shown in FIG. 5 to the state shown in FIG. 8, and expression using the same font is possible in the area 800 and the area 501.

  If it is determined in step S1000 in FIG. 10 that the extended font data has not been downloaded, the process branches to step S1007. This is a convenience for showing that the application platform 303 performs drawing and display. The processing by the Web engine 304 may end. Drawing by the application platform 303 is performed independently of the Web engine 304.

  Further, the font data once acquired by the application platform 303 in steps S1005 and S1006 can be rendered by the application platform 303 without any additional registration notification of extended font data from the Web engine thereafter. For this reason, for example, even if the HTML data downloaded by the WebView 302 called by the application 300 is changed and the extension font is not downloaded, drawing and display by the GUI control 301 using the already registered extension font is possible. Become.

<Application uninstall process>
FIG. 11 is a flowchart until the extended font data used by the application 300 is deleted when the application 300 operating on the application platform 303 is uninstalled in the embodiment of the present invention. This flowchart starts when the application platform 303 uninstalls the application 300 in response to a request from a user who uses the MFP 100.

In step S1100, the application platform 303 confirms (that is, determines) whether or not there is extended font data associated with the application identification information to be uninstalled in the font data 306. If it is determined that there is, the process proceeds to step S1101, and if it is determined that there is not, the process ends.
In step S1101, the application platform 303 instructs the font engine 304 to delete the corresponding extended font data, and the process advances to step S1102.

  In step S1102, the font engine 304 deletes the designated extended font data based on the command, and the process ends. If one extended font can be associated with a plurality of application programs, in step S1100, the extended font data associated with only the application identifier to be uninstalled is the extended font data to be deleted. You may judge.

  With the configuration described above, the entire screen of the application is composed of a plurality of areas, and even when WebView and other GUI components are used together as GUI components used to display each area, the same font is used on the mutual GUI components. Will be available. As a result, the restriction on expressing the application screen can be relaxed, the expressive power can be expanded, and the operability of the application can be improved.

[Second Embodiment]
<Modified example of extended font registration processing>
FIG. 12 is a follow chart obtained by expanding step S1007 in FIG. 10 according to the embodiment of the present invention. For example, some image forming apparatuses such as MFPs do not support multi-windows on the display and only display active applications. For this reason, even if the extended font is displayed again for an application that is not displayed, it is not actually displayed. Therefore, in this embodiment, the extended font is redisplayed only for the displayed application.

  Steps up to step S1006 are the same as those in FIG. 10, and when there are a plurality of applications using the WebView 302 on the MFP 100, this flowchart is started. Note that S1200 and S1201 may be executed instead of S1007.

In step S1200, application platform 303 determines whether or not an extended font associated with the application identification information of the application currently displayed on UI display device 205 of MFP 100 is stored in font data 306, that is, whether or not Check (determine) whether or not it exists. If it is determined that it exists, the process proceeds to step S1201. If it is determined that it does not exist, the process ends.
In step 1201, the application platform 303 draws the GUI control 301 using the acquired extended font data, and the process ends. Thus, when there are a plurality of applications that use the extended font, the extended font is displayed for the currently displayed application.

  According to the present embodiment, in addition to the effects according to the first embodiment, the processing load can be reduced by drawing the extended font for the currently displayed application.

[Other Examples]
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

Claims (11)

A first drawing unit and a second drawing unit, which provide a drawing function for an application and have different drawing methods;
Display means for displaying an image drawn by the first drawing means and the second drawing means;
The first drawing means is configured to add an extended font to the second drawing means when the extended font data acquired for drawing the first data by the first drawing means is newly registered. Notification of registration notification,
The second drawing means acquires the registered extended font data in response to the extended font registration notification, and uses the extended font data to obtain second data to be drawn by the second drawing means. An information processing apparatus characterized by drawing.   2. The information according to claim 1, wherein the first drawing unit acquires the extended font data together with the first data, and draws the first data using the extended font data. Processing equipment.   The information processing apparatus according to claim 2, wherein the first data and the second data are acquired from another apparatus connected to the information processing apparatus.   The said 2nd drawing means deletes the said extended font data linked | related with the uninstalled application, when an application is uninstalled, The Claim 1 thru | or 3 characterized by the above-mentioned. Information processing device.   The second drawing means draws the second data by using the extended font data when an application to be drawn by the second drawing means is drawn. Information processing apparatus as described in any one of thru | or 4.   6. The extended font data is registered together with an extended font name, a file name of the extended font data, and application identification information using the extended font data. The information processing apparatus described.   The first drawing means draws HTML data as the first data, and the second drawing means draws data specified by the application as the second data. The information processing apparatus according to any one of claims 1 to 6.   The first drawing means is a Web engine that draws HTML data as the first data, and the second drawing means is an application platform that draws data described in the application as the second data. The information processing apparatus according to claim 7, wherein:   The information processing apparatus according to claim 1, further comprising an image reading unit and an image forming unit.   The program for functioning a computer as an information processing apparatus as described in any one of Claims 1 thru | or 8. First drawing means and second drawing means for providing drawing to an application and having different drawing methods, and display means for displaying an image drawn by the first drawing means and the second drawing means A method of controlling an information processing apparatus comprising:
When the first drawing unit newly registers the extended font data acquired for drawing the first data by the first drawing unit, the first drawing unit adds the extended font to the second drawing unit. Notification of registration notification,
The second drawing means obtains the registered extended font data in response to the extended font registration notification, and uses the extended font data as second data to be drawn by the second drawing means. A method for controlling an information processing apparatus, characterized by drawing.

Images