CN116661827A - Method, device, equipment and readable storage medium for updating nested component - Google Patents
Method, device, equipment and readable storage medium for updating nested component Download PDFInfo
- Publication number
- CN116661827A CN116661827A CN202310644411.3A CN202310644411A CN116661827A CN 116661827 A CN116661827 A CN 116661827A CN 202310644411 A CN202310644411 A CN 202310644411A CN 116661827 A CN116661827 A CN 116661827A
- Authority
- CN
- China
- Prior art keywords
- component
- sub
- nested
- target sub
- level
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000004590 computer program Methods 0.000 claims description 8
- 238000004519 manufacturing process Methods 0.000 abstract description 9
- 230000000875 corresponding effect Effects 0.000 description 30
- 239000010410 layer Substances 0.000 description 14
- 238000010276 construction Methods 0.000 description 8
- 239000002356 single layer Substances 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 101000939676 Androctonus crassicauda Toxin a Proteins 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000009825 accumulation Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 239000003086 colorant Substances 0.000 description 1
- 238000011960 computer-aided design Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 208000015181 infectious disease Diseases 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/10—Geometric CAD
- G06F30/13—Architectural design, e.g. computer-aided architectural design [CAAD] related to design of buildings, bridges, landscapes, production plants or roads
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Geometry (AREA)
- Computer Hardware Design (AREA)
- Civil Engineering (AREA)
- Architecture (AREA)
- Computer Security & Cryptography (AREA)
- Structural Engineering (AREA)
- Computational Mathematics (AREA)
- Mathematical Analysis (AREA)
- Mathematical Optimization (AREA)
- Pure & Applied Mathematics (AREA)
- Evolutionary Computation (AREA)
- Numerical Control (AREA)
Abstract
The invention discloses a method, a device, equipment and a readable storage medium for nesting components, wherein the method comprises the following steps: acquiring a first sub-component and a second sub-component, wherein the first sub-component is provided with independent attribute information; the first sub-component and the second sub-component are deployed in a hierarchy mode to generate a nested component, wherein each hierarchy of the nested component can be edited independently; receiving an update instruction of a nested component, wherein the update instruction comprises a component update item; and determining a target sub-component in the nested component according to the component update item, and selecting a hierarchy corresponding to the target sub-component for editing so as to update the nested component. According to the invention, when the nested component is manufactured, independent attributes are added for the sub-components according to requirements, and the characteristics of the nested component unit, such as the sub-elements can be picked up, edited, replaced and the like in a project environment, can be controlled through example parameters, and the geometric shape of the nested component unit can be directly driven through the geometric parameters of the sub-components, so that the manufacturing efficiency of the complex nested component is improved.
Description
Technical Field
The present invention relates to the field of computer aided design technology, and in particular, to a method, an apparatus, a device, and a readable storage medium for updating a nested component.
Background
In a typical building model, the components are the basic units of the model composition, which are representations of reusable data structures and file storage structures composed by parameterized driven geometry and information descriptions; that is, each member has its corresponding properties and geometry, belonging to a single layer cell structure. However, for complex models, the use of only a single layer of cell structures (as in fig. 1) is disadvantageous for accumulation of existing modeling results, reducing modeling efficiency. Thus, a common way to do this is to solidify the local modeling effort into a repository for later use by combining, modular or nested components. The nested component internally comprises a data structure and a file storage structure representation of various single-layer unit structural components, and the nested component can have multiple layers in a hierarchy, namely the nested component internally can comprise the nested component.
In the prior art, the sub-components of the nested components are stored according to the attribute information, as shown in fig. 2, in the prior art, the sub-components of the nested components are divided according to whether the components can be shared, and finally, the components with shared attributes are divided into a group for the components of the same category, and meanwhile, the components with non-shared attributes are divided into a group. This approach has the following drawbacks in practice: 1. the operability of the embedded sub-components in the project is tightly coupled with the file attribute in the design process, which is not beneficial to quickly modifying the capability of the embedded components; 2. for geometric parameters and non-geometric parameters in the subcomponent, the parameters cannot be directly modified by the subcomponent instance; 3. the subcomponents can be driven only by binding the subcomponents layer by layer to the upper layer, so that the internal geometric parameters can be exposed to the project environment, and the component manufacturing efficiency is low; 4. the file properties of the subcomponent determine at which hierarchical depth it is replaced with a newly loaded homonymous component, which is undesirable in some scenarios.
Aiming at the technical problem that independent editing of sub-components is not beneficial to rapid construction of building models in the prior art, no effective solution exists at present.
Disclosure of Invention
The invention aims to provide a method, a device, equipment and a readable storage medium for updating nested components, which can solve the technical problem that independent editing of sub-components is not beneficial to rapid construction of a building model.
One aspect of the present invention provides a method of updating a nested component, the method comprising: acquiring a first sub-component and a second sub-component, wherein the first sub-component is provided with independent attribute information; the first sub-component and the second sub-component are deployed in a hierarchy mode to generate a nested component, wherein each hierarchy of the nested component can be edited independently; receiving an update instruction of a nested component, wherein the update instruction comprises a component update item; and determining a target sub-component in the nested component according to the component update item, and selecting a hierarchy corresponding to the target sub-component for editing so as to update the nested component.
Optionally, selecting a hierarchy corresponding to the target subcomponent for editing, including: judging whether the target sub-component is provided with independent attribute information, and selecting a hierarchy corresponding to the target sub-component to edit according to a judging result; if the target sub-component is provided with independent attribute information, selecting the target sub-component to edit at the level of the nested component; if the target sub-component does not have independent attribute information, determining a first level of the target sub-component in the nested component, and selecting a sub-component with independent attribute at the previous level/level of the first level for editing.
Optionally, if the target subcomponent is provided with independent attribute information, selecting the target subcomponent for editing at the level of the nested component includes: and (3) taking the highest level of the nested components as a starting point, clicking downwards step by step until reaching the level of the target sub-component, finishing clicking, and replacing component information corresponding to the target sub-component through a component updating item.
Optionally, hierarchically deploying the first sub-component and the second sub-component includes: creating a master component hierarchy, wherein the master component hierarchy is the highest hierarchy of nested components; embedding the second sub-component into the main component, and associating corresponding information between the second sub-component and the main component; and taking the first sub-component as a sub-stage of the main component, taking the main component level as a starting node, and deploying the first sub-component downwards step by step according to the level relation of the first sub-component.
Optionally, after determining the target sub-component in the nested component according to the component update item, the method further comprises: judging whether the target sub-component is provided with independent attribute information or not so as to realize targeted loading of the target sub-component; if the target sub-component does not have the non-independent attribute, loading the nested component in the project environment, and directly driving instance parameters of the target sub-component and the nested component according to loading operation; and if the target sub-component is provided with the independent attribute, extracting the type parameter of the target sub-component, and reversely driving the target sub-component through the type parameter.
Optionally, after hierarchically deploying the first sub-component and the second sub-component to generate the nested component, the method further comprises: and classifying and storing the nested components according to the example parameters of the sub-components.
Another aspect of the present invention provides an apparatus for updating a nesting component, the apparatus comprising: the acquisition module is used for acquiring a first sub-component and a second sub-component, wherein the first sub-component is provided with independent attribute information; the deployment module is used for performing hierarchical deployment on the first sub-component and the second sub-component to generate a nested component, wherein each hierarchy of the nested component can be independently edited; the receiving module is used for receiving an update instruction of the nested component, wherein the update instruction comprises a component update item; and the updating module is used for determining a target sub-component in the nested component according to the component updating item, and selecting a level corresponding to the target sub-component for editing so as to update the nested component.
Optionally, the deployment module is specifically configured to: creating a master component hierarchy, wherein the master component hierarchy is the highest hierarchy of nested components; embedding the second sub-component into the main component, and associating corresponding information between the second sub-component and the main component; and taking the first sub-component as a sub-stage of the main component, taking the main component level as a starting node, and deploying the first sub-component downwards step by step according to the level relation of the first sub-component.
Yet another aspect of the present invention provides a computer device comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of updating nested elements of any of the embodiments described above when the computer program is executed by the processor.
Yet another aspect of the invention provides a computer storage medium having stored thereon a computer program which when executed by a processor implements the method of updating nested members of any of the embodiments described above. Further, the computer-readable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created from the use of blockchain nodes, and the like.
According to the invention, when the nested component is manufactured, independent attributes are added for the sub-components according to requirements, and the characteristics of the nested component unit, such as the sub-elements can be picked up, edited, replaced and the like in a project environment, can be controlled through example parameters, and the geometric shape of the nested component unit can be directly driven through the geometric parameters of the sub-components, so that the manufacturing efficiency of the complex nested component is improved. Meanwhile, the subcomponents with independent attributes and the subcomponents with non-independent attributes are updated in a distinguishing mode, and the situation that different types of components are infected during updating is avoided.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 shows an alternative structural schematic of a single-layer cell structure provided by the summary of the invention;
FIG. 2 illustrates an alternative structural schematic of a prior art nesting component store provided by the present disclosure;
FIG. 3 illustrates an alternative flow chart of a method of updating a nested component provided in accordance with an embodiment of the present invention;
FIG. 4 illustrates an alternative application schematic of nested component loading provided by an embodiment of the present invention;
FIG. 5 illustrates an alternative application schematic of the nested member store provided by the first embodiment of the present invention;
FIG. 6 is a block diagram showing a nested member updating device according to a second embodiment of the present invention; and
fig. 7 shows a block diagram of a computer device adapted to implement the method for updating nested components according to the third embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
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.
Example 1
The present embodiment provides a method for updating a nested member, and fig. 3 shows a flowchart of the method for updating a nested member, and as shown in fig. 3, the method for updating a nested member may include steps S301 to S304, where:
step S301, a first sub-component and a second sub-component are obtained, wherein the first sub-component is provided with independent attribute information;
in particular, the first sub-component may be a single-layer cell structure or may be a nested component, i.e. a complex multi-layer cell structure, and the second sub-component is a basic geometry. The first sub-component contains instance project information and basic geometry information, and the acquisition mode can be drawn in design software or screened from the existing components of the database. The number and structure of the first sub-component and the second sub-component are determined by actual scene requirements, and are not limited herein.
In particular, independent properties means that the corresponding component can be individually loaded, edited and picked up in the project environment, while sub-components provided with independent properties are not affected when other components are loaded, edited or picked up. Accordingly, sub-components without independent attributes cannot be handled separately, requiring editing or loading by attaching upper layer components. The independent attributes may be marked by text, accent symbols/colors in the actual building information model, without limitation.
Step S302, performing hierarchical deployment on the first sub-component and the second sub-component to generate nested components, wherein each hierarchy of the nested components can be edited independently;
since the single-layer cell structure is disadvantageous for accumulation of existing modeling results, it is necessary to combine them into a structure having a higher level for more accurate expression of actual construction. The hierarchical deployment mode of the first sub-component and the second sub-component is determined by actual scene requirements, and can be a flat structure and a parent-child structure, the structure formed by combining the first sub-component and the second sub-component is used as a main structure, the main structure instance information is arranged according to the scene requirements, and finally the nested component is obtained. In particular, the nesting member is a multi-layered unit structure,
preferably, step S302 may include steps S3021 to S3023, wherein:
step S3021, creating a main component hierarchy, wherein the main component hierarchy is the highest hierarchy of nested components;
wherein the master component hierarchy characterizes the hierarchy at which the nested components are located.
Step S3022, embedding the second sub-component in the main component, and associating the correspondence information between the second sub-component and the main component;
because the second sub-component has no independent attribute, the second sub-component cannot be processed independently during updating, the second sub-component is bound with the main component, and the association relationship between the second sub-component and the main component is established, so that the second sub-component can be updated through the main component.
In step S3023, the first sub-component is used as a sub-level of the main component, and the main component level is used as a starting node, and is deployed downwards step by step according to the level relationship of the first sub-component.
The first sub-member may be a single-layer unit structure or a multi-layer unit structure, i.e., a nested member.
When the first sub-component is of a single-layer unit structure, taking a main component level as a starting node, and downwards deploying a level node to deploy the first sub-component;
when the first sub-component is of a multi-layer unit structure, the main component layer is taken as an initial node, the corresponding layer nodes are arranged according to the number of the layers of the first sub-component, and the association relation between the component information corresponding to each layer of the first sub-component and the corresponding layer nodes is built.
The nested components are arranged into a multi-level structure, and meanwhile, the first sub-component is provided with independent attributes, so that each level of sub-component can be processed independently, upper-level component information of the sub-component is bound layer by layer to update when the sub-component of a single level is not needed to update, and the efficiency of model construction is improved.
Step S303, receiving an update instruction of a nested component, wherein the update instruction comprises a component update item;
the component update item is item information required to be updated for the current nested component, and can be type parameters or geometric attribute information, and is not limited herein.
Step S304, determining a target sub-component in the nested component according to the component update item, and selecting a hierarchy corresponding to the target sub-component for editing so as to update the nested component.
The target sub-component may be a first sub-component or a second sub-component, or may be a structure formed by combining the first sub-component and the second sub-component, that is, a main structure.
When the component update item is obtained, the embodiment does not adopt the component update item to directly replace corresponding information in the nested component, but determines the target sub-component in the nested component through the component update item, and then judges the attribute information of the target sub-component, thereby selecting the hierarchy corresponding to the target sub-component for editing. The method ensures that only the target sub-components of the selected level are independently processed, structural information of other components except the target sub-components is not affected/infected, design experience of a user is improved, and rapid construction of a building model is facilitated.
Preferably, step S304 may include steps S3041 to S3043, wherein:
step S3041, judging whether the target sub-component is provided with independent attribute information, and selecting a hierarchy corresponding to the target sub-component for editing according to a judging result;
the attribute information of the target sub-components is different, the corresponding updating modes are also different, and the corresponding levels are selected in the nested components to edit by judging whether the target sub-components are provided with independent attribute information, so that the targeted updating of the different types of sub-components is realized, and the efficiency of model construction is improved.
Step S3042, if the target sub-component is provided with independent attribute information, selecting the target sub-component to edit at the level of the nested component;
preferably, the highest level of the nested components is used as a starting point, clicking is performed downwards step by step until the level of the target sub-component is reached, clicking is finished, and component information corresponding to the target sub-component is replaced through a component updating item.
Specifically, the nested hierarchical structure is inherited in the project environment, the highest hierarchy of the nested components (namely the hierarchy where the main component is located) is taken as a starting point through shortcut key and mouse operation, the hierarchical clicking operation is finished when the clicking operation reaches the hierarchy where the target sub-component is located. And traversing all component information in a hierarchy where the target sub-component is located, retrieving parameters of which the type is the same as that of the component update item, and replacing the retrieved parameters through the component update item.
In step S3043, if the target sub-component does not have independent attribute information, determining a first level of the target sub-component in the nested component, and selecting a sub-component having independent attribute at a level/peer above the first level for editing.
Because the target sub-component has no independent attribute information, the target sub-component cannot be processed independently and needs to be updated by attaching other components. The present embodiment sets the update object of this type of target sub-component as an upper component of this sub-component or as an independent sub-component of the same level (i.e., a sub-component provided with independent properties). Meanwhile, the target sub-component is embedded in the nested component, and the upper component can be the main component.
It should be noted that, for the sub-component with independent attribute, if the category of the component update item is a type parameter, the component information of the level where the target sub-component is located is matched with the component update item to realize the update of the target sub-component;
if the category of the component update item is an instance parameter, there are two update methods:
one is to utilize the component instance parameter of the level where the target sub-component is located to match with the component update item, when matching is successful, the corresponding instance parameter is replaced by the component update item, so as to realize the update of the target sub-component;
and the other is to match the type parameter of the upper-level component of the level where the target sub-component is positioned with the component updating item, and when the matching is successful, the corresponding type parameter is replaced by the component updating item, so that the target sub-component is updated.
The two updating modes can be independently processed in the corresponding hierarchical structure of the sub-components, so that the real-time editing requirement of the nested components is met, and the efficiency of model construction is improved.
When the component update item is utilized for carrying out the overlay update, a nested main component is selected and a sub-component needing to be updated and replaced is selected; when the sub-component information or geometry is updated by the main component, the main component and all sub-component examples are refreshed, and corresponding update type information is updated. Direct replacement capability of sub-components or sub-nested components is prevented in the project environment, while the manner of synchronously updating to the project environment after replacement in the nested main component is used so as to distinguish the scenes which are not expected to be infected when the sub-components are uniformly updated.
Preferably, the method further comprises steps A1 to A3, wherein:
a1, judging whether the target sub-component is provided with independent attribute information or not so as to realize targeted loading of the target sub-component;
after the target sub-component is determined in the nested component from the component update item, an update flow to the target sub-component needs to be performed. The first step of component updating is to load components, the loading modes of components with different attribute information are different, and the loading flow adapting to the corresponding application scene is executed by judging whether the target sub-component is provided with independent attribute information or not.
A2, if the target sub-component does not have the non-independent attribute, loading the nested component in the project environment, and directly driving instance parameters of the target sub-component and the nested component according to loading operation;
the subcomponent of the dependent attribute is embedded in the main component, and the loading operation is bound with the main component. The method comprises the steps of loading nested components in a project environment, extracting main component types of the nested components, directly driving examples of the nested components and target sub-components through the main component types, wherein the sub-components cannot independently extract type parameters for driving.
And step A3, extracting type parameters of the target sub-component if the target sub-component is provided with independent attributes, and reversely driving the target sub-component through the type parameters.
The subcomponents of the independent attributes may be loaded individually, specifically: in the project environment, a target sub-component at a corresponding position is directly selected through a UI (user interface) interaction mode, type parameters of the target sub-component are extracted, and the target sub-component is reversely driven through the type parameters.
The purpose of the differentiated setting of the loading operation is to avoid information infection between the different sub-components, while improving the efficiency of building the building model.
Fig. 4 shows an application diagram of a loading flow of nested components, which is divided into two phases, a component fabrication phase and a component loading phase, as shown in fig. 4. Specifically, in the component manufacturing stage, the sub-component is manufactured and stored according to the requirements of a user, the sub-component supports component upgrading, and the upgrading does not destroy the data of the component; then finishing the manufacture of the main component based on the sub-component, and setting project independent attributes in the sub-component instance; in the component loading stage, loading a nested component in a project environment, and extracting a main component type of the nested component for the non-independent sub-component by means of whether the sub-components independently execute different loading modes to obtain a main component instance and the non-independent sub-component; for the independent sub-component, the type and the type parameter are abstracted from the independent sub-component to form the independent sub-component type, and the independent sub-component is reversely driven based on the independent sub-component type.
Preferably, the method further comprises step B1, wherein:
and B1, classifying and storing the nested components according to the example parameters of the sub-components.
After the nested components are generated, the nested components are sorted and stored according to example parameters of the sub-components. Fig. 5 shows an application schematic of a nested component storage, as shown in fig. 3, the nested component is divided into a sub-component a and a sub-component B, wherein the sub-component a and the sub-component B each comprise an independent attribute and a non-independent attribute (embedded in the main component), and the sub-component a and the sub-component B are respectively classified into different examples, so that the sub-component a and the sub-component B are respectively stored. In this way, since the subcomponents with independent attributes are individually marked, even if two types of parameters (such as the subcomponent instance A1-1 and the subcomponent instance A1-2) are stored in one folder, the update of the two cannot infect each other, thereby accelerating the efficiency of model construction.
In addition, in the project environment, aiming at the updating operation of the independent sub-components, the types of the sub-components in the nested components can be switched, the connection relation between the nested components can be accurately expressed, the relation between the nested components and the sub-components and other components can be switched, and the view display of the main component and the sub-components can be respectively controlled.
According to the steps, the manufacturing of the nested component and the application logic of the nested component in the project environment are perfected, the manufacturing efficiency of the complex nested component is improved, the nested component is provided with a more flexible use mode in the project environment, the nested hierarchical structure of the nested component is inherited, and the connection deduction relation between the nested component and the sub-component and between the sub-component and the sub-component is reserved.
According to the embodiment, when the nested component is manufactured, independent attributes are added for the sub-components according to requirements, and the characteristics that sub-elements of the nested component unit can be picked up, edited, replaced and the like in a project environment can be controlled through example parameters, so that the geometric shape of the nested component unit can be directly driven through the geometric parameters of the sub-components, and the manufacturing efficiency of the complex nested component is improved. Meanwhile, the subcomponents with independent attributes and the subcomponents with non-independent attributes are updated in a distinguishing mode, and the situation that different types of components are infected during updating is avoided.
Example two
The second embodiment of the present invention further provides a device for updating a nested member, where the device for updating a nested member corresponds to the method for updating a nested member provided in the first embodiment, and corresponding technical features and technical effects are not described in detail in this embodiment, and reference is made to the first embodiment for relevant points. Specifically, fig. 6 shows a block diagram of the structure of the updating device of the nesting component. As shown in fig. 6, the updating apparatus 600 of the nesting component includes an acquisition module 601, a deployment module 602, a receiving module 603, and an updating module 604, wherein:
an obtaining module 601, configured to obtain a first sub-component and a second sub-component, where the first sub-component is provided with independent attribute information;
the deployment module 602 is connected with the acquisition module 601 and is used for performing hierarchical deployment on the first sub-component and the second sub-component to generate a nested component, wherein each hierarchy of the nested component can be independently edited;
a receiving module 603, connected to the deployment module 602, for receiving an update instruction of the nested component, where the update instruction includes a component update item;
and the updating module 604 is connected with the receiving module 603 and is used for determining a target sub-component in the nested component according to the component updating item, and selecting a hierarchy corresponding to the target sub-component for editing so as to update the nested component.
Optionally, the updating module includes: the judging sub-module is used for judging whether the target sub-component is provided with independent attribute information or not, and selecting a hierarchy corresponding to the target sub-component to edit according to a judging result; the first updating sub-module is used for selecting the target sub-component to edit at the level of the nested component if the target sub-component is provided with independent attribute information; and the second updating sub-module is used for determining a first level of the target sub-component in the nested component if the target sub-component does not have independent attribute information, and selecting a sub-component with independent attribute at the previous level/same level of the first level for editing.
Optionally, the first update submodule is specifically configured to: and (3) taking the highest level of the nested components as a starting point, clicking downwards step by step until reaching the level of the target sub-component, finishing clicking, and replacing component information corresponding to the target sub-component through a component updating item.
Optionally, the deployment module is specifically configured to: creating a master component hierarchy, wherein the master component hierarchy is the highest hierarchy of nested components; embedding the second sub-component into the main component, and associating corresponding information between the second sub-component and the main component; and taking the first sub-component as a sub-stage of the main component, taking the main component level as a starting node, and deploying the first sub-component downwards step by step according to the level relation of the first sub-component.
Optionally, the apparatus further comprises a loading module for: judging whether the target sub-component is provided with independent attribute information or not so as to realize targeted loading of the target sub-component; if the target sub-component does not have the non-independent attribute, loading the nested component in the project environment, and directly driving instance parameters of the target sub-component and the nested component according to loading operation; and if the target sub-component is provided with the independent attribute, extracting the type parameter of the target sub-component, and reversely driving the target sub-component through the type parameter.
Optionally, the device further comprises a storage module, specifically configured to: and classifying and storing the nested components according to the example parameters of the sub-components.
Example III
Fig. 7 shows a block diagram of a computer device adapted to implement the method for updating nested components according to the third embodiment of the present invention. In this embodiment, the computer device 700 may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack-mounted server, a blade server, a tower server, or a rack-mounted server (including a stand-alone server or a server cluster formed by a plurality of servers), etc. for executing the program. As shown in fig. 7, the computer device 700 of the present embodiment includes at least, but is not limited to: a memory 701, a processor 702, and a network interface 703 that may be communicatively coupled to each other via a system bus. It is noted that FIG. 7 only shows a computer device 700 having components 701-703, but it is to be understood that not all of the illustrated components are required to be implemented, and that more or fewer components may be implemented instead.
In this embodiment, the memory 703 includes at least one type of computer-readable storage medium, including flash memory, hard disk, multimedia card, card memory (e.g., SD or DX memory, etc.), random Access Memory (RAM), static Random Access Memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 701 may be an internal storage unit of the computer device 700, such as a hard disk or memory of the computer device 700. In other embodiments, the memory 701 may also be an external storage device of the computer device 700, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the computer device 700. Of course, the memory 701 may also include both internal storage units of the computer device 700 and external storage devices. In the present embodiment, the memory 701 is typically used to store an operating system installed on the computer device 700 and various types of application software, such as program codes of an update method of nested members, and the like.
The processor 702 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 702 is generally used to control the overall operation of the computer device 700. Such as performing control and processing related to data interaction or communication with the computer device 700. In this embodiment, the processor 702 is configured to execute program code for executing steps of a method for updating nested members stored in the memory 701.
In this embodiment, the method for updating the nested components stored in the memory 701 may also be divided into one or more program modules and executed by one or more processors (the processor 702 in this embodiment) to complete the present invention.
The network interface 703 may include a wireless network interface or a wired network interface, the network interface 703 typically being used to establish a communication link between the computer device 700 and other computer devices. For example, the network interface 703 is used to connect the computer device 700 to an external terminal through a network, establish a data transmission channel and a communication link between the computer device 700 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a global system for mobile communications (Global System of Mobile communication, abbreviated as GSM), wideband code division multiple access (Wideband Code Division Multiple Access, abbreviated as WCDMA), a 4G network, a 5G network, bluetooth (Bluetooth), wi-Fi, etc.
Example IV
The present embodiment also provides a computer readable storage medium including a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., having stored thereon a computer program that when executed by a processor implements the steps of the method of updating a nesting component.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the invention described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may alternatively be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be separately fabricated into individual integrated circuit modules, or a plurality of modules or steps in them may be fabricated into a single integrated circuit module. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.
It should be noted that, the embodiment numbers of the present invention are only for description, and do not represent the advantages and disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (10)
1. A method of updating a nested component, the method comprising:
acquiring a first sub-component and a second sub-component, wherein the first sub-component is provided with independent attribute information;
performing hierarchical deployment on the first sub-component and the second sub-component to generate nested components, wherein each hierarchy of the nested components can be edited separately;
receiving an update instruction of the nested component, wherein the update instruction comprises a component update item;
and determining a target sub-component in the nested component according to the component updating item, and selecting a level corresponding to the target sub-component for editing so as to update the nested component.
2. The method of claim 1, wherein selecting the hierarchy to which the target subcomponent corresponds for editing comprises:
judging whether the target sub-component is provided with independent attribute information, and selecting a hierarchy corresponding to the target sub-component to edit according to a judging result;
if the target sub-component is provided with independent attribute information, selecting the target sub-component to edit at the level of the nested component;
and if the target sub-component does not have independent attribute information, determining a first level of the target sub-component in the nested component, and selecting a sub-component with independent attribute at the level/level above the first level for editing.
3. The method according to claim 2, wherein selecting the target sub-component for editing at the level of the nested component if the target sub-component is provided with independent attribute information comprises:
and taking the highest level of the nested components as a starting point, clicking downwards step by step until reaching the level of the target sub-component, finishing clicking, and replacing component information corresponding to the target sub-component through a component updating item.
4. The method of claim 1, wherein the hierarchically deploying the first sub-component and the second sub-component comprises:
creating a master component hierarchy, wherein the master component hierarchy is the highest hierarchy of the nested components;
embedding the second sub-component into the main component, and associating corresponding information between the second sub-component and the main component;
and taking the first sub-component as a sub-stage of the main component, taking the main component level as an initial node, and deploying downwards step by step according to the level relation of the first sub-component.
5. The method of claim 1, wherein after determining a target sub-component in the nested component according to the component update item, the method further comprises:
judging whether the target sub-component is provided with independent attribute information or not so as to realize targeted loading of the target sub-component;
if the target sub-component does not have the non-independent attribute, loading the nested component in a project environment, and directly driving instance parameters of the target sub-component and the nested component according to loading operation;
and if the target sub-component is provided with the independent attribute, extracting the type parameter of the target sub-component, and reversely driving the target sub-component through the type parameter.
6. The method of any of claims 1-5, wherein after hierarchically deploying the first and second sub-members to generate a nested member, the method further comprises:
and classifying and storing the nested components according to the example parameters of the sub-components.
7. A device for updating a nesting component, said device comprising:
the device comprises an acquisition module, a first control module and a second control module, wherein the acquisition module is used for acquiring a first sub-component and a second sub-component, and the first sub-component is provided with independent attribute information;
the deployment module is used for performing hierarchical deployment on the first sub-component and the second sub-component to generate a nested component, wherein each level of the nested component can be independently edited;
the receiving module is used for receiving an update instruction of the nested component, wherein the update instruction comprises a component update item;
and the updating module is used for determining a target sub-component in the nested component according to the component updating item, and selecting a level corresponding to the target sub-component for editing so as to update the nested component.
8. The apparatus of claim 7, wherein the deployment module is specifically configured to:
creating a master component hierarchy, wherein the master component hierarchy is the highest hierarchy of the nested components;
embedding the second sub-component into the main component, and associating corresponding information between the second sub-component and the main component;
and taking the first sub-component as a sub-stage of the main component, taking the main component level as an initial node, and deploying downwards step by step according to the level relation of the first sub-component.
9. A computer device, the computer device comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 6 when executing the computer program.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310644411.3A CN116661827A (en) | 2023-06-01 | 2023-06-01 | Method, device, equipment and readable storage medium for updating nested component |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310644411.3A CN116661827A (en) | 2023-06-01 | 2023-06-01 | Method, device, equipment and readable storage medium for updating nested component |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116661827A true CN116661827A (en) | 2023-08-29 |
Family
ID=87727422
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310644411.3A Pending CN116661827A (en) | 2023-06-01 | 2023-06-01 | Method, device, equipment and readable storage medium for updating nested component |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116661827A (en) |
-
2023
- 2023-06-01 CN CN202310644411.3A patent/CN116661827A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108876121B (en) | Work order processing method and device, computer equipment and storage medium | |
| CN110727687B (en) | Material list conversion method and system | |
| US20100153941A1 (en) | Flexible content update via deployment order template | |
| CN110705237B (en) | Automatic document generation method, data processing device and storage medium | |
| CN108170820B (en) | Container processing method, control server and distributed cluster | |
| US9380001B2 (en) | Deploying and modifying a service-oriented architecture deployment environment model | |
| US20220066764A1 (en) | Generating a software release based on controller metadata | |
| CN114237754B (en) | Data loading method and device, electronic equipment and storage medium | |
| CN114546432A (en) | Multi-application deployment method, device, equipment and readable storage medium | |
| CN111738145A (en) | Method and device for identifying stirrup winding method, computer equipment and readable storage medium | |
| CN113535206B (en) | Multi-version code upgrading method and system | |
| CN111221517A (en) | Model creating method and device, computer equipment and readable storage medium | |
| CN110737458A (en) | code updating method and related device | |
| CN116661827A (en) | Method, device, equipment and readable storage medium for updating nested component | |
| WO2016032496A1 (en) | Workflow customization | |
| CN116185853A (en) | Code verification method and device | |
| JP5172073B2 (en) | Editing system, server and program | |
| CN115033936A (en) | Material model management method for SolidWorks system | |
| CN114791985A (en) | Domain name matching method and device and prefix tree updating method and device | |
| CN108958823A (en) | The method for modifying basic input output system setting value | |
| CN113919033A (en) | Method and device for determining steel bar throwing in construction section | |
| CN106886420B (en) | Program code management device and method and program code manager | |
| CN113722045A (en) | Cluster application deployment method and device | |
| US20060248490A1 (en) | System and method for text based placement engine for custom circuit design | |
| CN110659042A (en) | Server firmware management method and device |
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 |