JP5262978B2 - User interface screen display method and terminal used for the method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To easily generate a user interface screen according to each of mobile terminals with different devices mounted thereon. <P>SOLUTION: A hardware information recording unit records hardware information showing configurations of a display device and an input device. An information extraction unit extracts user interface component information defining a user interface component used by software to be executed in an information processing terminal, from the software. A condition item recording unit records condition items for defining the display of the user interface component. A resource file generation unit generates a resource file recording display conditions of the user interface component by assigning the input device to the user interface component and satisfying the condition items in the hardware information and the user interface component information. A screen display unit uses the resource file to display the user interface component on the display device. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to a method for displaying a user interface screen.

  In order to improve the operability of the mobile terminal, a user interface (UI) is often used, but a variety of devices are mounted on the mobile terminal. Therefore, between mobile terminals with different installed devices, it may be difficult to operate an application developed for operating on one mobile terminal on another mobile terminal. As a method for generating a UI screen that can be used in a plurality of mobile terminals with different mounted devices, a method is known in which information corresponding to the device mounted on the mobile terminal to be used is provided in each application. .

  On the other hand, a device that prevents complicated user operations related to a graphical user interface has been devised, and a communication device that can display content information of a plurality of application functions and realize a simple user interface according to user needs is also known. ing.

JP 2008-301377 A

  If information corresponding to each information processing terminal on which each application is likely to be installed is prepared for each application, application development may become complicated. In addition, when an application is operated on an information processing terminal for which information on a device is not prepared, a problem may occur. In the background art, reference is made to related technologies for mobile terminals, but these problems are not limited to mobile terminals, and can be said to be problems that may occur when a user interface is displayed on a terminal that performs information processing. .

  An object of the present invention is to provide a method of easily generating a UI screen corresponding to each information processing terminal for information processing terminals equipped with different devices.

  According to one aspect of the present invention, a hardware information recording unit that records hardware information representing configurations of a display device and an input device provided in an information processing terminal, and software executed in the information processing terminal are used. User interface component information that defines user interface components, an information extraction unit that extracts from the software, a condition item recording unit that records condition items for defining display of the user interface component, and the user interface component A resource file generation unit that generates a resource file in which display conditions of the user interface component are recorded by allocating the input device and satisfying the condition item with the hardware information and the user interface component information; The information processing terminal comprising a screen display unit for displaying the user interface component on the display device by using the file is provided.

  For information processing terminals equipped with different devices, user interface screens corresponding to the information processing terminals can be easily generated.

It is a block diagram which shows an example of the mobile terminal which concerns on embodiment. It is a figure which shows an example of the hardware of the mobile telephone terminal which concerns on embodiment. It is a table which shows the example of the information recorded on a terminal information file. It is a figure explaining the expression method of soft key information. It is a figure explaining the production | generation method of the information regarding the soft key in a terminal information file. It is a table which shows the example of the item recorded as a template. It is a flowchart explaining the case where a user interface screen is displayed by embodiment (1). It is a flowchart explaining the creation method of a resource file. It is a flowchart explaining the operation | movement performed when GUI is displayed on a screen. It is a figure explaining calculation of the drawing conditions of a soft key. It is a figure which shows an example when displaying a GUI component with the mobile terminal carrying three soft keys. It is a figure explaining the production | generation method of the terminal information file used with the mobile terminal carrying five soft keys. It is a figure which shows an example when displaying a GUI component with the mobile terminal carrying five soft keys. It is a flowchart explaining the creation method of the resource file in embodiment (2).

  Hereinafter, a case where the user interface is a graphical user interface (GUI) and the GUI is displayed on the mobile terminal will be described in detail with reference to the drawings. However, the user interface to which this embodiment can be applied is not limited to the GUI, and can be any user interface. Further, the case where the information processing terminal is a mobile terminal is an example, and the present embodiment can be applied to any information processing terminal.

<Device configuration>
FIG. 1 is a block diagram illustrating an example of a mobile terminal according to the embodiment. The mobile terminal includes a terminal information analysis unit 11, a terminal information file generation unit 12, a resource management unit 13, a user interface screen generation unit 14, a screen display unit 15, a terminal information file 20, and a user interface screen resource 30.

  For example, when an application for displaying a GUI component corresponding to a device mounted on a mobile terminal including a key and a display is activated, the terminal information analysis unit 11 analyzes the information on the device and displays the analysis result as the terminal information. The file generation unit 12 is notified. The terminal information analysis unit 11 can also collect information on the mobile terminal device as hardware information and notify the terminal information file generation unit 12 of the information. Note that information used as hardware information is stored in advance on a memory mounted on the mobile terminal, for example. Or the area | region where hardware information is recorded can also be provided in memory as a hardware information recording part.

  The terminal information file generation unit 12 generates the terminal information file 20 using the information notified from the terminal information analysis unit 11. If settings for displaying GUI components, such as GUI display character strings, are specified by software (for example, application programs), the terminal information file generation unit 12 stores the information in the memory. And is recorded in the terminal information file 20. Here, when the terminal information file generation unit 12 includes an information extraction unit, the information extraction unit can extract and record settings used to display the GUI from information specified by the application. . The terminal information file 20 will be described in detail later.

  Information for displaying the GUI component is described in, for example, an application program. This information defines at least the name of the GUI component. In this case, the terminal information file generation unit 12 and the information extraction unit extract information for displaying the GUI component by analyzing the application program.

  The user interface screen resource 30 records condition items used when generating a resource file used for GUI display. The condition items recorded by the user interface screen resource 30 do not depend on the device mounted on the mobile terminal such as the condition item whose value varies depending on the device mounted on the mobile terminal and information on the color of the GUI component. Both condition items can be included. In the following description, information representing a condition item may be referred to as a “template”, and a portion of the user interface screen resource 30 that records the condition item may be referred to as a condition item recording unit. The template will be described later with an example. The user interface screen resource 30 can also store a generated resource file.

  The resource management unit 13 reads the terminal information file 20 and the template, generates a resource file for use in GUI display, and outputs the resource file to the user interface screen generation unit 14. The resource management unit 13 may include a plurality of parts such as a condition item acquisition unit and a resource information acquisition unit depending on the implementation. Here, the condition item acquisition unit acquires the condition item from the template, and the resource information acquisition unit acquires information specifying the condition item acquired by the condition item acquisition unit from the terminal information file 20. Although the resource file generated by the resource management unit 13 will be described in detail later, the size and position of the device corresponding to the GUI component are recorded.

  The user interface screen generation unit 14 calculates the size and display position on the screen when displaying the GUI component based on the information recorded in the resource file, and notifies the screen display unit 15 of the size. The screen display unit 15 displays GUI parts according to the notification from the user interface screen generation unit 14 and displays images, characters, and the like as appropriate on the screen of the mobile terminal.

  With the above operation, when an application is started on the mobile terminal, the mobile terminal autonomously generates a resource file that matches the hardware provided in the mobile terminal, and the GUI component is generated based on the resource file. Is displayed.

  The mobile terminal shown in FIG. 1 can be any mobile terminal that displays a GUI, but in the following description, an example in which the mobile terminal is a mobile phone terminal will be described. FIG. 2 is a diagram illustrating an example of hardware of the mobile phone terminal according to the embodiment. Here, the mobile phone terminal includes a memory 41, a wireless unit 42, a CPU 43, a sound input / output unit 44, a speaker 45, a microphone 46, a display control unit 47, a main LCD 48, a sub LCD 49, an input control unit 50, a touch panel 51, and It is assumed that a key 60 is provided.

  The memory 41 stores a program used for processing by the CPU 43 and stores data and a database used in the mobile phone terminal as appropriate. In the mobile terminal according to the embodiment, the terminal information file 20 and the user interface screen resource 30 illustrated in FIG. 1 are stored in the memory 41. In addition, a table or database that records information about hardware installed in the mobile terminal is also stored in the memory 41 as appropriate according to the implementation.

  The CPU 43 operates as a terminal information analysis unit 11, a terminal information file generation unit 12, a resource management unit 13, and a user interface screen generation unit 14 by executing a program stored in the memory 41. Further, the CPU 43 appropriately executes other programs and performs other processes.

  The wireless unit 42 controls wireless communication performed by the mobile phone terminal. The sound input / output unit 44 performs processing related to input and output of audio data to the mobile phone terminal, and controls the speaker 45 and the microphone 46. The display control unit 47 operates as the screen display unit 15 to control the display of the GUI on the screen of the mobile phone terminal, and appropriately controls the main LCD 48 and the sub LCD 49. The input control unit 50 controls the touch panel 51 and keys 60 used for input to the mobile phone terminal. Here, the device corresponding to the GUI component displayed by the screen display unit 15 is an arbitrary hardware mounted on the mobile phone terminal such as the speaker 45, the microphone 46, the main LCD 48, the sub LCD 49, the touch panel 51, and the key 60. Can be. In the following description, as an example, a case where a soft key of the keys 60 is associated with a GUI component will be described as an example.

<Embodiment (1)>
FIG. 3 is a table showing an example of information recorded in the terminal information file 20. In the terminal information file 20, hardware information and information extracted from the application by the terminal information file generation unit 12 are recorded. In the example of FIG. 3, the display size and the number, size, and position of the soft keys installed in the mobile terminal are acquired from the hardware information and recorded. In hardware information, the width and height of the display can be, for example, the number of horizontal and vertical pixels of the display. Further, the size and position of the soft key can be expressed by the coordinates of the position of each key when XY coordinates are assigned to the portion where the key of the mobile terminal is mounted.

FIG. 4 is a diagram illustrating a method for expressing soft key information. In the following description, it is assumed that the upper left of the entire area to which the coordinates are assigned is the origin, the X axis is the right direction, and the Y axis is the downward direction. The position of the soft key 61 (61a to 61c) is the position of each key. Expressed as upper left corner coordinates. For example, it is assumed that the soft key 61a is a rectangular key recognized as soft key number = 1, and the coordinates of its four corners are as follows.
Upper left corner (X, Y) = (5, 10)
Upper right corner (X, Y) = (13,10)
Lower left corner (X, Y) = (5, 14)
Lower right corner (X, Y) = (13,14)
Then, the terminal information analysis unit 11 recognizes that the soft key 61a is a rectangle having a width of 8 and a height of 4 with (X, Y) = (5, 10) as a reference of the upper left corner based on the coordinate values of the four corners. To do. Similarly, when the result of analyzing the information related to the soft keys 61b and 61c is also notified, information described in a field other than the key display name column in FIG. 4B is recorded together with the display size and the like as hardware information. That is, the hardware information records values indicating the size and position of the device corresponding to the GUI component as hardware.

  FIG. 5 is a diagram illustrating a method for generating information related to the soft key 61 in the terminal information file 20. The terminal information file generation unit 12 generates the terminal information file 20 using the notified hardware information and the information extracted from the memory 41 by the information extraction unit.

  After the terminal information file generation unit 12 acquires hardware information, the information extraction unit acquires information on the number of GUI components displayed by the application from the memory 41. Here, the hardware information notifies that the mobile terminal is equipped with three soft keys 61, and the number of GUI parts set corresponding to the soft keys 61 by the application is also three. Suppose there is. Then, the information extraction unit is designated by the application because the number of GUI parts specified in association with the soft key 61 in the application matches the number of soft keys 61 installed in the mobile terminal. It is determined that three GUI parts can be displayed.

  Next, the information extraction unit refers to the memory 41 and acquires information specified by the application for the display name described in the GUI component. Here, it is assumed that the information extraction unit detects that the key display name is not specified in the application. In such a case, the key display name stored in the memory 41 as a default setting is appropriately extracted and recorded in the terminal information file 20. Note that the default setting may be, for example, a character printed on the soft key 61 of the mobile terminal. If the default settings are “MENU”, “Guide”, and “Details” in the order of the soft key numbers, they are recorded in the terminal information file 20 as shown in the “default” column of FIG. The terminal information file generation unit 12 adds hardware information to the key display name information, and includes a “default” column in FIG. 5 and items such as a key number, X, Y, width, and height. 20 is generated.

  Similarly, when a “type A” application that displays three GUI parts corresponding to the soft key 61 is operated in the mobile terminal having the three soft keys 61, the terminal information file 20 is generated. In this case, the information extraction unit compares the number of GUI parts used by the application with the number of soft keys 61 mounted on the mobile terminal, and recognizes that they match. Next, the information extraction unit extracts the key display name of “Type A” from the memory 41 and assigns the extracted display name to the three soft keys 61. For example, “MENU”, “Edit”, and “Select” are extracted as key display names of the application of “Type A”, and the key display names are shown in the “Type A” column of FIG. Assigned as follows. In this case, the terminal information file 20 includes a “type A” field and items such as a key number, X, Y, width, and height.

  Next, a method for generating the terminal information file 20 when the number of GUI parts used by the application is larger than the number of soft keys 61 installed in the mobile terminal will be described. For example, in the “type B” application, there are five GUI parts corresponding to the soft key 61, and five key display names “MENU”, “history”, “select”, “previous month”, “next month” are displayed. Is set. In a mobile terminal equipped with three soft keys 61, it is not possible to display five GUI parts by associating one GUI part with each soft key 61. Therefore, the information extraction unit determines three GUI parts designated by the application as GUI parts to be displayed and assigns them to each soft key 61. Here, it is assumed that the information extraction unit selects a GUI component corresponding to the menu display function, history reference function, and selection function as a target GUI component to be displayed. Next, the information extraction unit extracts a key display name corresponding to the GUI component to be displayed from information related to the “type B” application stored in the memory 41. Then, three display names “MENU”, “history”, and “select” are acquired, and the GUI information assigned to each soft key 61 and the terminal information file 20 recorded so that the key display name matches are displayed. Generated. In the terminal information file 20, for example, a column of “Type B” and items such as a key number, X, Y, width, and height are recorded.

  On the other hand, when the number of GUI parts used by the application is smaller than the number of soft keys 61 mounted on the mobile terminal, the information extraction unit sets the GUI parts specified by the application as part of the soft keys 61. assign. For example, in a mobile terminal having five soft keys 61, when an application that displays three GUI parts to which the soft keys 61 are assigned is operated, the information extracting unit 3 of the five soft keys 61 Assign GUI parts to each. Further, the key display name is acquired, and the terminal information file 20 is generated so that the assigned GUI component matches the key display name.

  FIG. 6 is a table showing examples of items recorded as templates. In the template, a list of types of GUI parts displayed by the corresponding application and items of conditions used for displaying each type of GUI part are recorded. In the example of FIG. 6, GUI parts such as application parts, GUI parts to which soft keys are assigned, texts, lists, and the like are recorded as objects to be displayed. It should be noted that a template having some of the items shown in FIG. 6 as condition items can be used, and a template including items not shown in FIG. 6 can also be used.

  Since the template is information that does not depend on the hardware configuration of the mobile terminal, numerical values that vary depending on the device mounted on the mobile terminal are not included in the template, and the types of condition items are listed in the template. For example, since the number of soft keys 61 depends on the device mounted on the mobile terminal, as shown in FIG. 6, it is recorded in the template that the GUI component to which the soft key 61 is assigned is a display target. But that number is not represented. The template lists condition items used for display in association with GUI parts corresponding to the respective soft keys 61. Therefore, in the generation of the resource file, the resource management unit 13 reads the template, extracts a numerical value specifying the recorded condition item from the terminal information file 20, and records it in association with the condition item. For the GUI parts corresponding to the devices mounted on the mobile terminal, not only in the case of the soft key 61, the number of GUI parts is specified according to the record of the terminal information file 20, and the number of GUI parts for each GUI part is specified. A resource file with defined conditions is generated.

  Among the information for displaying the GUI parts, values are defined in the template for condition items that do not depend on the device mounted on the mobile terminal. The condition items whose values are recorded in the template include background color, outline color, display character color, initial value of character size, initial value of display character start position, and the like. The initial values of the character size and the display character start position are described in the template, and are changed when the GUI component is displayed using the values as will be described later.

  On the other hand, the position and size of the GUI component corresponding to the soft key 61 vary depending on the soft key 61 mounted on the mobile terminal. Therefore, the resource management unit 13 extracts the values recorded in the terminal information file 20 for each item, and generates a resource file.

  FIG. 7 is a flowchart illustrating a case where a user interface screen is displayed according to the embodiment (1). With reference to FIG. 7, an example of displaying a GUI component to which an application area and a soft key 61 are assigned will be described. Here, an example in which an application using the display name “type A” is started and the GUI is displayed using the terminal information file 20 including information about the display and information about the soft key 61 will be described as an example. In FIG. 7, steps S1 and S2 are operations of the terminal information analysis unit 11, steps S3 to S13 are operations of the terminal information file generation unit 12, step S14 is an operation of the resource management unit 13, and step S15 is a user interface screen generation unit. 14 and the screen display unit 15.

  When the application is activated, the terminal information analysis unit 11 confirms whether the terminal information file 20 created corresponding to the activated application is stored in the memory 41 (step S1). If the terminal information file 20 is not stored, the terminal information analysis unit 11 accesses the memory 41, acquires hardware information, and notifies the terminal information file generation unit 12 (step S2).

As described above, the hardware information is information in which information such as the number and size of devices mounted on the mobile terminal is collected for each type of device. As an example, the following information is included.
Display size: Width = 486, Height = 864
Maximum value of X coordinate: 48
Maximum value of Y coordinate: 86
Number of installed soft keys: 3
Soft key number = 1 soft key position: (X, Y) = (5, 10)
Soft key number = 1 soft key size: width = 8, height = 4
Soft key number = 2 soft key position: (X, Y) = (30, 10)
Soft key number = 2 Soft key size: Width = 8, Height = 4
Soft key number = 3 soft key position: (X, Y) = (15, 15)
Soft key number = 3, soft key size: width = 8, height = 8
Also, other arbitrary information related to the mobile terminal, such as the presence or absence of a touch input panel, can be recorded as hardware information.

  The terminal information file generation unit 12 extracts the display size and the maximum values of the X and Y coordinates from the acquired information, and stores these pieces of information as a display size definition (step S3).

  When the generation of the display size definition is finished, the information extraction unit uses the number of GUI parts specified by the application and the total number of soft keys 61 included in the hardware information, and the GUI corresponding to the soft key 61. The total number of parts is acquired (step S4). Here, as described with reference to FIG. 5, the number of soft keys 61 associated with the GUI parts is mounted on the mobile terminal and the number of GUI parts whose key display names are specified by the application. This is the smaller number of the soft keys 61. A case where the number of GUI parts specified by the application and the number of soft keys 61 on the mobile terminal are different will be described later, and here, the description will be made assuming that the two match. For example, if the number of GUI parts corresponding to the soft key and the number of installed soft keys 61 are both 3, it is determined that the total number of GUI parts for which “3” is displayed.

  Next, the soft key number to be processed is set to “1”, and the terminal information file generation unit 12 extracts the position and size of the soft key having the soft key number “1” from the hardware information. (Steps S5 to S7). Next, the information extraction unit confirms the type of the key display name used in the activated application, and acquires the corresponding key display name when an individual soft key display is used in the application (step S8). , S9). Here, it is assumed that the “type A” application is activated and “MENU” is acquired as the display name of the key of the soft key number “1”. On the other hand, when the display corresponding to the activated application is not used, the information extraction unit acquires and stores a default key display name (step S10).

Through the processing from step S6 to step S10, the position, size, and key display name of the soft key to be processed are acquired and stored as definitions. For example, the following information is stored as the definition for the key with soft key number = 1.
Position: (X, Y) = (5, 10)
Size: Width = 8, Height = 4
Key display name: “MENU”

  When the definition relating to one soft key is stored, the terminal information file generation unit 12 compares the total number of soft keys associated with the GUI component with the soft key number to be processed (step S11). If the two do not match, it is determined that there remains a soft key for which no definition has been created, and the definition of the next soft key is created by incrementing the soft key number to be processed by one. (Step S12, Steps S6 to S11).

When the creation of the definitions for the soft keys 61 of the soft key numbers 2 and 3 is finished, the soft key number is set to “3”, which matches the total number of the soft keys 61. If the total number of soft keys matches the soft key number to be processed in step S11, the terminal information file generation unit 12 determines that the creation of the definition of the GUI component corresponding to the soft key is completed, and the following contents Terminal information file 20 is created (step S13). The created terminal information file 20 is stored in the memory 41 and appropriately read into the resource management unit 13 or the like.
Display size: Width = 486, Height = 864
Number of installed soft keys: 3
The coordinates of the position of the first soft key: (X, Y) = (5, 10)
First soft key size: Width = 8, Height = 4
Display name of the GUI part corresponding to the first soft key: MENU
The coordinates of the position of the second soft key: (X, Y) = (30, 10)
Second soft key size: Width = 8, Height = 4
Display name of the GUI part corresponding to the second soft key: Edit The coordinates of the position of the third soft key: (X, Y) = (15, 15)
Third soft key size: Width = 8, Height = 8
Display name of the GUI part corresponding to the third soft key: Selection Maximum value of X coordinate: 48
Maximum value of Y coordinate: 86

  When the terminal information file 20 is generated, the resource management unit 13 creates a resource file using a template and outputs it to the user interface screen generation unit 14 as will be described in detail later (step S14). When the resource file is created, values used in the screen display unit 15 are calculated as appropriate, and the screen display unit 15 displays the GUI component on the main LCD 48 and the sub LCD 49 (step S15).

  FIG. 8 is a flowchart for explaining a resource file creation method. The process performed in step S14 of FIG. 7 will be described in detail with reference to FIG. The operation performed in the flowchart of FIG. 8 is the operation of the resource management unit 13.

When the terminal information file generation unit 12 is notified that the terminal information file 20 has been created, the resource management unit 13 reads the template from the user interface screen resource 30 and acquires the recorded condition items (steps). S21). Even when the terminal information file 20 is detected in step S1, the resource management unit 13 acquires the condition item in the template and generates a resource file (steps S1 and S14). In the following example, the UI part definition included in the template is an application area and a soft key, and the condition item is
(a) End position of application area (XY coordinate),
(b) the size of the application area,
(c) Soft key start position,
(d) Soft key size,
(e) Display character string of soft key,
(f) Assume that this is the initial character size of the soft key. Here, it is assumed that the initial value of the character size of the soft key is recorded in the template as a value that does not vary depending on the mobile terminal.

  When the resource management unit 13 recognizes that the application area size and the end position of the application area are included in the condition item, the resource management unit 13 determines whether the recognized condition item is a target for acquiring information from the terminal information file 20. . As described above, for condition items whose numerical value does not depend on the device mounted on the mobile terminal, the numerical value is not read because the value is defined in the template. However, since the end position of the application area depends on the device mounted on the mobile terminal, no value is set in the template. Therefore, the resource management unit 13 extracts values from the terminal information file 20 and stores them in association with the condition items for the numerical values determined to be information acquisition targets from the terminal information file 20 (step S22). . That is, from the terminal information file 20, the end position of the application area is set to (X, Y) = (48, 86), which is the maximum value of each of the X coordinate and the Y coordinate, and the size of the application area is the display size width 486, Height 864 is obtained.

  When acquisition of the value for the application area is completed, the resource management unit 13 refers to the UI component definition of the template and recognizes that the soft key remains as the UI component definition to be processed. For the condition item of the soft key, it is confirmed whether the template includes a numerical value, and it is confirmed that the initial value of the character size of the soft key is recorded in the template. Then, the resource management unit 13 recognizes that the object whose value is acquired from the terminal information file 20 is the start position, size, and display character string of the soft key.

  When recognizing that there is a value to be acquired from the terminal information file 20 for the soft key 61, the resource management unit 13 acquires the number of GUI components displayed in association with the soft key. In this example, the resource management unit 13 reads from the terminal information file 20 that the number of soft keys associated with the GUI component is 3, and sets the soft key number to be processed to “1” ( Steps S23 and S24). Next, after the coordinates, size, and key display name of the key of soft key number = 1 are stored in correspondence with the condition items from the terminal information file 20, the soft key number to be processed is associated with the GUI component. It is confirmed whether it is equal to the number of soft keys 61 (steps S25 to S28). Here, since the total number of the soft keys 61 associated with the soft key number and the GUI component does not match, the resource management unit 13 increments the soft key number by 1 and executes the process for the next GUI component ( Steps S28 and S29).

When the soft key number to be processed and the total number of soft keys 61 associated with the GUI component match, the resource management unit 13 recognizes that the acquisition of information about the soft key 61 has ended (step S28). The resource management unit 13 creates the following resource file by associating the values acquired from the terminal information file 20 with the condition items.
End position of application area (XY coordinate): (X, Y) = (48, 86)
Application area size: Width = 486, Height = 864
Soft key number = 1
Position coordinates: (X, Y) = (5, 10)
Size: Width = 8, Height = 4
Display name of corresponding GUI parts: MENU
Initial value of character size: 10 points Soft key number = 2
Position coordinates: (X, Y) = (30, 10)
Size: Width = 8, Height = 4
Display name of corresponding GUI parts: Edit Initial value of character size: 10 points Soft key number = 3
Position coordinates: (X, Y) = (15, 15)
Size: Width = 8, Height = 8
Display name of the corresponding GUI part: Selection Initial value of character size: 10 points

  When titles, lists, and the like are recorded in the template as UI parts, values corresponding to the condition items are appropriately acquired from the memory 41 for the title area and list information (steps S30 and S31). . In this case, a file in which the value acquired from the terminal information file 20 is associated with the condition item is also output as a resource file for values such as list information.

  FIG. 9 is a flowchart for explaining an operation performed when the GUI is displayed on the screen. The process performed in step S15 of FIG. 7 will be described with reference to FIG. Here, steps S41 to S43 and steps S47 to S53 are operations of the screen display unit 15, and steps S44 to S46 are operations of the user interface screen generation unit 14.

  When the application area is defined in the resource file as a user interface component, as in the resource file described above as an example, the screen display unit 15 draws with the background color according to the designation in the resource file (step S41, S42). Next, it is confirmed whether the soft key 61 is defined in the resource file. If the soft key 61 is included as a user interface component, the screen display unit 15 informs the user interface screen generation unit 14 to that effect. Is notified (step S43). Upon receiving the notification, the user interface screen generation unit 14 calculates the drawing conditions for the soft key 61 (steps S43 to S46).

  FIG. 10 is a diagram for explaining the calculation of the drawing conditions of the soft key 61. The processing in steps S44 to S46 will be described with reference to FIG. In FIG. 10, in order to easily distinguish from the coordinate system set in the key mounting portion of the mobile terminal, it is expressed as xy coordinates as shown in FIG. Here, the xy coordinates are expressed with the upper left corner of the display as the origin, the positive value of the x-axis set in the right direction of the display, and the positive value of the y-axis set in the downward direction, and the coordinates expressed in units of pixels. And

  The user interface screen generation unit 14 sets the ratio of the soft key 61 mounted on the mobile terminal to the area where the XY coordinates of the mobile terminal are set to the ratio of the GUI component corresponding to the soft key 61 with respect to the application area. (Step S44). For example, the key of the soft key 61a occupies the area of X = 5 to 13 and Y = 10 to 14 in the area where the XY coordinates of X = 0 to 48 and Y = 0 to 86 are set. Since the application area is x = 0 to 486 and y = 0 to 864, the user interface screen generation unit 14 calculates the GUI parts corresponding to the soft key 61a as x = 50 to 130 and y = 100 to 140. FIG. 10A shows an image of the GUI displayed as the number of pixels at the calculated xy coordinates for the soft keys 61b and 61c.

  Next, the user interface screen generation unit 14 calculates whether the soft key 61 fits in the assigned GUI component when the display character string is displayed with the initial value of the character size set in the resource file. To do. When the character string protrudes from the GUI component as shown in FIG. 10B, the font used for displaying the character string is reduced and recalculated, and the font that fits in the GUI component as shown in FIG. Find a number. At this time, by changing the size of the GUI component without changing the font, the character string can be stored in the GUI component, and both the number of fonts and the size of the GUI component are recalculated. It can also be performed (step S45).

When the font calculation is completed, the user interface screen generation unit 14 displays each GUI component so that the maximum value of the y coordinate of the GUI component associated with the soft key 61 is displayed at the lowest position in the application area. The y coordinate is changed (step S46). For example, if the size of the GUI part is not changed in step S46, since the coordinates of the soft key 61c are X = 15 to 23 and Y = 15 to 23, the coordinates of the GUI part corresponding to the soft key 61c are x = 150 to 230 and y = 150 to 230. Since the bottom of the GUI component corresponding to the soft key 61c is the maximum value of the y coordinate of the GUI component, the y coordinate of the soft key 61 is set so that the coordinate of the bottom of the GUI component corresponding to the soft key 61c is y = 864. change. As a result, as shown in FIG. 10D, the coordinates of each soft key 61 and the following values are set, and the calculation result is notified from the user interface screen generation unit 14 to the screen display unit 15.
GUI parts corresponding to the soft key 61a: x = 50 to 130, y = 734 to 774
GUI parts corresponding to the soft key 61b: x = 300 to 380, y = 734 to 774
GUI parts corresponding to the soft key 61c: x = 150 to 230, y = 784 to 864

  The screen display unit 15 uses the value notified from the user interface screen generation unit 14 to draw the frame line, background, and character string of the GUI component corresponding to each of the soft keys 61 (steps S47 to S49). If the resource file has a definition for a GUI component for displaying text or a list, the settings of the resource file are appropriately read (steps S50 and S52), and the text and list are drawn (steps S51 and S53). .

  FIG. 11 is a diagram illustrating an example when a GUI component is displayed on a mobile terminal equipped with three soft keys 61. As described above, by using the resource file created based on the template provided in the application, it corresponds to the mobile terminal equipped with three soft keys 61 shown in FIG. The GUI screen is displayed as shown in (b). In this example, a screen when the incoming call history reference application is activated is shown, and a soft key 61 with a default display name is displayed. In this way, by creating a resource file using a template, even if a resource file that describes specific setting values is not prepared in the application, it is compatible with mobile terminals equipped with three soft keys 61 The GUI screen can be displayed.

  Next, a case where the number of GUI parts specified by the application is larger than the number of soft keys 61 mounted on the mobile terminal will be described. Here, a case will be described in which an application started on a mobile terminal equipped with three soft keys 61 is designed to display five GUI parts as GUI parts corresponding to the soft keys 61. As described with reference to FIG. 7, the total number of soft keys corresponding to the GUI parts is the number of GUI parts whose key display names are specified by the application and the number of soft keys 61 mounted on the mobile terminal. The smaller number of them. Here, even if the application defines five GUI parts in association with the soft keys 61, since the number of soft keys 61 installed in the mobile terminal is three, the software associated with the GUI parts It is determined that the number of keys 61 is three (step S4). Therefore, information about the soft keys having the soft key numbers 1 to 3 is recorded in the terminal information file 20, and a resource file is generated based on the terminal information file 20. For this reason, information about the three soft keys 61 is recorded in the resource file. Of the GUI parts defined in the application, the GUI parts associated with the soft keys not mounted on the mobile terminal are recorded. Information is not written in the resource file. Since the screen is displayed by the screen display unit 15 or the like based on this resource file, the GUI component associated with the soft key 61 that is not mounted on the mobile terminal is not displayed on the screen of the mobile terminal. A GUI screen as shown in b) is displayed. Therefore, even if the number of GUI parts defined in the application in association with the soft key 61 is larger than the number of soft keys 61 mounted on the mobile terminal, the soft key 61 mounted on the mobile terminal The number of GUI parts corresponding to is displayed. That is, in this embodiment, it is possible to prevent display of GUI parts corresponding to the soft keys 61 that are not mounted on the mobile terminal.

  Further, when the number of GUI parts specified by the application is smaller than the number of soft keys 61 mounted on the mobile terminal, the number of GUI parts corresponding to the soft key 61 is set to the soft key mounted on the mobile terminal. Compare with the number 61.

  First, in a mobile terminal equipped with five soft keys 61, when an application using five GUI parts corresponding to the soft keys 61 is started, the operation described with reference to FIGS. The terminal information analysis unit 11 and the screen display unit 15 operate in the same manner as in FIG. However, in step S2, the terminal information analysis unit 11 generates hardware information in which information about each of the five soft keys 61 mounted on the mobile terminal is described. FIG. 12 is a diagram for explaining a method for generating the terminal information file 20 used in a mobile terminal equipped with five soft keys 61.

  The information extraction unit obtains the number of keys for which the application designates the key display name and compares it with the number of soft keys 61 recorded in the hardware information, thereby displaying the information in association with the soft key 61. The number of GUI parts is acquired (step S4). Here, since the number of soft keys 61 mounted on the mobile terminal and the number of GUI parts for which the application has designated key display names are both 5, the number of GUI parts associated with the soft key 61 is It is determined to be “5”. Next, information specifying a condition item for each of the five soft keys 61 is acquired, and the terminal information file 20 is generated (steps S5 to S13). The procedure when the resource file is generated using the terminal information file 20 and the procedure when the GUI is displayed based on the resource file are the same as those described with reference to the flowcharts of FIGS. It is. When the terminal information file 20 including the information such as the position and size of the soft key 61 shown in FIG. 12 and the key display name designated by the application is generated by the above procedure, the resource file is generated based on the terminal information file 20. Generated and the screen is displayed. Therefore, in a mobile terminal equipped with five soft keys 61 as shown in FIG. 13 (a), the GUI screen of the incoming call history reference application is displayed as shown in FIG. 13 (b).

  On the other hand, when an application that uses three GUI parts corresponding to the soft key 61 is started in a mobile terminal equipped with five soft keys 61, the number of GUI parts specified by the application is the soft key. Less than 61 numbers. Therefore, in step S4, “3”, which is the smaller of the number of GUI parts whose key display name is specified by the application and the number of soft keys 61 mounted on the mobile terminal, is the GUI part. The total number of soft keys associated with. Therefore, the information extraction unit acquires information corresponding to the condition items for the soft keys 61 having the soft key numbers 1 to 3 (steps S5 to S12). When the soft key number is 3, it is determined that a condition item has been acquired for each of the displayed GUI parts, and a terminal information file 20 including information about the GUI parts corresponding to each of the three soft keys 61 is generated. (Steps S11 and S13). After that, as described with reference to FIG. 8, a resource file is generated based on the terminal information file 20. In this resource file, three GUI parts are defined as GUI parts corresponding to the soft keys 61. Has been. When the processing described with reference to FIG. 9 is performed using the generated resource file, as shown in FIG. 13A, the mobile terminal having five soft keys 61 is used as shown in FIG. As shown in (), a screen with three GUI parts corresponding to the soft key 61 is displayed. Therefore, when the number of GUI parts defined in the application in association with the soft key 61 is smaller than the number of soft keys 61 installed in the mobile terminal, the number of GUI parts defined in the application Is displayed. For this reason, it is possible to prevent display of GUI parts corresponding to keys to which functions in the application are not assigned.

  As described above, according to the present embodiment, the resource file is autonomously generated in the mobile terminal without setting the resource file used for displaying the GUI screen of the application according to the device information of the mobile terminal. . Moreover, since the setting according to the device information of the mobile terminal is recorded in the generated resource file, a GUI screen corresponding to the hardware included in the mobile terminal is displayed. Furthermore, it is possible to prevent display of GUI parts corresponding to the soft keys 61 to which no function in the application is assigned.

<Embodiment (2)>
In the embodiment (1), the GUI display method when the resource file is created using the terminal information file 20 has been described. However, the GUI screen is displayed using the resource file created without using the terminal information file 20. Can also be displayed. In this case, when notified that the application is activated, the resource management unit 13 acquires information on the device mounted on the mobile terminal from the terminal information analysis unit 11 or the terminal information file generation unit 12. Create a resource file.

  FIG. 14 is a flowchart illustrating a method for creating a resource file in the embodiment (2). When starting the creation of a resource file, the resource management unit 13 reads a template from the user interface screen resource 30 and acquires a condition item (step S61). Then, the terminal information analysis unit 11 extracts the size of the application area, the maximum value of the X coordinate and the Y coordinate of the area where the XY coordinates are set, from the information recorded in the memory 41, and sends it to the resource management unit 13. Notification is made (step S62). The resource management unit 13 stores information on the notified application area in association with the condition item.

  When the soft key 61 is mounted on the mobile terminal, the terminal information analysis unit 11 acquires the number of soft keys 61 mounted on the mobile terminal from the memory 41 and notifies the resource management unit 13 of the number. Further, the information extraction unit acquires the number of GUI components specified by the application as the GUI component to be displayed in association with the soft key 61 and notifies the resource management unit 13 of the number. The resource management unit 13 compares the number of soft keys 61 installed in the mobile terminal with the number of GUI parts corresponding to the soft key 61 specified by the application, and determines the smaller number as the software corresponding to the GUI part. The number of keys 61 is set (step S63). Next, both the terminal information analysis unit 11 and the resource management unit 13 set the soft key number to “1” (step S64). When the terminal information analysis unit 11 acquires the position and size of the soft key 61 having the soft key number “1” and notifies the resource management unit 13 of the information, the resource management unit 13 also corresponds to the condition item. Add and store (steps S65, S66). Note that the information on the position and size of the soft key 61 acquired here is information in the XY coordinates set as described in the embodiment (1).

  Furthermore, the information extraction unit determines whether a key display name to be displayed on the GUI component corresponding to the soft key 61 is specified in the activated application (step S67). When the key display name is specified, the information extraction unit reads the display name corresponding to the application to be activated and notifies the resource management unit 13 of the information, and the resource management unit 13 records the notified key display name (step). S67, S68). On the other hand, when the activated application does not specify the key display name of the soft key 61, the default key display name assigned to the soft key 61 is read and recorded by the resource management unit 13 (step S67, S69). When the recording of the key display name is completed, the resource management unit 13 compares the soft key number of the soft key 61 that has acquired information such as the position and the key display name with the total number of the soft keys 61 corresponding to the GUI component (Step S1). S70). If the soft key number of the key from which information is acquired does not match the total number of soft keys 61, the resource management unit 13 increments the soft key number from which information is to be acquired by 1, and analyzes the terminal information. Notification to the unit 11 (step S71). Then, the terminal information analysis unit 11 and the information extraction unit perform the operation described in Steps S65 to S69 for the soft key 61 newly targeted for information acquisition, and the resource management unit 13 appropriately transmits the notified information. ,Record.

  On the other hand, when the soft key number of the soft key 61 from which the information has been acquired matches the total number of the soft keys 61, the resource management unit 13 determines that the acquisition of information regarding the soft key 61 has ended, and the terminal information analysis unit 11 The terminal information file generator 12 is notified. The information extraction unit appropriately acquires the title area, list information, and the like from the memory 41 and notifies the resource management unit 13 of the information, and the resource management unit 13 records the notified information (steps S72 and S73).

  When the resource management unit 13 records the condition item and information notified from the terminal information analysis unit 11 or the information extraction unit in association with each other, the resource management unit 13 outputs the recorded file as a resource file (step S14). When the resource file is generated, as described above with reference to FIGS. 9 and 10, a GUI screen is displayed based on the resource file (step S15).

  Thus, by changing the operations of the terminal information analysis unit 11, the terminal information file generation unit 12, and the resource management unit 13, a resource file can be created from a template without using the terminal information file 20, and the resource The GUI screen can be displayed based on the file. Here, the information stored in the memory 41 has been described as being notified from the terminal information analysis unit 11 and the terminal information file generation unit 12 to the resource management unit 13, but this is an example. For example, the information acquired by the terminal information analysis unit 11 can be acquired by the resource management unit 13 via the terminal information file generation unit 12, and information used by the resource management unit 13 to create a resource file from the memory 41 It can also be modified to obtain When the resource management unit 13 acquires information used to create a resource file and creates a resource file without using the terminal information file 20, the resource management unit 13 replaces the terminal information analysis unit 11 and the terminal information file generation unit 12. It can also be included.

  Also in such an embodiment, the GUI component corresponding to the soft key 61 to which the application assigns the function can be displayed on the screen, and the GUI component corresponding to the soft key 61 not mounted on the mobile terminal is not displayed. In addition, the GUI component corresponding to the soft key 61 to which no function is assigned by the application is not displayed. Also, a GUI screen corresponding to each mobile terminal can be generated without creating an application in which resource files are individually set for mobile terminals equipped with different devices.

The present invention is not limited to the above-described embodiment, and can be variously modified. Some examples are described below.
In the above description, the case where the coordinates are set and the position is specified based on the upper left corner is taken as an example. However, the position of the origin of the coordinates can be changed according to the implementation and is used for specifying the position of the soft key 61. Coordinates can also be changed.

  7, 8, 14, and the like are flowcharts for processing the GUI part information corresponding to the soft key 61 after the information about the application area is processed. However, the order of the information to be processed is changed. You can also

  Furthermore, the terminal information analysis unit 11, the terminal information file generation unit 12, the resource management unit 13, and the user interface screen generation unit 14 are not only realized by software, but also part or all of these parts are implemented by hardware circuits. It can also be configured to be realized.

  When hardware information is stored in the memory 41 in advance, a mobile terminal that does not include the terminal information analysis unit 11 may be used. In this case, the terminal information file generation unit 12 creates the terminal information file 20 from the information acquired from the hardware information recording unit and the definition of the GUI component assigned by the application. The GUI is displayed using the resource file generated based on the terminal information file 20.

  Furthermore, when the terminal information file 20 is stored in the memory 41 in advance, a mobile terminal that does not include the terminal information analysis unit 11 and the terminal information file generation unit 12 may be used. In this case, a resource file is generated using the terminal information file 20 and the template in the memory 41, and the GUI is displayed.

The following additional notes are further disclosed for each of the embodiments described above.
(Appendix 1)
A hardware information recording unit for recording hardware information representing a configuration of a display device and an input device provided in the information processing terminal;
An information extraction unit for extracting user interface component information defining user interface components used by software executed in the information processing terminal from the software;
A condition item recording unit for recording condition items for defining display of the user interface component;
A resource file that assigns the input device to the user interface component and generates a resource file that records display conditions of the user interface component by satisfying the condition items with the hardware information and the user interface component information A generator,
An information processing terminal comprising: a screen display unit that displays the user interface component on the display device using the resource file.
(Appendix 2)
The condition item includes a component display name for identifying the user interface component on the screen, and the resource file generation unit associates a device identifier for specifying the input device with the component display name to identify the resource. The information processing terminal according to appendix 1, which is recorded in a file.
(Appendix 3)
The resource file generation unit generates a resource file for each of the input devices corresponding to the user interface component by giving the hardware information and the user interface component information to the condition item,
The information processing terminal according to appendix 1, wherein the screen display unit displays the user interface component corresponding to each of the input devices using the resource file.
(Appendix 4)
The resource file generator
A condition item acquisition unit for acquiring the condition item recorded in the condition item recording unit;
A resource information acquisition unit that acquires information specifying the condition item extracted by the condition item acquisition unit from the hardware information and the user interface component information,
The information processing terminal according to appendix 1, wherein the resource file generation unit generates the resource file by recording information specified by the resource information acquisition unit in association with the condition item.
(Appendix 5)
The resource file generation unit generates the resource file including information specifying the size of the input device with respect to the size of the information processing terminal and the position of the input device on the information processing terminal,
The screen display unit determines the size of the user interface component with respect to the screen of the information processing terminal and the position of the user interface component on the screen of the information processing terminal according to the information recorded in the resource file. The information processing terminal according to Supplementary Note 1, wherein
(Appendix 6)
An information processing apparatus included in the information processing terminal
Hardware information recording means for recording hardware information representing a configuration of a display device and an input device provided in the information processing terminal;
Information extracting means for extracting user interface component information defining user interface components used by software executed in the information processing terminal from the software;
Condition item recording means for recording condition items for defining display of the user interface component;
A resource file that assigns the input device to the user interface component and generates a resource file that records display conditions of the user interface component by satisfying the condition items with the hardware information and the user interface component information Generating means,
A program for operating as a screen display means for displaying the user interface component on the display device using the resource file.
(Appendix 7)
Obtain hardware information representing the configuration of the display device and input device provided in the information processing terminal,
User interface component information defining user interface components used by software executed in the information processing terminal is extracted from the software;
Obtain a condition item for defining the display of the user interface component,
Assigning the input device to the user interface component and satisfying the condition item with the hardware information and the user interface component information, generate a resource file that records the display conditions of the user interface component,
The user interface screen display method, wherein the user interface component is displayed on the display device using the resource file.

DESCRIPTION OF SYMBOLS 11 Terminal information analysis part 12 Terminal information file generation part 13 Resource management part 14 User interface screen generation part 15 Screen display part 20 Terminal information file 30 User interface screen resource 41 Memory 42 Radio | wireless part 43 CPU
44 Sound input / output unit 45 Speaker 46 Microphone 47 Display control unit 48 Main LCD
49 Sub LCD
50 Input control unit 51 Touch panel 60 keys 61 Soft keys

Claims (4)

A hardware information recording unit for recording hardware information representing a configuration of a display device and an input device provided in the information processing terminal;
An information extraction unit for extracting user interface component information defining user interface components used by software executed in the information processing terminal from the software;
A condition item recording unit for recording condition items for defining display of the user interface component;
A resource file that assigns the input device to the user interface component and generates a resource file that records display conditions of the user interface component by satisfying the condition items with the hardware information and the user interface component information A generator,
A screen display unit for displaying the user interface component on the display device using the resource file ;
The resource file generator
A condition item acquisition unit for acquiring the condition item recorded in the condition item recording unit;
A resource information acquisition unit that acquires information specifying the condition item extracted by the condition item acquisition unit from the hardware information and the user interface component information,
The information processing terminal , wherein the resource file generation unit generates the resource file by recording information specified by the resource information acquisition unit in association with the condition item . The condition item includes a component display name for identifying the user interface component on the screen, and the resource file generation unit associates a device identifier for specifying the input device with the component display name to identify the resource. The information processing terminal according to claim 1, wherein the information processing terminal is recorded in a file. The resource file generation unit generates the resource file including information specifying the size of the input device with respect to the size of the information processing terminal and the position of the input device on the information processing terminal,
The screen display unit determines the size of the user interface component with respect to the screen of the information processing terminal and the position of the user interface component on the screen of the information processing terminal according to the information recorded in the resource file. The information processing terminal according to claim 1. A hardware information acquisition step for acquiring hardware information representing the configuration of a display device and an input device provided in the information processing terminal;
An information extracting step for extracting user interface component information defining user interface components used by software executed in the information processing terminal from the software;
A condition item recording step of acquiring and recording a condition item for defining display of the user interface component;
A resource file that assigns the input device to the user interface component and generates a resource file that records display conditions of the user interface component by satisfying the condition items with the hardware information and the user interface component information Generation step ;
A display step of displaying the user interface component on the display device using the resource file ;
With
In the resource file generation step,
Obtain the recorded condition items,
From the hardware information and the user interface component information, obtain information specifying the obtained condition item,
A user interface screen display method , wherein the resource file is generated by recording the designated information in association with the condition item .