Methods, Apparatus, Devices, and Storage Media for Information Processing

Abstract

One or more embodiments of this specification provide a method, apparatus, device, and storage medium for information processing. Among them, the method includes: obtaining application scenario information of a target component for which attribute information is to be configured; determining a naming rule engine for the attribute information of the target component according to the application scenario information, where the semantic naming logic in the naming rule engine matches the application scenario information; generating a set of optional attribute information for the target component based on the semantic naming logic in the naming rule engine, the set of optional attribute information includes multiple optional attribute information of the target component, and the multiple optional attribute information conforms to the above semantic naming logic; and associatively saving the set of optional attribute information with the component identifier of the target component.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular, to a method, apparatus, device, and storage medium for information processing. Background Art

[0002] Designers can design the front-end interface through an interface design system. Taking the design of an input box interface as an example, designers can select corresponding attribute values for each attribute of the input box interface in the interface design system. For example, select a corresponding size value for the size attribute of the input box interface, and select a corresponding background color value for the background color attribute of the input box interface. However, there is no unified standard for the naming of each attribute value option provided in the current interface design system, and the naming of each attribute value option is not standardized. For example, the background color options are named "100", "200", etc., resulting in designers being unable to quickly understand the meaning represented by each attribute value option through the naming of each attribute value option. Designers need to spend more time retrieving suitable options from each attribute value option to design the interface, reducing the interface design efficiency. Summary of the Invention

[0003] An object of one or more embodiments of this specification is to provide a method for information processing, the method including: obtaining application scenario information of a target component for which attribute information is to be configured. According to the application scenario information, determining a naming rule engine for the attribute information of the target component. The semantic naming logic in the naming rule engine matches the application scenario information. Based on the semantic naming logic in the naming rule engine, generating a set of optional attribute information for the target component. The set of optional attribute information includes multiple optional attribute information of the target component. The multiple optional attribute information conforms to the above semantic naming logic. Associatively storing the set of optional attribute information with the component identifier of the target component.

[0004] An object of one or more embodiments of this specification is to provide an apparatus for information processing, including: an information acquisition unit that acquires application scenario information of a target component for which attribute information is to be configured. An engine determination unit that determines a naming rule engine for the attribute information of the target component according to the application scenario information. The semantic naming logic in the naming rule engine matches the application scenario information. A set generation unit that generates a set of optional attribute information for the target component based on the semantic naming logic in the naming rule engine. The set of optional attribute information includes multiple optional attribute information of the target component. The multiple optional attribute information conforms to the above semantic naming logic. An association storage unit that associatively stores the set of optional attribute information with the component identifier of the target component.

[0005] The purpose of one or more embodiments of this specification is to provide an information processing device, including: a processor; and a memory arranged to store computer-executable instructions. When the computer-executable instructions are executed by the processor, the processor implements the following method: obtaining application scenario information of a target component for which attribute information is to be configured. According to the application scenario information, determining a naming rule engine for the attribute information of the target component. The semantic naming logic in the naming rule engine matches the application scenario information. Based on the semantic naming logic in the naming rule engine, generating a set of optional attribute information for the target component. The set of optional attribute information includes multiple pieces of optional attribute information of the target component. The multiple pieces of optional attribute information conform to the above semantic naming logic. Associatively storing the set of optional attribute information with the component identifier of the target component.

[0006] The purpose of one or more embodiments of this specification is to provide a storage medium for storing computer-executable instructions. When the computer-executable instructions are executed by the processor, the processor implements the following method: obtaining application scenario information of a target component for which attribute information is to be configured. According to the application scenario information, determining a naming rule engine for the attribute information of the target component. The semantic naming logic in the naming rule engine matches the application scenario information. Based on the semantic naming logic in the naming rule engine, generating a set of optional attribute information for the target component. The set of optional attribute information includes multiple pieces of optional attribute information of the target component. The multiple pieces of optional attribute information conform to the above semantic naming logic. Associatively storing the set of optional attribute information with the component identifier of the target component. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] In order to more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in one or more of this specification. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0008] Figure 1 It is a flowchart of the information processing method provided by an embodiment of this specification;

[0009] Figure 2 It is a flowchart of the information processing method provided by another embodiment of this specification;

[0010] Figure 3 It is a flowchart of the information processing method provided by another embodiment of this specification;

[0011] Figure 4 It is a structural diagram of the information processing device provided by an embodiment of this specification;

[0012] Figure 5 A structural schematic diagram of a device for information processing provided for one or more embodiments of this specification. Detailed implementation manners

[0013] In order to enable those skilled in the art to better understand the technical solutions in one or more of this specification, the following will clearly and completely describe the technical solutions in one or more embodiments of this specification with reference to the accompanying drawings in one or more embodiments of this specification. Obviously, the described embodiments are only a part of the embodiments in one or more of this specification, rather than all the embodiments. Based on the embodiments in one or more of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this document.

[0014] It should be noted that, without conflict, the embodiments in this specification and the features in the embodiments can be combined with each other. The following will refer to the drawings and combine the embodiments to detail one or more embodiments of this specification.

[0015] One or more embodiments of this specification provide a method, device, equipment and storage medium for information processing, which can generate optional attribute information of a target component through semantic naming logic based on the application scenario of the target component, so that the naming of the optional attribute information is semantic, facilitating designers to select appropriate attribute information from the optional attribute information of the target component according to the naming of the optional attribute information when designing the target component, avoiding designers spending a lot of time selecting appropriate attribute information, and improving the component design efficiency.

[0016] Figure 1 A flowchart of the method for information processing provided for an embodiment of this specification, as Figure 1 shown, this process includes the following steps:

[0017] Step S102, obtain the application scenario information of the target component whose attribute information is to be configured;

[0018] Step S104, determine the naming rule engine of the attribute information of the target component according to the application scenario information; the semantic naming logic in the naming rule engine matches the application scenario information;

[0019] Step S106, generate a set of optional attribute information of the target component based on the semantic naming logic in the naming rule engine; the set of optional attribute information includes multiple optional attribute information of the target component; the multiple optional attribute information conforms to the above semantic naming logic;

[0020] Step S108, associate and save the set of optional attribute information with the component identifier of the target component.

[0021] It can be seen that through this embodiment, based on the application scenario of the target component, optional attribute information of the target component can be generated through semantic naming logic, so that the naming of the optional attribute information is semanticized, which is convenient for designers to select appropriate attribute information from the optional attribute information of the target component for use when designing the target component, avoiding the designers spending a lot of time selecting appropriate attribute information and improving the component design efficiency.

[0022] Figure 1 The method flow in can be applied to a background server and executed by the background server. Figure 1 In, in the above step S102, application scenario information of the target component for obtaining the attribute information to be configured is obtained. Specifically, the target component can be exemplified by common front-end components such as input boxes and lists. The attribute information of the target component can be exemplified by information such as the foreground color, background color, border size, and border thickness of the target component. The attribute information of the target component is used to determine the display style of the target component. When designing the target component, the designer selects appropriate attribute information of the target component, such as appropriate background color and border size, to generate the target component.

[0023] The application scenario information of the target component includes but is not limited to the program type information of the application program where the target component is located. For example, if the target component is an input box, the program type information of the application program where the input box is located is an instant messaging application program. Another example is that if the target component is a list, the program type information of the application program where the list is located is a financial application program.

[0024] In the above step S102, when the designer is about to design the target component, the application scenario information input by the designer can be obtained, or the designer can pre-set default application scenario information inside the server to indicate that all subsequent designed components are applied to this application scenario, so that the server uses this default application scenario information as the application scenario information of the target component.

[0025] In the above step S104, according to the application scenario information, a naming rule engine for the attribute information of the target component is determined. The semantic naming logic in the naming rule engine for the attribute information of the target component matches the application scenario information. In one embodiment, according to the application scenario information, determining the naming rule engine for the attribute information of the target component is specifically:

[0026] (a1) Among multiple preset application scenarios, select a target scenario that matches the application scenario information;

[0027] (a2) Among multiple component templates pre-configured for the target scenario, select a target component template that matches the target component;

[0028] (a3) Determine the naming rule engine pre-created for the attribute information of the target component template as the naming rule engine for the attribute information of the target component.

[0029] In this embodiment, multiple application scenarios are preset. For example, instant messaging application scenarios, financial application scenarios, video application scenarios, etc. are preset. Among these multiple application scenarios, a target scenario matching the application scenario information is selected. For example, if the application scenario information is the program type information of the application where the target component is located and it is an instant messaging application program, then the instant messaging application scenario is selected as the target scenario.

[0030] In this embodiment, under each application scenario, multiple component templates are configured. For example, under the instant messaging application scenario, an input box template and a list template are configured. Then, among the multiple component templates configured for the target scenario, the component template matching the target component is selected as the target component template. For example, if the target component is an input box, then among the multiple component templates configured for the target scenario, the input box template is selected as the target component template.

[0031] In this embodiment, a naming rule engine is pre-created for the attribute information of each component template under each application scenario. Through this naming rule engine, optional attribute information can be generated for the corresponding component template and the name of the optional attribute information can be determined. Since the most suitable target component template has been selected from each component template under each application scenario for the target component, the naming rule engine pre-created for the attribute information of the target component template is determined as the naming rule engine for the attribute information of the target component.

[0032] The naming rule engine for the attribute information of the target component includes a naming semanticization logic. Based on this naming semanticization logic, optional attribute information of the target component can be generated. Since the most suitable target component template is selected from each component template under each application scenario for the target component and the naming rule engine pre-created for the attribute information of the target component template is determined as the naming rule engine for the attribute information of the target component, the semantic naming logic in the naming rule engine for the attribute information of the target component matches the application scenario information of the target component. Through the semantic naming logic in the naming rule engine for the attribute information of the target component, a suitable set of optional attribute information can be generated for the target component under the application scenario information of the target component.

[0033] In one embodiment, in the above step (a1), when selecting a target scenario matching the application scenario information from the preset multiple application scenarios, specifically:

[0034] (a11) Determine the application scenario name corresponding to the application scenario information;

[0035] (a12) Among a variety of preset application scenarios, select the application scenario whose semantic similarity between the scenario name and the application scenario name meets the preset requirements as the target scenario that matches the application scenario information.

[0036] First, determine the application scenario name corresponding to the application scenario information of the target component, which is preset in advance. For example, if the application scenario information of the target component is the program type information of the application program where the target component is located and it is an instant messaging application program, then the corresponding application scenario name is "instant messaging application scenario" or "instant messaging application program".

[0037] Then, obtain the scenario names of each preset application scenario. For example, the preset application scenarios include instant messaging application scenarios, financial application scenarios, video application scenarios, etc., and the corresponding scenario names are "instant messaging application scenario", "financial application scenario", "video application scenario".

[0038] Finally, compare the semantic similarity between the application scenario name corresponding to the application scenario information and the scenario names of each application scenario, and determine the scenario name whose semantic similarity with the application scenario name corresponding to the application scenario information meets the preset requirements among the scenario names of the preset variety of application scenarios. The application scenario corresponding to the determined scenario name is used as the target scenario that matches the application scenario information. Among them, the preset requirement can be that the semantic similarity is greater than the preset similarity.

[0039] Considering that for the same scenario that is essentially the same, the scenario name of the preset application scenario may not be exactly the same as the application scenario name corresponding to the application scenario information of the target component. For example, among the preset application scenarios, there is a communication application scenario but no instant messaging application scenario, then the corresponding scenario name is "communication application scenario", not "instant messaging application scenario", while the application scenario name corresponding to the application scenario information is "instant messaging application scenario". In this case, through the comparison of semantic similarity, it can be not restricted by the scenario name and the target scenario that matches the application scenario information of the target component can be determined.

[0040] In one embodiment, in step (a2) above, among the variety of component templates preset for the target scenario, select the target component template that matches the target component. Specifically:

[0041] (a21) If among the variety of component templates preset for the target scenario, there is a component template whose component template name is the same as the component name of the target component, then use this component template as the target component template that matches the target component;

[0042] (a22) If there is no component template in the multiple component templates pre-configured for the target scenario whose component template name is the same as the component name of the target component, then obtain the usage information of the target component, and select, from the multiple component templates, the component template whose usage information matches the usage information of the target component as the target component template that matches the target component.

[0043] Specifically, each component template in each application scenario is pre-set with a component template name and usage information. When the component template is an input box, the usage information can be, for example: for inputting information. When the component template is a list, the usage information can be, for example: for displaying information. The target component also has corresponding component name and usage information. First, in the multiple component templates of the target scenario, determine whether there is a component template whose component template name is the same as the component name of the target component. If so, this identical component template is the target component template that matches the target component. For example, in the target scenario, a certain component template is called "input box", and the component name of the target component is also "input box", then this component template is used as the target component template that matches the target component.

[0044] If there is no component template in the multiple component templates of the target scenario whose component template name is the same as the component name of the target component, then compare the usage information of the target component with the usage information of each component template in the target scenario in turn, and use the component template whose usage is the same as that of the target component as the target component template that matches the target component.

[0045] It can be seen that through this embodiment, after determining the target scenario corresponding to the target component, it is preferable to use the component template in the target scenario whose component template name is the same as the component name of the target component as the target component template that matches the target component. In the case where there is no component template whose component template name is the same as the component name of the target component, use the component template whose usage is the same as that of the target component as the target component template that matches the target component. Thus, according to the priority order of name-usage, accurately select the target component template that matches the target component from each component template in the target scenario.

[0046] In a specific embodiment, the target component is an input box for inputting information, and the application scenario information of the target component is a video application program. Then, among the component templates of various preset application scenarios, select the input box template in the video application scenario as the target component template that matches the target component, and determine the naming rule engine created for the attribute information of the input box template as the naming rule engine for the attribute information of the target component.

[0047] It can be understood from the above description that the naming rule engine for the attribute information of the target component is one of the naming rule engines for the attribute information of each component template in various preset application scenarios. Therefore, taking the naming rule engine for the attribute information of the target component as an example, the specific content and functions of the naming rule engine are introduced below. The naming rule engines for the attribute information of each component template in various preset application scenarios can be inferred by analogy and will not be repeated here.

[0048] Taking the naming rule engine for the attribute information of the target component as an example, the naming rule engine includes a semantic naming logic. The semantic naming logic is used to generate multiple optional attribute information for the target component and determine the name of each optional attribute information. The multiple optional attribute information forms an optional attribute information set. Designers can create the target component by selecting appropriate optional attribute information from the optional attribute information set. For example, if the target component is an input box and the application scenario information of the target component is an instant messaging application, through the semantic naming logic, multiple optional attribute information for the target component are generated, which are respectively the optional attribute information for the border size, the optional attribute information for the background color, and the optional attribute information for the border thickness.

[0049] Among them, the optional attribute information for the border size specifically includes 3 optional attribute information, named Border Size 1 - Maximum, Border Size 2 - Medium, and Border Size 3 - Minimum. Designers can generate a border of the corresponding size by selecting appropriate optional attribute information from these three optional attribute information. Among them, the optional attribute information for the background color specifically includes 3 optional attribute information, named Background Color - Bright, Background Color - Neutral, and Background Color - Dull. Designers can generate a background of the corresponding color by selecting appropriate optional attribute information from these three optional attribute information. Among them, the optional attribute information for the border thickness specifically includes 3 optional attribute information, named Border Thickness 1 - Thickest, Border Thickness 2 - Medium, and Border Thickness 3 - Thinnest. Designers can generate a border of the corresponding thickness by selecting appropriate optional attribute information from these three optional attribute information.

[0050] The optional attribute information of the target component can be displayed in the form of options, which is convenient for designers to select. It can be seen that the naming of the optional attribute information generated by the semantic naming logic is semantic. Designers can easily select appropriate attribute information through this naming, thereby improving the component design efficiency.

[0051] In one embodiment, based on the semantic naming logic in the naming rule engine, an optional attribute information set for the target component is generated, specifically as follows:

[0052] (b1) Determine the attribute dimensions of the target component based on the semantic naming logic in the naming rule engine, and generate the dimension names of the attribute dimensions;

[0053] (b2) Determine the measurement values of the target component under the attribute dimensions based on the semantic naming logic in the naming rule engine;

[0054] (b3) Generate an optional attribute information set of the target component according to the dimension names of the attribute dimensions and the measurement values of the target component under the attribute dimensions.

[0055] First, based on the semantic naming logic in the naming rule engine, determine multiple attribute dimensions of the target component, and generate the dimension names of each attribute dimension. It should be noted that the style of the target component consists of multiple attribute dimensions, and the attribute information under each attribute dimension determines the style of the target component under that attribute dimension. For example, the style of the target component consists of border size, background color, and border thickness. The specific value of the border size determines the style of the target component under the border size dimension, the specific value of the background color determines the style of the target component under the background color dimension, and the specific value of the border thickness determines the style of the target component under the border thickness dimension. Based on this, taking the target component as an input box as an example, the attribute dimensions of the target component include but are not limited to border size, background color, and border thickness. Correspondingly, the dimension names of the attribute dimensions can be: border size, background color, and border thickness.

[0056] Then, based on the semantic naming logic in the naming rule engine, determine the measurement values of the target component under each attribute dimension. The measurement value under each attribute dimension is the attribute information under that attribute dimension. Taking the attribute dimension of border size as an example, the measurement values can include border size No. 1, border size No. 2, etc. Among them, there are multiple measurement values under one attribute dimension, and each measurement value represents a variety of different attribute information under that attribute dimension. For example, they respectively represent various border sizes under the border size dimension.

[0057] Finally, generate an optional attribute information set of the target component according to the dimension names of the attribute dimensions and the measurement values of the target component under the attribute dimensions. For a measurement value under an attribute dimension, combine the dimension name of the attribute dimension and the measurement value with or without a separator to obtain an optional attribute information under that attribute dimension. By combining the dimension name of the attribute dimension and each measurement value under that attribute dimension with or without a separator respectively, obtain the respective optional attribute information under that attribute dimension. For each attribute dimension, obtain the respective optional attribute information under each attribute dimension in this way. All the optional attribute information of the target component constitutes the optional attribute information set of the target component.

[0058] For example, for the attribute dimension border size, its measurement values include size 1 and size 2. Then, the dimension name border size of this attribute dimension is combined with each measurement respectively to obtain two optional attribute information under this attribute dimension, border size 1 and border size 2. For the attribute dimension background color, its measurement values include dark color system and light color system. Then, the dimension name background color of this attribute dimension is combined with each measurement value respectively to obtain two optional attribute information under this attribute dimension, background color - dark color system and background color - light color system. Here, border size 1, border size 2, background color - dark color system and background color - light color system together form the set of optional attribute information of the target component.

[0059] It can be seen that in this embodiment, the style of the target component is split into multiple attribute dimensions, and each attribute dimension includes multiple measurement values, which are used to represent various style parameters under this attribute dimension. By combining the dimension name of each attribute dimension and the corresponding measurement values respectively, the optional attribute information under this attribute dimension is obtained. Combining the optional attribute information of the target component under each attribute dimension, the set of optional attribute information is obtained, which has the advantage of high efficiency in generating the set of optional attribute information.

[0060] In one embodiment, based on the semantic naming logic in the naming rule engine, the attribute dimensions of the target component are determined, and the dimension names of the attribute dimensions are generated. Specifically:

[0061] (b11) Based on the semantic naming logic in the naming rule engine, determine the disassembly dimension of the target component under the application scenario information, and disassemble the attributes of the target component according to the disassembly dimension to obtain the attribute dimensions of the target component;

[0062] (b12) Obtain the description information of the attribute dimension, and generate the dimension name of the attribute dimension according to the description information; wherein, the description information of the attribute dimension includes at least one of the identification information of the attribute dimension and the usage information of the attribute dimension.

[0063] First, based on the semantic naming logic in the naming rule engine, determine the disassembly dimensions of the target component under the application scenario information. In the semantic naming logic of the naming rule engine corresponding to the target component, the disassembly dimensions of the target component under the application scenario information are predefined. For example, it is predefined that the input component is disassembled into background color, border size, and border thickness. These predefined disassembly dimensions can be preconfigured into the semantic naming logic of the naming rule engine when configuring the naming rule engine corresponding to each component template. Thus, here, directly use the disassembly dimensions configured in the semantic naming logic as the disassembly dimensions of the target component under the application scenario information. Then, disassemble the attributes of the target component according to the disassembly dimensions to obtain the attribute dimensions of the target component. For example, obtain the attribute dimensions including background color, border size, and border thickness.

[0064] Then, for each attribute dimension, obtain the description information of the attribute dimension and use the description information as the dimension name of the attribute dimension. Among them, the description information of the attribute dimension includes at least one of the identification information of the attribute dimension and the usage information of the attribute dimension. For example, for the attribute dimension of background color, obtain the description information of the attribute dimension. The description information includes the identification information "background color" and the usage information "used to display the background". Then, combine the identification information "background color" and the usage information "used to display the background" to obtain "background color - used to display the background" as the dimension name of the attribute dimension.

[0065] It can be seen that in this embodiment, the disassembly dimensions configured in the semantic naming logic can be used as the disassembly dimensions of the target component under the application scenario information. Disassemble the attributes of the target component according to the disassembly dimensions to obtain the attribute dimensions of the target component. Then, use the identification information and / or usage information of each attribute dimension as the dimension name of the attribute dimension. Therefore, through this embodiment, after determining the naming rule engine, it is possible to quickly and efficiently generate the dimension names of each attribute dimension of the target component, improving the efficiency of generating attribute information.

[0066] In one embodiment, based on the semantic naming logic in the naming rule engine, determine the measurement value of the target component under the attribute dimension, specifically:

[0067] (b21) Based on the semantic naming logic in the naming rule engine, determine the measurement unit of the target component under the attribute dimension;

[0068] (b22) According to the measurement unit of the target component under the attribute dimension, generate the measurement value of the target component under the attribute dimension;

[0069] Among them, the measurement value is the style identifier of the target component under the attribute dimension and corresponds to the style parameter of the target component under the attribute dimension.

[0070] First, according to the semantic naming logic in the naming rule engine, determine the measurement unit of the target component in each attribute dimension. There is a measurement unit for each attribute dimension, and the measurement units for each attribute dimension can be pre-configured in the semantic naming logic. Specifically, when configuring the naming rule engine corresponding to each component template, pre-configure the measurement unit for each attribute dimension in the semantic naming logic of the naming rule engine. Thus, here, directly obtain the measurement unit for each attribute dimension configured in the semantic naming logic. In an example, the measurement unit for the border size can be "number", such as size number 1, size number 2, etc.; the measurement unit for the background color can be "layer", such as dark layer 1, dark layer 2, etc.; the measurement unit for the border thickness can be "number", such as thickness number 1, thickness number 2, etc.

[0071] Next, for each attribute dimension, generate the measurement value of the target component in this attribute dimension according to the measurement unit under this attribute dimension. The number of measurement values for each attribute dimension can be pre-set in the semantic naming logic. Then, generate the measurement values for each attribute dimension according to this number and this measurement unit. Among them, for an attribute dimension, the starting value of its preset number of measurement values and the gradient (i.e., the difference) between every two adjacent measurement values can also be preset in the semantic naming logic.

[0072] For example, it is defined in the semantic naming logic that for the border size, its measurement unit is "number", it has 3 measurement values, the gradient between every two adjacent measurement values is 1, and its starting value is also 1. Then generate three measurement values for the border size: size number 1, size number 2, and size number 3. Thus, it can be seen that by combining each measurement value with the dimension name of the corresponding attribute dimension, multiple optional attribute information in this attribute dimension can be obtained.

[0073] In this embodiment, the measurement value is the style identifier of the target component in the attribute dimension, corresponding to the style parameter of the target component in the attribute dimension. Specifically, for designers, the measurement value can be expressed as number 1, number 2, etc. The measurement value is used to represent the style of the target component in this attribute dimension and is a style identifier. For a computer design system, the measurement value corresponds to specific style parameters. For example, measurement value number 1 corresponds to a certain size or thickness, and measurement value number 2 corresponds to a certain size or thickness.

[0074] Regarding the style parameter values of the target component corresponding to each measurement value in the computer design system in the corresponding attribute dimension, they can be pre-configured in the computer system or pre-configured in the semantic naming logic.

[0075] Therefore, through this embodiment, it is possible to determine the measurement unit of the target component in the attribute dimension based on the semantic naming logic in the naming rule engine. Based on this measurement unit, generate the measurement value of the target component in the attribute dimension, and represent the style of the target component in the attribute dimension through the measurement value, and set the style parameter value of the target component represented by the measurement value in the attribute dimension, so as to achieve the effect of quickly determining the measurement value and using the measurement value to map the specific style parameter value.

[0076] In one embodiment, the number of measurement values is multiple. The gradient between each measurement value meets the gradient requirements corresponding to the measurement unit. Among the various optional attribute information of the target component, each measurement value is sorted according to the preset sorting requirements.

[0077] Specifically, for any one attribute dimension, the corresponding measurement values are multiple, and the specific number of measurement values is pre-configured in the semantic naming logic. As mentioned above, for any one attribute dimension, the gradient between each measurement value, that is, the difference between every two adjacent measurement values, is also predefined in the semantic naming logic, and the difference between every two adjacent measurement values meets the gradient requirements corresponding to the corresponding measurement unit. For example, if the measurement unit is "number", the gradient requirement is that the difference between every two adjacent measurement values is at least 1 number.

[0078] Furthermore, among the various optional attribute information of the target component, for each attribute dimension, there are multiple measurement values, and each measurement value is sorted according to the preset sorting requirements. The preset sorting requirements can be the order of the style parameter values mapped by the measurement values from small to large. For example, for the attribute dimension of border size, its measurement values include 3, namely number 1, number 2, and number 3. Correspondingly, its optional attribute information is three, and in order, they are: border size number 1, border size number 2, border size number 3. Among them, the actual border size corresponding to border size number 1 is the smallest, and the actual border size corresponding to border size number 3 is the largest. Therefore, when displaying each optional attribute information of the target component on the interface, under each attribute dimension, each optional attribute information is displayed according to the sorting of each measurement value.

[0079] After generating the set of optional attribute information of the target component according to the semantic naming logic in the naming rule engine through the above process, obviously, the multiple optional attribute information in the set of optional attribute information conforms to the above-mentioned semantic naming logic. Among them, the set of optional attribute information includes multiple optional attribute information of the target component under each attribute dimension, and there are multiple optional attribute information under one attribute dimension.

[0080] Next, in the above step S108, the optional attribute information set is associated and saved with the component identifier of the target component. Thus, when a designer needs to design the target component, the optional attribute information set can be directly called for design.

[0081] In one embodiment, after generating the optional attribute information set of the target component, the following steps can also be performed:

[0082] (c1) Determine the default optional attribute information in the optional attribute information set of the target component;

[0083] (c2) Set the display format of the default optional attribute information to a preset format to prominently display the default optional attribute information in the optional attribute information set.

[0084] Specifically, the optional attribute information set of the target component includes multiple optional attribute information of the target component under each attribute dimension, where there are multiple optional attribute information under one attribute dimension. Then, in action (c1), under each attribute dimension, determine the default optional attribute information under that attribute dimension, such as determining the default border size, default background color, etc. Among the multiple optional attribute information included in each attribute dimension, one default optional attribute information under that attribute dimension is selected. Therefore, the number of default optional attribute information is the same as the number of attribute dimensions of the target component. The default optional attribute information can be the optional attribute information most frequently used when designing the target component.

[0085] Then, in action (c2), set the display format of each default optional attribute information to the preset format to prominently display the default optional attribute information in the optional attribute information set. Thus, when a designer designs the target component, it is convenient for the designer to preferentially select the default optional attribute information, improving the design efficiency of the designer.

[0086] It can be seen that through this embodiment, the default optional attribute information can be determined, and the display format of the default optional attribute information is set to the preset format to prominently display the default optional attribute information in the optional attribute information set, thereby assisting the designer in designing the target component and improving the design efficiency of the target component.

[0087] Figure 2 The flowchart of the information processing method provided by another embodiment of this specification is as Figure 2 shown. In this process, after associating and saving the optional attribute information set with the component identifier of the target component in step S108, step S110 can also be executed to set the optional attribute information set of the target component as the global attribute information set of the target component under various preset application scenarios.

[0088] Specifically, the set of optional attribute information of the target component is the set of optional attribute information in the application scenario corresponding to the application scenario information of the target component in step S102. For example, in the instant messaging application scenario, the target component is an input box component, which may include multiple pieces of first optional attribute information. However, in other scenarios, the target component is also an input component, which includes multiple pieces of second optional attribute information. Due to different application scenarios, the attribute dimensions and measurement values may be different, and the first optional attribute information and the second optional attribute information may also be different. Therefore, the set of optional attribute information of the target component in step S108 is the set of optional attribute information in the application scenario corresponding to the application scenario information of the target component in step S102.

[0089] To improve the applicable scenarios of the set of optional attribute information of the target component, in this embodiment, the set of optional attribute information of the target component in step S108 is set as the global attribute information set of the target component in various preset application scenarios, so that the set of optional attribute information of the target component in step S108 can be applicable to various scenarios, eliminating the process of repeatedly determining the optional attribute information for the same target component in other application scenarios, and improving the efficiency of designers designing the target component in other scenarios.

[0090] Figure 3 It is a schematic flowchart of a method for information processing provided by another embodiment of this specification. As Figure 3 shown, in this process, after associating and saving the set of optional attribute information with the component identifier of the target component in step S108, the following operations can also be performed:

[0091] Step S112, in response to a user's startup operation on the visual component creation interface, display the visual component creation interface;

[0092] Step S114, in the visual component creation interface, display the set of optional attribute information of the target component;

[0093] Step S116, in response to a user's selection operation on the optional attribute information in the set of optional attribute information of the target component, create the target component.

[0094] Specifically, the design system provides a visual component creation interface. If a user, such as a designer, starts this interface, then the design system, in response to the user's startup operation on the visual component creation interface, displays the visual component creation interface. The visual component creation interface is used for designers to design and create various components.

[0095] Next, in the visual component creation interface, a set of optional attribute information of the target component is displayed. Among them, each piece of optional attribute information in the set of optional attribute information is displayed in the visual component creation interface in the form of an optional option. For example, in the visual component creation interface, each piece of optional attribute information of the input box component is displayed in the form of an optional option, including at least multiple pieces of optional attribute information about the border size and multiple pieces of optional attribute information about the border thickness.

[0096] Finally, according to the user's selection operation on the optional attribute information in the set of optional attribute information of the target component, the target component is created based on the selected optional attribute information by the user. For example, an input box component is created according to the border size and border thickness selected by the user.

[0097] It can be seen that through this embodiment, it is also possible to display a set of optional attribute information of the target component in the visual component creation interface, and create the target component according to the user's selection operation on the optional attribute information in the set of optional attribute information of the target component, thereby improving the efficiency of the user, such as a designer, in creating the target component.

[0098] Furthermore, in this embodiment, for any piece of optional attribute information of the target component, the name of the optional attribute information contains the user interaction state parameter corresponding to the optional attribute information. For example, for the background color information of the selection component, its name can be "background-color-visited-3", where "visited" is the user interaction state parameter of the selection component. Correspondingly, the background color information of the selection component is used to represent that the background color is color No. 3 in the user access state. Similarly, for the same selection component, there are multiple user interaction state parameters, such as "focus", "active", etc. Under different user interaction state parameters, its background color information can be the same or different, such as "background-color-focus-4", "background-color-active-2".

[0099] In a specific embodiment, the user interaction state parameters are pre-configured in the semantic naming logic. When generating the optional attribute information, the user interaction state parameters can be directly obtained from the semantic naming logic. The semantic naming logic is also configured with the association relationship between the user interaction state parameters, the dimension name of the attribute dimension, and the dimension value of the attribute dimension. Based on this association relationship, the user interaction state parameters, the dimension name of the attribute dimension, and the measurement value of the attribute dimension are combined to obtain the optional attribute information.

[0100] It can be seen that in this embodiment, the naming of the optional attribute information of the target component includes the user interaction status parameter corresponding to the optional attribute information. Through this user interaction status parameter, designers can conveniently design the display styles of components in different interaction states, improving the design efficiency.

[0101] In summary, through this embodiment, it is possible to generate the optional attribute information of the target component based on the application scenario of the target component through the semantic naming logic, so that the naming of the optional attribute information is semantic, facilitating designers to select appropriate attribute information from the optional attribute information of the target component according to the naming of the optional attribute information when designing the target component, avoiding designers spending a lot of time selecting appropriate attribute information, and improving the component design efficiency.

[0102] Figure 4 FIG. is a schematic structural diagram of an information processing device provided in an embodiment of this specification. As Figure 4 shown, the device includes:

[0103] An information acquisition unit 41 that acquires the application scenario information of the target component whose attribute information is to be configured;

[0104] An engine determination unit 42 that determines, according to the application scenario information, a naming rule engine for the attribute information of the target component; the semantic naming logic in the naming rule engine matches the application scenario information;

[0105] A set generation unit 43 that generates a set of optional attribute information of the target component based on the semantic naming logic in the naming rule engine; the set of optional attribute information includes multiple optional attribute information of the target component; the multiple optional attribute information conforms to the semantic naming logic;

[0106] An association storage unit 44 that stores the set of optional attribute information in association with the component identifier of the target component.

[0107] Optionally, the engine determination unit 42,

[0108] selects a target scenario that matches the application scenario information from a preset variety of application scenarios;

[0109] selects a target component template that matches the target component from a variety of component templates pre-configured for the target scenario;

[0110] determines the naming rule engine created for the attribute information of the target component template as the naming rule engine for the attribute information of the target component.

[0111] Optionally, the engine determination unit 42,

[0112] Determine the application scenario name corresponding to the application scenario information;

[0113] Among multiple preset application scenarios, select the application scenario whose semantic similarity with the application scenario name meets the preset requirements as the target scenario matching the application scenario information.

[0114] Optionally, the engine determination unit 42,

[0115] If among multiple component templates pre-configured for the target scenario, there is a component template with the same component name as the target component, then use this component template as the target component template matching the target component;

[0116] If among multiple component templates pre-configured for the target scenario, there is no component template with the same component name as the target component, then obtain the usage information of the target component, and among the multiple component templates, select the component template whose usage information matches the usage information of the target component as the target component template matching the target component.

[0117] Optionally, the set generation unit 43,

[0118] Based on the semantic naming logic in the naming rule engine, determine the attribute dimension of the target component and generate the dimension name of the attribute dimension;

[0119] Based on the semantic naming logic in the naming rule engine, determine the measurement value of the target component under the attribute dimension;

[0120] According to the dimension name of the attribute dimension and the measurement value of the target component under the attribute dimension, generate the set of optional attribute information of the target component.

[0121] Optionally, the set generation unit 43,

[0122] Based on the semantic naming logic in the naming rule engine, determine the disassembly dimension of the target component under the application scenario information, disassemble the attributes of the target component according to the disassembly dimension to obtain the attribute dimension of the target component;

[0123] Obtain the description information of the attribute dimension, and generate the dimension name of the attribute dimension according to the description information; wherein, the description information of the attribute dimension includes at least one of the identification information of the attribute dimension and the usage information of the attribute dimension.

[0124] Optionally, the set generation unit 43,

[0125] Determine the measurement unit of the target component in the attribute dimension based on the semantic naming logic in the naming rule engine;

[0126] Generate the measurement value of the target component in the attribute dimension according to the measurement unit of the target component in the attribute dimension;

[0127] Wherein, the measurement value is the style identifier of the target component in the attribute dimension, corresponding to the style parameter of the target component in the attribute dimension.

[0128] Optionally, the number of the measurement values is multiple; the gradient between each of the measurement values meets the gradient requirement corresponding to the measurement unit;

[0129] In each of the optional attribute information of the target component, each of the measurement values is sorted according to a preset sorting requirement.

[0130] Optionally, the device further includes: a format setting unit, which

[0131] After generating the set of optional attribute information of the target component, determine the default optional attribute information in the set of optional attribute information of the target component;

[0132] Set the display format of the default optional attribute information to a preset format to highlight the default optional attribute information in the set of optional attribute information.

[0133] Optionally, the device further includes: a range setting unit, which

[0134] After associatively saving the set of optional attribute information with the component identifier of the target component, set the set of optional attribute information of the target component as the global attribute information set of the target component in various preset application scenarios.

[0135] Optionally, the device further includes: a component creation unit, which

[0136] After associatively saving the set of optional attribute information with the component identifier of the target component, in response to a user's start operation on the visual component creation interface, display the visual component creation interface;

[0137] In the visual component creation interface, display the set of optional attribute information of the target component;

[0138] In response to a user's selection operation on the optional attribute information in the set of optional attribute information of the target component, create the target component.

[0139] The information processing device in this embodiment can implement each process of the above-mentioned information processing method embodiment, and achieve the same effects and functions, which will not be repeated here.

[0140] One or more embodiments of this specification also provide an information processing device, which is used to execute the above-mentioned information processing method. Figure 5 As shown in the structure schematic diagram of an information processing device provided by one or more embodiments of this specification. Figure 5 As shown, the information processing device may vary greatly due to different configurations or performances, and may include one or more processors 1001 and a memory 1002. One or more applications or data may be stored in the memory 1002. Among them, the memory 1002 may be short-term storage or persistent storage. The applications stored in the memory 1002 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the information processing device. Further, the processor 1001 may be set to communicate with the memory 1002 and execute a series of computer-executable instructions in the memory 1002 on the information processing device. The information processing device may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input / output interfaces 1005, one or more keyboards 1006, etc.

[0141] In a specific embodiment, the information processing device includes: a processor; and a memory arranged to store computer-executable instructions, and when the computer-executable instructions are executed by the processor, the processor implements the following processes:

[0142] Obtain the application scenario information of the target component of the to-be-configured attribute information;

[0143] According to the application scenario information, determine the naming rule engine for the attribute information of the target component; the semantic naming logic in the naming rule engine matches the application scenario information;

[0144] Based on the semantic naming logic in the naming rule engine, generate a set of optional attribute information for the target component; the set of optional attribute information includes multiple optional attribute information of the target component; the multiple optional attribute information conforms to the semantic naming logic;

[0145] Associate and save the set of optional attribute information with the component identifier of the target component.

[0146] The information processing device in this embodiment can implement each process of the above-mentioned information processing method embodiment, and achieve the same effects and functions, which will not be repeated here.

[0147] Furthermore, one or more embodiments of this specification also provide a storage medium for storing computer-executable instructions. In a specific embodiment, the storage medium can be a USB flash drive, an optical disc, a hard disk, etc. When the computer-executable instructions stored in the storage medium are executed by a processor, the following processes can be implemented:

[0148] Obtain the application scenario information of the target component for which the attribute information to be configured is to be obtained;

[0149] According to the application scenario information, determine a naming rule engine for the attribute information of the target component; the semantic naming logic in the naming rule engine matches the application scenario information;

[0150] Based on the semantic naming logic in the naming rule engine, generate a set of optional attribute information for the target component; the set of optional attribute information includes multiple pieces of optional attribute information of the target component; the multiple pieces of optional attribute information conform to the semantic naming logic;

[0151] Associate and save the set of optional attribute information with the component identifier of the target component.

[0152] The storage medium in this embodiment can implement each process of the method embodiment of the above information processing, and achieve the same effects and functions, which will not be repeated here.

[0153] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be executed in a different order than in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0154] In the 1990s, it was obvious to distinguish whether an improvement in a technology was an improvement in hardware (e.g., improvement in circuit structures such as diodes, transistors, switches, etc.) or an improvement in software (improvement in method flows). However, with the development of technology, many improvements in method flows today can be regarded as direct improvements in hardware circuit structures. Almost all designers obtain the corresponding hardware circuit structures by programming the improved method flows into the hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented with a hardware entity module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. The designer can program by himself / herself to "integrate" a digital system on a piece of PLD without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called Hardware Description Language (HDL). And there is not only one type of HDL, but many types, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones currently are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that by simply performing a little logical programming on the method flow with the above-mentioned several hardware description languages and programming it into the integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0155] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to implement the same function by logically programming the method steps so that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or structures within the hardware component.

[0156] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0157] For the convenience of description, when describing the above devices, they are described separately as various units according to their functions. Of course, when implementing one or more of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0158] Those skilled in the art should understand that the embodiments of one or more of this specification can be provided as a method, a system, or a computer program product. Therefore, one or more of this specification can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, one or more of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program code.

[0159] One or more aspects of this specification are described with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to one or more embodiments of the specification. It should be understood that each flow and / or block in the flowchart and / or block diagram, and combinations of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce means for implementing the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more blocks.

[0160] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable memory produce a manufacture including instruction means that implement the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more blocks.

[0161] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in one or more blocks.

[0162] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0163] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory, such as read-only memory (ROM) or flash memory. Memory is an example of computer-readable media.

[0164] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0165] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0166] It should be understood by those skilled in the art that one or more embodiments of this specification may be provided as methods, systems or computer program products. Therefore, one or more of this specification may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, one or more of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0167] One or more of the present descriptions may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more of the present descriptions may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0168] The various embodiments in this specification are described in a progressive manner. For the same or similar parts among the various embodiments, reference can be made to each other, and each embodiment focuses on the differences from other embodiments. In particular, for system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and reference can be made to the relevant parts of the method embodiments for the related content.

[0169] The above description is only for one or more embodiments of this specification and is not intended to limit one or more of this specification. For those skilled in the art, various changes and modifications can be made to one or more of this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more of this specification shall be included within the scope of the claims of one or more of this specification.

Claims

1. A method for information processing, comprising: Obtain the application scenario information of the target component for the property information to be configured; Determine the naming rule engine for the property information of the target component according to the application scenario information; The semantic naming logic in the naming rule engine matches the application scenario information; Generate a set of optional property information for the target component based on the semantic naming logic in the naming rule engine; the set of optional property information includes multiple optional property information of the target component; the multiple optional property information conforms to the semantic naming logic; Associate and save the set of optional property information with the component identifier of the target component.

2. The method according to claim 1, wherein, Determine the naming rule engine for the property information of the target component according to the application scenario information, including: Select a target scenario that matches the application scenario information from a variety of preset application scenarios; Select a target component template that matches the target component from a variety of component templates pre-configured for the target scenario; Determine the naming rule engine created for the property information of the target component template as the naming rule engine for the property information of the target component.

3. The method according to claim 2, wherein, Select a target scenario that matches the application scenario information from a variety of preset application scenarios, including: Determine the application scenario name corresponding to the application scenario information; Select, from a variety of preset application scenarios, an application scenario whose semantic similarity between the scenario name and the application scenario name meets the preset requirements as the target scenario that matches the application scenario information.

4. The method according to claim 2, wherein, Select a target component template that matches the target component from a variety of component templates pre-configured for the target scenario, including: If there is a component template whose component template name is the same as the component name of the target component among the variety of component templates pre-configured for the target scenario, then use the component template as the target component template that matches the target component; If there is no component template whose component template name is the same as the component name of the target component among the variety of component templates pre-configured for the target scenario, then obtain the usage information of the target component, and select, from the variety of component templates, a component template whose usage information matches the usage information of the target component as the target component template that matches the target component.

5. The method according to claim 1, wherein, Generate a set of optional property information for the target component based on the semantic naming logic in the naming rule engine, including: Determine the property dimension of the target component based on the semantic naming logic in the naming rule engine, and generate the dimension name of the property dimension; Determine the measurement value of the target component under the property dimension based on the semantic naming logic in the naming rule engine; Generate a set of optional property information for the target component according to the dimension name of the property dimension and the measurement value of the target component under the property dimension.

6. The method according to claim 5, wherein, Determine the property dimension of the target component based on the semantic naming logic in the naming rule engine, and generate the dimension name of the property dimension, including: Based on the semantic naming logic in the naming rule engine, determine the disassembly dimension of the target component under the application scenario information, and disassemble the attributes of the target component according to the disassembly dimension to obtain the attribute dimension of the target component; Obtain the description information of the attribute dimension, and generate the dimension name of the attribute dimension according to the description information; wherein, the description information of the attribute dimension includes at least one of the identification information of the attribute dimension and the usage information of the attribute dimension.

7. The method according to claim 5, wherein, Based on the semantic naming logic in the naming rule engine, determine the measurement value of the target component under the attribute dimension, including: Based on the semantic naming logic in the naming rule engine, determine the measurement unit of the target component under the attribute dimension; Generate the measurement value of the target component under the attribute dimension according to the measurement unit of the target component under the attribute dimension; Wherein, the measurement value is the style identifier of the target component under the attribute dimension, corresponding to the style parameter of the target component under the attribute dimension.

8. The method according to claim 7, wherein, The number of the measurement values is multiple; the gradient between the measurement values meets the gradient requirements corresponding to the measurement unit; Among the optional attribute information of the target component, the measurement values are sorted according to the preset sorting requirements.

9. The method according to claim 1, wherein, After generating the set of optional attribute information of the target component, the method further includes: Determine the default optional attribute information in the set of optional attribute information of the target component; Set the display format of the default optional attribute information to a preset format to highlight the default optional attribute information in the set of optional attribute information.

10. The method according to claim 1, wherein,After associatively saving the set of optional attribute information with the component identifier of the target component, the method further includes: Set the set of optional attribute information of the target component as the global attribute information set of the target component under various preset application scenarios.

11. According to the method of claim 1, wherein, After associatively saving the set of optional attribute information with the component identifier of the target component, the method further includes: In response to a user's startup operation on the visual component creation interface, display the visual component creation interface; In the visual component creation interface, display the set of optional attribute information of the target component; In response to a user's selection operation on the optional attribute information in the set of optional attribute information of the target component, create the target component.

12. An information processing apparatus, comprising: An information acquisition unit that acquires the application scenario information of the target component whose attribute information is to be configured; An engine determination unit that determines the naming rule engine for the attribute information of the target component according to the application scenario information; The semantic naming logic in the naming rule engine matches the application scenario information; A set generation unit that generates a set of optional attribute information of the target component based on the semantic naming logic in the naming rule engine; the set of optional attribute information includes multiple optional attribute information of the target component; the multiple optional attribute information conforms to the semantic naming logic; An association saving unit that associatively saves the set of optional attribute information with the component identifier of the target component.

13. An information processing device, comprising: A processor; and a memory arranged to store computer-executable instructions which, when executed by the processor, cause the processor to implement the steps of the method according to any one of claims 1-11 above.

14. A storage medium for storing computer-executable instructions, which when executed by a processor cause the processor to implement the steps of the method according to any one of claims 1-11 above.

Images