A method and system for visualizing platform element management

Abstract

The application belongs to the field of software development and provides a visual platform element management method and system, which comprises the following steps: creating independent namespaces of different elements according to the self space names of the different elements; registering the component identifiers of the corresponding elements in the independent namespaces of the different elements; creating element version numbers according to the component identifiers of the elements; generating specified element registration names with the independent namespaces, the component identifiers and the element version numbers; and managing the elements based on the element registration names. The application generates different namespaces, which facilitates different groups of people to load elements suitable for their own scenarios and created by themselves when using, determines unique element information through the management of unique element identifiers under the namespaces, and effectively controls the version content information of the elements themselves through the management of versions, so that the elements have specific name-oriented content through unique element registration names.

Description

Technical Field

[0001] This invention belongs to the field of software development technology, specifically relating to a method and system for managing components on a visual platform. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] With the rapid development of data visualization platforms, conventional fixed visualization dashboards are increasingly constrained, making it impossible to quickly build a suitable visualization dashboard or platform for one's own scenario. Driven by this situation, custom visualization platforms have gradually emerged. Along with the output of visualization platforms, there are also essential components for building the platform. As the content scenarios increase, the data of the components will increase in order to adapt to more scenarios and content. At this time, the standardization and management of the components become particularly important. How to manage complex and diverse components has become a necessary problem. Summary of the Invention

[0004] To address the aforementioned issues, this invention proposes a visual platform component management method and system. This invention generates different namespaces, allowing different users to load components suitable for their own scenarios and belonging to their own created space. By managing unique component identifiers within a space, unique component information can be determined. Version management can effectively control the version content information of the component itself. Through a unique component registration name, the component has specific name-related content.

[0005] According to some embodiments, the first aspect of the present invention provides a visual platform component management method, which adopts the following technical solution:

[0006] A visual platform component management method includes:

[0007] Create independent namespaces for different components based on their own namespace names;

[0008] Register the component identifiers of the corresponding components within their independent namespaces;

[0009] Create a component version number based on the component's component identifier;

[0010] Generate a specified component registration name with an independent namespace, component identifier, and component version number;

[0011] Component management is implemented based on the component registration name.

[0012] Furthermore, the field format of the independent namespace is @+its own namespace name.

[0013] Furthermore, the independent namespace of each component spatially isolates all the unordered components, allowing different components to be loaded according to different directories.

[0014] Furthermore, the management of components based on their registration names includes:

[0015] The component's own namespace is determined by its own namespace name, and the component is loaded based on its own namespace to distinguish the component's content.

[0016] Different versions of the same type of component are distinguished based on the component's component identifier;

[0017] When a component is updated, the component's version number is used to determine whether to iterate the component version.

[0018] Furthermore, when a component is updated, the system determines whether to iterate on the component version based on the component's version number, including:

[0019] If the version number of a component changes, an iteration is performed to generate a new version number, while retaining the original component version and the latest component version. The component is then loaded with the latest component version and an iteration notification is pushed to the user.

[0020] If the version number of a component is the same as the previous version number, no iteration is performed. Instead, the latest data of the component is saved under the original version number of the component, and the latest component content is updated.

[0021] Furthermore, when iterating over component versions, the earliest component version will not overwrite the original component version. The latest component version and the original component version exist independently in different packages based on the component's version number.

[0022] Furthermore, when a component is updated, the front end will select the latest version under the same component identifier to display.

[0023] According to some embodiments, the second aspect of the present invention provides a visual platform component management system, which adopts the following technical solution:

[0024] A visual platform component management system, comprising:

[0025] The component-independent namespace creation module is configured to create independent namespaces for different components based on their own namespace names.

[0026] The component unique identifier creation module is configured to register the component identifiers of corresponding components in independent namespaces for different components;

[0027] The component version creation module is configured to create a component version number based on the component's component identifier;

[0028] The component registration name creation module is configured to generate a specified component registration name with an independent namespace, component identifier, and component version number.

[0029] The component management module is configured to manage components based on their registration names.

[0030] According to some embodiments, a third aspect of the present invention provides a computer-readable storage medium.

[0031] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of a visualization platform component management method as described in the first aspect above.

[0032] According to some embodiments, a fourth aspect of the present invention provides a computer device.

[0033] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the steps of a visualization platform component management method as described in the first aspect above.

[0034] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0035] 1. Compared with the original unified storage and management of component information, this invention generates different namespaces, which makes it easier for different users to load components suitable for their own scenarios and their own created space. This makes the usage process more directional and specific, eliminates the need to load redundant content, reduces the pressure on API interfaces and component data downloads, and improves the user experience.

[0036] 2. This invention identifies unique component information by managing unique component identifiers within a spatial domain. This provides targeted guidance for all other behaviors of the component. The identifier ensures that the corresponding component is loaded during the loading process, reducing performance overhead during use.

[0037] 3. The version management of this invention, namely [Major.Minor.Patch], can effectively control the version information of the component itself, determine whether to perform update and iteration operations, and better constrain the overall external display and upgrade management of the component.

[0038] 4. This invention uses a unique component registration name to give the component specific name-directed content. This allows the visualization platform to better target the component itself and load and retrieve the package or content of the unique component. Attached Figure Description

[0039] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0040] Figure 1 This is a flowchart of a visual platform component management method according to an embodiment of the present invention. Detailed Implementation

[0041] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0042] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0043] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0044] Where there is no conflict, the embodiments and features in the embodiments of the present invention can be combined with each other.

[0045] Terminology Explanation:

[0046] Visualization Platform: A tool for quickly generating rich visualization applications through a graphical interface and action configuration. Based on the design principles of low barrier to entry and high scalability, it enables data visualization for various business scenarios.

[0047] Components: Independent entities that present data and content in the form of graphics, charts, or text, enabling visual operations.

[0048] Example 1

[0049] like Figure 1As shown, this embodiment provides a method for managing components on a visual platform. This embodiment uses the application of this method to a server as an example for illustration. It is understood that this method can also be applied to terminals, and can also be applied to systems including terminals, servers, and other components, achieving component management through interaction between the terminal and the server. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network servers, cloud communication, middleware services, domain name services, CDN security services, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, smart speaker, smartwatch, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, which is not limited herein. In this embodiment, the method includes the following steps:

[0050] Create independent namespaces for different components based on their own namespace names;

[0051] Register the component identifiers of the corresponding components within their independent namespaces;

[0052] Create a component version number based on the component's component identifier;

[0053] Generate a specified component registration name with an independent namespace, component identifier, and component version number;

[0054] Component management is implemented based on the component registration name.

[0055] The management of components based on their registration names includes:

[0056] The component's own namespace is determined by its own namespace name, and the component is loaded based on its own namespace to distinguish the component's content.

[0057] Different versions of the same type of component are distinguished based on the component's component identifier;

[0058] When a component is updated, the component's version number is used to determine whether to iterate the component version.

[0059] When a component is updated, the system determines whether to iterate on the component version based on the component's version number, including:

[0060] If the version number of a component changes, an iteration is performed to generate a new version number, while retaining the original component version and the latest component version. The component is then loaded with the latest component version and an iteration notification is pushed to the user.

[0061] If the version number of a component is the same as the previous version number, no iteration is performed. Instead, the latest data of the component is saved under the original version number of the component, and the latest component content is updated.

[0062] Specifically, such as Figure 1 As shown, the process of the method described in this embodiment specifically includes:

[0063] 1. Use namespaces to define component namespaces with special formats.

[0064] Create fields in the format (@+namespace name) to define the namespace of components. This isolates all unordered components spatially, loading different components according to different directories. This achieves component-level isolation, content-level isolation, and scenario-level isolation within each different content area and development zone. When using components, the component with the namespace (@+namespace name) can be loaded from its respective namespace based on different scenarios and development accounts.

[0065] Each component is guaranteed to be in a specific, independent space, distinguished by (@ + its own space name). This ensures that each component loaded by an individual using the visualization platform is in its own specific space, avoiding the waste of APIs and download resources during component loading. At the same time, the loaded components are perfectly suited to the user, improving efficiency.

[0066] 2. Register a unique component identifier under the (@+your_space_name) space.

[0067] Within a predefined namespace, components are created and unique component identifiers are registered to ensure their uniqueness within the namespace. This allows for precise identification of components categorized by their unique identifiers, enabling operations such as front-end loading and dynamic display of the specified components.

[0068] 3. Management of component version [Major.Minor.Patch]

[0069] In the component management within the visualization platform, component iteration and upgrades are a common occurrence, making component version management particularly important. Here, a component version is created as version-[Major.Minor.Patch], forming a unique version identifier for the current component. After a component is modified, the version version-[Major.Minor.Patch] will be used to determine whether to iterate and provide a notification for the component.

[0070] This ensures the rigor of component version iteration, providing two different update modes: overwriting the original version and generating a new version. The frontend selects the latest version for display within the same component. During component upload, the `cover` field is used to determine whether version iteration is required, and `version-[Major.Minor.Patch]` is used to verify its validity. The existence of `version-[Major.Minor.Patch]` imposes strict version constraints on the component itself. In actual use, new and old versions of components do not affect each other, existing independently as separate packages through the version identifier `version-[Major.Minor.Patch]`.

[0071] 4. Generate unique component registration names using unified utility functions.

[0072] The component is identified by its namespace (@ + its own namespace name) and version (version - [Major.Minor.Patch]). A unified utility function is used to generate a unique component registration name, i.e., $namespace_$component_[Major.Minor.Patch]. After creating the unified registration name, when loading the component, the registration name will be used to generate the content and information of the specified unique component package.

[0073] By specifying a function, a unique component registration name is generated, consisting of a space (@+self space name), an identifier component, and a version (version-[Major.Minor.Patch]). This ensures that each component has a unique registration name, facilitating component management. Furthermore, during loading, the specified component content can be loaded using the registration name, allowing the visualization platform to retrieve unique components. This improves API loading efficiency and reduces resource waste during component downloads.

[0074] The components in the visualization data platform are developed, managed, and used in the manner described above. When there are many components, their respective component spaces are determined by (@+self-space name), such as @+usr, to load components under @+usr, thus differentiating component content and facilitating their use in the visualization data platform. The component identifier (component) is used to distinguish different versions of the same type of component. Combined with the version number (version-[Major.Minor.Patch]), this creates a system where the latest version is displayed, and older and newer versions can coexist without affecting each other, preventing the corruption of older data.

[0075] Example 2

[0076] This embodiment provides a visual platform component management system, including:

[0077] The component-independent namespace creation module is configured to create independent namespaces for different components based on their own namespace names.

[0078] The component unique identifier creation module is configured to register the component identifiers of corresponding components in independent namespaces for different components;

[0079] The component version creation module is configured to create a component version number based on the component's component identifier;

[0080] The component registration name creation module is configured to generate a specified component registration name with an independent namespace, component identifier, and component version number.

[0081] The component management module is configured to manage components based on their registration names.

[0082] The examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the content disclosed in Embodiment 1 above. It should be noted that the above modules, as part of the system, can be executed in a computer system such as a set of computer-executable instructions.

[0083] The descriptions of each embodiment in the above embodiments have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0084] The proposed system can be implemented in other ways. For example, the system embodiments described above are merely illustrative, and the division of modules described above is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system, or some features may be ignored or not executed.

[0085] Example 3

[0086] This embodiment provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of a visualization platform component management method as described in Embodiment 1 above.

[0087] Example 4

[0088] This embodiment provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps in the visualization platform component management method described in Embodiment 1 above.

[0089] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of hardware embodiments, software embodiments, or embodiments combining software and hardware aspects. Furthermore, the present invention 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 and optical storage) containing computer-usable program code.

[0090] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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 illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0091] 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.

[0092] 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.

[0093] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0094] While the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, this is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.

Claims

1. A method for managing components on a visual platform, characterized in that, include: Create independent namespaces for different components based on their own namespace names; The field format of the independent namespace is @+its own namespace name; Each component's independent namespace spatially isolates all the unordered components. Different components are loaded according to different directories, achieving component isolation, content isolation, and scenario isolation within each different content area and development zone. When a component is used, the component with the namespace "@" plus its own namespace name is loaded according to different scenarios and development accounts. Register the component identifiers of the corresponding components within their independent namespaces; Create a component version number based on the component's component identifier; Generate a specified component registration name with an independent namespace, component identifier, and component version number; Component management is implemented based on component registration names, including: The component's own namespace is determined by its own namespace name, and the component is loaded based on its own namespace to distinguish the component's content. Different versions of the same type of component are distinguished based on the component's component identifier; When a component is updated, the component's version number is used to determine whether to iterate the component version. When a component is updated, the system determines whether to iterate on the component version based on the component's version number, including: If the version number of a component changes, an iteration is performed to generate a new version number, while retaining the original component version and the latest component version. The component is then loaded with the latest component version and an iteration notification is pushed to the user. When iterating over component versions, the earliest component version will not overwrite the original component version. The latest component version and the original component version exist independently in different packages based on the component version number. When a component is updated, the front end will select the latest version under the same component identifier to display; If the version number of a component is the same as the previous version number, no iteration is performed. Instead, the latest data of the component is saved under the original version number of the component, and the latest component content is updated.

2. A visual platform component management system, employing the visual platform component management method as described in claim 1, characterized in that, include: The component-independent namespace creation module is configured to create independent namespaces for different components based on their own namespace names. The component unique identifier creation module is configured to register the component identifiers of corresponding components in independent namespaces for different components; The component version creation module is configured to create a component version number based on the component's component identifier; The component registration name creation module is configured to generate a specified component registration name with an independent namespace, component identifier, and component version number. The component management module is configured to manage components based on their registration names.

3. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps in the visual platform component management method as described in claim 1.

4. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps in the visual platform component management method as described in claim 1.

Images