JP2011034154A - Program and method for converting display layout information - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To newly create a screen definition file corresponding to a dynamically varying window size in an execution environment of application. <P>SOLUTION: An application conversion part 10 includes an information obtaining means 10a and an information creation means 10b and creates display layout information 10c for a target. The information obtaining means 10a communicates with a debugger 20b and obtains variables (display layout information of items to be displayed) during execution of the application 20a via the debugger 20b. The information creation means 10b creates the display layout information 10c for the target based on the variables (the display layout information of the items to be displayed) during execution of the application 20a obtained by the information obtaining means 10a. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a display layout information conversion program and a display layout information conversion method for converting display layout information of a source file into display layout information of a target file.

  When replacing an existing application program (source program) with an application program (target program) written in a different programming language, it may be necessary to create a new screen definition file. For example, when an existing Java (registered trademark) client application (Applet, JavaGUI) is replaced with a Web application, it is necessary to newly create a screen definition file (for example, an HTML file). In such a replacement operation, when a new screen definition file is created, the screen definition file of the target program may need to be input or modified to adapt to the execution environment.

  Thus, for example, there is a proposal of a technique for efficiently converting a character user interface screen into a screen defined in a markup language (see Patent Document 1).

JP 2007-94490 A

  However, there is a request not only to convert definition information for configuring a character user interface format screen into a graphic user interface format screen as input source information, but also to convert screen definitions between graphic user interface formats. . When such screen definition conversion is performed, the display layout of the screen after conversion may differ from the display layout of the screen before conversion, such as a shift in the display position, reflecting the display layout before conversion. The display layout may not be obtained. In that case, the operator needs to correct the display layout after conversion. In particular, when the window size dynamically changes in the application execution environment, there is a case where there is no specific information in the source program, which makes it difficult to generate the target program.

  Accordingly, it is an object of the present invention to provide a display layout information conversion program capable of newly creating a screen definition file corresponding to a window size that dynamically changes in an application execution environment.

  In order to solve the above problem, in a display layout information conversion program for converting display layout information of a source file described in one language into display layout information of a target file described in another language, the computer includes the source Information acquisition means for acquiring display layout information of an item to be displayed from an application executed based on the file, and target display layout information for the item displayed by the target file from the display layout information acquired by the information acquisition means A display layout information conversion program is provided that functions as information generation means for generating a display layout information.

  The information acquisition unit acquires display layout information of items to be displayed from an application executed based on the source file. The information generation unit generates target display layout information of items displayed by the target file from the display layout information acquired by the information acquisition unit.

  According to the above display layout information conversion program, it is possible to newly create a screen definition file corresponding to a window size that dynamically changes in the execution environment of the application.

It is a functional block diagram of the layout information conversion tool of the embodiment. It is a figure which shows the system configuration | structure in the case of using a display layout information conversion technique. It is an example of a system configuration in the case of using a display layout information conversion technique when converting a Java application into HTML. A display example of a Java application and a display example after conversion to HTML. It is a system configuration example in the case of using a display layout information conversion technique when converting the Java application of the embodiment into HTML. It is the example of a display of the Java application of embodiment, and the example of a display after converting into HTML. It is an item information table of an embodiment. It is an output example of the HTML file of the embodiment. It is a figure which shows the hardware structural example of the display layout information conversion apparatus of embodiment. It is a functional block diagram of the layout information conversion tool of the second embodiment. It is a main flowchart of the application conversion part of 2nd embodiment. It is a flowchart of the screen information acquisition process of 2nd embodiment. It is a flowchart of the output process of the HTML file of 2nd embodiment. It is a figure which shows an example of the HTML tag conversion rule of 2nd embodiment. It is a figure which shows an example of the HTML tag conversion rule of 2nd embodiment. It is a figure which shows the example of a production | generation of the item information table of 2nd embodiment. It is a figure which shows the output example of the HTML file of 2nd embodiment. It is a figure which shows the example of acquisition of the display layout information of 2nd embodiment. It is a figure which shows the example of acquisition of the display layout information in one window size of 2nd embodiment. It is a figure which shows the example of acquisition of the display layout information in the other window size of 2nd embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
FIG. 1 is a functional block diagram of the layout information conversion tool of the embodiment. The layout information conversion tool 1 includes an application conversion unit 10 and an application process 20 that are processes on a computer. The application process 20 includes an application 20a and a debugger 20b. The application 20a is executed after converting an existing application program (source program) into an execution format. The debugger 20b refers to variables (display layout information of items to be displayed) during execution of the application 20a.

  The application conversion unit 10 includes an information acquisition unit 10a and an information generation unit 10b, and generates target display layout information 10c. The information acquisition unit 10a communicates with the debugger 20b, and acquires variables during execution of the application 20a (display layout information of items to be displayed) via the debugger 20b. The information generation unit 10b generates the target display layout information 10c based on the variable (display layout information of the item to be displayed) being executed by the application 20a acquired by the information acquisition unit 10a.

The application conversion unit 10 implements various functions of the application conversion unit 10 by executing a display layout information conversion program on a computer.
In this way, the display layout information (item name, type, display position, size, font, value, etc.) of the item is acquired from the dynamically changing display during execution of the application 20a, and the target program is required. A new screen definition file can be created.

  First, an example of a system configuration when the display layout information conversion technique is used will be described with reference to FIG. FIG. 2 is a diagram showing a system configuration when the display layout information conversion technique is used.

  In general, when converting a part or all of a source program described in one language into a part or all of a target program described in another language, the layout information conversion tool 900 includes a source file 901 or a source file. A binary file 902 obtained by converting 901 into an execution format is input. Then, the layout information conversion tool 900 outputs a Web application screen file 903 as a target program, for example.

  Here, in order to explain more specifically, an example in which a Java application is converted into HTML (HyperText Markup Language) will be described with reference to FIGS. FIG. 3 shows an example of a system configuration in the case of using a display layout information conversion technique when converting a Java application into HTML. FIG. 4 shows a display example of a Java application and a display example after conversion to HTML.

  The source file 901a is a program written in Java. In order to be independent of the operating system (OS) and hardware, the source file 901a is an absolute (specifically specifying the display position) of each component unit (display item) in the source file. ) Display layout information. The display layout information has relative display layout information or display layout information based on display rules by the layout manager. That is, it does not indicate a specific display position on the display device, such as center placement for text parts and right alignment for button parts, but has display layout information as a relative or display rule. Therefore, even when the Web application screen file (target file) 903a is obtained when the source file 901a is converted by the layout information conversion tool 900a, information relating to the display layout regarding the specific display position is lacking. That is, the display position of the text part is “undefined” and the display position of the button is “undefined”.

  In a window display example 910 obtained by executing the source file 901a, labels 911 and 913, text 912 and 914, and buttons 915 that are items are arranged in an orderly manner. However, in the window display example 920 obtained by executing the Web application screen file 903a, labels 921, 923, texts 922, 924, and buttons 925, which are items, are arranged in a cluttered manner. The cluttered arrangement as in the window display example 920 is due to the fact that the specific display layout information of the Web application screen file 903a is not generated in the conversion process by the layout information conversion tool 900a. In order to solve a cluttered arrangement such as the window display example 920, it is necessary to check the display contents and input specific numerical information.

  This is because when replacing the screen of an existing Java client application with a Web application, when converting the screen definition, the implementation source or the compiled asset (binary data) is used as the screen information to be converted. It depends. Even when a layout manager is used to create a screen layout for a Java application, specific display layout information (arrangement position, size) in screen item units is included in the input implementation source (or compiled asset). Because there is no information etc.), specific display layout information (arrangement position, size information, etc.) cannot be output in the output result, and the output result is shifted.

  The item arrangement function provided by the layout manager exists in the execution environment of the Java application. However, since a corresponding function does not exist in a Web application (for example, HTML or the like), it is necessary to separately create (or modify) a layout by using an HTML tag.

  Next, another example of the system configuration when the display layout information conversion technique is used will be described with reference to FIGS. 5, 6, 7, and 8. FIG. 5 is a system configuration example in the case of using a display layout information conversion technique when converting the Java application of the embodiment into HTML. FIG. 6 shows a display example of the Java application of the embodiment and a display example after conversion to HTML. FIG. 7 is an item information table of the embodiment. FIG. 8 shows an output example of the HTML file of the embodiment.

  The source application execution environment 901b is an execution environment for a program written in Java, and includes an application (Java bytecode) 904, a layout manager 905, and a virtual machine (JavaVM) 906 that compiles a program written in Java. Is done. The source application execution environment 901b has specific display layout information about the display screen under the execution status of the application 904.

  The layout information conversion tool 900b acquires specific display layout information about the display screen from the source application execution environment 901b. Specific display layout information is acquired by referring to variable information in the work area of the source application execution environment 901b. For example, the work area of the source application execution environment 901b stores variable information (for example, display position, size, font, etc.) for laying out application windows, panels, screen items and the like on the display screen. The variable information stored in these work areas can be acquired by an application such as a debugger.

  Then, the layout information conversion tool 900b generates the item information table 200 as target display layout information from the specific display layout information acquired from the source application execution environment 901b. The item information table 200 summarizes specific display layout information for a plurality of items in a table format (table). The specific display layout information of the item information table 200 includes item name 210, type 220, display position 230 (x coordinate 230a, y coordinate 230b), size 240 (width (width) 240a, vertical (height) 240b), There are a font 250 (size 250a, type 250b) and an item name (display character) 260. The item name 210 is information serving as a key of the item, and is given a name having a distinctiveness. The type 220 is information for specifying the type of component of the item. The display position 230 is information for specifying the display position of the item, and includes an x coordinate 230a and a y coordinate 230b. The size 240 is information for specifying the display size of the item, and includes a width 240a and a vertical 240b. The font 250 is information for specifying the display font of the item, and includes a size 250a and a type 250b. The item name (display character) 260 is a character displayed as the nominal name of the item. It should be noted that not all of the specific display layout information for these items is essential. For example, when the font is fixed in the target file, the font 250 may not be included. .

  The layout information conversion tool 900b uses the generated item information table 200 to obtain a Web application screen file (target file) 903b. The web application screen file 903b is, for example, an HTML file 300. The parameters in the program list in the HTML file 300 are determined with reference to the item information table 200. The layout information conversion tool 900b refers to the item information table 200 using the item name (label_a) 311 in the program list as a key, and finds the item name (label_a) 211. Then, the layout information conversion tool 900b determines the x coordinate (10) 331a and the y coordinate (10) 331b as parameters in the program list from the x coordinate (10) 231a and y coordinate (10) 231b of the display position 230. To do. Similarly, the layout information conversion tool 900b determines width (80) 341a and vertical (40) 341b as parameters in the program list from the size 240 width (80) 241a and vertical (40) 241b. Similarly, the layout information conversion tool 900b determines the size (10) 351a and the type (Gothic) 351b as parameters in the program list from the size (10) 251a and the type (Gothic) 251b of the font 250. Similarly, the layout information conversion tool 900b determines an item name (item A) 361 as a parameter in the program list from the item name (item A) 261. The unit of the display position 230 and the size 240 illustrated is a pixel, and the unit of the font size 250a is a point (pt).

  Accordingly, the Web application screen file 903a includes information relating to the display layout of the specific arrangement position and size of the display position of the text component and the display position of the button. In other words, in the window display example 910 displayed in the source application execution environment 901b, the labels 911 and 913, the texts 912 and 914, and the buttons 915 that are items are arranged in an orderly manner. In the window display example 930 obtained by executing the Web application screen file 903b, labels 931 and 933, texts 932 and 934, and buttons 935 are arranged in an orderly manner. The orderly arrangement as in the window display example 930 is because specific display layout information is acquired from the source application execution environment 901b in the conversion process by the layout information conversion tool 900b. This eliminates the need for confirming the display contents and inputting specific numerical information.

  Next, a hardware configuration example of the display layout information conversion apparatus according to the present embodiment will be described. FIG. 9 is a diagram illustrating a hardware configuration example of the display layout information conversion apparatus according to the embodiment. The entire display layout information conversion apparatus 100 is controlled by a CPU (Central Processing Unit) 101. A random access memory (RAM) 102, a hard disk drive (HDD) 103, a communication interface 104, a graphic processing device 105, and an input / output interface 106 are connected to the CPU 101 via a bus 107.

  The RAM 102 temporarily stores at least a part of an OS (Operating System) program to be executed by the CPU 101, a display layout information conversion program, and an application program executed in the source application execution environment 901b. The RAM 102 stores various data necessary for processing by the CPU 101 and various variables in the source application execution environment 901b. The HDD 103 stores an OS and application programs.

  The communication interface 104 is connected to the network 111. The communication interface 104 transmits / receives data to / from another computer via the network 111.

  A monitor 110 is connected to the graphic processing device 105. The graphic processing device 105 displays an image on the screen of the monitor 110 in accordance with a command from the CPU 101.

  A keyboard 108 and a mouse 109 are connected to the input / output interface 106. The input / output interface 106 transmits signals sent from the keyboard 108 and mouse 109 to the CPU 101 via the bus 107.

  With the hardware configuration as described above, the processing functions of this embodiment can be realized. Note that other computers connected via the network 111 can also be realized with the same hardware configuration.

Next, the layout information conversion tool of the second embodiment will be described with reference to FIG. FIG. 10 is a functional block diagram of the layout information conversion tool of the second embodiment.
The layout information conversion tool 2 includes an application conversion unit 11 and an application process 21 that are processes on a computer. The application process 21 includes an application 21a and a debugger 21b. The application 21a is executed after converting an existing application program (source program) into an execution format. The debugger 21b refers to variables (display layout information of items to be displayed) during execution of the application 21a.

  The application conversion unit 11 includes a communication unit 11a, an activation control unit 11b, a parameter designation unit 11c, an information acquisition unit 11e, an information generation unit 11f, and a target generation unit 11h. The communication unit 11a communicates with the debugger 21b. The activation control unit 11b controls the activation and execution state of the application 21a by instructing the debugger 21b via the communication unit 11a. The parameter designation unit 11c acquires the parameter designation 11d from the outside (another computer connected via the network 111, a parameter designation file, an input unit such as the keyboard 108 and the mouse 109). The parameter specification 11d includes specification of an application to be converted, file name of an HTML file to be output, storage destination, specification of a window for acquiring display layout information, and size specification of a window for acquiring display layout information. The activation control unit 11b instructs the debugger 21b to activate the application 21a and control the execution state based on the parameter designation 11d. The information acquisition unit 11e acquires a variable during execution of the application 21a from the debugger 21b via the communication unit 11a. The information generation unit 11f generates the target display layout information 11g based on the variable being executed by the application 21a acquired by the information acquisition unit 11e. The target display layout information 11g is generated in a table format like the item information table 200, for example. The target generation unit 11h generates the target file 11i using the target display layout information 11g.

  In this way, the display layout information (item name, type, display position, size, font, value, etc.) of the item is acquired from the dynamically changing display during execution of the application 21a, and the target file 11i is acquired. Can be created.

  Note that the application conversion unit 11 implements various functions of the application conversion unit 11 by executing a display layout information conversion program on a computer.

  Next, the flow of processing in the application conversion unit 11 of the second embodiment will be described with reference to FIG. FIG. 11 is a main flowchart of the application conversion unit of the second embodiment. Here, a case where an HTML file is output from the display contents of the target application will be described.

  [Step S11] The application conversion unit 11 receives the designation of the target application by the parameter designation unit 11c. At this time, the parameter designation 11d designates the file name and file path of the target application. The reception of the parameter specification 11d including the specification of the target application may be performed by parameter specification at startup.

[Step S12] The application conversion unit 11 activates the application 21a designated as the target application by the activation control unit 11b.
[Step S13] The application conversion unit 11 causes the application 21a to display a screen from which the display layout information is acquired by the activation control unit 11b. Then, the activation control unit 11b adjusts the window size displayed on the screen to the window size displayed on the screen based on the HTML file. This operation is executed based on the parameter designation 11d. Here, the parameter designation 11d by the parameter designation unit 11c can be obtained based on a preset display setting of the screen. For example, the parameter designation 11d can be acquired sequentially by listing the screen to be displayed, the window type, size, and display timing. Further, input of parameter designation 11d may be received from input means such as the keyboard 108 and the mouse 109.

  [Step S14] The application conversion unit 11 determines a screen (window) displayed by the application 21a as a display layout information conversion target by the activation control unit 11b. At the same time, the application conversion unit 11 accepts designation of the file name and file path of the HTML file by the parameter designation unit 11c. The file name may be automatically generated according to a predetermined rule.

  [Step S15] The application conversion unit 11 acquires display layout information of a screen (window) displayed by the application 21a from the debugger 21b via the communication unit 11a by the information acquisition unit 11e. And the application conversion part 11 produces | generates the display layout information 11g for targets (for example, item information table 200) by the information generation means 11f, and adds the acquired display layout information.

  [Step S16] The application conversion unit 11 generates and outputs an HTML file (target file 11i) by using the target display layout information 11g by the target generation unit 11h.

  [Step S17] The application conversion unit 11 determines whether conversion has been completed for all screens. If the conversion has not been completed for all screens, the application conversion unit 11 proceeds to step S13. If the conversion has been completed for all screens, the application conversion unit 11 ends the process.

  Execution of the display layout information conversion program may be terminated upon completion of the processing. Further, the activated application 21a and debugger 21b may be terminated.

  Next, the detailed process flow of the screen information acquisition process (step S15) of the second embodiment will be described with reference to FIG. FIG. 12 is a flowchart of screen information acquisition processing according to the second embodiment.

  [Step S21] The information acquisition unit 11e connects to the application process 21. Specifically, the interface of the debugger 21b is accessed via the communication means 11a, and the work area of the application process 21 is made accessible.

  [Step S22] The information acquisition unit 11e acquires items (label, button, text, etc.) constituting the screen (window) displayed by the application 21a. Details will be described later with reference to a specific example using FIG.

  [Step S23] The information acquisition unit 11e determines whether or not display layout information of all items has been acquired. If not, the information acquisition unit 11e proceeds to step S24. If it has been acquired, the information acquisition unit 11e proceeds to step S26.

  [Step S24] The information acquisition unit 11e collects specific display layout information for one item in a table format (table). For example, for one item, item name 210, type 220, display position 230 (x coordinate 230a, y coordinate 230b), size 240 (width (width) 240a, vertical (height) 240b), font 250 (size 250a, Type 250b) and item name (display character) 260 are acquired.

  [Step S25] The information generating unit 11f creates an item information table 200 (target display layout information 11g) from specific display layout information for one item acquired by the information acquiring unit 11e. In the item information table 200, one line of data is added each time specific display layout information for one item is acquired.

[Step S26] The information generating unit 11f outputs the item information table 200 and makes it available to the target generating unit 11h.
Through the above processing, the display layout information of each item constituting the screen (window) displayed by the application 21a is collected as the item information table 200 and can be used by the target generation unit 11h.

  Next, a detailed processing flow of the HTML file output processing (step S16) according to the second embodiment will be described with reference to FIGS. FIG. 13 is a flowchart of HTML file output processing according to the second embodiment. FIG. 14 is a diagram illustrating an example of an HTML tag conversion rule according to the second embodiment. FIG. 15 is a diagram illustrating an example of an HTML tag conversion rule according to the second embodiment. FIG. 16 is a diagram illustrating an example of generating an item information table according to the second embodiment. FIG. 17 is a diagram illustrating an output example of an HTML file according to the second embodiment.

[Step S31] The target generation unit 11h opens an HTML file for output with the file name and file path specified with reference to the parameter specification 11d.
[Step S32] The target generation unit 11h determines whether or not the processing has been completed for all the data (items) in the generated item display table. If completed, the process proceeds to step S35 and must be completed. If so, the process proceeds to step S33. Here, it is assumed that the item information table 201 (FIG. 16) has been generated. There are two items, label_a212 and txt_a213.

[Step S33] The target generation unit 11h converts data of one record (one line) into an HTML tag for one item in the item information table 201.
Here, the target generation unit 11h prepares a conversion rule for each item type when converting data of one record into an HTML tag. Conversion rules are prepared in the form of HTML templates to be output. The target generation unit 11h can generate an HTML tag by applying the acquired data of one record to a corresponding template. For example, for label_a 212, since the type 220 is the label 222, the label conversion rule 400 is applied. By replacing the part described by “$ {}” in the conversion rule with the data in the item information table 201, a target HTML tag can be generated.

  For example, the target generation unit 11h replaces “$ {English item name}” 411 of the label conversion rule 400 with label_a212. Similarly, the target generation unit 11h sets the “$ {display position−x}” 431a and “$ {display position−y}” 431b of the label conversion rule 400 to the x coordinate (10) 232a and the y coordinate (10). Replace with 232b. Similarly, the target generation unit 11h replaces “$ {size-width}” 441a and “$ {size-height}” 441b of the label conversion rule 400 with width (80) 242a and vertical (40) 242b. To do. Similarly, the target generation unit 11h replaces “$ {font-type}” 451b and “$ {font-size}” 451a of the label conversion rule 400 with the type (gothic) 252b and size (10) 252a. . Similarly, the target generation unit 11 h replaces “$ {display character}” 461 of the label conversion rule 400 with the value (user ID) 262.

  For another item, txt_a 213, since the type 220 is text 223, the label conversion rule 401 is applied. In this case, the target generation unit 11 h replaces “$ {English item name}” 412 of the label conversion rule 401 with txt_a 213. Similarly, the target generation unit 11h converts “$ {display position−x}” 432a and “$ {display position−y}” 432b of the label conversion rule 401 into the x coordinate (100) 233a and the y coordinate (10). Replace with 233b. Similarly, the target generation unit 11h replaces “$ {size-width}” 442a and “$ {size-height}” 442b of the label conversion rule 401 with width (280) 243a and vertical (40) 243b. To do. Similarly, the target generation unit 11h replaces “$ {font-type}” 452b and “$ {font-size}” 452a of the label conversion rule 401 with the type (gothic) 253b and the size (10) 253a. . Similarly, the target generation unit 11 h replaces “$ {display character}” 462 of the label conversion rule 401 with the value (123456) 263.

  [Step S34] The target generation unit 11h outputs the converted HTML tag information to an open HTML file. For example, the HTML tag information corresponding to label_a212 is output as the HTML tag 501 to the HTML file 500 by the target generation unit 11h. Similarly, HTML tag information corresponding to txt_a 213 is output as an HTML tag 502 to the HTML file 500 by the target generation unit 11h.

[Step S35] The target generation unit 11h closes the HTML file 500 and ends the process.
Next, acquisition of screen information being displayed in step S22 will be described with a specific example. FIG. 18 is a diagram illustrating an example of acquiring display layout information according to the second embodiment.

  The display screen 600 is displayed by executing the application 21a. The selection of the display screen and the selection of the window size are instructed from the activation control unit 11b to the application 21a via the communication unit 11a and the debugger 21b based on the parameter designation 11d received by the parameter designation unit 11c. Display layout information related to the display screen 600 is acquired from the work area (for example, on the RAM 102) of the application 21a by the debugger 21b. The display screen 600 includes a plurality of items (an application window 601, a panel 602, a screen item 603, and a screen item 604). For each of these items, display layout information is stored in the work area of the application 21a. By reading the display layout information stored in the work area of the application 21a with the debugger 21b, it is possible to grasp specific display layout information for each item.

  For example, the application window 610 that is a storage area corresponding to the display of the application window 601 includes “600 px” as the height information 611, “400 px” as the width information 612, “xxx system” as the title information 613, and display panel information 614. “(Panel)” is stored.

  The panel 620, which is a storage area corresponding to the display of the panel 602, has “0 px” as the start position (x) 621, “0 px” as the start position (y) 622, “displaying” as the display presence / absence 623, and the screen item 624. “(Component) × n” is stored.

  The screen item 630 that is a storage area corresponding to the display of the screen item 603 includes “label” as the type 631, “label_a” as the item name 632, “10 px” as the start position (x) 633, and the start position (y) 634. “10 px” is stored, and “item A” is stored as the display character 635.

  The screen item 640 which is a storage area corresponding to the display of the screen item 604 includes “text” as the type 641, “txt_a” as the item name 642, “100 px” as the start position (x) 643, and start position (y) 644. “10 px” is stored as the display character 645 and “123456” is stored as the display character 645.

  The display panel information 614 “(panel)” is link information to the panel 620 which is a storage area corresponding to the display of the panel 602. Similarly, by following the link information for “(Component)” and “n”, the activation control unit 11b can instruct access to the necessary screen item being displayed. The information acquisition unit 11e can acquire necessary display layout information.

  Next, since the value of the memory stored in the work area changes in conjunction with the change of the window size, an example in which a plurality of display layout information is acquired by changing the window size for one screen will be described. FIG. 19 is a diagram illustrating an example of obtaining display layout information in the window size according to the second embodiment. FIG. 20 is a diagram illustrating an example of acquiring display layout information in another window size according to the second embodiment.

  For example, the display screen 700 includes a screen item 701. The screen item 710 which is a storage area corresponding to the display of the screen item 701 includes “text” as the type 711, “txt_a” as the item name 712, “100 px” as the start position (x) 713, and the start position (y) 714. “10 px”, “200 px” as the width 715, “40 px” as the height 716, and “123456” as the display character 717 are stored.

  Then, a display screen 720 is displayed by the application 21a by designating a different window size by the parameter designation 11d received by the parameter designation unit 11c. Although the window size is enlarged and changed here, it is possible to change it to reduce it, or to change it to enlarge or reduce it with a different aspect ratio.

  The display screen 720 includes a screen item 721. By expanding the window size, the screen item 730 which is a storage area corresponding to the display of the screen item 721 includes “text” as the type 731, “txt_a” as the item name 732, “100 px” as the start position (x) 733, “10 px” is stored as the start position (y) 734, “200 px” is stored as the width 735, “40 px” is stored as the height 736, and “123456” is stored as the display character 737.

  This makes it easy to obtain display layout information corresponding to the size of each monitor, even if the size of the monitor differs between desktop computers, notebook computers, mobile phones, and other portable devices. Become.

  Although the source file is described as a program described in the Java language, the present invention is not limited to this. It is effective to apply to a source file in which specific information on the display screen is not included in the source file and specific information is determined in the execution environment. Further, even when specific information on the display screen is included in the source file, application to a source file that can change specific information in the execution environment is also effective.

  Although the target file has been described as HTML, the present invention is not limited to this. In particular, when data conversion is performed focusing on tags, it is suitable for markup languages such as SGML (Standard Generalized Markup Language) and TeX described using tags.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the function that the layout information conversion tool should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of the computer-readable recording medium include a magnetic recording device, an optical disk, a magneto-optical recording medium, and a semiconductor memory. Examples of the magnetic recording device include a hard disk device (HDD), a flexible disk (FD), and a magnetic tape. Optical discs include DVD (Digital Versatile Disc), DVD-RAM, CD-ROM, CD-R (Recordable) / RW (ReWritable), and the like. Magneto-optical recording media include MO (Magneto-Optical disk).

  When distributing the program, for example, portable recording media such as a DVD and a CD-ROM in which the program is recorded are sold. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

The above-described embodiment can be variously modified within a range not departing from the gist of the embodiment.
Further, the above-described embodiments can be modified and changed in many ways by those skilled in the art, and are not limited to the exact configurations and application examples described.

DESCRIPTION OF SYMBOLS 1 Layout information conversion tool 10 Application conversion part 10a Information acquisition means 10b Information generation means 10c Display layout information for targets 20 Application process 20a Application 20b Debugger

Claims (9)

In a display layout information conversion program for converting display layout information of a source file described in one language into display layout information of a target file described in another language,
Computer
Information acquisition means for acquiring display layout information of items to be displayed from an application executed based on the source file;
Information generating means for generating target display layout information of the item displayed by the target file from the display layout information acquired by the information acquiring means;
A display layout information conversion program characterized in that it functions as a display layout information. Computer
Furthermore, target generation means for generating a target file including the target display layout information generated by the information generation means,
The display layout information conversion program according to claim 1, wherein In a display layout information conversion program for converting display layout information of a source file described in one language into display layout information of a target file described in another language,
Computer
Start control means for controlling start of an application executed based on the source file;
A communication means for communicating with the application;
Information acquisition means for acquiring display layout information of items displayed by the application by the communication;
Information generating means for generating target display layout information of the item displayed by the target file from the display layout information acquired by the information acquiring means;
A display layout information conversion program characterized in that it functions as a display layout information. Computer
Furthermore, target generation means for generating a target file including the target display layout information generated by the information generation means,
4. The display layout information conversion program according to claim 3, wherein The display layout information of the source file described in the one language is information on a relative positional relationship of display objects in the display area or an arrangement rule of display objects.
The display layout information of the target file described in the other language is information on the absolute positional relationship of the display target in the display area,
5. The display layout information conversion program according to claim 4. Computer
Further, parameter specifying means for specifying a window including the item displayed by the application,
6. The display layout information conversion program according to claim 5, wherein the display layout information conversion program is made to function as: Computer
Further, parameter specifying means for specifying the size of the window including the item displayed by the application,
6. The display layout information conversion program according to claim 5, wherein the display layout information conversion program is made to function as: The parameter specifying means includes
Specify a plurality of different sizes for one window containing the item displayed by the application,
8. The display layout information conversion program according to claim 7, wherein the information acquisition unit acquires display layout information for a plurality of different sizes for the one window. A display layout information conversion method for converting display layout information of a source file described in one language into display layout information of a target file described in another language by a computer,
Controlling the launch of an application executed based on the source file;
Through communication with the activated application, obtain display layout information of items displayed by the application,
A display layout information conversion method for generating target display layout information of the item displayed by the target file from the acquired display layout information.

Images