Embedded program, screen display program, and screen display method

The embedded program addresses the challenge of linking information between web applications by detecting events and integrating with the parent program, facilitating real-time interaction without source code modifications, suitable for third-party and cloud systems.

JP2024158043AActive Publication Date: 2024-11-08MITSUBISHI ELECTRIC DIGITAL INNOVATION CORP
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023072879
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-04-27
Publication Date
2024-11-08
Estimated Expiration
2043-04-27

AI Technical Summary

Technical Problem

Existing methods for linking information between web application programs, such as using APIs, CSV formats, and inline frames, struggle with real-time information linkage and require significant modifications to the source code, especially when dealing with third-party or cloud-based applications.

Method used

An embedded program is called from a parent web application program, detecting specified events to link information between the two, allowing for real-time interaction without modifying the parent program's source code.

Benefits of technology

The embedded program can detect events and link information with the parent program, reducing the need for source code modifications and enabling seamless integration, even with third-party or cloud-based applications, while avoiding security risks and testing complexities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024158043000001_ABST
    Figure 2024158043000001_ABST
Patent Text Reader

Abstract

To realize information sharing linked to screen movements or the like between existing web application programs while reducing modifications to source codes of existing web application programs.SOLUTION: An embedded program 20 is a web application program that is called from a parent program 10, which is a web application program that displays a parent screen 11 on the browser 30, and is different from the parent program 10. The embedded program 20 detects a specified event that occurs in the browser 30. When the specified event is detected, information sharing is performed between the parent program 10 and the embedded program 20, by the embedded program 20.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a technique for linking information between web application programs. [Background technology]

[0002] There are cases where functions need to be added to an existing web application program. In this case, modifications can be made to the source code of the existing web application program. However, modifying the source code of an existing web application program can be difficult. For example, if the existing web application program is a product of another company, modifications can be difficult because the detailed specifications of the existing web application program cannot be understood. Also, if the existing web application program is a cloud system, free modifications are not permitted, and modifications can be difficult. When it is difficult to modify the source code of an existing web application program, a possible method is to create a separate web application program that realizes the additional functions and link information between the separate web application program and the existing web application program.

[0003] There are three methods for sharing information between web application programs: using API to transfer information, inputting and outputting files in CSV format, and using inline frames. API stands for Application Programming Interface. CSV stands for Comma-Separated It is an abbreviation for Values. Patent Document 1 describes a technology that uses inline frames. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2023-26702 Summary of the Invention [Problem to be solved by the invention]

[0005] With the method of transferring information using an API and the method of inputting and outputting files in a format such as CSV, it is difficult to realize processing linked to the movement of the screen displayed in a web application program. Therefore, it is not suitable for realizing two-way information sharing between web application programs linked to the movement of the screen, or information sharing in real time.

[0006] The method using inline frames makes it possible to realize processing linked to screen movements. However, the method using inline frames requires that the program structures of the link source and link destination be taken into consideration, and that the link source and destination are tightly coupled in implementation.

[0007] The present disclosure aims to make it possible to realize information linkage with screen movements, etc., between existing web application programs while reducing modifications to the source code of existing web application programs. [Means for solving the problem]

[0008] The embedding program according to the present disclosure comprises: an embedded program which is a web application program different from a parent program that displays a parent screen on a browser and is called from the parent program, an event detection process for detecting a specified event occurring in the browser; an information linking process for linking information between the parent program and the embedded program when the designated event is detected by the event detection process; to be executed by the computer. Effect of the Invention

[0009] In the present disclosure, the embedded program is called and executed by the parent program. As a result, when viewed from the browser, the embedded program becomes a program that constitutes one web screen together with the parent program. This makes it possible for the embedded program to detect a designated event in the browser that displays the parent screen and to link information between the parent program and the embedded program. As a result, information linkage becomes possible simply by writing a process for calling the embedded program in the parent program. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a configuration diagram of a screen display system 100 according to a first embodiment. [Diagram 2] FIG. 2 is an explanatory diagram of a web screen according to the first embodiment. [Diagram 3] FIG. 2 is an explanatory diagram of the hardware configuration of a first server 101, a second server 102, and a user terminal 103 according to the first embodiment. [Figure 4] 4 is a flowchart showing an outline of the operation of the screen display system 100 according to the first embodiment. [Diagram 5] 4 is a flowchart showing a detailed operation of the screen display system 100 according to the first embodiment. [Figure 6] 4 is a flowchart showing a detailed operation of the screen display system 100 according to the first embodiment. [Figure 7] 3 is an explanatory diagram of a method for adding a function to a parent program 10 using an embedding program 20 according to the first embodiment. [Figure 8] 3 is an explanatory diagram of a method for adding a function to a parent program 10 using an embedding program 20 according to the first embodiment. [Figure 9] FIG. 11 is a configuration diagram of a screen display system 100 according to a second modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Embodiment 1 ***Configuration Description*** The configuration of a screen display system 100 according to the first embodiment will be described with reference to FIG. The screen display system 100 includes a first server 101, a second server 102, and a user terminal 103. The first server 101, the second server 102, and the user terminal 103 are connected via a network 109 such as the Internet.

[0012] A parent program 10, which is a web application program, is stored in the first server 101. An embedded program 20, which is a web application program different from the parent program, is stored in the second server 102.

[0013] The user terminal 103 includes a browser 30 for web browsing. The user terminal 103 accesses the first server 101 via the browser 30, and acquires and executes the parent program 10. As a result, the parent program 10 renders a parent screen 11 on the browser 30 included in the user terminal 103, as shown in FIG. 2. The parent program 10 also calls and executes the embedded program 20 stored in the second server 102. As a result, an embedded screen 21 is rendered as a part of the parent screen 11, as shown in FIG. 2.

[0014] With reference to FIG. 3, the hardware configurations of first server 101, second server 102, and user terminal 103 according to the first embodiment will be described. The first server 101, the second server 102, and the user terminal 103 are computers. The first server 101, the second server 102, and the user terminal 103 each include the following hardware: a processor 201, a memory 202, a storage 203, and a communication interface 204. The processor 201 is connected to other hardware via signal lines and controls the other hardware.

[0015] The processor 201 is an integrated circuit (IC) that performs processing. The abbreviation stands for Circuit. Specific examples of the processor 201 include a CPU, a DSP, and a GPU. CPU stands for Central Processing Unit. DSP stands for Digital Signal Processor. GPU stands for Graphics Processing Unit.

[0016] The memory 202 is a storage device that temporarily stores information. Specific examples of the memory 202 include SRAM and DRAM. SRAM is an abbreviation for Static Random Access Memory. DRAM is an abbreviation for Dynamic Random Access Memory.

[0017] Storage 203 is a storage device that stores information. A specific example of storage 203 is a HDD. HDD is an abbreviation for Hard Disk Drive. Storage 203 may also be a portable recording medium such as an SD (registered trademark) memory card, CompactFlash (registered trademark), NAND flash, a flexible disk, an optical disk, a compact disk, a Blu-ray (registered trademark) disk, or a DVD. SD is an abbreviation for Secure Digital. DVD is an abbreviation for Digital Versatile Disk.

[0018] The communication interface 204 is an interface for communicating with an external device. Specific examples of the communication interface 204 include Ethernet (registered trademark), USB, and HDMI (registered trademark) ports. USB is an abbreviation for Universal Serial Bus. HDMI is an abbreviation for High-Definition Multimedia Interface.

[0019] ***Explanation of Operation*** The operation of the screen display system 100 according to the first embodiment will be described with reference to FIGS. The operation procedure of the screen display system 100 according to the embodiment 1 corresponds to the screen display method according to the embodiment 1. Moreover, the parent program and the embedded program that realize the operation of the screen display system 100 according to the embodiment 1 correspond to the screen display program according to the embodiment 1.

[0020] An outline of the operation of the screen display system 100 according to the first embodiment will be described with reference to FIG. (Step S1: Parent drawing process) The user terminal 103 accesses the first server 101 via the browser 30, and acquires and executes the parent program 10. This starts the parent program 10 in the browser 30. The parent program 10 renders a parent screen 11 on the browser 30. The parent program 10 also executes a call process to call the embedded program 20.

[0021] (Step S2: Embedded drawing process) The embedded program 20 called in step S1 is started in the browser 30. The embedded program 20 draws the embedded screen 21 as a part of the parent screen 11. The embedded program 20 also hooks a designated event of the browser 30. The designated event is set in the application information or initial information as described later, and indicates an event caused by a user's key operation, mouse operation, or the like on the parent screen 11 or the embedded screen 21. Hooking a designated event means designating that the occurrence of the designated event should be notified to the embedded program 20, and details will be described later.

[0022] 2, a web screen on which the embedded screen 21 is drawn is displayed as a part of the parent screen 11. The user performs operations on this web screen. For example, the user may move the cursor on the web screen, change the size of the browser 30, input data into a text box on the parent screen 11, or press a button on the embedded screen 21.

[0023] (Step S3: Event detection process) The embedding program 20 detects a designated event that has occurred in the browser 30. If the embedded program 20 detects a designated event, the embedding program 20 advances the process to step S4. On the other hand, if the embedded program 20 does not detect a designated event, the embedding program 20 returns the process to step S3.

[0024] (Step S4: Information linkage processing) The embedding program 20 coordinates information between the parent program 10 and the embedding program 20 . As a specific example, the embedded program 20 acquires information managed by the parent program 10 and executes processing according to the designated event using the acquired information. The embedded program 20 may execute processing to update information displayed on the embedded screen 21 based on the acquired information. As another specific example, the embedded program 20 passes information managed by the embedded program 20 to the parent program 10 and sets it in the parent screen 11. Here, the linkage of information between the parent program 10 and the embedded program 20 includes passing information managed by the parent program 10 shown as a specific example to the embedded program 20, and indicates the passing of information regarding input values ​​or display values ​​in response to the user's screen operations on the parent screen 11 or embedded screen 21, information regarding display values ​​based on the results of processing in the parent program 10 or embedded program 20, etc. between the parent program 10 and the embedded program 20.

[0025] The user performs an operation on the web screen, and the processes from step S3 to step S4 are repeatedly executed, whereby the parent program 10 and the embedded program 20 execute the processes while exchanging information with each other.

[0026] The detailed operation of the screen display system 100 according to the first embodiment will be described with reference to FIGS. First, the parent program 10 runs on the browser 30. The processes from step S11 to step S13 correspond to the process of step S1 in FIG.

[0027] As a specific example, the parent program 10 is written in HTML, and the embedded program 20 is written in JavaScript. HTML is an abbreviation for HyperText Markup Language. By accessing the first server 101, an HTML program constituting the parent program 10 is read into the browser 30 (step S11). This starts the parent program 10 in the browser 30. The parent program 10 displays a parent screen 11 on the browser 30. The parent program 10 calls the embedded program 20 (step S12). Specifically, the HTML program describes a script tag that specifies an engine js file that constitutes the embedded program 20. When this script tag is executed, the engine js file of the embedded program 20 is read from the second server 102. The browser 30 starts the engine js (step S13). Here, it is assumed that the engine js has an execution command written at the end. Therefore, the browser 30 starts the loaded engine js.

[0028] By executing the engine js, the subject of operation is shifted to the embedding program 20. The processes from step S21 to step S29 correspond to the process of step S2 in FIG.

[0029] Since the engine js does not have information about the process to be executed, the embedded program 20 inquires of the second server 102 about the process to be executed (step S21). The second server 102 then reads the startup.json file to be executed initially, and transmits the startup.json file to the browser 30 as application information (step S22). The startup.json file indicates information about the execution module and an initialization method. The embedded program 20 instructs the second server 102 to execute an initialization method of the execution module indicated in the startup.json file, which is application information (step S23). The second server 102 calls the initialization method of the execution module (step S24). Then, the initialization method of the execution module is executed, and the design file and information for initially displaying a web screen on which the embedded screen 21 is drawn as a part of the parent screen 11 are returned to the browser 30 (step S25). Here, application information refers to information that defines the information necessary for the operation of an application. Also, a design file refers to a file that defines the design information of the embedded screen 21. The area in which drawing can be done using JavaScript is called a Canvas, and a design file is a file that defines the information of the screen design to be drawn on the Canvas, specifically including information such as the button coordinates, size, and character string to be displayed. The embedding program 20 embeds a Canvas tag in the parent program 10 based on the design file (step S26). As a result, the embedded screen 21 indicated by the Canvas tag is drawn as a part of the parent screen 11 (step S27). The embedding program 20 hooks a designated event of the browser 30 (step S28). The designated event is set in the application information or initial information. The designated event is an event such as inputting into a text box in the parent screen 11 or pressing a button in the embedded screen 21. The embedded program 20 reads the screen component js file and the individual event js file indicated in any one of the application information, the design information, and the initial information from the second server 102 (step S29). The screen component js file is a program for changing the embedded screen 21. The individual event js file is a program for information linkage between the parent program 10 and the embedded program 20.

[0030] Through the above processing, as shown in Fig. 2, a web screen on which the embedded screen 21 is drawn is displayed as a part of the parent screen 11. In other words, the web screen on which the embedded screen 21 is drawn is displayed in the Canvas area of ​​the parent screen 11. The user performs operations on this web screen. For example, the user moves the cursor, inputs keys on the keyboard, changes the screen size, starts a timer, and the like. When the user performs an operation, the processing from step S31 onwards is executed. The processes from step S31 to step S32 correspond to the process of step S3 in Fig. 4. The processes from step S41 to step S47 correspond to the process of step S4 in Fig. 4.

[0031] The embedded program 20 detects an event that occurs in the browser 30 (step S31). As mentioned above, in the Canvas, which is an area where drawing can be done using JavaScript, normally only operations such as whether or not the mouse has moved on the Canvas can be detected. However, by creating the embedded screen 21 using the embedded program 20, it becomes possible to detect mouse operations or keyboard operations on buttons on the Canvas as events occurring in the browser 30. If the detected event is an event that requires redrawing of the embedded screen 21, the embedded program 20 calls and executes the drawing process of the screen component js file (step S32). As a result, the embedded screen 21 is redrawn in response to the event. An event that requires redrawing of the embedded screen 21 is, for example, an event in which the cursor is placed on a button on the embedded screen 21 or the screen size of the browser 30 is changed. For example, when the cursor is placed on a button on the embedded screen 21, the embedded program 20 changes the color of the button. Also, when the screen size of the browser 30 is changed, the embedded program 20 changes the size of the embedded screen 21. If the detected event is a specified event, the embedding program 20 advances the process to step S41.

[0032] The embedding program 20 generates a signal corresponding to the detected designated event (step S41). The signal is an event in the embedding program 20. The embedding program 20 determines whether or not there is an event method corresponding to the signal (step S42). If there is an event method, the embedding program 20 instructs the second server 102 to execute the event method (step S43). On the other hand, if there is no event method, the embedding program 20 returns the process to step S31. When execution of the event method is instructed, the second server 102 calls the corresponding event method of the execution module (step S44). Then, the corresponding event method of the execution module is executed (step S45). Then, the embedded program 20 performs processing such as setting a value in the parent screen 11 or redrawing the embedded screen 21 according to the execution result of the event method (step S46). Note that, depending on the event method, the processing of step S46 may be skipped. Then, the process returns to step S31. A signal indicates, when a designated event is detected, information that the designated event has been detected. An event method corresponding to a signal defines the processing content in the second server 102 according to the designated event. Information as to whether or not there is an event method corresponding to a signal is assumed to be linked between the second server 102 and the embedded program 20.

[0033] A method of adding a function to the parent program 10 using the embedded program 20 according to the first embodiment will be described with reference to Figures 7 and 8. For comparison, Figures 7 and 8 also show a case where a function is added to the parent program 10 using a method that uses an inline frame.

[0034] FIG. 7 shows an example in which a function for transferring information entered in a text box on the parent screen 11 to the embedding program 20 is added. When adding this function using the method in the first embodiment, a script tag that calls the embedded program 20 is added to the parent program 10. On the embedded program 20 side, input of information into a text box on the parent screen 11 is set as a specified event, and a process for acquiring information when the specified event is detected is written. On the other hand, when adding this function using an inline frame, the parent program 10 is written to postMessage the entered information when it is entered into a text box on the parent screen 11. postMessage is communication between windows within a browser. The embedded program 20 is written to obtain the information when a message waiting event (onMessage) is received and the URL of the message sender is the parent program 10. URL is an abbreviation for Uniform Resource Locator.

[0035] FIG. 8 shows an example in which a function is added to set information in the embedded program 20 in a text box on the parent screen 11 when a button on the embedded screen 21 is pressed. When adding this function using the method in the first embodiment, a script tag that calls the embedded program 20 is added to the parent program 10. Pressing a button on the embedded screen 21 is set as a specified event on the embedded program 20 side, and a process is written for setting information in the embedded program 20 in a text box on the parent screen 11 when the specified event is detected. Note that since the parent screen 11 and the embedded screen 21 are the same web screen, no special process is required, and the information in the embedded program 20 may simply be set in the text box on the parent screen 11. On the other hand, when adding this function using an inline frame, the parent program 10 is written with a process for obtaining information and setting it in a text box on the parent screen 11 when a message waiting event (onMessage) is received and the URL of the message sender is the embedded program 20. The embedded program 20 is written to postMessage the entered information when a button on the embedded screen 21 is pressed.

[0036] ***Advantages of the First Embodiment*** As described above, in the screen display system 100 according to the first embodiment, the embedded program 20 is called and executed by the parent program 10. As a result, when viewed from the browser 30, the embedded program 20 and the parent program 10 become a program that constitutes one web screen. This makes it possible for the embedded program 20 to detect a designated event in the browser 30 that displays the parent screen 11, and for information to be linked between the parent program 10 and the embedded program 20. As a result, information linkage becomes possible simply by writing in the parent program 10 the process of calling the embedded program 20.

[0037] 7 and 8, in principle, all that is required is to add a script tag that calls the embedded program 20 to the parent program 10. Therefore, even if the parent program 10 is a product of another company and the specifications of the parent program 10 are unknown, work on the parent program 10 can be easily performed. Also, even if the parent program 10 is a cloud system, work on the parent program 10 can be easily performed by only permitting the addition of a script tag. In contrast, the method using an inline frame requires that the structures of the programs of the link destination and the link source be taken into consideration, and that the link destination and the link source be tightly coupled in implementation. In other words, it is necessary to understand the specifications of the parent program 10 as well before making modifications. Therefore, if the parent program 10 is a product of another company and the specifications of the parent program 10 are unknown, it is difficult to perform work on the parent program 10. Also, if the parent program 10 is a cloud system, it is difficult to give permission to perform work, and it is difficult to perform work on the parent program 10.

[0038] By utilizing such features, any function can be added to a web application program that is a product of another company. Also, any function can be added to an old web application program that is no longer supported. Also, by implementing a web application program with basic functions as a cloud system and creating and linking embedded programs 20 for each destination, the cloud system can be customized.

[0039] In the screen display system 100 according to the first embodiment, as described above, it is sufficient to simply add a script tag to the parent program 10. Therefore, even if a function is added by the embedding program 20, it is sufficient to test only the part of the parent program 10 related to the embedding program 20. Therefore, it is possible to reduce the number of testing steps required for adding a function.

[0040] Furthermore, in the method using an inline frame, there is a restriction of the same origin policy, and if the first server 101 and the second server 102 are not in the same domain, restrictions are imposed on the acquisition and operation of information. However, in the screen display system 100 according to the first embodiment, when viewed from the browser 30, the embedded program 20 becomes a program that configures one web screen together with the parent program 10. Therefore, there are no restrictions on information acquisition and information operation, as in the method using an inline frame.

[0041] Furthermore, in the method using an inline frame, there is a risk that linked information may be intercepted by other web application programs. Specifically, in the example of Fig. 7, when information is entered into a text box on parent screen 11, parent program 10 posts the entered information as a message. At this time, the posted information can be obtained from any window displayed on parent screen 11. Therefore, if a malicious window is displayed, there is a risk that the information may be obtained. However, in the screen display system 100 according to the first embodiment, there is no risk of information being obtained from other windows.

[0042] ***Other configurations*** <Variation 1> In the first embodiment, the embedded screen 21 is drawn as a part of the parent screen 11. However, the embedded screen 21 does not have to be drawn. In this case, the embedded program 20 is a program that performs processing using information of the parent program 10 without displaying information on the parent screen 11. For example, the embedded program 20 is a program that edits and records information input to the parent program 10.

[0043] <Variation 2> In the first embodiment, the user terminal 103 having the browser 30 that executes the parent program 10 and the second server 102 that stores the embedded program 20 are separate devices. However, as shown in Fig. 9, the embedded program 20 may be stored in the user terminal 103 having the browser 30 that executes the parent program 10. In this case, the embedded program 20 can obtain information on the device 104 connected to the user terminal 103. Specific examples of the device 104 include an IC card reader and a camera. For example, the embedded program 20 can obtain information on the device 104 and set the information on the parent screen 11. This makes it possible to perform processing in which the parent program 10 and the device 104, which is a local device, cooperate with each other in information.

[0044] <Variation 3> In the first embodiment, there is only one embedding program 20. However, the parent program 10 may call multiple embedding programs 20. This makes it possible to add multiple functions to the parent program 10. Also, it may be possible to select, on the parent screen 11, which of the multiple embedding programs 20 is to be linked to the parent program 10. This makes it possible for the user to select the function to be added.

[0045] Various aspects of the present disclosure are summarized below as appendices. (Appendix 1) an embedded program which is a web application program different from a parent program that displays a parent screen on a browser and is called from the parent program, an event detection process for detecting a specified event occurring in the browser; an information linking process for linking information between the parent program and the embedded program when the designated event is detected by the event detection process; An embedded program that causes a computer to execute the above. (Appendix 2) In the information linking process, information managed by the parent program is acquired, and a process corresponding to the specified event is executed using the acquired information. Attachment 1, an embedding program. (Appendix 3) The embedding program further comprises: an embedded drawing process for drawing an embedded screen as a part of the parent screen; on the computer, In the information linking process, a process of updating the embedded screen is executed based on the acquired information. Attachment 2, an embedding program. (Appendix 4) In the information linking process, information managed by the embedded program is set on the parent screen. 4. An embedding program according to any one of claims 1 to 3. (Appendix 5) In the information linking process, information acquired from a device connected to a computer in which the embedding program is installed is set on the parent screen. Attachment 4. An embedding program according to claim 4. (Appendix 6) The embedded program is located on a different computer than the parent program. 6. An embedding program according to any one of claims 1 to 5. (Appendix 7) a screen display program having a parent program which is a web application program and an embedded program which is a web application program different from the parent program, The parent program is A parent drawing process that displays the parent screen in the browser; a calling process for calling the embedded program; Run the following on your computer: The embedding program comprises: an event detection process for detecting a specified event occurring in the browser; an information linking process for linking information between the parent program and the embedded program when the designated event is detected by the event detection process; A screen display program that causes a computer to execute the following. (Appendix 8) The parent program, which is a web application program, displays the parent screen in the browser, the parent program calls an embedded program that is a web application program different from the parent program; The embedded program detects a specified event that has occurred in the browser; A screen display method, wherein the embedded program links information between the parent program and the embedded program when the specified event is detected.

[0046] The above describes the embodiments and modifications of the present disclosure. Some of these embodiments and modifications may be combined and implemented. Also, one or some of them may be partially implemented. Note that the present disclosure is not limited to the above embodiments and modifications, and various modifications are possible as necessary. [Explanation of symbols]

[0047] 100 screen display system, 101 first server, 102 second server, 103 user terminal, 104 device, 10 parent program, 11 parent screen, 20 embedded program, 21 embedded screen, 30 browser, 201 processor, 202 memory, 203 storage, 204 communication interface.

Claims

1. an embedded program which is a web application program different from a parent program that displays a parent screen on a browser and is called from the parent program, an event detection process for detecting a specified event occurring in the browser; an information linking process for linking information between the parent program and the embedded program when the designated event is detected by the event detection process; An embedded program that causes a computer to execute the above.

2. In the information linking process, information managed by the parent program is acquired, and a process corresponding to the specified event is executed using the acquired information. The embedding program according to claim 1 .

3. The embedding program further comprises: an embedded drawing process for drawing an embedded screen as a part of the parent screen; Run the following on your computer: In the information linking process, a process of updating the embedded screen is executed based on the acquired information. The embedding program according to claim 2.

4. In the information linking process, information managed by the embedded program is set on the parent screen. The embedding program according to claim 1 .

5. In the information linking process, information acquired from a device connected to a computer in which the embedding program is installed is set on the parent screen.

5. The embedding program according to claim 4.

6. The embedded program is located on a different computer than the parent program. The embedding program according to claim 1 .

7. a screen display program having a parent program which is a web application program and an embedded program which is a web application program different from the parent program, The parent program is A parent drawing process that displays the parent screen in the browser; a calling process for calling the embedded program; Run the following on your computer: The embedding program comprises: an event detection process for detecting a specified event occurring in the browser; an information linking process for linking information between the parent program and the embedded program when the designated event is detected by the event detection process; A screen display program that causes a computer to execute the following.

8. The parent program, which is a web application program, displays the parent screen in the browser, the parent program calls an embedded program that is a web application program different from the parent program; The embedded program detects a specified event that has occurred in the browser; The screen display method, wherein the embedded program links information between the parent program and the embedded program when the specified event is detected.

Citation Information

Patent Citations

  • System and method for providing information, and program

    JP2003050765A

  • Unified data collection and distribution

    JP2013535059A

  • Method and program for supporting provision of EC to overseas and device using same

    WO2019035368A1

  • Portal site display system, and program for portal site display system

    JP2023026702A