Method and device for generating web page, electronic equipment and storage medium
Patent Information
- Application Number
- CN202310293577.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-15
- Publication Date
- 2026-10-27
- Estimated Expiration
- 2043-03-15
AI Technical Summary
[0003]现有技术中,实现可视化数据展示的平台如FineBI、PowerBI等,这些平台通常是在Chrome浏览器中采用直接拖拽的方式完成WEB页面的创建,拖拽的对象为浏览器支持的各种图形用户界面(graphical user interface,GUI)控件,这些控件可与后台数据建立直接的关联,且在运行期支撑控件的数据刷新,由于FineBI、PowerBI的平台文件体量庞大,对承载平台的终端设备的存储空间要求比较高,且平台内模块化集成度有限,用于生成WEB页面的各控件之间关联性比较强,需要携带很多附加内容才能发布最终的WEB页面,使得生成WEB页面变得繁琐,用户体验感差
[0087]第四方面,本申请实施例提供一种存储介质,当所述存储介质中的计算机程序由电子设备的处理器执行时,所述电子设备能够执行上述WEB页面的生成方法。
Smart Images

Figure CN118673241B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of electronic information processing technology, and in particular to methods, apparatus, electronic devices and storage media for generating web pages. Background Technology
[0002] With the continuous development of electronic information technology, in order to meet the needs of various industries for product data visualization, visualizing data in the form of web pages has gradually become a trend.
[0003] In existing technologies, platforms for visual data display, such as FineBI and PowerBI, typically create web pages in the Chrome browser using a drag-and-drop method. The dragged objects are various graphical user interface (GUI) controls supported by the browser. These controls can establish direct connections with backend data and support data refresh during runtime. However, due to the large file size of FineBI and PowerBI platforms, they require a lot of storage space on the terminal devices hosting the platforms. Furthermore, the modular integration within the platforms is limited, and the controls used to generate web pages are highly interconnected, requiring a lot of additional content before the final web page can be published. This makes web page generation cumbersome and results in a poor user experience.
[0004] Therefore, how to reduce file size to make web page generation more convenient and improve user experience is an urgent technical problem to be solved. Summary of the Invention
[0005] This application provides a method, apparatus, electronic device, and storage medium for generating web pages, which reduces file size, makes web page generation more convenient, and improves user experience.
[0006] In a first aspect, embodiments of this application provide a method for generating a web page, comprising:
[0007] Receive a creation operation for the target web page, and display a list of controls in response to the creation operation;
[0008] In response to the selection operation of any control in the control list, the pre-configured control template file corresponding to the control is obtained from the server. The control template file corresponding to the control is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each module is an independent logical control.
[0009] Load the control template file, generate and display the control;
[0010] The target web page is generated and displayed by combining the various controls.
[0011] In this way, a template file is pre-configured for each control, and the control template file is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each module is an independent logical control, which can effectively reduce the file size. The control can be generated by loading the template file, and then the web page can be generated, making the generation of web pages more convenient and thus improving the user experience.
[0012] In some embodiments, the control template file includes at least a style module, a behavior module, a basic element module, and an attribute module; the style module is a logical control for displaying a corresponding display style on the interface; the behavior module is a logical control for displaying a corresponding operation behavior on the interface; the basic element module is a logical control for displaying a corresponding basic element on the interface; and the attribute module is a logical control for displaying attribute parameters that can be set for operation behaviors on the interface.
[0013] In some embodiments, the operational behavior includes adjustment behavior, and further includes:
[0014] Receive an adjustment action for the control, update the control in response to the adjustment action, and display the updated control;
[0015] The adjustment behavior operation includes at least the operation of copying the control and the operation of deleting the control.
[0016] In this way, the behavior of controls can be extended based on copy and delete operations, making the expansion of controls more flexible.
[0017] In some embodiments, obtaining the pre-configured control template file corresponding to the control from the server includes:
[0018] Obtain the file indexes of various modules in the pre-configured control template file corresponding to the control from the server;
[0019] Based on the file indexes of the various modules, obtain the various modules corresponding to the file indexes from the server;
[0020] Loading the control template file, generating and displaying the control, includes:
[0021] Load the style module and basic element module, and display the initial interface of the control;
[0022] In response to a click operation on the initial interface of the control, the behavior module and the property module are loaded, and the property list of the control is displayed.
[0023] In this way, by first obtaining the file index of each module in the control template corresponding to the control, and then obtaining the corresponding modules based on the index, the file size of the control template file can be reduced.
[0024] In some embodiments, it also includes:
[0025] The system receives a change operation for an attribute in the attribute list of the control, and in response to the change operation, calls a local adjustment function for changing the attribute parameters of the control to update the control, and displays the updated control.
[0026] In this way, the properties in the control's property list can be flexibly changed, making the generated and displayed controls more personalized and diverse, further enhancing the user experience.
[0027] In some embodiments, generating and displaying the target web page by combining the controls includes:
[0028] A target web page is generated by combining the various controls and their nesting relationships. The target web page is then embedded as a child page into a pre-generated first page, which is the parent page, for display. Alternatively, the first page can be embedded as a child page into the target web page, which is the parent page, for display. The nesting relationship is the correspondence between the parent page and the child page. The nesting relationship includes the correspondence between the target web page and the first page.
[0029] By establishing nested relationships between parent and child pages, the diversity of page display can be increased, and the user experience can be improved.
[0030] In some embodiments, the method further includes:
[0031] The nesting relationship is established in the following manner:
[0032] Receive an embedding operation for any parent page, and in response to the embedding operation, generate a page control in a blank area of the parent page;
[0033] Receive settings for page document properties of the page control, and obtain the identifier of the subpage for which the page document properties are set;
[0034] Based on the identifier of the child page and the identifier of any parent page, establish a correspondence between the parent page and the child page.
[0035] In this way, by simply generating a page control in the blank area of the parent page and setting the page document property of the page control to the identifier of the child page, the correspondence between the parent page and the child page can be established, and the child page can be embedded in the parent page for display, making the page display more flexible and convenient.
[0036] In some embodiments, generating and displaying the target web page by combining the controls includes:
[0037] The system receives a click operation that requests a jump from a parent page to a child page. In response to the click operation, based on a pre-established jump relationship between the parent page and the child page, the system jumps from the current page (which is the parent page) to the target web page (which is the child page), or from the target web page (which is the parent page) to the child page.
[0038] Establishing a navigation relationship between parent and child pages in this way can increase the diversity of page display and further enhance the user experience.
[0039] In some embodiments, the method further includes:
[0040] The following method can be used to establish a navigation relationship between a parent page and a child page:
[0041] Receive navigation property setting operation for any control within any parent page, and in response to the navigation property setting operation, receive the input name of the child page;
[0042] Set the navigation property of the control to the name of the lower-level page to establish a navigation relationship between the upper-level page and the lower-level page.
[0043] In this way, by simply setting the navigation property of any control on the parent page to the name of the child page, a navigation relationship between the parent and child pages can be established. Users can navigate from the parent page to the child page by manipulating the controls, and then display the child page, making page display more flexible and convenient.
[0044] In some embodiments, after generating and displaying the target web page in conjunction with the controls, the method further includes:
[0045] Receive linkage operations set for the target web page or any control in the target web page;
[0046] In response to the linkage operation, determine the target web page or any control in the target web page as the triggering party to generate the triggering event;
[0047] When the triggering event is determined to be valid, it is determined that there is an associated party that receives the same event as the triggering event;
[0048] When the received event is determined to be valid, the interface of the associated party is changed accordingly based on the linkage relationship between the triggering party and the associated party.
[0049] In this way, if the triggering event is valid, the associated party that receives the same event as the triggering event is determined based on the triggering event generated by the triggering party. If the receiving event is valid, the interface of the associated party can be changed accordingly based on the linkage relationship between the triggering party and the associated party. Through the linkage between the triggering party and the associated party, data transfer between the triggering party and the associated party is realized, which improves the user experience.
[0050] Secondly, embodiments of this application provide a web page generation apparatus, comprising:
[0051] The receiving module is used to receive a creation operation for the target web page and display a list of controls in response to the creation operation;
[0052] The acquisition module is used to retrieve the pre-configured control template file corresponding to the control from the server in response to the selection operation of any control in the control list. The control template file corresponding to the control is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each module is an independent logical control.
[0053] A loading module is used to load the control template file, generate and display the control;
[0054] The generation module is used to combine the various controls to generate and display the target web page.
[0055] In some embodiments, the control template file includes at least a style module, a behavior module, a basic element module, and an attribute module; the style module is a logical control for displaying a corresponding display style on the interface; the behavior module is a logical control for displaying a corresponding operation behavior on the interface; the basic element module is a logical control for displaying a corresponding basic element on the interface; and the attribute module is a logical control for displaying attribute parameters that can be set for operation behaviors on the interface.
[0056] In some embodiments, the operational behavior includes adjustment behavior, and further includes:
[0057] An update module is configured to receive an adjustment behavior operation for the control, update the control in response to the adjustment behavior operation, and display the updated control;
[0058] The adjustment behavior operation includes at least the operation of copying the control and the operation of deleting the control.
[0059] In some embodiments, the acquisition module is specifically used for:
[0060] Obtain the file indexes of various modules in the pre-configured control template file corresponding to the control from the server;
[0061] Based on the file indexes of the various modules, obtain the various modules corresponding to the file indexes from the server;
[0062] The loading module is specifically used for:
[0063] Load the style module and basic element module, and display the initial interface of the control;
[0064] In response to a click operation on the initial interface of the control, the behavior module and the property module are loaded, and the property list of the control is displayed.
[0065] In some embodiments, the updating module is further configured to:
[0066] The system receives a change operation for an attribute in the attribute list of the control, and in response to the change operation, calls a local adjustment function for changing the attribute parameters of the control to update the control, and displays the updated control.
[0067] In some embodiments, the generation module is specifically used for:
[0068] A target web page is generated by combining the various controls and their nesting relationships. The target web page is then embedded as a child page into a pre-generated first page, which is the parent page, for display. Alternatively, the first page can be embedded as a child page into the target web page, which is the parent page, for display. The nesting relationship is the correspondence between the parent page and the child page. The nesting relationship includes the correspondence between the target web page and the first page.
[0069] In some embodiments, it also includes:
[0070] A module is created to establish the nested relationship in the following manner:
[0071] Receive an embedding operation for any parent page, and in response to the embedding operation, generate a page control in a blank area of the parent page;
[0072] Receive settings for page document properties of the page control, and obtain the identifier of the subpage for which the page document properties are set;
[0073] Based on the identifier of the child page and the identifier of any parent page, establish a correspondence between the parent page and the child page.
[0074] In some embodiments, the generation module is specifically used for:
[0075] The system receives a click operation that requests a jump from a parent page to a child page. In response to the click operation, based on a pre-established jump relationship between the parent page and the child page, the system jumps from the current page (which is the parent page) to the target web page (which is the child page), or from the target web page (which is the parent page) to the child page.
[0076] In some embodiments, the establishing module is further configured to:
[0077] The following method can be used to establish a navigation relationship between a parent page and a child page:
[0078] Receive navigation property setting operation for any control within any parent page, and in response to the navigation property setting operation, receive the input name of the child page;
[0079] Set the navigation property of the control to the name of the lower-level page to establish a navigation relationship between the upper-level page and the lower-level page.
[0080] In some embodiments, after the generation module generates and displays the target web page in conjunction with the controls, the update module is further configured to:
[0081] Receive linkage operations set for the target web page or any control in the target web page;
[0082] In response to the linkage operation, determine the target web page or any control in the target web page as the triggering party to generate the triggering event;
[0083] When the triggering event is determined to be valid, it is determined that there is an associated party that receives the same event as the triggering event;
[0084] When the received event is determined to be valid, the interface of the associated party is changed accordingly based on the linkage relationship between the triggering party and the associated party.
[0085] Thirdly, embodiments of this application provide an electronic device, including: at least one processor, and a memory communicatively connected to the at least one processor, wherein:
[0086] The memory stores a computer program that can be executed by at least one processor, which enables the at least one processor to perform the above-described method for generating web pages.
[0087] Fourthly, embodiments of this application provide a storage medium in which, when a computer program in the storage medium is executed by a processor of an electronic device, the electronic device is able to execute the aforementioned method for generating web pages.
[0088] In this embodiment, a creation operation for a target web page is received. In response to the creation operation, a control list is displayed. In response to a selection operation of any control in the control list, a pre-configured control template file corresponding to the control is obtained from the server. The control template file is obtained by the server based on a combination of various modules corresponding to the control in the module library. Each module represents an independent logical control. The control template file is loaded, the control is generated and displayed, and the target web page is generated and displayed by combining all the controls. This pre-configuration of a template file for each control, with the template file obtained by the server based on a combination of various modules corresponding to the control in the module library and each module representing an independent logical control, effectively reduces file size. Loading the template file generates the control, and thus the web page, making web page generation more convenient and improving the user experience. Attached Figure Description
[0089] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:
[0090] Figure 1 A flowchart illustrating a method for generating a web page as provided in an embodiment of this application;
[0091] Figure 2 An interactive flowchart illustrating a method for generating a web page, as provided in an embodiment of this application;
[0092] Figure 3 A schematic diagram of a visual portal platform interface for generating web pages, provided as an embodiment of this application;
[0093] Figure 4 A schematic diagram of a visual portal platform creation interface provided in this application embodiment;
[0094] Figure 5 This is a schematic diagram of the initial interface of a bar chart control provided in an embodiment of this application;
[0095] Figure 6 A schematic diagram of an attribute list provided for an embodiment of this application;
[0096] Figure 7 This application provides a schematic diagram of a page after a control update.
[0097] Figure 8 A schematic diagram of a page display provided for an embodiment of this application;
[0098] Figure 9 Another schematic diagram of page display provided for an embodiment of this application;
[0099] Figure 10 A schematic diagram of a web page generation device provided in an embodiment of this application;
[0100] Figure 11 This is a schematic diagram of the hardware structure of an electronic device for implementing a method for generating web pages, provided as an embodiment of this application. Detailed Implementation
[0101] To reduce file size, make web page generation more convenient, and improve user experience, this application provides a web page generation method, apparatus, electronic device, and storage medium.
[0102] The preferred embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are for illustration and explanation only and are not intended to limit this application. Furthermore, the embodiments and features in the embodiments of this application can be combined with each other without conflict.
[0103] For ease of understanding, the technical terms used in this application are as follows:
[0104] EChart: A visualization chart library is an open-source charting library maintained by the Apache Foundation.
[0105] This application embodiment can be applied to a client, where the client can be a visual portal platform deployed on any smart device such as smartphones, tablets, and portable personal computers. The visual portal platform can provide a corresponding user interface (UI), which can display various controls for generating web pages. Users can select the corresponding controls based on their web page generation needs. The visual portal platform receives the creation operation for the target web page, displays a control list in response to the creation operation, and, in response to the user's selection of any control in the control list, retrieves the pre-configured control template file corresponding to the control from the server, loads the control template file, generates and displays the control, and finally, combines all the controls to generate and display the target web page. The control template file corresponding to the control is obtained by the server based on the combination of various modules corresponding to the control in the module library, and each module is an independent logical control. In this way, the target web page can be generated by dragging and dropping or clicking the required control, making web page generation more convenient. Furthermore, pre-setting template files for each control can effectively reduce the file size of the visual portal platform. The visual portal platform can be deployed on a server, and users can access and use the visual portal platform through a web page or a specified application.
[0106] The generation of web pages proposed in this application will be described below with specific embodiments. Figure 1 A flowchart of a method for generating a web page provided in an embodiment of this application is shown. The method includes the following steps.
[0107] In step 101, a creation operation for the target web page is received, and a list of controls is displayed in response to the creation operation.
[0108] In practice, the client has a menu bar with a create button. When a user clicks the create button, they can create a new web page interface. The client responds to the create operation by displaying a list of controls, such as basic controls, chart controls, and electrical controls.
[0109] In step 102, in response to the selection operation of any control in the control list, the pre-configured control template file corresponding to the control is obtained from the server. The control template file corresponding to the control is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each type of module is an independent logical control.
[0110] In practice, the selection of any control can be triggered by a user's click or drag action, and there is no limitation here.
[0111] In some embodiments, the control template file includes at least a style module, a behavior module, a basic element module, and an attribute module. The style module is a logical control for displaying the corresponding display style on the interface, the behavior module is a logical control for displaying the corresponding operation behavior on the interface, the basic element module is a logical control for displaying the corresponding basic element on the interface, and the attribute module is a logical control for displaying the attribute parameters corresponding to the settable operation behavior on the interface.
[0112] For example, taking the EChart control as a visual chart control, the control's style can be a bar chart style, a line chart style, etc.; the control's behavior can be a basic attribute class, a binding class, a boundary class, a fill class, etc.; the control's basic elements can be the control's outer size and background color, etc.; the control's properties can be the same as the control's behavior properties that can be set. For example, basic properties can be set to width, height, top and bottom margins, etc.; binding properties can be set to the name of the bound data file and whether it is valid, etc.; boundary properties can be set to boundary color, boundary line style, etc.; and fill properties can be set to fill color, fill color transparency, etc.
[0113] In practice, the control template can be obtained by combining various modules corresponding to the control in the module library. Each module has independent control logic, which means that the modules can be reused. For example, the behavior of the bar chart control and the line chart control is the same. They both have basic attribute classes, data binding classes, boundary classes, and fill classes. Therefore, the behavior modules of these two controls are the same. In this way, the template file configuration can be more flexible, without repeated coding, and the file size of the platform can be reduced.
[0114] In practical implementation, to further reduce the size of the template file, the control template file can also record only the file index of various modules. For example, the control template file format is: {"Style Module": ["folder f / folder g / file m.file format"; "Behavior Module": ["folder f / folder k.file format"; "Basic Element Module": ["folder f / folder j / file t.file format"; "Attribute Module": ["folder f / folder q / file x.file format"; ]} ...
[0115] In practice, when the client obtains the pre-configured control template file corresponding to the control from the server, it can first obtain the file index of various modules in the pre-configured control template file corresponding to the control from the server, and then obtain the various modules corresponding to the file index from the server based on the file index of various modules.
[0116] It should be noted that the control template file can also add other functional modules as needed, such as an option module, to add additional parameters to the control. The specifics can be set by technical personnel and are not limited here.
[0117] In step 103, the control template file is loaded, and the control is generated and displayed.
[0118] In practice, the initial interface of the control is displayed by loading the style module and the basic element module. Then, in response to a click operation on the initial interface of the control, the client loads the behavior module and the attribute module to display the list of attributes of the control.
[0119] In practice, the properties in the property list of each control can be flexibly changed. The client receives the change operation for the property in the property list of the control, responds to the change operation, calls the local adjustment function used to change the control property parameters to update the control, and displays the updated control, making the generated and displayed controls more personalized and diverse, and further improving the user experience.
[0120] These include adjustment functions such as initialization functions, size adjustment functions, data refresh functions, property bar parameter setting functions, and property bar attribute value retrieval functions. The initialization function is called when initializing and loading the control's various attribute parameters; the size adjustment function is called when adjusting the control's basic attributes; the data refresh function is called when refreshing the data bound to the control; the property bar parameter setting function is called when changing the property bar parameters; and the property bar attribute value retrieval function is called when displaying the property bar attribute values.
[0121] In practice, to make the expansion of the control more flexible, the modified control can also be adjusted. The client can receive adjustment behavior operations for the control, update the control in response to the adjustment behavior operations, and display the updated control. The adjustment behavior operations include at least copying the control and deleting the control.
[0122] In step 104, the target web page is generated and displayed by combining the various controls.
[0123] In practice, the final interface of each control can be combined, for example, the order of the controls can be determined according to the user's preferences.
[0124] In some embodiments, the page can be displayed in a nested manner, combining various controls and nesting relationships to generate a target web page, and then embedding the target web page as a child page into a pre-generated first page as the parent page for display, or embedding the first page as a child page into the target web page as the parent page for display; wherein, the nesting relationship is the correspondence between the parent page and the child page, and the nesting relationship includes the correspondence between the target web page and the first page.
[0125] In practice, the nesting relationship can be established in the following way: receive the embedding operation for any parent page, generate a page control in the blank area of the parent page in response to the embedding operation, receive the setting of the page document property of the page control, obtain the identifier of the child page for the setting of the page document property, and establish the correspondence between any parent page and the child page based on the identifier of the child page and the identifier of any parent page.
[0126] For example, an embed button can be set on the menu bar of the parent page. In response to the click of the embed button, a page control can be generated in the blank area of the parent page. After setting the page document properties of the page control, the size of the page control can also be adjusted. For example, through the property list, or by selecting the page control and dragging the identifier that appears on the boundary of the page control inward or outward until it is adjusted to the target size. The page control can also be moved to the target area on the parent page by dragging it.
[0127] In some embodiments, the page may be displayed in a jump manner, receiving a click operation to jump from the parent page to the lower page, and in response to the click operation, based on the pre-established jump relationship between the parent page and the lower page, jumping from the current page, which is the parent page, to the target web page, which is the lower page, or jumping from the target web page, which is the parent page, to the lower page.
[0128] In practice, the following method can be used to establish the navigation relationship between the parent page and the child page: receive the navigation property setting operation for any control within any parent page; respond to the navigation property setting operation; receive the input name of the child page; set the navigation property of the control to the name of the child page; and establish the navigation relationship between the parent page and the child page.
[0129] For example, taking the current page as the parent page, and the parent page being a map of country A, with three province controls labeled a, b, and c on the map of country A, navigation properties can be set for any control within the parent page. For instance, the user first selects the province a control, then right-clicks and selects "Navigation Properties Settings." A pop-up window will then appear, displaying "Please enter the name of the next page to navigate to." The user can enter the name of the next page in this pop-up window, such as the map name of province a. In response to the navigation property setting operation, the client receives the entered map name of province a and sets the navigation property of the province a control to the map name of province a. After the setting is complete, clicking the province a control on the map of country A will navigate to the map page of province a.
[0130] In some embodiments, after generating and displaying the target web page in conjunction with each control, it can also receive linkage operations set for the target web page or any control in the target web page. In response to the linkage operation, it determines the trigger event generated by the target web page or any control in the target web page as the triggering party. When the trigger event is determined to be valid, it determines the associated party that has set the same receiving event as the trigger event. When the receiving event is determined to be valid, it makes corresponding changes to the interface of the associated party according to the linkage relationship between the triggering party and the associated party.
[0131] In practice, the linkage relationships are pre-set for data transfer between controls, between controls and pages, and between pages. There must be at least one associated party linked to the triggering party. When an event occurs on the triggering party, it can trigger corresponding changes in the associated parties. For example, clicking a button triggers a page switch, data refresh triggers changes in other control data, clicking a switch triggers the start and stop of an animation, etc. Here, "trigger event" refers to the name of the event emitted by the triggering party, "trigger valid" means the triggering party is allowed to emit the event, "receive event" refers to the name of the event that the receiving party can receive, and "receive valid" means the receiving party is allowed to receive the event.
[0132] In this embodiment, by pre-configuring template files for each control, and ensuring that each module of the control template file is independent and reusable, the platform size is effectively reduced. When generating a web page, only the template files of each control that makes up the page need to be obtained and then loaded to generate the web page, making web page generation more convenient and improving user experience. At the same time, the controls are easy to extend, which makes it easy to use existing web plugins for extensions. The page nesting is flexible, and the linkage scheme is convenient and flexible, which can increase the diversity of page display and further improve user experience.
[0133] Figure 2 The present application provides an interactive flowchart of a method for generating a web page, including a client and a server. The method includes the following steps.
[0134] In step 201, the client receives a creation operation for the target web page and displays a list of controls in response to the creation operation.
[0135] For specific implementation details, please refer to step 101, which will not be repeated here.
[0136] In step 202, in response to the selection operation of any control in the control list, the client sends a request to the server to obtain the pre-configured control template file corresponding to that control.
[0137] In practice, the control template file corresponding to the control is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each module is an independent logical control. The control template file includes at least a style module, a behavior module, a basic element module, and an attribute module. The style module is the logical control used to display the corresponding display style on the interface. The behavior module is the logical control used to display the corresponding operation behavior on the interface. The basic element module is the logical control used to display the corresponding basic element on the interface. The attribute module is the logical control used to display the attribute parameters corresponding to the settable operation behavior on the interface.
[0138] In step 203, the server receives a request from the client to obtain the pre-configured control template file corresponding to the control, and sends the control template file corresponding to the control to the client.
[0139] In step 204, the client receives the control template file sent by the server and determines the file index of each module in the control template file.
[0140] In step 205, the client sends a request to the server to retrieve the various modules corresponding to the file index.
[0141] In step 206, the server receives a request from the client to obtain the various modules corresponding to the file index, and sends the various modules corresponding to the file index to the client.
[0142] In step 207, the client receives various modules corresponding to each file index, loads the style module and basic element module, and displays the initial interface of the control.
[0143] In step 208, in response to a click on the initial interface of the control, the client loads the behavior module and the property module and displays the control's property list.
[0144] In step 209, the client receives a change operation for an attribute in the attribute list of the control, and in response to the change operation, calls a local adjustment function used to change the control attribute parameters to update the control and displays the updated control.
[0145] In step 210, the client combines the various controls to generate and display the target web page.
[0146] The following uses a bar chart control within the target web page as an example to illustrate the solution of this application embodiment. The client of this application embodiment is a visual portal platform.
[0147] Figure 3 This application provides a schematic diagram of a visual portal platform interface for generating web pages, as shown in the embodiments of this application. Figure 3 As shown, the interface can be divided into an editing area, an attribute list area, and a control area. The following steps will explain in detail the process of creating a bar chart control to generate the target web page.
[0148] Step 1: The user creates an operation page on the visual portal platform, and then the visual portal platform responds by creating a list of operation display controls, such as... Figure 4 As shown, Figure 4 This is a schematic diagram of a visual portal platform creation interface provided in an embodiment of this application.
[0149] Step 2: The user selects a chart in the control area with the mouse. The visualization portal platform responds to the click operation by displaying a list of chart controls, such as bar charts, line charts, and pie charts. The user can then select a bar chart control. In response to the selection of the bar chart control, the visualization portal platform retrieves the pre-configured control template file corresponding to the bar chart control from the server.
[0150] In practice, the control template file is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each module is an independent logical control. The control template file of the bar chart control links the four main components of the control: style module, behavior module, basic element module, and attribute module. Among them, the style module can be a style module, the behavior module can be a class module, the basic element module can be an HTML module, and the attribute module can be a param module. The style module is used for the logical control of displaying the corresponding display style on the interface; the class module is used for the logical control of displaying the corresponding operation behavior on the interface; the HTML module is used for the logical control of displaying the corresponding basic element on the interface; and the param module is used for the logical control of displaying the attribute parameters corresponding to the configurable operation behavior on the interface.
[0151] In practice, after the server sends the control template file to the client, the client parses the control template file to obtain the file indexes of various modules in the control template file. Then, based on the file indexes of various modules, the client retrieves the corresponding modules from the server.
[0152] For example, in a control template file, the `style` module is formatted as: `{"style": ["folder f / folder g / file m.css"]`, where `style` represents the module name, and `folder f / folder g / file m.css` represents the file index of the module, with the file format being `.css`. Similarly, the `class` module is formatted as: `"class": ["name":"basic behavior","js":"all-base.js"]`, defining the basic behavior of the control. Additionally, binding behavior, padding behavior, and boundary behavior can be defined. The `HTML` module can have static constraints, such as `width = '300'`. `height='300'` limits the width and height of the control's outer perimeter. The `param` module format is `{"##beg": boundary attribute start code,"url":"param / boundary behavior.json"}`, where the boundary attribute start code is a natural number. Each type of attribute contains settable attribute parameters with a certain code range. For example, if there are two settable attribute parameters for the boundary attribute, namely boundary color and boundary line type, then a code can be set for each attribute parameter. If the boundary color code is set to 1 and the boundary line type code is set to 2, then 1 is the start code for the boundary attribute. The start codes for subsequent fill attributes are set starting from 3, and so on.
[0153] In practice, the properties in the property list of each control can be flexibly changed. The client receives the change operation for the property in the property list of the control, responds to the change operation, calls the local adjustment function used to change the control property parameters to update the control, and displays the updated control. It can also add deletion and copying behavior of the control, such as adjustment functions such as the initialization function reinit, the size adjustment function resize, the property bar parameter setting function setv, the property bar property value getting function getv, the deletion function remove, the copy function clone, and the data refresh function reset.
[0154] 1. reinit: Called when initializing the various property parameters of the control during loading;
[0155] 2. resize: Called when resizing the basic properties of a control;
[0156] 3. setv: Called when changing parameters in the attribute panel;
[0157] 4. getv: Called when displaying the values of each attribute in the attribute bar;
[0158] 5. remove: Called when deleting a control;
[0159] 6. clone: Called when copying a control;
[0160] 7. reset: Called when refreshing the data bound to the control.
[0161] Step 3: The visual portal platform loads the control template file, generates and displays the controls.
[0162] In practice, the visual portal platform loads the control template file using a dynamic loading method, loading four modules sequentially and making them available on the front end. This achieves modularization and dynamic loading of the controls. Here, the visual portal platform can display the initial interface of the controls by loading the style module and the HTML module, such as... Figure 5 As shown, Figure 5 This is a schematic diagram of the initial interface of a bar chart control provided in an embodiment of this application.
[0163] Subsequently, in response to a click on the initial interface of the bar chart control, the visualization portal platform loads the class and param modules and displays the control's property list. Figure 6 This is a schematic diagram of an attribute list provided for an embodiment of this application. For example... Figure 6As shown, the initial interface of the bar chart control is marked with dots, and the attribute list area on the right displays the attribute list. Then, based on the user's parameter settings for each attribute of the control in the attribute list of the control's initial interface, such as basic parameter settings, binding parameter settings, boundary parameter settings, and fill parameter settings, the visualization portal platform receives the change operations for the attributes in the control's attribute list. In response to the change operations, it calls the local adjustment function used to change the control's attribute parameters to update the control and displays the updated control. Figure 7 As shown, Figure 7 This is a schematic diagram of a page after a control update, provided in an embodiment of this application.
[0164] Step 4: Generate the target web page.
[0165] In practice, after creation, the page can be named and saved.
[0166] In practice, the page can be displayed in a nested manner or by jumping to another page.
[0167] For example, displaying pages through nesting can be done by embedding the target web page as a child page into a pre-generated first page that is the parent page, or by embedding the first page as a child page into the target web page that is the parent page. The nesting relationship is the correspondence between the parent page and the child page, including the correspondence between the target web page and the first page.
[0168] In practical implementation, nesting relationships can be established as follows: receiving embedding operations for any parent page; responding to the embedding operation, generating page controls in the blank area of the parent page; receiving settings for the page document properties of the page controls; obtaining the identifier of the child page whose page document properties are set; and establishing a correspondence between any parent page and its child page based on the child page's identifier and the identifier of any parent page. For example... Figure 8 As shown, Figure 8 This is a schematic diagram of a page display provided for an embodiment of this application.
[0169] For example, displaying information via page navigation could involve receiving a click operation to navigate from a parent page to a child page, and responding to the click operation by navigating from the current page (which is the parent page) to the target web page (which is the child page) based on a pre-established navigation relationship between the parent and child pages. Alternatively, it could involve navigating from the target web page (which is the parent page) to the child page.
[0170] In specific implementation, the following method is used to establish the navigation relationship between the parent page and the child page: It receives navigation property setting operations for any control within any parent page; responds to the navigation property setting operation; receives the input name of the child page; sets the navigation property of the control to the name of the child page; and establishes the navigation relationship between the parent page and the child page. For example... Figure 9 As shown, Figure 9 This is another page display diagram provided for an embodiment of this application. After the user sets the navigation attribute of the triangle button to the page name of the next level page, clicking the triangle button on the parent page will allow the user to jump from the parent page to the next level page, that is, display the next level page on the current page.
[0171] In practical implementation, after generating the target web page, it can also receive linked operations set for the target web page or any control within the target web page. In response to the linked operation, it determines the target web page or any control within the target web page as the triggering party to generate a trigger event. If the trigger event is valid, it determines an associated party with the same receiving event as the trigger event. If the receiving event is valid, it makes corresponding changes to the associated party's interface based on the linkage relationship between the triggering party and the associated party. The linkage relationship is pre-set and used for data transfer between controls, between controls and pages, and between pages. There must be at least one associated party linked with the triggering party. When an event occurs on the triggering party, it can trigger corresponding changes in the associated party. For example, clicking a button triggers a page switch, data refresh triggers changes in other control data, clicking a switch triggers the start and stop of an animation, etc. Here, "trigger event" refers to the name of the event emitted by the triggering party, "trigger valid" means the triggering party is allowed to emit the event, "received event" refers to the name of the event that the receiver can receive, and "receive valid" means the receiver is allowed to receive the event.
[0172] In this embodiment, by pre-configuring template files for each control, and ensuring that each module of the control template file is independent and reusable, the platform size is effectively reduced. When generating a web page, only the templates of each control that makes up the page need to be obtained and then the templates are parsed to generate the web page, making web page generation more convenient and improving the user experience. At the same time, the controls are easy to extend, which makes it easy to use existing web plugins for extensions. The page nesting is flexible, and the linkage scheme is flexible, further improving the user experience.
[0173] Based on the same technical concept, this application also provides a web page generation device. The principle of the web page generation device in solving the problem is similar to that of the web page generation method described above. Therefore, the implementation of the web page generation device can refer to the implementation of the web page generation method, and the repeated parts will not be described again.
[0174] Figure 10A schematic diagram of a web page generation device provided in this application embodiment includes a receiving module 1001, an acquisition module 1002, a loading module 1003, and a generation module 1004.
[0175] The receiving module 1001 is used to receive a creation operation on the target web page and display a list of controls in response to the creation operation;
[0176] The acquisition module 1002 is used to obtain a pre-configured control template file corresponding to the control from the server in response to the selection operation of any control in the control list. The control template file corresponding to the control is obtained by the server according to the combination of various modules corresponding to the control in the module library. Each module is an independent logical control.
[0177] Loading module 1003 is used to load the control template file, generate and display the control;
[0178] The generation module 1004 is used to generate and display the target web page by combining the various controls.
[0179] In some embodiments, the control template file includes at least a style module, a behavior module, a basic element module, and an attribute module; the style module is a logical control for displaying a corresponding display style on the interface; the behavior module is a logical control for displaying a corresponding operation behavior on the interface; the basic element module is a logical control for displaying a corresponding basic element on the interface; and the attribute module is a logical control for displaying attribute parameters that can be set for operation behaviors on the interface.
[0180] In some embodiments, the operational behavior includes adjustment behavior, and further includes:
[0181] The update module 1005 is configured to receive an adjustment behavior operation for the control, update the control in response to the adjustment behavior operation, and display the updated control.
[0182] The adjustment behavior operation includes at least the operation of copying the control and the operation of deleting the control.
[0183] In some embodiments, the acquisition module 1002 is specifically used for:
[0184] Obtain the file indexes of various modules in the pre-configured control template file corresponding to the control from the server;
[0185] Based on the file indexes of the various modules, obtain the various modules corresponding to the file indexes from the server;
[0186] The loading module 1003 is specifically used for:
[0187] Load the style module and basic element module, and display the initial interface of the control;
[0188] In response to a click operation on the initial interface of the control, the behavior module and the property module are loaded, and the property list of the control is displayed.
[0189] In some embodiments, the update module 1005 is further configured to:
[0190] The system receives a change operation for an attribute in the attribute list of the control, and in response to the change operation, calls a local adjustment function for changing the attribute parameters of the control to update the control, and displays the updated control.
[0191] In some embodiments, the generation module 1004 is specifically used for:
[0192] A target web page is generated by combining the various controls and their nesting relationships. The target web page is then embedded as a child page into a pre-generated first page, which is the parent page, for display. Alternatively, the first page can be embedded as a child page into the target web page, which is the parent page, for display. The nesting relationship is the correspondence between the parent page and the child page. The nesting relationship includes the correspondence between the target web page and the first page.
[0193] In some embodiments, it also includes:
[0194] Module 1006 is used to establish the nested relationship in the following manner:
[0195] Receive an embedding operation for any parent page, and in response to the embedding operation, generate a page control in a blank area of the parent page;
[0196] Receive settings for page document properties of the page control, and obtain the identifier of the subpage for which the page document properties are set;
[0197] Based on the identifier of the child page and the identifier of any parent page, establish a correspondence between the parent page and the child page.
[0198] In some embodiments, the generation module 1004 is specifically used for:
[0199] The system receives a click operation that requests a jump from a parent page to a child page. In response to the click operation, based on a pre-established jump relationship between the parent page and the child page, the system jumps from the current page (which is the parent page) to the target web page (which is the child page), or from the target web page (which is the parent page) to the child page.
[0200] In some embodiments, the establishment module 1006 is further configured to:
[0201] The following method can be used to establish a navigation relationship between a parent page and a child page:
[0202] Receive navigation property setting operation for any control within any parent page, and in response to the navigation property setting operation, receive the input name of the child page;
[0203] Set the navigation property of the control to the name of the lower-level page to establish a navigation relationship between the upper-level page and the lower-level page.
[0204] In some embodiments, after the generation module generates and displays the target web page in conjunction with the controls, the update module 1005 is further configured to:
[0205] Receive linkage operations set for the target web page or any control in the target web page;
[0206] In response to the linkage operation, determine the target web page or any control in the target web page as the triggering party to generate the triggering event;
[0207] When the triggering event is determined to be valid, it is determined that there is an associated party that receives the same event as the triggering event;
[0208] When the received event is determined to be valid, the interface of the associated party is changed accordingly based on the linkage relationship between the triggering party and the associated party.
[0209] The module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, other division methods are possible. Furthermore, the functional modules in each embodiment of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. Coupling between modules can be achieved through interfaces, typically electrical communication interfaces, but mechanical interfaces or other types of interfaces are also possible. Therefore, modules described as separate components may or may not be physically separate; they can be located in one place or distributed across different locations on the same or different devices. The integrated modules described above can be implemented in hardware or as software functional modules.
[0210] Having introduced the web page generation method and apparatus according to exemplary embodiments of this application, we will now introduce an electronic device according to another exemplary embodiment of this application.
[0211] The following reference Figure 11To describe an electronic device 130 implemented according to this embodiment of the present application. Figure 11 The electronic device 130 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.
[0212] like Figure 11 As shown, the electronic device 130 is presented in the form of a general-purpose electronic device. The components of the electronic device 130 may include, but are not limited to: at least one processor 131, at least one memory 132, and a bus 133 connecting different system components (including memory 132 and processor 131).
[0213] Bus 133 represents one or more of several bus structures, including a memory bus or memory controller, peripheral bus, processor, or local bus using any of the various bus structures.
[0214] The memory 132 may include a readable medium in the form of volatile memory, such as random access memory (RAM) 1321 and / or cache memory 1322, and may further include read-only memory (ROM) 1323.
[0215] The memory 132 may also include a program / utility 1325 having a set (at least one) of program modules 1324, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.
[0216] Electronic device 130 can also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), and with one or more devices that enable a user to interact with electronic device 130, and / or with any device that enables electronic device 130 to communicate with one or more other electronic devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 135. Furthermore, electronic device 130 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 136. As shown, network adapter 136 communicates with other modules used in electronic device 130 via bus 133. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0217] In an exemplary embodiment, a storage medium is also provided, which, when executed by a processor of an electronic device, enables the electronic device to perform the aforementioned method for generating web pages. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.
[0218] In an exemplary embodiment, the electronic device of this application may include at least one processor and a memory communicatively connected to the at least one processor, wherein the memory stores a computer program executable by the at least one processor, and when the computer program is executed by the at least one processor, it enables the at least one processor to perform the steps of any of the web page generation methods provided in the embodiments of this application.
[0219] In an exemplary embodiment, a computer program product is also provided, which, when executed by an electronic device, enables the electronic device to implement any of the exemplary methods provided in this application.
[0220] Furthermore, computer program products may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, RAM, ROM, erasable programmable read-only memory (EPROM), flash memory, optical fiber, compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0221] The program product for generating web pages in the embodiments of this application may be a CD-ROM and include program code, and may run on a computing device. However, the program product of this application is not limited thereto. In this document, the readable storage medium may be any tangible medium that contains or stores a program, which may be used by or in conjunction with an instruction execution system, apparatus, or device.
[0222] A readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. This propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting a program for use by or in conjunction with an instruction execution system, apparatus, or device.
[0223] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, radio frequency (RF) and so on, or any suitable combination thereof.
[0224] Program code for performing the operations of this application can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's computing device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, such as a Local Area Network (LAN) or a Wide Area Network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0225] It should be noted that although several units or sub-units of the device have been mentioned in the detailed description above, this division is merely exemplary and not mandatory. In fact, according to embodiments of this application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided and embodied by multiple units.
[0226] Furthermore, although the operations of the method of this application are described in a specific order in the accompanying drawings, this does not require or imply that these operations must be performed in that specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.
[0227] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0228] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.
[0229] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0230] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.
[0231] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.
[0232] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
Claims
1. A method for generating a web page, characterized in that, include: Receive a creation operation for the target web page, and display a list of controls in response to the creation operation; In response to the selection operation of any control in the control list, the pre-configured control template file corresponding to the control is obtained from the server. The control template file corresponding to the control is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each module is an independent logical control. Load the control template file, generate and display the control; The target web page is generated and displayed by combining the various controls.
2. The generation method as described in claim 1, characterized in that, The control template file includes at least a style module, a behavior module, a basic element module, and an attribute module; the style module is a logical control for displaying the corresponding display style on the interface; the behavior module is a logical control for displaying the corresponding operation behavior on the interface; the basic element module is a logical control for displaying the corresponding basic element on the interface; and the attribute module is a logical control for displaying the attribute parameters corresponding to the settable operation behavior on the interface.
3. The generation method according to claim 2, characterized in that, The operational behavior includes adjustment behavior, and also includes: Receive an adjustment action for the control, update the control in response to the adjustment action, and display the updated control; The adjustment behavior operation includes at least the operation of copying the control and the operation of deleting the control.
4. The generation method as described in claim 1 or 2, characterized in that, Obtain the pre-configured control template file corresponding to the control from the server, including: Obtain the file indexes of various modules in the pre-configured control template file corresponding to the control from the server; Based on the file indexes of the various modules, obtain the various modules corresponding to the file indexes from the server; Loading the control template file, generating and displaying the control, includes: Load the style module and basic element module, and display the initial interface of the control; In response to a click operation on the initial interface of the control, the behavior module and the property module are loaded, and the property list of the control is displayed.
5. The generation method according to claim 4, characterized in that, Also includes: The system receives a change operation for an attribute in the attribute list of the control, and in response to the change operation, calls a local adjustment function for changing the control attribute parameters to update the control, and displays the updated control.
6. The generation method as described in claim 1, characterized in that, The process of generating and displaying the target web page by combining the aforementioned controls includes: A target web page is generated by combining the various controls and their nesting relationships. The target web page is then embedded as a child page into a pre-generated first page, which is the parent page, for display. Alternatively, the first page can be embedded as a child page into the target web page, which is the parent page, for display. The nesting relationship is the correspondence between the parent page and the child page. The nesting relationship includes the correspondence between the target web page and the first page.
7. The generation method as described in claim 6, characterized in that, The method further includes: The nesting relationship is established in the following manner: Receive an embedding operation for any parent page, and in response to the embedding operation, generate a page control in a blank area of the parent page; Receive settings for page document properties of the page control, and obtain the identifier of the subpage for which the page document properties are set; Based on the identifier of the child page and the identifier of any parent page, establish a correspondence between the parent page and the child page.
8. The generation method as described in claim 1, characterized in that, The process of generating and displaying the target web page by combining the aforementioned controls includes: The system receives a click operation that requests a jump from a parent page to a child page. In response to the click operation, based on a pre-established jump relationship between the parent page and the child page, the system jumps from the current page (which is the parent page) to the target web page (which is the child page), or from the target web page (which is the parent page) to the child page.
9. The generation method as described in claim 8, characterized in that, The method further includes: The following method can be used to establish a navigation relationship between a parent page and a child page: Receive navigation property setting operation for any control within any parent page, and in response to the navigation property setting operation, receive the input name of the child page; Set the navigation property of the control to the name of the lower-level page to establish a navigation relationship between the upper-level page and the lower-level page.
10. The generation method as described in claim 1, characterized in that, After generating and displaying the target web page by combining the aforementioned controls, the method further includes: Receive linkage operations set for the target web page or any control in the target web page; In response to the linkage operation, determine the target web page or any control in the target web page as the triggering party to generate the triggering event; When the triggering event is determined to be valid, it is determined that there is an associated party that receives the same event as the triggering event; When the received event is determined to be valid, the interface of the associated party is changed accordingly based on the linkage relationship between the triggering party and the associated party.
11. A web page generation device, characterized in that, include: The receiving module is used to receive the creation operation of the target web page and display a list of controls in response to the creation operation; The acquisition module is used to retrieve the pre-configured control template file corresponding to the control from the server in response to the selection operation of any control in the control list. The control template file corresponding to the control is obtained by the server based on the combination of various modules corresponding to the control in the module library. Each type of module is an independent logical control. A loading module is used to load the control template file, generate and display the control; The generation module is used to combine the various controls to generate and display the target web page.
12. An electronic device, characterized in that, include: At least one processor, and a memory communicatively connected to said at least one processor, wherein: The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the method as described in any one of claims 1-10.
13. A storage medium, characterized in that, When the computer program in the storage medium is executed by the processor of the electronic device, the electronic device is able to perform the method as described in any one of claims 1-10.
Citation Information
Patent Citations
Webpage generation method and system, electronic equipment and storage medium
CN115408002A