Method, device, computer equipment and storage medium for identifying interface components

Abstract

The present disclosure provides an interface component identification method, apparatus, computer equipment and storage medium, wherein the method comprises: obtaining component attribute information of at least one interface component in a UI interface design draft; determining the component type of each of the interface components based on the component attribute information, obtaining at least one component type, and determining a component identification pattern corresponding to each of the component types; identifying a target interface component in a corresponding interface component based on the component identification pattern; wherein the target interface component is an interface component whose rendering result in an interface component belonging to a corresponding component type is not displayed on the UI interface design draft.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to an interface component identification method, apparatus, computer equipment, and storage medium. Background Art

[0002] Since designers usually do not consider the rendering effect of the UI interface during the design process, the resulting UI interface design draft is often too messy and filled with several useless interface components. As a result, the UI interface code generated from the UI interface design draft through the D2C (design to code) method is relatively complex, which increases the subsequent maintenance cost of the UI interface and causes a large amount of terminal device memory to be occupied when loading the UI interface. Summary of the Invention

[0003] The embodiments of the present disclosure at least provide a method, apparatus, computer device, and storage medium for identifying an interface component.

[0004] In a first aspect, an embodiment of the present disclosure provides an interface component identification method, comprising:

[0005] Obtain component attribute information of at least one interface component in the UI interface design draft;

[0006] Determining a component type of each of the interface components based on the component attribute information, obtaining at least one component type, and determining a component identification mode corresponding to each of the component types;

[0007] A target interface component is identified in the corresponding interface components based on the component identification pattern; wherein the target interface component is an interface component of the corresponding component type whose rendering result is not displayed on the UI interface design draft.

[0008] In an optional implementation, identifying the target interface component in the corresponding interface components based on the component identification pattern includes:

[0009] In the case where the component type of the interface component is a first type component, obtaining a preset hierarchical relationship of the interface component based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information;

[0010] Determining whether the rendering range corresponding to the interface component includes the upper-layer interface component based on the preset hierarchical relationship;

[0011] When it is determined that the rendering range corresponding to the interface component does not include the upper-layer interface component, the interface component is determined as the target interface component.

[0012] In an optional implementation, the method further includes:

[0013] In a case where the rendering range corresponding to the interface component does not include an upper-layer interface component, determining, based on the component attribute information, whether the component type of the interface component is a first preset subtype;

[0014] In a case where the component type of the interface component is not a first preset subtype, the interface component is determined as a target interface component.

[0015] In an optional implementation, identifying the target interface component in the corresponding interface components based on the component identification pattern includes:

[0016] In a case where the component type of the interface component is a first type component, determining whether the interface component is a second preset subtype based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information;

[0017] In a case where the interface component is of a second preset subtype, determining component size information and a preset hierarchical relationship of the interface component based on the component attribute information;

[0018] When the component size information of the interface component does not meet the preset size requirement and it is determined based on the preset hierarchical relationship that the interface component does not include a lower-layer interface component, the interface component is determined as a target interface component.

[0019] In an optional implementation, identifying a target interface component from corresponding interface components based on the component identification pattern includes:

[0020] When the component type of the interface component is a second-type component, obtaining visual setting information of the interface component determined based on the component attribute information; the visual setting information includes at least one of the following: component size information, transparency information, and hidden information; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0021] Determining whether the visual setting information meets the setting requirements;

[0022] If it is determined that the visual setting information does not meet the setting requirements, the interface component is determined as a target interface component.

[0023] In an optional implementation, identifying the target interface component in the corresponding interface components based on the component identification pattern includes:

[0024] In a case where the component type of the interface component is a second-type component, determining a component subtype of the interface component based on the component attribute information, and determining a component sub-identification mode corresponding to the component subtype; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0025] When it is determined that the interface component does not satisfy the identification condition corresponding to the component sub-identification mode, the interface component is determined as a target interface component.

[0026] In an optional implementation, identifying the target interface component in the corresponding interface components based on the component identification pattern includes:

[0027] In a case where the component type of the interface component is a second-type component, determining an adjacent interface component of the interface component; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0028] Determining an intersection type between the interface component and the adjacent interface component; the intersection type includes a first intersection type and a second intersection type;

[0029] When the intersection type is the first intersection type, obtaining a preset hierarchical relationship of the interface components, and determining an overlapping relationship between the interface component and the adjacent interface component based on the hierarchical relationship;

[0030] A covered interface component between the interface component and the adjacent interface component is determined based on the covering relationship, and the covered interface component is determined as a target interface component.

[0031] In an optional implementation, the method further includes:

[0032] When the intersection type is the second intersection type, determining intersection area data between the interface component and the adjacent interface component;

[0033] Determining whether the intersection area data meets the intersection area requirement;

[0034] When it is determined that the intersection area data does not meet the intersection area requirement, obtaining a preset hierarchical relationship of the interface components, and determining an overlapping relationship between the interface component and the adjacent interface component based on the hierarchical relationship;

[0035] A covered interface component between the interface component and the adjacent interface component is determined based on the covering relationship, and the covered interface component is determined as a target interface component.

[0036] In a second aspect, an embodiment of the present disclosure further provides an interface component identification device, comprising:

[0037] An acquisition unit, configured to acquire component attribute information of at least one interface component in a UI interface design draft;

[0038] a determining unit, configured to determine a component type of each of the interface components based on the component attribute information, obtain at least one component type, and determine a component identification mode corresponding to each of the component types;

[0039] An identification unit is used to identify a target interface component in the corresponding interface component based on the component identification pattern; wherein, the target interface component is an interface component whose rendering result is not displayed on the UI interface design draft among the interface components belonging to the corresponding component type.

[0040] In a third aspect, an embodiment of the present disclosure further provides a computer device comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the computer device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the above-mentioned first aspect or any possible implementation of the first aspect are performed.

[0041] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned first aspect or any possible implementation of the first aspect are executed.

[0042] In an embodiment of the present disclosure, after obtaining the component attribute information of at least one interface component in the UI interface design draft, the component type of each interface component can be determined, and the component identification mode corresponding to each component type can be determined, so as to identify the target interface component whose rendering result is not displayed on the UI interface design draft according to the component identification mode, thereby achieving the effect of identifying the target interface component that does not need to be rendered, so that the designer can process the target interface component, thereby simplifying the UI interface design draft, and reducing the later maintenance cost of the UI interface determined according to the UI interface design draft and the terminal device memory occupied when the UI interface is loaded.

[0043] In order to make the above-mentioned objectives, features and advantages of the present disclosure more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the embodiments. The drawings herein are incorporated into and constitute a part of the specification. These drawings illustrate embodiments consistent with the present disclosure and, together with the specification, are used to illustrate the technical solutions of the present disclosure. It should be understood that the following drawings only illustrate certain embodiments of the present disclosure and should not be regarded as limiting the scope. For those of ordinary skill in the art, other relevant drawings can be obtained based on these drawings without inventive effort.

[0045] Figure 1 A flow chart of an interface component identification method provided by an embodiment of the present disclosure is shown;

[0046] Figure 2 A schematic diagram showing some interface components in the UI interface design draft provided by an embodiment of the present disclosure is shown;

[0047] Figure 3 A schematic diagram showing the rendering effect of the Mask interface component provided by an embodiment of the present disclosure is shown;

[0048] Figure 4 A schematic diagram of an interface component identification device provided by an embodiment of the present disclosure is shown;

[0049] Figure 5 A schematic diagram of a computer device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. The components of the embodiments of the present disclosure generally described and shown in the drawings herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the disclosure for which protection is sought, but merely represents selected embodiments of the present disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present disclosure.

[0051] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings.

[0052] The term "and / or" herein simply describes an association relationship, indicating that three relationships can exist. For example, A and / or B can represent the existence of A alone, the simultaneous existence of A and B, and the existence of B alone. In addition, the term "at least one" herein refers to any combination of at least two of any one or more of a plurality of items. For example, "at least one of A, B, and C" can represent any one or more elements selected from the set consisting of A, B, and C.

[0053] Research has found that because designers usually do not consider the rendering effect of the UI interface during the design process, the resulting UI interface design drafts are often too messy and filled with several useless interface components. As a result, the UI interface code generated for the UI interface design draft through the D2C (design to code) method is relatively complex, which increases the subsequent maintenance cost of the UI interface and causes a large amount of terminal device memory to be occupied when loading the UI interface.

[0054] Based on the above research, the present disclosure provides an interface component identification method, apparatus, computer equipment and storage medium. In an embodiment of the present disclosure, after obtaining the component attribute information of at least one interface component in the UI interface design draft, the component type of each interface component can be determined, and the component identification mode corresponding to each component type can be determined, so as to identify the target interface component whose rendering result is not displayed on the UI interface design draft according to the component identification mode, thereby achieving the effect of identifying the target interface component that does not need to be rendered, so that the designer can process the target interface component, thereby simplifying the UI interface design draft, thereby reducing the later maintenance cost of the UI interface determined according to the UI interface design draft and the terminal device memory occupied when the UI interface is loaded.

[0055] To facilitate understanding of this embodiment, we first provide a detailed introduction to a method for identifying an interface component disclosed in this embodiment. The method provided in this embodiment is generally executed by a computer device with sufficient computing power. In some possible implementations, this method can be implemented by a processor invoking computer-readable instructions stored in a memory.

[0056] See also Figure 1 FIG. 1 is a flow chart of an interface component identification method provided by an embodiment of the present disclosure, the method comprising steps S101 to S105, wherein:

[0057] S101: Obtain component attribute information of at least one interface component in a UI interface design draft.

[0058] In the embodiment of the present disclosure, the above-mentioned UI interface design draft may be a design draft of a user interface. Here, the interface code of the user interface may be obtained based on the UI interface design draft through a D2C (design to code) method.

[0059] Before performing D2C on the above UI interface design draft, the interface components in the UI interface design draft may be identified first, and the UI interface design draft may be modified according to the identification results, thereby improving the quality of the UI interface design draft.

[0060] In a specific implementation, component attribute information of at least one interface component in the UI interface design draft can be first obtained. Here, in the process of obtaining component attribute information, all interface components included in the UI interface design draft can be identified and component attribute information of all interface components can be obtained. Interface components with to-be-identified identifiers in the UI interface design draft can also be identified and component attribute information of the identified interface components can be obtained.

[0061] It should be understood that users can mark the interface components in the UI interface design draft through the identifier to be identified. For example, users can mark all Icon-type interface components in the UI interface design draft through the identifier to be identified to obtain component attribute information of all Icon-type interface components in the UI interface design draft.

[0062] S103: Determine the component type of each of the interface components based on the component attribute information, obtain at least one component type, and determine a component identification mode corresponding to each of the component types.

[0063] In the embodiment of the present disclosure, the above-mentioned component attribute information includes component type information, and the component type of the corresponding interface component can be determined based on the component type information, thereby obtaining at least one component type.

[0064] For example, the above component types may include UI interface components and structural interface components. Here, UI interface components may be interface components with visual meaning, that is, interface components that can be seen by users, such as Icon type interface components, Image type interface components, and Text type interface components.

[0065] Alternatively, structural interface components can be structurally meaningful, i.e., components used to form the UI structure. Structural interface components are typically containers for UI components and may not have visual significance, i.e., be invisible to the user. Examples include Frame and Mask interface components.

[0066] For example, if Figure 2 The following diagram shows some interface components in the UI design draft. The Icon1, Icon2, Image, and Text components are UI-class components, visible to the user and enabling them to interact with the UI. The Frame component is a structural component, serving as the framework for these components and supporting the Icon1, Icon2, Image, and Text components. However, the Frame component is invisible to the user during actual use.

[0067] It should be understood that for interface components of different component types, the standards for determining whether the rendering results of the interface components are displayed are different. Therefore, after determining at least one of the above component types, the component identification mode corresponding to the interface components of each component type can be determined.

[0068] S105: Identify a target interface component in the corresponding interface components based on the component identification pattern; wherein the target interface component is an interface component of the corresponding component type whose rendering result is not displayed on the UI interface design draft.

[0069] In the embodiment of the present disclosure, when displaying the above-mentioned UI interface design draft on the display interface, it is necessary to render each interface component in the UI interface design draft, so that each rendering result obtained is displayed on the display interface to realize the display of the UI interface design draft.

[0070] However, since the UI interface design draft may have redundant and messy interface components during the design process, during the rendering process of each interface component, the rendering results of some interface components may not be displayed on the display interface.

[0071] For example, in the above UI interface design draft, there are five Image interface components stacked up, resulting in the user only being able to see the rendering results of the Image interface component on the top layer. Although the four Image interface components on the bottom layer are also rendered, the rendering results are blocked by the Image interface component on the top layer, so the user cannot see the rendering results of the four Image interface components on the bottom layer.

[0072] Based on this, in an embodiment of the present disclosure, the target interface component that is not displayed in the rendering result can be identified in the corresponding interface component based on the component identification pattern, so that the designer of the UI interface design draft can adjust the UI interface design draft according to the identified target interface component, thereby simplifying the UI interface design draft.

[0073] From the above description, it can be seen that the present disclosure provides an interface component identification method, device, computer equipment and storage medium. In an embodiment of the present disclosure, after obtaining the component attribute information of at least one interface component in the UI interface design draft, the component type of each interface component can be determined, and the component identification mode corresponding to each component type can be determined, so as to identify the target interface component whose rendering result is not displayed on the UI interface design draft according to the component identification mode, thereby achieving the effect of identifying the target interface component that does not need to be rendered, so that the designer can process the target interface component, thereby simplifying the UI interface design draft, thereby reducing the later maintenance cost of the UI interface determined according to the UI interface design draft and the terminal device memory occupied when the UI interface is loaded.

[0074] In an optional embodiment, the above step S105, identifying the target interface component in the corresponding interface components based on the component identification pattern, specifically includes the following process:

[0075] S1051: When the component type of the interface component is a first-type component, obtain a preset hierarchical relationship of the interface component based on the component attribute information; wherein the first-type component is used to indicate that the interface component includes corresponding component structure information.

[0076] In the embodiment of the present disclosure, the above-mentioned first type component can be a structural interface component. When it is determined that the component type of the interface component is a first type component, the component attribute information of the interface component can be obtained, and the preset hierarchical relationship of the interface component indicated by the component attribute information can be determined.

[0077] Here, the preset hierarchical relationship can be used to indicate other interface components that have a stacking relationship with the interface component, for example, to indicate other interface components that contain the interface component, and to indicate other interface components contained in the interface component.

[0078] For example, if Figure 2 As shown, the interface components with a preset hierarchical relationship with the Frame component can be the above-mentioned Icon1 interface component, Icon2 interface component, Image interface component and Text interface component. Taking the Image interface component as an example, the preset hierarchical relationship between the Frame component and the Image interface component can be used to indicate that the Frame component contains the Image interface component.

[0079] S1052: Determine whether the rendering range corresponding to the interface component includes an upper-level interface component based on the preset hierarchical relationship.

[0080] In the embodiment of the present disclosure, the interface components included in the above interface components can be determined as upper-layer interface components, for example, Figure 2 For example, the Image interface component can be determined as the upper interface component of the Frame component.

[0081] After determining the upper-layer interface component corresponding to the above interface component, the rendering range of the upper-layer interface component may be obtained, and it may be determined whether the rendering range of the upper-layer interface component is included in the rendering range of the interface component.

[0082] Here, if the rendering range of the upper-level interface component A is not included in the rendering range of the interface component, it can also be considered that the upper-level interface component A is not the upper-level interface component of the interface component. For example, if the rendering range of the upper-level interface component A exceeds the rendering range of the interface component, then it can be considered that the upper-level interface component A is not the upper-level interface component of the interface component.

[0083] S1053: When it is determined that the rendering range corresponding to the interface component does not include the upper-layer interface component, the interface component is determined as a target interface component.

[0084] In the embodiment of the present disclosure, since the above-mentioned interface component is a structural interface component, the rendering result of the interface component itself is empty. Then, when the rendering range of the interface component does not include the upper-level interface component, it can be determined that the interface component has no rendering meaning, and the interface component is determined as the target interface component.

[0085] It should be noted that, in the case where the above-mentioned interface component is a first type component, if the interface component is determined to be a target interface component, it means that the interface component has no structural significance.

[0086] In the embodiment of the present disclosure, when the component type of the interface component is a first-type component, it can be determined based on the preset hierarchical relationship of the interface component whether the rendering range of the interface component includes the upper-level interface component. When the rendering range of the interface component does not include the upper-level interface component, the interface component can be determined as the target interface component, so that the designer can simplify the UI interface design draft according to the determined target interface component.

[0087] In one embodiment, when the rendering range corresponding to the above interface component does not include the upper interface component, the above method further includes the following process:

[0088] (1) determining whether the component type of the interface component is a first preset subtype based on the component attribute information;

[0089] (2) When the component type of the interface component is not the first preset subtype, the interface component is determined as a target interface component.

[0090] In an embodiment of the present disclosure, when it is determined that the rendering range corresponding to the above-mentioned interface component does not include the upper-level interface component, it can also be determined whether the interface component hits the first preset sub-type. When the interface component does not hit the first preset sub-type, the interface component can be determined as the target interface component.

[0091] Here, the above-mentioned first preset subtype can be a Frame type. It should be understood that in the process of designing the above-mentioned UI interface design draft, a blank area can be reserved in the UI interface design draft through a Frame type interface component. For example, when the UI interface design draft is a certain agreement signing interface, the blank area can be a user name signing area. In addition, the above-mentioned first preset subtype can also be other interface component types that can reserve a blank area in the UI interface design draft, and this disclosure does not make specific limitations on this.

[0092] In the disclosed embodiment, when it is determined that the rendering range corresponding to the above-mentioned interface component does not include the upper-level interface component, the parent node of the interface component can also be determined. The parent node can be another interface component that includes the interface component. Here, when the parent node of the interface component is the above-mentioned Frame-type interface component, it can also be considered that the interface component has rendering significance and is not the target interface component.

[0093] For example, if the above interface component is located within a Frame-type interface component, and the interface component does not contain an upper-level interface component, then the interface component can serve as a placeholder interface component, thereby occupying a certain position in the UI interface design draft and visually separating the different interface components in the UI interface design draft. For example, in the above UI interface design draft, the Frame interface component contains two functional areas, and each functional area contains several interface components. Then, another Frame interface component can be inserted between the two functional areas to separate the two functional areas.

[0094] In the embodiment of the present disclosure, when the above-mentioned interface component does not include the upper-layer interface component, it is also possible to determine whether the interface component is of the first preset subtype, and only when the interface component is of the first preset subtype, the interface component will be determined as the target interface component, thereby making the method of determining the target interface component more flexible and reducing the possibility of misjudging the target interface component.

[0095] In an optional embodiment, the above step S105, identifying the target interface component in the corresponding interface components based on the component identification pattern, specifically further includes the following process:

[0096] (1) When the component type of the interface component is a first type component, determining whether the interface component is a second preset subtype based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information;

[0097] (2) when the interface component is of the second preset subtype, determining the component size information and the preset hierarchical relationship of the interface component based on the component attribute information;

[0098] (3) When the component size information of the interface component does not meet the preset size requirement and it is determined based on the preset hierarchical relationship that the interface component does not include a lower-layer interface component, the interface component is determined as a target interface component.

[0099] In the embodiment of the present disclosure, the above-mentioned first type of components can also be divided into multiple different subtypes. Since the rendering mechanisms of interface components of different subtypes may be different, the component identification modes of the target interface components corresponding to interface components of different subtypes may also be different.

[0100] During specific implementation, it may be determined whether the interface component of the first type component is of a second preset subtype, wherein the second preset subtype may be a Mask type.

[0101] Here, the rendering effect of the Mask interface component is as follows Figure 3 As shown, within the rendering range of the Mask interface group, at least part of the rendering results of the lower interface component A of the Mask interface can be viewed, wherein the at least part of the rendering results is the partial rendering results located within the rendering range of the Mask interface component.

[0102] When the component type of the above-mentioned interface component is the above-mentioned first type component, the component size information and preset hierarchical relationship of the interface component can be obtained, and it can be determined whether the component size information of the interface component meets the preset size requirements, and whether the rendering range of the interface component contains the lower-level interface component.

[0103] In specific implementations, the preset size requirement may include fixed size data. For example, if the size is not 0, then if the component size information of the interface component is 0, it can be determined that the interface component does not meet the preset size requirement. In addition, if the interface component includes a lower-level interface component, the preset size requirement may also be used to represent the area ratio of at least a portion of the rendering result of the lower-level interface component that can be viewed to the entire rendering result.

[0104] For example, Figure 3 For example, Figure 3 Within the rendering range of the Mask interface component, it can be seen that the area of ​​at least part of the rendering result of the lower interface component A of the Mask interface is A1, the area of ​​the entire rendering result of the lower interface component A is A2, the result of A1 / A2 is 60%, and the area ratio indicated by the above preset size requirement is 70%. The result of A1 / A2 is smaller than the area ratio indicated by the preset size requirement, then, it can be determined that the Mask interface component does not meet the preset size requirement, and the Mask interface component is determined to be the target interface component.

[0105] In addition, when the rendering range of the second preset sub-type interface component does not include the lower-layer interface component, the interface component can also be directly determined as the target interface component.

[0106] In an embodiment of the present disclosure, when the above-mentioned interface component is of the second preset sub-type, it can be determined whether the interface component meets the preset size requirements and whether the interface component includes a lower-layer interface component. In the case that the interface component does not meet the preset size requirements and does not include a lower-layer interface component, the interface component is determined to be the target interface component. Therefore, the present disclosure can determine the interface component of the second preset sub-type through two determination methods, thereby reducing the possibility of misjudging the target interface component.

[0107] In an optional embodiment, the above step S105, identifying the target interface component in the corresponding interface components based on the component identification pattern, specifically further includes the following process:

[0108] (1) when the component type of the interface component is a second-type component, obtaining visual setting information of the interface component determined based on the component attribute information; the visual setting information includes at least one of the following: component size information, transparency information, and hidden information; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0109] (2) determining whether the visual setting information meets the setting requirements;

[0110] (3) When it is determined that the visual setting information does not meet the setting requirements, the interface component is determined as the target interface component.

[0111] In an embodiment of the present disclosure, the above-mentioned second-type component can be a UI-type interface component. When it is determined that the component type of the interface component is a second-type component, the visual setting information of the interface component can be obtained, and it can be determined whether the visual setting information meets the setting requirements, wherein the visual setting information includes at least one of the following: component size information, transparency information, and hidden information.

[0112] When the above-mentioned visual setting information of the interface component includes component size information, in the process of determining whether the component size information meets the setting requirements, the determination can be made through the following two steps:

[0113] Step 1:

[0114] Obtain the preset size requirements in the above setting requirements, and determine whether the component size information of the above interface component meets the above component size requirements. If the component size requirements of the above interface component do not meet the preset size requirements, the interface component can be determined as the target interface component.

[0115] For example, the above-mentioned preset size requirement may include fixed size data, for example, the size is not 0. Then, when the component size information of the interface component is 0, it can be determined that the interface component does not meet the preset size requirement.

[0116] It should be noted that when the rendering result of the interface component is not affected by the component size information, if the component size information of the interface component does not meet the preset size requirements, it can also be determined that the interface component is not the target interface component. For example, if the interface component is a Text-type interface component, the text in the interface component may not be affected by the component size information of the interface component when rendering. Therefore, if the size information of the Text-type interface component does not meet the preset size requirements, it can also be determined that the Text-type interface component is not the target interface component.

[0117] In addition, when it is determined that the component size information of the above-mentioned interface component meets the preset size requirement, the following step 2 can be performed.

[0118] Step 2:

[0119] Based on the preset hierarchical relationship of the above-mentioned interface components, the lower-level interface component corresponding to the interface component is determined, and the component size information of the lower-level interface component is determined based on the component attribute information of the lower-level interface component. If the component size information of the lower-level interface component is smaller than the component size information of the interface component, it can be determined that the display range of the rendering result of the interface component exceeds the rendering range of the lower-level interface component. Therefore, the display setting information of the lower-level interface component can be determined based on the component attribute information of the lower-level interface component.

[0120] Here, the display setting information of the interface component can be divided into allowing out-of-bounds rendering and not allowing out-of-bounds rendering. When the display setting information is not allowing out-of-bounds rendering, for the upper-level interface component whose component size information is smaller than the component size information of the interface component, the rendering result of the upper-level interface component can only be displayed within the rendering range of the interface component, so the rendering result of the upper-level interface cannot be fully displayed. In addition, when the display setting information is allowing out-of-bounds rendering, the rendering result of any upper-level interface component in the interface component can be displayed.

[0121] Therefore, when the display range of the rendering result of the interface component of the above-mentioned second type component exceeds the rendering range of the lower-level interface component of the interface component, the display setting information of the lower-level interface component can be determined. When the display setting information of the lower-level interface component does not allow out-of-bounds rendering, it can be considered that the rendering result of the interface component cannot be fully displayed. Therefore, the interface component can be determined as the target interface component.

[0122] If the visual setting information of the interface component includes transparency information, the preset transparency requirement in the setting requirements can be obtained, and if the transparency information of the interface component does not meet the preset transparency requirement, the interface component can be determined as a target interface component that does not meet the setting requirements. It should be understood that if the interface component does not meet the preset transparency requirement, it can be determined that the interface component has no visual significance, that is, it is approximately invisible to the naked eye.

[0123] For example, the preset transparency requirement may be 5%. When the transparency information of an interface component is less than the preset transparency requirement, the interface component may be determined to be a target interface component without visual significance.

[0124] In the case where the visual setting information of the above-mentioned interface component includes hidden information, the hidden information can be divided into hidden and visible. Therefore, when the hidden information of the interface component is set to hidden, it can be determined that the interface component is a target interface component that does not meet the setting requirements. Conversely, when the hidden information of the interface component is set to visible, it can be determined that the interface component is not a target interface component.

[0125] It should be noted that, in the case where the above-mentioned interface component is a second-type component, if the interface component is determined to be a target interface component, it means that the interface component has no visual meaning.

[0126] In an embodiment of the present disclosure, when the component type of the interface component is the second type, the visual setting information of the interface component can be obtained, and it can be determined whether the visual setting information meets the setting requirements. If the visual setting information of the interface component does not meet the setting requirements, the interface component is determined to be the target interface component, thereby enriching the determination method of whether interface components of different component types are target interface components of the present disclosure and improving the scope of application of the present disclosure.

[0127] In an optional embodiment, the above step S105, identifying the target interface component in the corresponding interface components based on the component identification pattern, specifically further includes the following process:

[0128] (1) When the component type of the interface component is a second-type component, determining a component subtype of the interface component based on the component attribute information, and determining a component sub-identification mode corresponding to the component subtype; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0129] (2) When it is determined that the interface component does not satisfy the identification condition corresponding to the component sub-identification mode, the interface component is determined as a target interface component.

[0130] In the embodiment of the present disclosure, the interface component whose component type is the second type component may further include different component subtypes, and the component sub-identification modes corresponding to each component subtype may be different.

[0131] It should be noted that, when the aforementioned UI interface component contains corresponding component rendering information, the component type of the interface component can be both a first-type component and a second-type component. Therefore, the component subtype here can first be a UI interface component containing corresponding component rendering information, for example, a Boolean_Operation (logical border) interface component or a Frame / Rectangle (border) interface component.

[0132] When the component subtype of the above-mentioned interface component is Boolean_Operation type, whether the interface component is the target component depends on whether the interface component has an upper-level interface component. Specifically, when the interface component does not have an upper-level interface component, it can be determined that the interface component is the target interface component.

[0133] Therefore, for an interface component whose subtype is Boolean_Operation, it is first necessary to obtain the preset hierarchical relationship of the interface component based on the attribute information of the interface component, and then determine whether the interface component contains an upper-level interface component based on the preset hierarchical relationship. If the interface component does not contain an upper-level interface component, the interface component is determined to be the target interface component.

[0134] In the case that the component subtype of the above interface component is Frame / Rectangle type, it is first determined whether the interface component has a frame. If the interface component does not have a frame, the interface component is determined to be the target interface component.

[0135] In addition, when the interface component has a border, it is possible to determine whether the filling information of the interface meets the filling requirements, wherein the filling information can be used to indicate whether the interface component contains a filling instance or a shadow fill, and the filling instance can be a filling color or a filling background image.

[0136] In specific implementation, the filling information of the interface component can be first determined based on the component attribute information of the above-mentioned interface component. When it is determined based on the filling information of the interface component that the interface component does not contain a filling instance and does not contain shadow filling, it can be determined that the interface component does not meet the filling requirements, and the interface component can be determined as the target interface component.

[0137] In addition, the component subtype of the above-mentioned interface component can also be a Text type. Whether the interface component of the Text type is the target interface component depends on the text content contained in the interface component. Specifically, when the text content contained in the interface component is empty, the interface component is determined to be the target interface component. Therefore, in the process of determining whether the interface component is the target interface component, the text content contained in the interface component can first be obtained based on the component attribute information of the interface component. When it is determined that the text content is empty, the interface component can be determined to be the target interface component.

[0138] In the embodiment of the present disclosure, interface components of different component subtypes may correspond to different component sub-identification modes, thereby improving the flexibility of the method for identifying the target interface component and improving the accuracy of identifying the target interface component.

[0139] In an optional embodiment, the above step S105, identifying the target interface component in the corresponding interface components based on the component identification pattern, specifically further includes the following process:

[0140] (1) When the component type of the interface component is a second-type component, determining an adjacent interface component of the interface component; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0141] (2) determining an intersection type between the interface component and the adjacent interface component; the intersection type includes a first intersection type and a second intersection type;

[0142] (3) when the intersection type is the first intersection type, obtaining a preset hierarchical relationship of the interface components, and determining an overlay relationship between the interface component and the adjacent interface component based on the hierarchical relationship;

[0143] (4) Determine the covered interface component between the interface component and the adjacent interface component based on the covering relationship, and determine the covered interface component as the target interface component.

[0144] In the embodiment of the present disclosure, when the component type of the above-mentioned interface component is a second-type component, it is also possible to determine whether the interface drilling and the adjacent interface component intersect based on the adjacent interface components of the interface component. If so, the type of intersection between the interface component and the adjacent interface component is determined.

[0145] During specific implementation, the adjacent interface components in the four directions of up, down, left and right of the above-mentioned interface component can be obtained respectively, and the rendering range of each adjacent interface component can be obtained respectively. When the rendering range of any adjacent interface component intersects with the interface component, the adjacent interface components intersecting with the interface component can be determined, and the intersection type can be determined.

[0146] Here, the first intersection type can be used to indicate that the interface component and the adjacent interface component are in a covering relationship of inclusion and being included. For example, the interface component is a lower-level interface component of the adjacent interface component, and the rendering range of the interface component includes the rendering range of the adjacent interface component.

[0147] Therefore, when it is determined that the intersection type between the interface component and the adjacent interface component is the first intersection type, the preset hierarchical relationship between the interface component and the adjacent interface component can be determined first based on the component attribute information, and based on the preset hierarchical relationship, it can be determined as the lower-level interface component among the interface component and the adjacent interface component, and the remaining other interface component can be determined as the upper-level interface component.

[0148] After determining the lower interface component among the interface component and the adjacent interface components, it can be determined whether the rendering range of the lower interface component exceeds the rendering range of the upper interface component, thereby determining the coverage relationship between the interface component and the adjacent interface components.

[0149] When the rendering range of the lower-level interface component does not exceed the rendering range of the upper-level interface component, it can be determined that the coverage relationship between the interface component and the adjacent interface component is that the lower-level interface component is covered by the upper-level interface, and the lower-level interface component is the covered interface component, and the covered interface component is determined as the target interface component.

[0150] For example, the intersection type between interface component A and adjacent interface component B is the first intersection type, and in interface component A and adjacent interface component B, interface component A is the lower-layer interface component, then adjacent interface component B is the upper-layer interface component. At this time, it can be determined whether the rendering range of interface component A exceeds the rendering range of adjacent interface component B. If the rendering range of interface component A does not exceed the rendering range of adjacent interface component B, it can be determined that the covering relationship between interface component A and adjacent interface component B is that interface component A is covered by adjacent interface component B, and interface component A is the covering interface component. Then, it can be determined that interface component A is the target interface component.

[0151] In the embodiment of the present disclosure, when the component type of the interface component is a second-type component, the intersection type between the interface component and the adjacent interface component can also be determined, and the target interface component can be determined based on the intersection type, thereby improving the determination method of the target interface component and improving the accuracy of determining the target interface component.

[0152] In an optional embodiment, when the intersection type is the second intersection type, the method further includes the following process:

[0153] (1) determining the intersection area data between the interface component and the adjacent interface component;

[0154] (2) determining whether the intersection area data meets the intersection area requirement;

[0155] (3) When it is determined that the intersection area data does not meet the intersection area requirement, obtaining a preset hierarchical relationship of the interface components, and determining an overlay relationship between the interface component and the adjacent interface component based on the hierarchical relationship;

[0156] (4) Determine the covered interface component between the interface component and the adjacent interface component based on the covering relationship, and determine the covered interface component as the target interface component.

[0157] In the disclosed embodiment, the second type may be used to indicate that an interface component intersects and does not contain an adjacent interface component (the intersection area is less than 100%). When it is determined that the intersection type between the interface component and the adjacent interface component is the second intersection type, the intersection area data between the interface component and the adjacent interface component may be first determined, and then it may be determined whether the intersection area data meets the intersection area requirement.

[0158] Here, the above intersection area requirement can be expressed as Ratio < 0.9, where Ratio is the ratio of the intersection area data ISAB to the interface component area SA or the adjacent interface component area SB, that is, Ratio = ISAB / Min(SA, SB). Here, Min(SA, SB) means the smaller of the interface component area SA and the adjacent interface component area SB. For example, if the interface component area SA is smaller than the adjacent interface component area SB, then Min(SA, SB) = SA.

[0159] In the disclosed embodiment, the value of the Ratio can be calculated first, and if the Ratio is ≥ 0.9, it is determined that the intersection area data does not meet the intersection area requirement. Then, the preset hierarchical relationship of the interface components can be obtained, and the coverage relationship between the interface component and the adjacent interface components can be determined based on the preset hierarchical relationship.

[0160] Here, first, based on the above-mentioned preset hierarchical relationship, the layer number information of the interface component and the adjacent interface component can be obtained respectively. The larger the layer number information, the higher the hierarchy of the interface component. Specifically, the overlapping relationship between the interface component and the adjacent interface component can be determined based on the layer number information. For example, if the layer number information of the interface component is 1 and the layer number information of the adjacent interface component is 2, then the overlapping relationship between the interface component and the adjacent interface component can be: the interface component is the lower interface component of the adjacent interface component.

[0161] Next, based on the above-mentioned covering relationship, the lower interface component between the interface component and the adjacent interface component can be determined as the covered interface component, and the determined covered interface component can be determined as the target interface component. For example, if the interface component is the lower interface component of the adjacent interface component, the interface component can be determined as the target interface component.

[0162] In the embodiment of the present disclosure, when the intersection type between the interface component and the adjacent interface component is the second intersection type, it is possible to determine whether the intersection area data between the interface component and the adjacent interface component meets the intersection area requirement, and when the intersection requirement is not met, the covered interface component is determined, and the covered interface component is determined as the target interface component, so that the present solution can be applied to the determination of the target interface component when the interface components intersect but are not contained, thereby improving the scope of application of the present solution.

[0163] In summary, in the embodiment of the present disclosure, after obtaining the component attribute information of at least one interface component in the UI interface design draft, the component type of each interface component can be determined, and the component identification mode corresponding to each component type can be determined, so as to identify the target interface component whose rendering result is not displayed on the UI interface design draft according to the component identification mode, thereby achieving the effect of identifying the target interface component that does not need to be rendered, so that the designer can process the target interface component, thereby simplifying the UI interface design draft, and reducing the later maintenance cost of the UI interface determined according to the UI interface design draft and the terminal device memory occupied when the UI interface is loaded.

[0164] Those skilled in the art will understand that in the above-mentioned method of the specific implementation method, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0165] Based on the same inventive concept, an interface component identification device corresponding to the interface component identification method is also provided in the embodiment of the present disclosure. Since the principle of solving the problem by the device in the embodiment of the present disclosure is similar to the above-mentioned interface component identification method in the embodiment of the present disclosure, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0166] Reference Figure 4 FIG. 1 is a schematic diagram of an interface component identification device provided by an embodiment of the present disclosure, wherein the device includes: an acquisition unit 41, a determination unit 42, and an identification unit 43; wherein,

[0167] The acquisition unit 41 is used to acquire component attribute information of at least one interface component in the UI interface design draft;

[0168] a determining unit 42 configured to determine a component type of each of the interface components based on the component attribute information, obtain at least one component type, and determine a component identification mode corresponding to each component type;

[0169] The identification unit 43 is used to identify the target interface component in the corresponding interface component based on the component identification pattern; wherein, the target interface component is an interface component whose rendering result is not displayed on the UI interface design draft among the interface components belonging to the corresponding component type.

[0170] In an embodiment of the present disclosure, after obtaining the component attribute information of at least one interface component in the UI interface design draft, the component type of each interface component can be determined, and the component identification mode corresponding to each component type can be determined, so as to identify the target interface component whose rendering result is not displayed on the UI interface design draft according to the component identification mode, thereby achieving the effect of identifying the target interface component that does not need to be rendered, so that the designer can process the target interface component, thereby simplifying the UI interface design draft, and reducing the later maintenance cost of the UI interface determined according to the UI interface design draft and the terminal device memory occupied when the UI interface is loaded.

[0171] In a possible implementation, the identification unit 43 is further configured to:

[0172] In the case where the component type of the interface component is a first type component, obtaining a preset hierarchical relationship of the interface component based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information;

[0173] Determining whether the rendering range corresponding to the interface component includes the upper-layer interface component based on the preset hierarchical relationship;

[0174] When it is determined that the rendering range corresponding to the interface component does not include the upper-layer interface component, the interface component is determined as the target interface component.

[0175] In a possible implementation, the identification unit 43 is further configured to:

[0176] In a case where the rendering range corresponding to the interface component does not include an upper-layer interface component, determining, based on the component attribute information, whether the component type of the interface component is a first preset subtype;

[0177] In a case where the component type of the interface component is not a first preset subtype, the interface component is determined as a target interface component.

[0178] In a possible implementation, the identification unit 43 is further configured to:

[0179] In a case where the component type of the interface component is a first type component, determining whether the interface component is a second preset subtype based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information;

[0180] In a case where the interface component is of a second preset subtype, determining component size information and a preset hierarchical relationship of the interface component based on the component attribute information;

[0181] When the component size information of the interface component does not meet the preset size requirement and it is determined based on the preset hierarchical relationship that the interface component does not include a lower-layer interface component, the interface component is determined as a target interface component.

[0182] In a possible implementation, the identification unit 43 is further configured to:

[0183] When the component type of the interface component is a second-type component, obtaining visual setting information of the interface component determined based on the component attribute information; the visual setting information includes at least one of the following: component size information, transparency information, and hidden information; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0184] Determining whether the visual setting information meets the setting requirements;

[0185] If it is determined that the visual setting information does not meet the setting requirements, the interface component is determined as a target interface component.

[0186] In a possible implementation, the identification unit 43 is further configured to:

[0187] In a case where the component type of the interface component is a second-type component, determining a component subtype of the interface component based on the component attribute information, and determining a component sub-identification mode corresponding to the component subtype; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0188] When it is determined that the interface component does not satisfy the identification condition corresponding to the component sub-identification mode, the interface component is determined as a target interface component.

[0189] In a possible implementation, the identification unit 43 is further configured to:

[0190] In a case where the component type of the interface component is a second-type component, determining an adjacent interface component of the interface component; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information;

[0191] Determining an intersection type between the interface component and the adjacent interface component; the intersection type includes a first intersection type and a second intersection type;

[0192] When the intersection type is the first intersection type, obtaining a preset hierarchical relationship of the interface components, and determining an overlapping relationship between the interface component and the adjacent interface component based on the hierarchical relationship;

[0193] A covered interface component between the interface component and the adjacent interface component is determined based on the covering relationship, and the covered interface component is determined as a target interface component.

[0194] In a possible implementation, the identification unit 43 is further configured to:

[0195] When the intersection type is the second intersection type, determining intersection area data between the interface component and the adjacent interface component;

[0196] Determining whether the intersection area data meets the intersection area requirement;

[0197] When it is determined that the intersection area data does not meet the intersection area requirement, obtaining a preset hierarchical relationship of the interface components, and determining an overlapping relationship between the interface component and the adjacent interface component based on the hierarchical relationship;

[0198] A covered interface component between the interface component and the adjacent interface component is determined based on the covering relationship, and the covered interface component is determined as a target interface component.

[0199] For descriptions of the processing flow of each unit in the device and the interaction flow between each unit, reference can be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0200] Corresponding to Figure 1 The interface component identification method in the present disclosure also provides a computer device 500, such as Figure 5 FIG. 5 is a schematic diagram of the structure of a computer device 500 provided in an embodiment of the present disclosure, including:

[0201] Processor 51, memory 52, and bus 53; memory 52 is used to store execution instructions and includes internal memory 521 and external memory 522; the internal memory 521 is also called internal memory and is used to temporarily store operation data in the processor 51 and data exchanged with external memory 522 such as a hard disk. The processor 51 exchanges data with the external memory 522 through the internal memory 521. When the computer device 500 is running, the processor 51 communicates with the memory 52 via the bus 53, so that the processor 51 executes the following instructions:

[0202] Obtain component attribute information of at least one interface component in the UI interface design draft;

[0203] Determining a component type of each of the interface components based on the component attribute information, obtaining at least one component type, and determining a component identification mode corresponding to each of the component types;

[0204] A target interface component is identified in the corresponding interface components based on the component identification pattern; wherein the target interface component is an interface component of the corresponding component type whose rendering result is not displayed on the UI interface design draft.

[0205] The present disclosure also provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program executes the steps of the interface component identification method described in the above method embodiment. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0206] The embodiments of the present disclosure also provide a computer program product, which carries program code. The instructions included in the program code can be used to execute the steps of the interface component identification method described in the above method embodiment. For details, please refer to the above method embodiment and will not be repeated here.

[0207] The computer program product may be implemented in hardware, software, or a combination thereof. In one embodiment, the computer program product is implemented as a computer storage medium. In another embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0208] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems and devices described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0209] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0210] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0211] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0212] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present disclosure, which are used to illustrate the technical solutions of the present disclosure, rather than to limit them. The scope of protection of the present disclosure is not limited thereto. Although the present disclosure has been described in detail with reference to the above-described embodiments, those skilled in the art should understand that any person skilled in the art can modify or easily conceive of changes to the technical solutions described in the above-described embodiments within the technical scope disclosed in the present disclosure, or replace some of the technical features therein with equivalents. Such modifications, changes, or replacements do not deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure, and should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure shall be subject to the scope of protection of the claims.

Claims

1. A method for identifying an interface component, characterized in that: include: Obtain component attribute information of at least one interface component in the UI interface design draft; Determining a component type of each of the interface components based on the component attribute information to obtain at least one component type, wherein, for interface components of different component types, different criteria are used to determine whether a rendering result of the interface component is to be displayed; Based on the at least one component type, determining a component identification mode corresponding to each component type; Identify a target interface component in the corresponding interface components based on the component identification pattern; wherein the target interface component is an interface component whose rendering result is not displayed on the UI interface design draft among the interface components belonging to the corresponding component type, The step of identifying a target interface component in corresponding interface components based on the component identification pattern includes: In the case where the component type of the interface component is a first type component, obtaining a preset hierarchical relationship of the interface component based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information; Determining whether the rendering range corresponding to the interface component includes the upper-layer interface component based on the preset hierarchical relationship; When it is determined that the rendering range corresponding to the interface component does not include the upper-layer interface component, the interface component is determined as the target interface component. The method further comprises: In a case where the rendering range corresponding to the interface component does not include an upper-layer interface component, determining, based on the component attribute information, whether the component type of the interface component is a first preset subtype; In a case where the component type of the interface component is not a first preset subtype, the interface component is determined as a target interface component.

2. The method according to claim 1, characterized in that The identifying a target interface component in corresponding interface components based on the component identification pattern includes: In a case where the component type of the interface component is a first type component, determining whether the interface component is a second preset subtype based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information; In a case where the interface component is of a second preset subtype, determining component size information and a preset hierarchical relationship of the interface component based on the component attribute information; When the component size information of the interface component does not meet the preset size requirement and it is determined based on the preset hierarchical relationship that the interface component does not include a lower-layer interface component, the interface component is determined as a target interface component.

3. The method according to claim 1, characterized in that Identifying a target interface component in corresponding interface components based on the component identification pattern includes: When the component type of the interface component is a second-type component, obtaining visual setting information of the interface component determined based on the component attribute information; the visual setting information includes at least one of the following: component size information, transparency information, and hidden information; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information; Determining whether the visual setting information meets the setting requirements; If it is determined that the visual setting information does not meet the setting requirements, the interface component is determined as a target interface component.

4. The method according to claim 1, wherein The identifying a target interface component in corresponding interface components based on the component identification pattern includes: In a case where the component type of the interface component is a second-type component, determining a component subtype of the interface component based on the component attribute information, and determining a component sub-identification mode corresponding to the component subtype; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information; When it is determined that the interface component does not satisfy the identification condition corresponding to the component sub-identification mode, the interface component is determined as a target interface component.

5. The method according to claim 1, wherein The identifying a target interface component in corresponding interface components based on the component identification pattern includes: In a case where the component type of the interface component is a second-type component, determining an adjacent interface component of the interface component; wherein the second-type component is used to indicate that the interface component includes corresponding component rendering information; Determining an intersection type between the interface component and the adjacent interface component; the intersection type includes a first intersection type and a second intersection type; When the intersection type is the first intersection type, obtaining a preset hierarchical relationship of the interface components, and determining an overlapping relationship between the interface component and the adjacent interface component based on the hierarchical relationship; A covered interface component between the interface component and the adjacent interface component is determined based on the covering relationship, and the covered interface component is determined as a target interface component.

6. The method according to claim 5, characterized in that The method further comprises: When the intersection type is the second intersection type, determining intersection area data between the interface component and the adjacent interface component; Determining whether the intersection area data meets the intersection area requirement; When it is determined that the intersection area data does not meet the intersection area requirement, obtaining a preset hierarchical relationship of the interface components, and determining an overlapping relationship between the interface component and the adjacent interface component based on the hierarchical relationship; A covered interface component between the interface component and the adjacent interface component is determined based on the covering relationship, and the covered interface component is determined as a target interface component.

7. An interface component identification device, characterized in that: include: An acquisition unit, configured to acquire component attribute information of at least one interface component in a UI interface design draft; a determining unit, configured to determine a component type of each of the interface components based on the component attribute information, obtain at least one component type, and determine a component identification mode corresponding to each component type based on the at least one component type, wherein different criteria for determining whether to display a rendering result of the interface component are used for interface components of different component types; An identification unit is configured to identify a target interface component in the corresponding interface component based on the component identification pattern; wherein the target interface component is an interface component of the corresponding component type whose rendering result is not displayed on the UI interface design draft, Among them, the identification unit is configured as: In the case where the component type of the interface component is a first type component, obtaining a preset hierarchical relationship of the interface component based on the component attribute information; wherein the first type component is used to indicate that the interface component includes corresponding component structure information; Determining whether the rendering range corresponding to the interface component includes the upper-layer interface component based on the preset hierarchical relationship; When it is determined that the rendering range corresponding to the interface component does not include the upper-layer interface component, the interface component is determined as the target interface component. The identification unit is further configured to: In a case where the rendering range corresponding to the interface component does not include an upper-layer interface component, determining, based on the component attribute information, whether the component type of the interface component is a first preset subtype; In a case where the component type of the interface component is not a first preset subtype, the interface component is determined as a target interface component.

8. A computer device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor. When the computer device is running, the processor and the memory communicate via the bus. When the machine-readable instructions are executed by the processor, the steps of the interface component identification method according to any one of claims 1 to 6 are performed.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, executes the steps of the interface component identification method according to any one of claims 1 to 6.

Images