CN114090083B - Visual component configuration method, device, equipment and storage medium - Google Patents
Visual component configuration method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114090083B CN114090083B CN202010760646.5A CN202010760646A CN114090083B CN 114090083 B CN114090083 B CN 114090083B CN 202010760646 A CN202010760646 A CN 202010760646A CN 114090083 B CN114090083 B CN 114090083B
- Authority
- CN
- China
- Prior art keywords
- component
- target
- client
- page
- adapter
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
- G06F16/986—Document structures and storage, e.g. HTML extensions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4416—Network booting; Remote initial program loading [RIPL]
Abstract
The embodiment of the application provides a visual component configuration method, a visual component configuration device and a visual component storage medium, wherein the visual component configuration method comprises the following steps: when a client initiates a page, determining the identification of a view element on the page; determining component configuration data bound with the view element according to the identification of the view element, wherein the component configuration data comprises component identification and component attribute information; acquiring a target component class of the page according to the component identifier; the target component class is obtained from a component server for updating the component; calling an analysis engine, and performing instantiation rendering according to the component attribute information and the target component class to obtain a target page; thus, when updating the component, the user can complete the updating of the component without additional operations.
Description
Technical Field
The present application relates to the field of component configuration, and relates to, but is not limited to, a method, an apparatus, a device, and a storage medium for configuring a visual component.
Background
The related art has the following problems in a way of generating a page by dynamic component configuration: the implementation of the configuration engine, the parsing engine and the components inside the page is static when publishing and packaging, which has a great disadvantage for using common components, especially open source components, for a large number of items, and when the logic inside the components has a problem and needs to be updated, all related items need to be updated and packaged again for repair, and then related components are reissued or manually replaced, which lacks enough flexibility.
Disclosure of Invention
In view of this, embodiments of the present application provide a method, an apparatus, a device, and a storage medium for configuring a visual component.
The technical scheme of the application is realized as follows:
the embodiment of the application provides a visual component configuration method, which comprises the following steps:
when a client initiates a page, determining the identification of a view element on the page;
determining component configuration data bound with the view element according to the identification of the view element, wherein the component configuration data comprises component identification and component attribute information;
acquiring a target component class of the page according to the component identifier; the target component class is obtained from a component server for updating the component;
and calling an analysis engine, and performing instantiation rendering according to the component attribute information and the target component class to obtain a target page.
The embodiment of the application provides a visual component configuration method, which comprises the following steps:
when the adapter and the component have upgrading requirements, the component server receives the uploaded component and adapter; the adapter is used for carrying out class packaging on the components according to the development modes of the components to obtain component classes so that the client can be compatible with the components in different development modes;
Establishing full duplex connection with a client;
receiving a loading component request and a loading adapter request sent by the client;
responding to the loading component request, and sending a first file path to the client so that the client accesses the first file path to obtain a target component;
and responding to the loading adapter request, and sending a second file path to the client so that the client accesses the second file path to obtain the target adapter.
The embodiment of the application provides a visual component configuration device, which comprises:
the first determining module is used for determining the identification of the view element on the page when the page is initialized;
a second determining module, configured to determine component configuration data bound to the view element according to the identifier of the view element, where the component configuration data includes a component identifier and component attribute information;
the acquisition module is used for acquiring the target component class of the page according to the component identifier; the target component class is obtained by obtaining an updated adapter from a component server and encapsulating the updated target component obtained from the component server according to a development mode of the target component;
And the rendering module is used for carrying out instantiation rendering according to the component attribute information and the target component class to obtain a target page.
The embodiment of the application provides a visual component configuration device, which comprises:
the second receiving module is used for receiving the uploaded component and the uploaded adapter when the adapter and the component have upgrading requirements; the adapter is used for carrying out class packaging on the components according to the development modes of the components to obtain component classes so that the client can be compatible with the components in different development modes;
the establishing module is used for establishing full duplex connection with the client;
the third receiving module is used for receiving the loading component request and the loading adapter request sent by the client;
the first sending module is used for responding to the loading component request and sending a first file path to the client so that the client accesses the first file path to obtain a target component;
and the second sending module is used for responding to the loading adapter request and sending a second file path to the client so that the client accesses the second file path to obtain a target adapter.
The embodiment of the application provides a computer device, which comprises a memory and a processor, wherein the memory stores a computer program which can be run on the processor, and the processor realizes the steps in the method when executing the program.
Embodiments of the present application provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the above method.
In the embodiment of the application, after the client side is initialized, the updated target component class is obtained from the component server side by calling; and then, calling an analysis engine, and performing instantiation rendering according to the target component class to obtain a target page. In the technical scheme provided by the embodiment of the application, a component server is newly added relative to the related technology, and is used for realizing the management and updating of the components; thus, when updating the component, the user can complete the updating of the component at the time of initialization without additional operations.
Drawings
In the drawings (which are not necessarily drawn to scale), like numerals may describe similar components in different views. Like reference numerals having different letter suffixes may represent different instances of similar components. The drawings illustrate generally, by way of example and not by way of limitation, various embodiments discussed herein.
FIG. 1 is a schematic diagram of a dynamic component configuration generation page in the related art.
Fig. 2 is a schematic implementation flow chart of a visual component configuration method according to an embodiment of the present application.
Fig. 3 is a schematic diagram of a composition structure of a visual component configuration system based on a dynamic loading technique according to an embodiment of the present application.
Fig. 4 is a schematic diagram of the composition structure of a visual component configuration device according to an embodiment of the present application.
Fig. 5 is a schematic diagram of the composition structure of a visual component configuration device according to an embodiment of the present application.
Fig. 6 is a schematic diagram of a hardware entity of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the following detailed description of the specific technical solutions of the present application will be given with reference to the accompanying drawings in the embodiments of the present application. The following examples are illustrative of the application and are not intended to limit the scope of the application.
In the following description, suffixes such as "module" or "unit" for representing elements are used only for facilitating the description of the present application, and have no specific meaning per se. Thus, "module" or "unit" may be used in a hybrid.
At present, related technologies in the field of dynamic component configuration, for example, the configuration of a dynamic form is to drag a component to a configuration interface in a dragging mode, change layout attributes, change the appearance and layout of the component by component object attributes, and then save the related attributes as data for persistence; the interface dynamically generates an expected interface by reading relevant component configuration data (including component identification and component style attribute) and combining the analysis engine during display. In the process, the new addition, modification and release of the online use view control are realized through the configuration interface, so that the working efficiency and the flexibility of service support are improved, the manpower and time investment of research personnel are reduced, and the cost is reduced.
The manner of generating the page by dynamic component configuration in the related art is shown in fig. 1, the interface on the client side comprises a configuration interface 10 and a presentation interface 20, the configuration interface 10 comprises a configuration engine 11 and a component file (component or component set) 12, wherein the component file 12 comprises a common component 13; the presentation interface 20 includes a parsing engine 21 and a component file 22, wherein the component file 22 includes a common component 23.
When the configuration of the components is completed by the configuration engine 11 at the configuration interface 10, the configuration data of the components are saved, and in the implementation process, the configuration data of the components can be saved at the data server. And when the target display page is displayed, the stored component configuration data is read, and the analysis engine renders the identification of the page view element by using the read component configuration data to obtain the target display page.
The manner in which the dynamic component configuration provided in FIG. 1 generates pages has several problems: 1) The implementation of the configuration engine, the parsing engine and the component internal of the page is static when publishing and packaging, which has a great disadvantage for using public components, especially open source components, for a large number of items, when the internal logic of the component has a problem and needs to be updated, the packaging of all relevant items is updated again for repair, and then related component files are reissued or manually replaced, which lacks enough flexibility. 2) A single development mode is adopted, and components developed in different development modes cannot be compatible (for example: the configuration interface developed based on the Vue mode cannot be compatible with the component developed based on the React mode, and in view of the diversification of the mainstream development modes in the current web front-end technical field, the mode lacks sufficient compatibility. 3) The rendering mechanism of the page view cannot be dynamically changed after loading is completed, so that the client interface needs to be refreshed again when updating is needed, and enough usability is lacked.
Example 1
The present embodiment proposes a visual component configuration method, which is applied to a computer device, where the functions implemented by the method may be implemented by a processor in the computer device calling program code, and of course the program code may be stored in a computer storage medium, where the computer device includes at least a processor and a storage medium.
Fig. 2 is a schematic flow chart of an implementation of a method for configuring a visual component according to an embodiment of the present application, as shown in fig. 2, where the method includes:
step S201, when a client side initializes a page, determining the identification of view elements on the page;
in some embodiments, the page initialization is initiated when a user opens a page, which may be considered a particular page (i.e., a target page), and thus, the identity of the view element on the page may be determined.
In other embodiments, step S201 includes: when initializing a page, reading page configuration data generated and stored by a configuration engine from a configuration server, wherein the page configuration data comprises view elements contained in the page; and determining the identification of the view elements contained in the page according to the read page configuration data.
Step S202, determining component configuration data bound with the view element according to the identification of the view element, wherein the component configuration data comprises component identification and component attribute information;
the component attribute information includes layout attributes of the components and style attributes of the components.
Step S203, obtaining a target component class of the page according to the component identifier; the target component class is obtained from a component server for updating the component;
in some embodiments, the target component class is obtained by calling an adapter updated from a component server and encapsulating the updated target component obtained from the component server according to a development mode of the target component; the component server is newly added in the related technology and is used for realizing the management and updating of the components. It can be seen that, according to the technical scheme provided by the embodiment of the application, the adapter encapsulates the updated target component according to the development mode of the target component to obtain a target component class, and then invokes the parsing engine to perform instantiation rendering according to the component attribute information and the target component class to obtain a target page; therefore, the problem that a single development mode in the related technology cannot be compatible with components developed in different development modes can be solved, and the compatibility is improved.
The adapter and the target component can be obtained from the component server side during initialization, or can be obtained from the component server side in a page opening state after the initialization, that is, the technical scheme provided by the embodiment of the application can realize dynamic component replacement, and the updating of the component can be completed both during the initialization and in the page opening state after the initialization.
Here, the obtaining the target component class may be requested from the component server, or may be found locally, where it is to be noted that the local finding is a component file requested from the component server during initialization, where the component file includes many components, and of course includes a target component of the target page, where the target component class is obtained by calling an adapter and encapsulating the components in the component file according to a development mode of the components.
The development modes of the component may include, for example: a Vue mode, a reaction mode, and the like.
Step S204, calling a parsing engine, and performing instantiation rendering according to the component attribute information and the target component class to obtain a target page.
In general, the solution provided in the embodiment of the present application may be applied to a browser/server (C/S) architecture, and may also be applied to a client/server (C/S) architecture, where a browser and a client in the two architectures will be collectively referred to as a client in the embodiment of the present application.
In the related art, when there is a component to be upgraded in the browser/server architecture, it is necessary for the user to manually refresh the component, and if the component is not refreshed, the page opened by the user is problematic. In client/server architectures, if there are components to be upgraded, the reloading of the upgrade is complete, which is cumbersome and time consuming, even if the most conventional way today is an over-mount.
The technical scheme provided by the embodiment of the application obtains the updated target component class from the component server by calling; and then, calling an analysis engine, and performing instantiation rendering according to the target component class to obtain a target page. Therefore, in the technical scheme provided by the embodiment of the application, compared with the related technology, the component server is newly added and is used for realizing the management and updating of the components; therefore, the related art user needs one more step to manually refresh or reload to realize, and the technical scheme provided by the embodiment of the application does not need redundant steps for the user and is completely unaware.
The present embodiment proposes a visual component configuration method, which is applied to a computer device, where the functions implemented by the method may be implemented by a processor in the computer device calling program code, and of course the program code may be stored in a computer storage medium, where the computer device includes at least a processor and a storage medium.
The visual component configuration method provided by the embodiment of the application comprises the following steps:
step S301, when a client initiates a page, determining the identification of a view element on the page;
before step S301, the component server receives the uploaded component and adapter when the adapter and the component have upgrading requirements; the adapter is used for carrying out class packaging on the components according to the development modes of the components to obtain component classes so that the client can be compatible with the components in different development modes; here, when the page is initialized, the client establishes full duplex connection with the component server.
Step S302, the client determines component configuration data bound with the view element according to the identifier of the view element, wherein the component configuration data comprises component identifiers and component attribute information;
step S303, the client requests a target component and a target adapter corresponding to the component identifier from the component server;
in some embodiments, the requesting the component server for the target component and the target adapter corresponding to the component identifier includes: sending a component loading request and an adapter loading request which both carry the component identification to a component server; receiving a first file path returned by the component server in response to the loading component request and a second file path returned by the loading adapter request respectively; and respectively accessing the first file path and the second file path to correspondingly obtain the target assembly and the target adapter.
Correspondingly, the component server receives a component loading request and an adapter loading request sent by the client; responding to the loading component request, and sending a first file path to the client by the component server side so that the client accesses the first file path to obtain a target component; and responding to the adapter loading request, and sending a second file path to the client by the component server side so that the client accesses the second file path to obtain the target adapter. In another embodiment, the load component request and the load adapter request both carry component identification; the first file path is a path for storing the component corresponding to the component identifier, and the second file path is a path for storing the adapter corresponding to the component identifier.
In other embodiments, the requesting the component server for the target component and the target adapter corresponding to the component identifier includes: when the client side initializes the page, reading service configuration information of the page; and sending a component loading request and an adapter loading request which both carry the component identifier to the component server according to the service configuration information of the page. The service configuration information is used for indicating the service end information stored by the component to be requested and the adapter, so that the component and the adapter can be requested from the corresponding component service end according to the service configuration information.
In some embodiments, when the client initiates a page, reading service configuration information of the page includes: when the client initiates the page, the client establishes connection with a data server to obtain a storage path; obtaining service configuration information of the page by accessing the storage path; or the client reads the service configuration information of the page from the local when the page is initialized.
In other embodiments, the requesting the component server for the target component and the target adapter corresponding to the component identifier includes: when the client side initializes the page, reading service configuration information of the page; according to the service configuration information of the page, sending a component loading request and an adapter loading request which both carry the component identifier to a component server; receiving a first file path returned by the component server in response to the loading component request and a second file path returned by the loading adapter request respectively; and respectively accessing the first file path and the second file path to correspondingly obtain the target assembly and the target adapter.
Step S304, the client calls the target adapter, and class packaging is carried out on the target component according to the development mode of the target component, so as to obtain a target component class;
here, the above-described step S303 and step S305 actually provide a way to implement the step of "acquiring the target component class of the page according to the component identifier".
Step S305, the client calls a parsing engine, and performs instantiation rendering according to the component attribute information and the target component class to obtain a target page.
The embodiment of the application provides a process for realizing component compatibility upgrade through a dynamic replacement adapter, which comprises the following steps: the client side initializes and establishes connection with the component server side; the client sends a request for acquiring the component and the adapter to the component server; the component server returns the component and the adapter, and the client reads the component and the adapter; the client parses the component and renders into view elements according to the parsing engine and the adapter. When an adapter and a component have upgrading requirements, the component server receives the uploaded component and adapter; the client realizes compatibility upgrade through the non-perception replacement adapter file; the client performs view rendering mechanism non-aware updating through the non-aware replacement component in combination with the adapter.
The present embodiment proposes a visual component configuration method, which is applied to a computer device, where the functions implemented by the method may be implemented by a processor in the computer device calling program code, and of course the program code may be stored in a computer storage medium, where the computer device includes at least a processor and a storage medium.
The visual component configuration method provided by the embodiment of the application comprises the following steps:
step S401, when the adapter and the component have upgrading requirements, the component server receives the uploaded component and adapter; the adapter is used for carrying out class packaging on the components according to the development modes of the components to obtain component classes so that the client can be compatible with the components in different development modes;
here, the component server may receive some specific components, for example, a target component on a certain page, and may also be many components.
Step S402, when the client side initializes the page, the client side establishes full duplex communication connection with the component server side;
step S403, the client determines the identity of the view element on the page;
step S404, the client determines component configuration data bound with the view element according to the identifier of the view element, wherein the component configuration data comprises component identifiers and component attribute information;
In some embodiments, the component configuration data may be stored at a data server from which the client obtains the component configuration data by request. In other embodiments, it may also be stored locally.
In step S405, the component server establishes a full duplex connection with the client, and sends an update notification to the client that has established the full duplex communication connection, where the update notification includes an identifier of the component to be updated.
Step S406, the client receives an update notification broadcasted by the component server, where the update notification includes a component identifier of the component to be updated;
step S407, when the client detects that the component identifier of the component to be updated is the same as the component identifier in the component configuration data, an update request is sent to the component server, where the update request carries the component identifier;
step S408, the component server receives a component loading request and an adapter loading request sent by the client;
here, if the component identifier is carried in the component loading request and the component loading adapter request, the component server may consider that the client requests a specific component (i.e., a target component) corresponding to the component identifier and a specific adapter (i.e., a target adapter) corresponding to the component identifier. In another embodiment, if the component identifier is not carried in the component loading request and the component loading adapter request, the component server side sends the updated component and/or the updated adapter to the client side.
Step S409, the component server responds to the loading component request and sends a first file path to the client so that the client accesses the first file path to obtain a target component;
in step S410, the component server sends a second file path to the client in response to the loading adapter request, so that the client accesses the second file path to obtain the target adapter.
In some embodiments, the load component request and the load adapter request both carry component identification; the first file path is a path for storing the component corresponding to the component identifier, and the second file path is a path for storing the adapter corresponding to the component identifier.
Step S411, the client receives the file path and development mode of the component to be updated returned by the component server in response to the update request;
in step S412, the client accesses the file path of the component to be updated to obtain the updated target component.
Here, steps S406 to S412 provide a way to implement "the target component is requested to the component server according to the component identifier, at least after updating".
Step S413, the client calls a target adapter corresponding to the target component, and class packaging is carried out on the updated target component according to the development mode of the updated target component to obtain a target component class;
Here, step S413 provides a way to implement step "acquire the target component class of the page according to the component identifier".
Step S414, the client calls a parsing engine, and performs instantiation rendering according to the component attribute information and the target component class to obtain a target page.
In other embodiments, the method further comprises: and the client saves the updated target component according to the component instance of the updated component corresponding to the component identifier.
The present embodiment proposes a visual component configuration method, which is applied to a computer device, where the functions implemented by the method may be implemented by a processor in the computer device calling program code, and of course the program code may be stored in a computer storage medium, where the computer device includes at least a processor and a storage medium.
The visual component configuration method provided by the embodiment comprises the following steps:
step S501, when the adapter and the component have upgrading requirements, the component server receives the uploaded component set and adapter; the adapter is used for carrying out class packaging on the components according to the development modes of the components in the component set to obtain component classes, so that the client can be compatible with the components in different development modes;
Step S502, when the client side initializes the page, the service configuration information is read;
step S503, the client requests the component set and the adapter to the component server according to the service configuration information;
step S504, the component server returns the component set and the adapter to the client;
in step S505, the client calls the adapter, and encapsulates the corresponding component according to the development mode of each component in the component set, so as to obtain the component class of the component set.
Step S506, the client determines the identification of the view element on the page;
step S507, the client determines component configuration data bound with the view element according to the identifier of the view element, wherein the component configuration data comprises component identifiers and component attribute information;
step S508, the client determines the target component class from the component classes in the loaded component set according to the component identification;
here, a way of implementing "get target component class of the page according to the component identification" is provided.
Step S509, the client calls a parsing engine, and performs instantiation rendering according to the component attribute information and the target component class to obtain a target page.
In the embodiment of the application, the internal logic of the component is separated from the client by designing a component service model, a broadcasting mechanism is established with the client through full duplex communication connection, all the client is actively informed of updating related component files when the updating of the component of the server is observed, and meanwhile, an adaptation mechanism is established to realize the compatibility of the client to components based on different development modes.
Fig. 3 is a schematic structural diagram of a visual component configuration system based on a dynamic loading technique according to an embodiment of the present application, and as shown in fig. 3, the system includes: a server and a client, wherein the server comprises a data server 30 and a component server 40, the client comprises a configuration client (which can be understood as a configuration interface 50) and a presentation client (which can be understood as a presentation interface 60), wherein: the configuration client 50 and the presentation client 60 each include a component file and an adapter file, the configuration client further includes a configuration engine, and the presentation client further includes a parsing engine. It should be noted that, the client may be a computer device, for example, a mobile phone, a personal computer, or other devices with information processing capability; the component server and the data server are logically divided and can be located on the same hardware entity. In implementation, the server may also be a computer device, for example, a personal computer, a server, or a device with information processing capability.
1) Configuration client
And the configuration client is used for configuring and storing the identification of the view element required by the pre-display interface, the component identification of the component to which the view element belongs and the component attribute information. The component attribute information comprises layout attributes of components and style attributes of the components;
and initializing and reading service configuration information by the client interface, and respectively initiating a component file loading request and an adapter file loading request to a designated component server according to the service configuration information. Rendering logic of view components based on different development modes can be effectively and correctly identified through a configuration engine and an internal mechanism of an adapter after loading is completed, so that a conversion process from component files to page view element presentation is realized. In addition, the visual configuration of the page view elements is carried out by using a dragging mode, the layout attribute and the style attribute of the elements are modified, and the modified elements are saved as page configuration data and interacted with a data server to realize persistence storage.
2) Display client
The configuration client is used for analyzing and rendering view elements of the pre-display interface.
The initialization mode of the client interface is consistent with the description in the configuration client, after the component files and the adapter files are read and loaded to the component server, page configuration data stored in the configuration client are read to the data server, then the internal implementation mechanism of the adapter is read through the analysis engine in the same analysis mode as that in the function 1, and the view elements are analyzed and rendered for the components of different types.
3) Component server
The server side mainly provides management functions such as component file loading service, deletion and verification.
The server side provides management and classification functions for the component files in an interface visual operation mode, has management functions of adding, deleting, modifying, inquiring, importing, exporting and the like, performs unified management on components used by all clients, and improves maintainability of the components. In addition, the permission classification is carried out for the permission levels of different clients, so that the configuration client and the display client are allowed to read the components corresponding to the permission levels.
In addition, a broadcast notification mechanism is realized by configuring the client, displaying the full duplex communication connection between the client and the component server, and when the component server component and the adapter maintenance version are updated, the client which has established the connection is notified to perform the update request to replace the component file.
A first part:
the process of achieving component compatibility upgrades by dynamically replacing an adapter is as follows:
step 1, a client side initially reads service configuration information and establishes connection to a component server side according to the service configuration information; the service configuration information comprises an address of a component server used for acquiring a component file and an adapter;
Step 2, the client sends a request for acquiring the component and the adapter to the component server;
step 3, the component server returns the component file and the adapter file, and the client reads the component file and the adapter file;
step 4, the client analyzes the component file according to the analysis engine and the adapter file and renders the component file into view elements;
step 5, when the adapter and the component updating requirement exists, the component server uploads a component file and an adapter file to be updated;
step 6, the client realizes compatibility upgrade through the non-perception replacement adapter file;
and 7, the client performs non-perception updating of the view rendering mechanism through the non-perception replacement component and the adapter.
It should be noted that the file type of the component may be js or the like that can be effectively identified by the presentation end.
A second part:
the process of realizing the non-perception replacement of the view rendering file through the broadcasting mechanism is as follows:
step 11, initializing a client and establishing full duplex communication connection with a component server;
step 12, uploading a component file to be updated on a page provided by a user at a component server;
step 13, the component server acquires the updated component file;
step 14, triggering a notification action after the component server detects the update of the component file;
Step 15, the component server detects the client end which has established the full duplex communication connection and sends an update notification, and the notification content contains the identification of the component to be updated;
step 16, the client initiates an update request to the component server after receiving the update notification;
step 17, the component server returns the latest path of the component file and the type of the component file;
step 18, the client receives the component file path to load and read the file;
step 19, the client deletes the original component tag and destroys the existing component instance;
step 20, the client records the view element identifier bound by the destroying assembly instance in step 19;
step 21, the client generates an instance according to the updated component class view element identifier, and establishes a component instance-view binding relationship according to the view element identifier recorded in the step 10;
and 22, rendering according to the latest component rendering mechanism when the view data are updated, so as to realize the non-perception replacement.
Third section:
the process of adapting to different development modes is as follows (taking component type a developed by mode a as an example):
step 31, initializing a client and establishing connection with a component server;
step 32, the client requests the adapter file from the component server and loads and reads the adapter file;
Step 33, the client sends out a request for acquiring the component file;
step 34, the component server returns file path information and type (A type) information of the component to be allowed to be loaded;
step 35, the client loads corresponding component files according to the component path information;
step 36, the client selects a packaging mode corresponding to the type to perform class packaging according to the type of the component and the matching specification in the matching file;
here, class encapsulation is the packaging of the same type of components, so that the updates are updated together. The class packaging comprises component style attributes and data attributes exposed by the components, and view rendering modes conforming to the type A specification;
step 37, the client establishes connection with the data server, and the client sends a request for acquiring view element information;
here, the view element information includes an identification of the view element; when loading a page, the identity of the view element to be loaded is known.
Step 38, the data server returns the component identifier and component attribute information bound with the corresponding view element on the page;
the data service stores component configuration data, namely component identification and component attribute information.
Step 39, after the client obtains the view element information, the class encapsulated in step 34 is found according to the belonging component identifier to be instantiated, and the required view element is generated on the client page by combining the component attribute information in step 36, so that the expected display effect is realized.
In the technical scheme provided by the embodiment of the application, the file management separation and the operation separation of packaging release of the client interface and the view component are realized by constructing a component service model, the view component based on different development modes is compatible by constructing an adapter model, and the view component and the adapter file of all clients are replaced in real time without perception by additionally constructing a broadcast notification model.
The technical scheme provided by the embodiment of the application solves three problems in the prior art in the field of dynamic component configuration: 1) When the view components needed by the client page are updated, all items with the introduction relation to the components are required to be repackaged and released to be effective, and the flexibility is not available; 2) The single development mode of the client interface and the view component cannot be compatible with components of multiple development modes, and the compatibility is lacking; 3) When a loophole exists in the view rendering mechanism or an updating requirement exists, the client interface needs to be refreshed again to acquire the latest component files, and the view rendering mechanism is unacceptable for important scenes such as demonstration, security and the like and lacks availability. In addition to solving the three problems, the embodiment of the application can package the same type of components into the same component file by configuring an automatic packaging mode in component service, thereby reducing the request times of a client and a server and achieving the effect of reducing the cost and improving the performance.
Based on the foregoing embodiments, embodiments of the present application provide a visual component configuration apparatus, where the apparatus includes units included, and modules included in the units may be implemented by a processor in a computer device; of course, the method can also be realized by a specific logic circuit; in an implementation, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.
Fig. 4 is a schematic structural diagram of a visual component configuration apparatus according to an embodiment of the present application, as shown in fig. 4, the apparatus 400 includes:
a first determining module 401, configured to determine, when initializing a page, an identifier of a view element on the page;
a second determining module 402, configured to determine component configuration data bound to the view element according to the identifier of the view element, where the component configuration data includes a component identifier and component attribute information;
an obtaining module 403, configured to obtain, according to the component identifier, a target component class of the page; the target component class is obtained from a component server for updating the component;
and the rendering module 404 is configured to perform instantiation rendering according to the component attribute information and the target component class, so as to obtain a target page.
In some embodiments, the acquisition module comprises: the request unit is used for requesting a target component and a target adapter corresponding to the component identifier from the component server; and the packaging unit is used for calling the target adapter, and performing class packaging on the target component according to the development mode of the target component to obtain a target component class.
In some embodiments, the request unit includes:
the reading subunit is used for reading the service configuration information of the page when the page is initialized;
and the request subunit is used for sending a component loading request and an adapter loading request which both carry the component identifier to the component server according to the service configuration information of the page so as to obtain a target component and a target adapter corresponding to the component identifier.
The reading subunit is configured to: when the client initiates the page, the client establishes connection with a data server to obtain a storage path; obtaining service configuration information of the page by accessing the storage path; or the client reads the service configuration information of the page from the local when the page is initialized.
In some embodiments, the apparatus further comprises:
the building module is used for building full duplex communication connection with the component server;
the first receiving module is used for receiving an update notification broadcast by the component server, wherein the update notification comprises a component identifier of a component to be updated;
correspondingly, the acquiring module is configured to, when detecting that the component identifier of the component to be updated is the same as the component identifier in the component configuration data, request at least the updated target component to the component server according to the component identifier.
In some embodiments, the acquiring module is configured to: and at least requesting the updated target component from the component server according to the component identifier, including: an update request is sent to the component server, wherein the update request carries a component identifier; receiving a file path and a development mode of a component to be updated, which are returned by the component server side in response to the update request; and accessing the file path of the component to be updated to obtain the updated target component.
In some embodiments, the apparatus further comprises: and the processing module is used for storing the updated target component according to the component instance of the updated component corresponding to the component identifier.
In some embodiments, the acquiring module is configured to: and determining the target component class from the component classes in the loaded component set according to the component identification.
In some embodiments, the apparatus further comprises: the reading module is used for reading the service configuration information when the page is initialized; the request module is used for requesting the component set and the adapter to the component server according to the service configuration information; and the packaging module is used for calling the adapter, and performing class packaging on the corresponding components according to the development mode of each component in the component set to obtain the component class of the component set.
Based on the foregoing embodiments, the embodiments of the present application provide a visual component configuration apparatus, where the apparatus includes units included, and modules included in the units may be implemented by a processor in a computer device (a client side may be understood as a terminal, and a component server or a data server may be understood as a server); of course, the method can also be realized by a specific logic circuit; in an implementation, the processor may be a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), or the like.
Fig. 5 is a schematic structural diagram of a visual component configuration apparatus according to an embodiment of the present application, as shown in fig. 5, the apparatus 500 includes:
the second receiving module 501 is configured to receive, when the adapter and the component have an upgrade requirement, the uploaded component and adapter by the component server; the adapter is used for carrying out class packaging on the components according to the development modes of the components to obtain component classes so that the client can be compatible with the components in different development modes;
an establishing module 502, configured to establish a full duplex connection with a client;
a third receiving module 503, configured to receive a load component request and a load adapter request sent by the client;
a first sending module 504, configured to send a first file path to the client in response to the loading component request, so that the client accesses the first file path to obtain a target component;
and the second sending module 505 is configured to send a second file path to the client in response to the loading adapter request, so that the client accesses the second file path to obtain a target adapter.
In some embodiments, the load component request and the load adapter request both carry component identification; the first file path is a path for storing the component corresponding to the component identifier, and the second file path is a path for storing the adapter corresponding to the component identifier.
In some embodiments, the apparatus further comprises: and the third sending module is used for sending an update notification to the client side which establishes the full duplex communication connection, wherein the update notification comprises the identification of the component to be updated.
The description of the apparatus embodiments above is similar to that of the method embodiments above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the apparatus of the present application, please refer to the description of the embodiments of the method of the present application.
It should be noted that, in the embodiment of the present application, if the above-mentioned configuration method of the visual component is implemented in the form of a software functional module, and sold or used as a separate product, the configuration method may also be stored in a computer readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be embodied essentially or in a part contributing to the related art in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, a mobile phone, etc.) to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, an optical disk, or other various media capable of storing program codes. Thus, embodiments of the application are not limited to any specific combination of hardware and software.
Correspondingly, the embodiment of the application provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor realizes the steps in the client or the server side method when executing the program.
Correspondingly, the embodiment of the application provides a computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the steps of the method of the client or the server side.
It should be noted here that: the description of the storage medium and apparatus embodiments above is similar to that of the method embodiments described above, with similar benefits as the method embodiments. For technical details not disclosed in the embodiments of the storage medium and the apparatus of the present application, please refer to the description of the method embodiments of the present application.
It should be noted that fig. 6 is a schematic diagram of a hardware entity of a computer device according to an embodiment of the present application, and as shown in fig. 6, the hardware entity of the computer device 600 includes: a processor 601, a communication interface 602 and a memory 603, wherein
The processor 601 generally controls the overall operation of the computer device 600.
The communication interface 602 may enable a computer device to communicate with other terminals or servers over a network.
The memory 603 is configured to store instructions and applications executable by the processor 601, and may also cache data to be processed or processed by various modules in the processor 601 and the computer device 600, and may be implemented by FLASH memory (FLASH) or random access memory (Random Access Memory, RAM).
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application. The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units; can be located in one place or distributed to a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, where the program, when executed, performs steps including the above method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read Only Memory (ROM), a magnetic disk or an optical disk, or the like, which can store program codes.
Alternatively, the above-described integrated units of the present application may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solution of the embodiments of the present application may be embodied essentially or in a part contributing to the related art in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.
The foregoing is merely an embodiment of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (14)
1. A method of configuring a visual component, comprising:
when a client initiates a page, determining the identification of a view element on the page;
determining component configuration data bound with the view element according to the identifier of the view element, wherein the component configuration data comprises component identifiers and component attribute information;
establishing full duplex communication connection with a component server, and receiving an update notification broadcasted by the component server, wherein the update notification comprises a component identifier of a component to be updated;
acquiring a target component class of the page according to the component identifier; the target component class is obtained from a component server for updating the component;
calling an analysis engine, and performing instantiation rendering according to the component attribute information and the target component class to obtain a target page;
the step of obtaining the target component class of the page according to the component identifier includes: when the component identification of the component to be updated is detected to be the same as the component identification in the component configuration data, at least requesting an updated target component from a component server according to the component identification;
And calling a target adapter corresponding to the target component, and performing class packaging on the updated target component according to the development mode of the updated target component to obtain a target component class.
2. The method according to claim 1, wherein the obtaining the target component class of the page according to the component identifier includes:
requesting a target component and a target adapter corresponding to the component identifier from a component server;
and calling the target adapter, and performing class packaging on the target component according to the development mode of the target component to obtain a target component class.
3. The method of claim 2, wherein the requesting the target component and the target adapter corresponding to the component identifier from the component server comprises:
when the client side initializes the page, reading service configuration information of the page;
and sending a component loading request and an adapter loading request which both carry the component identifier to the component server according to the service configuration information of the page.
4. The method according to claim 3, wherein the client, when performing the page initialization, reads service configuration information of the page, including:
When the client initiates the page, the client establishes connection with a data server to obtain a storage path; obtaining service configuration information of the page by accessing the storage path;
or alternatively, the process may be performed,
and the client reads the service configuration information of the page from the local when initializing the page.
5. The method according to claim 1, wherein the method further comprises:
and according to the component instance of the updated component corresponding to the component identifier, storing the updated target component.
6. The method according to claim 1, wherein the obtaining the target component class of the page according to the component identifier includes:
and determining the target component class from the component classes in the loaded component set according to the component identification.
7. The method of claim 6, wherein the method further comprises:
when the client side initializes the page, reading service configuration information;
requesting the component set and the adapter from the component server according to the service configuration information;
and calling the adapter, and performing class packaging on the corresponding components according to the development mode of each component in the component set to obtain the component class of the component set.
8. A method of configuring a visual component, comprising:
when the adapter and the component have upgrading requirements, the component server receives the uploaded component and adapter; the adapter is used for carrying out class packaging on the components according to the development modes of the components to obtain component classes so that the client can be compatible with the components in different development modes;
establishing full duplex connection with a client;
receiving a loading component request and a loading adapter request sent by the client;
responding to the loading component request, and sending a first file path to the client so that the client accesses the first file path to obtain a target component;
and responding to the loading adapter request, and sending a second file path to the client so that the client accesses the second file path to obtain the target adapter.
9. The method of claim 8, wherein the load component request and the load adapter request each carry a component identification; the first file path is a path for storing the component corresponding to the component identifier, and the second file path is a path for storing the adapter corresponding to the component identifier.
10. The method according to claim 8 or 9, characterized in that the method further comprises:
and sending an update notification to the client of the established full duplex communication connection, wherein the update notification comprises the identification of the component to be updated.
11. A visualization component configuration apparatus, comprising:
the first determining module is used for determining the identification of the view element on the page when the page is initialized;
a second determining module, configured to determine component configuration data bound to the view element according to the identifier of the view element, where the component configuration data includes a component identifier and component attribute information;
the building module is used for building full duplex communication connection with the component server;
the first receiving module is used for receiving an update notification broadcast by the component server, wherein the update notification comprises a component identifier of a component to be updated;
the acquisition module is used for acquiring the target component class of the page according to the component identifier; the target component class is obtained from a component server for updating the component;
the rendering module is used for performing instantiation rendering according to the component attribute information and the target component class to obtain a target page;
The acquiring module is specifically configured to: when the component identification of the component to be updated is detected to be the same as the component identification in the component configuration data, at least requesting an updated target component from a component server according to the component identification; and calling a target adapter corresponding to the target component, and performing class packaging on the updated target component according to the development mode of the updated target component to obtain a target component class.
12. A visualization component configuration apparatus, comprising:
the second receiving module is used for receiving the uploaded component and the uploaded adapter when the adapter and the component have upgrading requirements; the adapter is used for carrying out class packaging on the components according to the development modes of the components to obtain component classes so that the client can be compatible with the components in different development modes;
the establishing module is used for establishing full duplex connection with the client;
the third receiving module is used for receiving the loading component request and the loading adapter request sent by the client;
the first sending module is used for responding to the loading component request and sending a first file path to the client so that the client accesses the first file path to obtain a target component;
And the second sending module is used for responding to the loading adapter request and sending a second file path to the client so that the client accesses the second file path to obtain a target adapter.
13. A computer device comprising a memory and a processor, the memory storing a computer program executable on the processor, wherein the processor, when executing the program, implements the steps of the method of any one of claims 1 to 7, or the steps of the method of any one of claims 8 to 10.
14. A computer readable storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the method of any of claims 1 to 7, or the steps of the method of any of claims 8 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010760646.5A CN114090083B (en) | 2020-07-31 | 2020-07-31 | Visual component configuration method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010760646.5A CN114090083B (en) | 2020-07-31 | 2020-07-31 | Visual component configuration method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114090083A CN114090083A (en) | 2022-02-25 |
| CN114090083B true CN114090083B (en) | 2023-08-15 |
Family
ID=80295046
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010760646.5A Active CN114090083B (en) | 2020-07-31 | 2020-07-31 | Visual component configuration method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114090083B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114936031B (en) * | 2022-07-22 | 2022-11-11 | 浙江中控技术股份有限公司 | Component calling method and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107424033A (en) * | 2016-03-29 | 2017-12-01 | 阿里巴巴集团控股有限公司 | A kind of component rendering method, page display method, client, server and storage medium |
| CN108419089A (en) * | 2018-02-08 | 2018-08-17 | 广州虎牙信息科技有限公司 | Module data processing method, device, equipment and storage medium |
| CN108776592A (en) * | 2018-05-23 | 2018-11-09 | 北京五八信息技术有限公司 | A kind of method, apparatus of page makeup, equipment and storage medium |
| CN110333880A (en) * | 2018-03-29 | 2019-10-15 | 杭州海康威视数字技术股份有限公司 | A kind of configuration update method, device, equipment and storage medium |
| CN110727869A (en) * | 2019-10-18 | 2020-01-24 | 北京字节跳动网络技术有限公司 | Page construction method and device |
| CN111208974A (en) * | 2018-11-21 | 2020-05-29 | 北京京东尚科信息技术有限公司 | Component management method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8869138B2 (en) * | 2011-11-11 | 2014-10-21 | Wyse Technology L.L.C. | Robust firmware update with recovery logic |
-
2020
- 2020-07-31 CN CN202010760646.5A patent/CN114090083B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107424033A (en) * | 2016-03-29 | 2017-12-01 | 阿里巴巴集团控股有限公司 | A kind of component rendering method, page display method, client, server and storage medium |
| CN108419089A (en) * | 2018-02-08 | 2018-08-17 | 广州虎牙信息科技有限公司 | Module data processing method, device, equipment and storage medium |
| CN110333880A (en) * | 2018-03-29 | 2019-10-15 | 杭州海康威视数字技术股份有限公司 | A kind of configuration update method, device, equipment and storage medium |
| CN108776592A (en) * | 2018-05-23 | 2018-11-09 | 北京五八信息技术有限公司 | A kind of method, apparatus of page makeup, equipment and storage medium |
| CN111208974A (en) * | 2018-11-21 | 2020-05-29 | 北京京东尚科信息技术有限公司 | Component management method and device |
| CN110727869A (en) * | 2019-10-18 | 2020-01-24 | 北京字节跳动网络技术有限公司 | Page construction method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114090083A (en) | 2022-02-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11868785B2 (en) | Application program page processing method and device | |
| CN108964968B (en) | Service access management method and system in container cloud environment | |
| US20160170712A1 (en) | Method for integrally implementing development and release of APP | |
| CN103970563B (en) | The method of dynamic load Android class | |
| CN107291759B (en) | Method and device for processing browser page resources | |
| CN104395882A (en) | Creation and context-aware presentation of customized emoticon item sets | |
| CN108647032B (en) | Application loading method and device, computer device and computer readable storage medium | |
| CN103324517A (en) | Off-line application generation and call method, terminal and system | |
| CN104516885A (en) | Implementation method and device of browse program double-kernel assembly | |
| US20240103928A1 (en) | Information processing method and apparatus for animation resource, device, medium and product | |
| CN112416359A (en) | Dynamic partition customizing method, device, equipment and computer readable storage medium | |
| CN112347404A (en) | SPA page rendering method, device and system and storage medium | |
| CN114090083B (en) | Visual component configuration method, device, equipment and storage medium | |
| CN109032693B (en) | Method and device for loading display information, electronic equipment and readable storage medium | |
| CN106844763B (en) | A kind of method showed to the Internet media file formula of modifying and its device | |
| CN116974676A (en) | Page content sending method, device and equipment | |
| WO2023082813A1 (en) | Information sharing method and apparatus, electronic device and storage medium | |
| CN115811481A (en) | Interactive service testing method and device, computer equipment and storage medium | |
| CN108021567B (en) | Method and device for self-adaptively customizing fonts of browser | |
| CN115061785A (en) | Information issuing method and device, storage medium and server | |
| CN107092601B (en) | Resource file construction method, resource file application method and device | |
| CN110673827B (en) | Resource calling method and device based on android system and electronic equipment | |
| CN114637969A (en) | Target object authentication method and device | |
| CN112417818A (en) | Document directory generation method and device, storage medium and electronic equipment | |
| CN112631638A (en) | Terminal application updating method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |