A portal dynamic arrangement method and device
By constructing a visual orchestration interface to capture user operation events, generating structured configuration data, dynamically rendering pages, and storing them in association with user identities, the flexibility and performance issues of portal systems in personalized homepage customization are solved, achieving efficient "personalized presentation" for each user.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINESE PEOPLES LIBERATION ARMY INFORMATION SUPPORT CORPS ENGINEERING UNIVERSITY
- Filing Date
- 2026-07-03
- Publication Date
- 2026-07-31
AI Technical Summary
Existing portal systems suffer from problems such as insufficient page layout flexibility, degraded rendering performance, difficulty in storing and managing operations, and tight coupling between the presentation layer and business logic when implementing personalized and customized homepages, resulting in system redundancy and high maintenance costs.
By building a visual orchestration interface, capturing user operation events, generating structured configuration data, parsing and converting it into standardized descriptions, dynamically rendering pages, and storing it in association with user identities, differentiated presentations can be achieved.
It supports free drag and drop and real-time preview, which reduces the customization and maintenance costs of large-scale personalized portal systems, ensures rendering performance and smooth interaction, and realizes personalized customization of "a thousand people, a thousand faces".
Smart Images
Figure CN122489200A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of visual configuration technology, and more specifically, to a method and apparatus for dynamic portal orchestration. Background Technology
[0002] As enterprises become increasingly information-driven, portal systems, as the core entry point for information aggregation and display, are playing an increasingly important role. Currently, portal technology is evolving from an early, unified, and static display model to a more advanced form emphasizing personalization, role-based design, and contextualization. "Personalized experiences" have become a key objective for improving user experience and operational efficiency, requiring highly customized portal homepages dynamically tailored to users with different identities, roles, and preferences.
[0003] To achieve flexibility in page construction, existing technologies generally employ modular, low-code, or visual designer solutions. However, these solutions still have significant shortcomings: First, page layout flexibility is limited, making it difficult to support true drag-and-drop arrangement; second, as the number of page components increases, system rendering performance significantly degrades, affecting interactive smoothness; third, user operations lack a unified and persistent data abstraction, making it difficult to store, restore, and version-manage page states; fourth, the page presentation layer is tightly coupled with the underlying business logic, making it difficult to adapt to diverse personalized needs. Crucially, existing solutions typically publish and manage on a site-wide or page-by-page basis, failing to provide differentiated homepage presentations to a massive number of users based on a single access point without replicating the site structure. This leads to system redundancy, complex permissions, and high maintenance costs when implementing personalized experiences. Summary of the Invention
[0004] In view of at least one defect or improvement need of the prior art, this application provides a portal dynamic orchestration method and apparatus that can solve at least one of the problems existing in the background art.
[0005] To achieve the above objectives, according to the first aspect of this application, a portal dynamic orchestration method is provided, comprising the following steps: S1. Construct a visual arrangement interface to support visual operations such as page area division, component dragging and dropping, and attribute configuration; S2. Capture and record the visual operation events on the visual orchestration interface, and generate an operation event sequence; S3. Based on the preset structured configuration description specification, the operation event sequence is parsed and converted into structured configuration data to describe the portal page layout structure, component attributes and interaction logic; S4. Based on the structured configuration data, dynamically generate the corresponding portal page through the rendering engine; S5. The structured configuration data is associated with the user identity information and then stored.
[0006] Furthermore, the above-mentioned portal dynamic orchestration method stores the structured configuration data in association with user identity information. When a user visits the site, the associated structured configuration data is retrieved based on the user's identity information, and the corresponding portal homepage is dynamically rendered and generated.
[0007] Furthermore, in the aforementioned portal dynamic orchestration method, the visual orchestration interface includes a basic operation module, a display module, a component configuration module, and an operation bar module; The basic operation module is used to display a tree structure of draggable component resource library and interface data; The display module is used to receive dragged components and display the page layout; The component configuration module is used to configure the attributes, data, and interactions of the selected component; The operation bar module is used for saving, rewinding, and previewing canvas data.
[0008] Furthermore, in the above-mentioned portal dynamic orchestration method, the visual operation events include at least one of the following: component addition event, component deletion event, component position adjustment event, component attribute modification event, and component data binding event.
[0009] Furthermore, in the aforementioned portal dynamic orchestration method, the structured configuration data content includes the hierarchical nesting relationship of page nodes, the layout parameters and style attributes of each component, data model binding information, and interaction logic description information.
[0010] Furthermore, in the aforementioned portal dynamic orchestration method, the step of dynamically generating the corresponding portal page through a rendering engine specifically includes: The structured configuration data structure is parsed based on the rendering engine, and the nested structure is parsed into HTML DOM nodes; Parse the configuration attributes and styles of each node and attach them to each DOM node; The bound data and corresponding interaction orchestration are generated into a JavaScript code object, which is then passed to the component and rendered into real data and bound to the corresponding interaction logic through a fixed transformation.
[0011] Furthermore, in the aforementioned portal dynamic orchestration method, the structured configuration data is also stored in association with user role information and version metadata to support role-based access control and version management of configuration data.
[0012] According to a second aspect of this application, a portal dynamic orchestration apparatus is also provided, comprising: The interface building module is used to build a visual layout interface, which supports visual operations such as page area division, component drag and drop, and attribute configuration. An operation capture module is used to capture and record visual operation events on the visual orchestration interface and generate an operation event sequence. The structured module is used to parse and convert the operation event sequence into structured configuration data based on a preset structured configuration description specification, which is used to describe the portal page layout structure, component attributes and interaction logic. The interface generation module is used to dynamically generate the corresponding portal page based on the structured configuration data through the rendering engine; The storage module is used to store the structured configuration data after associating it with the user identity information.
[0013] According to a third aspect of this application, a portal dynamic orchestration device is also provided, comprising at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program that, when executed by the processing unit, causes the processing unit to perform the steps of any of the methods described above.
[0014] According to a fourth aspect of this application, a storage medium is also provided that stores a computer program executable by a portal dynamic orchestration device, which, when run on the portal dynamic orchestration device, causes the portal dynamic orchestration device to perform the steps of any of the methods described above.
[0015] In summary, compared with the prior art, the above-described technical solutions conceived in this application can achieve the following beneficial effects: The portal dynamic orchestration method provided in this application constructs a visual orchestration interface that supports free dragging and real-time preview. It captures user operation events and converts them into structured configuration data that uniformly describes page structure, component attributes, and interaction logic. Based on this configuration data, an engine dynamically renders the page, and the final configuration is stored in association with the user's identity. This enables the generation and dynamic presentation of differentiated personal homepages for a massive number of users without altering the site's engineering and publishing structure. This method decouples the page presentation layer from business logic, achieving a complete description and lossless restoration of the page state through standardized configuration data. It not only supports free orchestration and personalized customization, but also ensures rendering performance and smooth interaction in scenarios with a high number of components. Furthermore, it makes page configurations storable, recoverable, and version-manageable, significantly reducing the customization and maintenance costs of large-scale personalized portal systems. Attached Figure Description
[0016] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0017] Figure 1 A flowchart illustrating a portal dynamic orchestration method provided in an embodiment of this application; Figure 2 A schematic diagram of the dynamic and flexible arrangement customization method provided in the embodiments of this application; Figure 3 A schematic diagram of the dynamic and flexible orchestration customization system structure provided in the embodiments of this application. Detailed Implementation
[0018] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. Furthermore, the technical features involved in the various embodiments described below can be combined with each other as long as they do not conflict with each other.
[0019] The terms "first," "second," "third," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.
[0020] Figure 1 A flowchart illustrating a portal dynamic orchestration method provided in this application embodiment is shown below. Figure 1 As shown in the figure, an embodiment of this application provides a portal dynamic orchestration method, which includes the following steps: S1. Construct a visual arrangement interface to support visual operations such as page area division, component dragging and dropping, and attribute configuration; S2. Capture and record the visual operation events on the visual orchestration interface, and generate an operation event sequence; S3. Based on the preset structured configuration description specification, the operation event sequence is parsed and converted into structured configuration data to describe the portal page layout structure, component attributes and interaction logic; S4. Based on the structured configuration data, dynamically generate the corresponding portal page through the rendering engine; S5. The structured configuration data is associated with the user identity information and then stored.
[0021] Specifically, this application proposes a dynamic portal orchestration method that supports differentiated presentation of individual homepages for a unified website publishing scenario. Without altering the website's engineering and publishing structure, it generates an independent personal homepage configuration for each user. When a user accesses the site, the corresponding homepage is dynamically resolved based on the user's identity, thereby achieving a personalized portal presentation for each user within the same website access point. The specific implementation method is as follows: S1. Construct a visual orchestration interface to support visual operations such as page area division, component drag-and-drop, and attribute configuration. In this embodiment, the visual orchestration interface is specifically a visual orchestration canvas. The canvas is divided into four main areas: the left basic data operation panel, which contains three modules. The configuration page module manages multiple canvas data in a tree structure; the component resource module displays the component library maintained by the system in a tiled manner, and users can drag components to the canvas via the drag-and-drop API; the canvas data structure tree module displays the hierarchical relationship of components in the canvas in a structured form; the middle canvas display area serves as the placement and preview area for components, providing drag-and-drop position prompts for quickly building the page structure; the right component configuration panel displays the corresponding configuration form when the user clicks to select a component in the canvas, allowing the user to configure the component's attributes (such as size and color), bind data models, and interaction logic (such as jump links); the top operation bar panel provides overall operation functions for the canvas data, including saving, undoing, copying / pasting / deleting components, and real-time preview.
[0022] S2. Capture and record visual operation events on the visual arrangement interface, generating an operation event sequence. The system captures and processes all user interactions on the arrangement canvas in real time. These operation events include, but are not limited to, component addition, deletion, position adjustment, attribute modification, and data binding. All events are serialized and recorded, and updated to a unified canvas cache data. This mechanism enables the user's entire arrangement process to support undo and redo operations similar to document editing.
[0023] S3. Based on a preset structured configuration description specification, the operation event sequence is parsed and converted into structured configuration data to describe the portal page layout structure, component attributes, and interaction logic. The system parses and converts the current state of the canvas into complete structured configuration data according to a predefined standardized schema. This data is a JSON structure that can completely describe the portal page, specifically including: the hierarchical nesting relationship between the page and components; the layout parameters and style attributes of each component; the data model information bound to each component; and the interaction logic description information of each component. This structured configuration data achieves decoupling between page presentation and business logic, providing a lossless description of the page state.
[0024] S4. Based on the structured configuration data, the corresponding portal page is dynamically generated by the rendering engine. After receiving the structured configuration data, the rendering engine dynamically parses and renders it. The specific process includes: converting the nested structure in the configuration into an HTML DOM node tree; attaching the configuration attributes and styles of each node to the corresponding node; generating the data and interaction logic bound in the configuration into JavaScript code objects and injecting them into the corresponding components, thereby rendering a portal page containing real data and interactive functions. To improve performance, a hybrid rendering architecture combining Canvas and virtual DOM can be adopted, ensuring smoothness through component virtualization and asynchronous computation.
[0025] S5. The structured configuration data is associated with user identity information and then stored. The system persistently stores the generated structured configuration data and associates it with the accessing user's identity information, role permissions, and version metadata. Each user can have their own independent homepage configuration. When a user accesses the site, the system dynamically queries and parses the associated configuration data based on their identity to render a personalized homepage; if the user has not customized, the system reverts to the site's default homepage. This mechanism achieves a dynamic "personalized" presentation based on user identity under the same site access entry point, while supporting configuration rollback and maintenance through version management.
[0026] The portal dynamic orchestration method provided in this application constructs a visual orchestration interface that supports free dragging and real-time preview. It captures user operation events and converts them into structured configuration data that uniformly describes page structure, component attributes, and interaction logic. Based on this configuration data, an engine dynamically renders the page, and the final configuration is stored in association with the user's identity. This enables the generation and dynamic presentation of differentiated personal homepages for a massive number of users without altering the site's engineering and publishing structure. This method decouples the page presentation layer from business logic, achieving a complete description and lossless restoration of the page state through standardized configuration data. It not only supports free orchestration and personalized customization, but also ensures rendering performance and smooth interaction in scenarios with a high number of components. Furthermore, it makes page configurations storable, recoverable, and version-manageable, significantly reducing the customization and maintenance costs of large-scale personalized portal systems.
[0027] Optionally, the portal dynamic orchestration method provided in this application stores the structured configuration data in association with user identity information. When a user accesses the site, the associated structured configuration data is obtained based on the user's identity information, and the corresponding portal homepage is dynamically rendered and generated.
[0028] Optionally, the portal dynamic orchestration method provided in this application embodiment includes a visual orchestration interface comprising a basic operation module, a display module, a component configuration module, and an operation bar module; The basic operation module is used to display a tree structure of draggable component resource library and interface data; The display module is used to receive dragged components and display the page layout; The component configuration module is used to configure the attributes, data, and interactions of the selected component; The operation bar module is used for saving, rewinding, and previewing canvas data.
[0029] Optionally, the portal dynamic orchestration method provided in this application embodiment includes at least one of the following visual operation events: component addition event, component deletion event, component position adjustment event, component attribute modification event, and component data binding event.
[0030] Optionally, the portal dynamic orchestration method provided in this application embodiment includes structured configuration data content such as the hierarchical nesting relationship of page nodes, layout parameters and style attributes of each component, data model binding information, and interaction logic description information.
[0031] Optionally, the portal dynamic orchestration method provided in this application embodiment, wherein dynamically generating the corresponding portal page through a rendering engine specifically includes: The structured configuration data structure is parsed based on the rendering engine, and the nested structure is parsed into HTML DOM nodes; Parse the configuration attributes and styles of each node and attach them to each DOM node; The bound data and corresponding interaction orchestration are generated into a JavaScript code object, which is then passed to the component and rendered into real data and bound to the corresponding interaction logic through a fixed transformation.
[0032] Optionally, in the portal dynamic orchestration method provided in this application embodiment, the structured configuration data is also stored in association with user role information and version metadata to support role-based access control and version management of configuration data.
[0033] Specifically, Figure 2 This is a flowchart illustrating a method for dynamically and flexibly customizing a personalized portal according to one embodiment of this application. The method includes the following steps: S10: Building a Visualized Arrangement Canvas. Provides a user-friendly visual page arrangement interface, supporting page area division, component dragging, zooming, and real-time preview operations for unified arrangement of site pages and personal homepages. The visual arrangement interface is divided into a left-side basic data operation panel, a middle canvas display area, a right-side component configuration panel, and a top operation canvas data panel. The left-side basic data operation panel configures the page module, constructing multiple canvas data through structured tree data, with each node representing an independent canvas data; the component resource module displays the system-maintained component resource library in a tiled manner, and components can be dragged and dropped into the middle canvas using the "dragable" native API; the canvas data structure tree module provides a structured display of the data in the canvas, allowing users to view the hierarchical structure between components.
[0034] The central canvas display area is where components can be dragged and dropped from the component resource library. It provides location hints and placement suggestions for dragging components, allowing you to quickly build a complete page structure.
[0035] The right-hand component configuration panel allows you to drag and drop components onto the canvas and then select them. Once selected, the corresponding component configuration form will appear in the right-hand panel, including attribute configuration (button size, color), data configuration (data model bound to the chart), and interaction configuration (page address to jump to).
[0036] The top operation panel processes the data of the entire canvas, including saving, undoing, copying / pasting / deleting components, previewing, and other related operations. It allows for the maintenance of the overall canvas data and real-time preview of the page effect.
[0037] S20: Capture and record user visual operation events. Real-time capture of all user interactions within the arrangement canvas generates corresponding operation event sequences, including component addition, deletion, position adjustment, attribute modification, and data binding. All canvas data flows to all canvas-built panels. Both the canvas data structure tree module and the component configuration data module use a single set of cached data stored within the build project. Every operation within the interface arrangement involves data changes; the system captures and processes all interactions uniformly, allowing users to easily revert and undo actions throughout the arrangement process, much like editing a document.
[0038] S30: Generate structured configuration data. Based on predefined structured configuration description specifications, the operation event sequence is parsed and converted into standardized configuration data to fully describe the portal page's layout structure, component hierarchy, attribute parameters, data source binding, and interaction logic. The entire canvas data generates a basic nested structure hierarchy JSON based on the drag-and-drop placement position and nesting logic. Then, the component's attribute configuration, bound data, and interaction orchestration are uniformly processed into fixed attributes within the component.
[0039] S40: Page rendering based on configuration data. The rendering engine dynamically generates the portal page based on structured configuration data, enabling real-time preview and final presentation of the page. The rendering engine parses the data structure, converts the nested structure into HTML DOM nodes, then extracts the configuration attributes and styles of each node and mounts them onto each DOM node. Finally, it generates JavaScript code objects from the bound data and related interaction orchestrations, which are then passed to the component and rendered into real data and bound with corresponding interaction logic through fixed transformations.
[0040] S50: Storage and Management of Configuration Data. The generated structured configuration data is persistently stored and associated with user identity, role information, and version metadata for subsequent page restoration, version rollback, and cross-platform adaptation. The system stores the configured canvas data in each page, and the page data is stored in the corresponding project or site. User permissions and usage permissions for relevant components and data models are bound within the relevant project or site to control the data that can be displayed and used on the canvas. Each site has a corresponding version, which can be maintained. Specifying different versions as valid versions enables data version management.
[0041] Figure 3This is a schematic diagram of the structure of a personalized portal dynamic and flexible arrangement customization system according to one embodiment of this application. The system includes a visual arrangement module 100, an event capture and state management module 200, a structured configuration generation module 300, a high-performance rendering module 400, and a configuration storage and version management module 500. The visual arrangement module 100 provides a visual page arrangement canvas, supporting users to freely drag and drop and preview in real time. The event capture and state management module 200 captures user operation events in real time and manages the page state uniformly. The structured configuration generation module 300 generates structured configuration data conforming to predefined specifications based on operation events, and the configuration data is described using a standardized schema. The high-performance rendering module 400 dynamically renders the portal page based on the structured configuration data, supporting smooth interaction in scenarios with a high number of components. The configuration storage and version management module 500 encrypts and stores the configuration data, performs version control, and manages permissions.
[0042] This application binds page arrangement with business roles, component resources, and data strategies to achieve differentiated portal construction for different users and positions. All page arrangements have independent permission configurations for their available resources (component resources, data models, application data, professional system data, etc.), and each user has their own personal homepage customization module, ensuring that different levels and users can quickly customize their personal homepages, achieving a personalized experience for each individual.
[0043] This application employs a hybrid rendering approach combining Canvas and a virtual DOM. Through component virtualization, lazy loading, and asynchronous layout calculations, it significantly improves the smoothness of interaction in complex portal scenarios. The canvas uses Canvas to achieve the final preview rendering effect, and all interactions between components in the interface layout utilize the virtual DOM structure to achieve minimal performance consumption for drag-and-drop, movement, and other operations, ensuring a smooth canvas effect even in complex scenarios.
[0044] This application, through standardized and structured configuration description specifications, completely decouples page presentation from business logic, achieving a complete expression and lossless restoration of page state. All orchestrated data has an independent configuration schema data structure. Page display and interaction logic are all based on the data structure of the configuration data. Each independent page has independent business logic, truly achieving independent page logic within the system. It can handle independent page display and interaction without depending on the overall system's business logic.
[0045] The portal dynamic orchestration method provided in this application is described below with a specific embodiment. In this embodiment, the portal dynamic flexible orchestration customization method is applied to a portal orchestration page scenario of an information system.
[0046] The system supports multiple user roles. After logging into the system, different users need to dynamically arrange personalized portal homepages according to their role permissions, business scenarios, and usage habits.
[0047] 1) Step S110: Initialize the visual arrangement canvas After receiving a user's interface creation request, the system initializes a visual arrangement canvas and loads the corresponding permission configuration based on the user's identity information. This includes: the component resource module only loads the set of component resources that the user has permission to use; the canvas display area is initialized to a blank state; the component configuration panel is in the default configuration state; and the operation bar panel provides basic operation entry points such as save, zoom, center, undo, redo, page preview, and source code preview.
[0048] 2) Step S120: The user performs component drag-and-drop arrangement operations. The user selects a target component from the component resource module and drags it to a designated position in the central canvas display area. The system captures the user's actions in real time during the dragging process, including: drag start event; drag move event; drag release event. Once the component is released to the canvas area, the system automatically calculates the component's layout parameters on the canvas based on its release position and generates a corresponding component placeholder structure on the canvas.
[0049] 3) Step S130: Capture and record visual operation events After a component is dragged and dropped, the system converts this operation into a standardized operation event record and writes it to the canvas state cache data. These operation events include: a component unique identifier generation event; a component addition event; and a component initial position and size parameter recording event. By uniformly capturing and recording these operation events, the canvas can support undo, redo, and state restoration operations during subsequent arrangement.
[0050] 4) Step S140: Component property and data binding configuration After a user selects a component already placed on the canvas, the system displays the corresponding configuration form for that component in the component configuration panel. Users can configure the component through the panel, including but not limited to: component display style attributes; component attribute configuration; component interaction behavior configuration; and component data source binding configuration. When the system detects a change in component attributes or data binding, it synchronously generates a corresponding attribute change event and updates the component configuration data in the canvas cache in real time.
[0051] 5) Step S150: Generate structured configuration data After completing the component orchestration and configuration operations, the system parses the component structure within the canvas based on the current canvas state, generating complete structured configuration data. This structured configuration data includes: the hierarchical nesting relationship between page nodes and component nodes; the layout parameters, styles, and attribute information of each component; the data model binding information corresponding to each component; and the interaction logic description information of each component. This structured configuration data can completely describe the layout structure and behavioral logic of the portal page and can be used for page reconstruction and restoration.
[0052] 6) Step S160: Page rendering based on configuration data The system calls the rendering engine to parse the structured configuration data and dynamically generates the portal page based on the configuration content. During rendering: the page layout structure is converted into the corresponding page node structure according to the configuration data; the display style and interaction logic of each component are dynamically loaded according to the configuration parameters; the bound data model is parsed and injected into the components to realize the display of real data. In this way, the system can generate the corresponding portal page based on the configuration data without a fixed page template.
[0053] 7) Step S170: Configure data storage After the user confirms the current portal page configuration, the system will persistently store the structured configuration data and associate it with the user's identity information to generate an independent personal homepage configuration for each user. When the user visits the site, the system will dynamically parse the corresponding homepage according to the user's identity. When the user has not configured a personal homepage, the system will automatically fall back to the site's default homepage, thereby achieving a personalized portal presentation for each user under the same site link.
[0054] This application also provides a portal dynamic orchestration device, including: The interface building module is used to build a visual layout interface, which supports visual operations such as page area division, component drag and drop, and attribute configuration. An operation capture module is used to capture and record visual operation events on the visual orchestration interface and generate an operation event sequence. The structured module is used to parse and convert the operation event sequence into structured configuration data based on a preset structured configuration description specification, which is used to describe the portal page layout structure, component attributes and interaction logic. The interface generation module is used to dynamically generate the corresponding portal page based on the structured configuration data through the rendering engine; The storage module is used to store the structured configuration data after associating it with the user identity information.
[0055] The method and system described in this application support true free arrangement and real-time preview of portal pages; maintain good interactive performance even in scenarios with a high number of components; enable storable, recoverable, and versionable management of portal page configurations; support personalized portal presentation based on user roles and usage scenarios; reduce the cost of portal system customization and improve system scalability and maintainability.
[0056] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, as well as magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of medium or device suitable for storing instructions and / or data.
[0057] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.
[0058] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.
[0059] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between devices or units may be electrical or other forms.
[0060] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0061] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0062] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.
[0063] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.
[0064] The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Those skilled in the art will readily conceive of embodiments of this disclosure upon considering the specification and practicing the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described herein. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.
[0065] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0066] Those skilled in the art will readily understand that the above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A method for dynamic portal arrangement, characterized in that, Includes the following steps: S1. Construct a visual arrangement interface to support visual operations such as page area division, component dragging and dropping, and attribute configuration; S2. Capture and record the visual operation events on the visual orchestration interface, and generate an operation event sequence; S3. Based on the preset structured configuration description specification, the operation event sequence is parsed and converted into structured configuration data to describe the portal page layout structure, component attributes and interaction logic; S4. Based on the structured configuration data, dynamically generate the corresponding portal page through the rendering engine; S5. The structured configuration data is associated with the user identity information and then stored.
2. The portal dynamic orchestration method as described in claim 1, characterized in that, After the structured configuration data is associated with and stored with the user's identity information, when the user visits the site, the associated structured configuration data is retrieved based on the user's identity information, and the corresponding portal homepage is dynamically rendered and generated.
3. The portal dynamic orchestration method as described in claim 1, characterized in that, The visual orchestration interface includes a basic operation module, a display module, a component configuration module, and an operation bar module; The basic operation module is used to display a tree structure of draggable component resource library and interface data; The display module is used to receive dragged components and display the page layout; The component configuration module is used to configure the attributes, data, and interactions of the selected component; The operation bar module is used for saving, rewinding, and previewing canvas data.
4. The portal dynamic orchestration method as described in claim 1, characterized in that, The visual operation events include at least one of the following: component addition event, component deletion event, component position adjustment event, component attribute modification event, and component data binding event.
5. The portal dynamic orchestration method as described in claim 1, characterized in that, The structured configuration data includes the hierarchical nesting relationship of page nodes, the layout parameters and style attributes of each component, data model binding information, and interaction logic description information.
6. The portal dynamic orchestration method as described in claim 1, characterized in that, The process of dynamically generating the corresponding portal page through the rendering engine specifically includes: The structured configuration data structure is parsed based on the rendering engine, and the nested structure is parsed into HTML DOM nodes; Parse the configuration attributes and styles of each node and attach them to each DOM node; The bound data and corresponding interaction orchestration are generated into a JavaScript code object, which is then passed to the component and rendered into real data and bound to the corresponding interaction logic through a fixed transformation.
7. The portal dynamic orchestration method as described in claim 1, characterized in that, The structured configuration data is also stored in association with user role information and version metadata to support role-based access control and version management of configuration data.
8. A portal dynamic orchestration device, characterized in that, include: The interface building module is used to build a visual layout interface, which supports visual operations such as page area division, component drag and drop, and attribute configuration. An operation capture module is used to capture and record visual operation events on the visual orchestration interface and generate an operation event sequence. The structured module is used to parse and convert the operation event sequence into structured configuration data based on a preset structured configuration description specification, which is used to describe the portal page layout structure, component attributes and interaction logic. The interface generation module is used to dynamically generate the corresponding portal page based on the structured configuration data through the rendering engine; The storage module is used to store the structured configuration data after associating it with the user identity information.
9. A portal dynamic orchestration device, characterized in that, The method includes at least one processing unit and at least one storage unit, wherein the storage unit stores a computer program that, when executed by the processing unit, causes the processing unit to perform the steps of the method according to any one of claims 1 to 7.
10. A storage medium, characterized in that, It stores a computer program executable by a portal dynamic orchestration device, which, when run on the portal dynamic orchestration device, causes the portal dynamic orchestration device to perform the steps of the method according to any one of claims 1 to 7.