Method and device for generating UI component

The method and device for generating UI components address inefficiencies by identifying state information and determining sub-components to efficiently create different versions, enhancing the development process through sub-component reuse and reduced redundant work.

WO2024228409A1PCT designated stage expired Publication Date: 2024-11-07COUPANG CORP
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2023/006107
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-02
Filing Date
2023-05-04
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Existing methods for generating UI components lack efficiency in creating different versions of UI components, as they often require redundant work and do not effectively utilize reusable sub-components, leading to inefficiencies in modifying and updating UI components.

Method used

A method and device for generating UI components that identify state information from source code, determine sub-components based on this information, and create target components based on a hierarchical structure, allowing for the reuse of sub-components to efficiently generate different versions of UI components by modifying only specific sub-components.

Benefits of technology

This approach enables efficient creation of different UI component versions by reusing sub-components, minimizing redundant work and allowing for immediate use of updated sub-components without additional effort, thus improving the development process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2023006107_07112024_PF_FP_ABST
    Figure KR2023006107_07112024_PF_FP_ABST
Patent Text Reader

Abstract

A method for generating a UI component in an electronic device is disclosed. Specifically, the method for generating a UI component may comprise the steps of: identifying a target component; identifying at least one slot of the target component; identifying state information related to the at least one slot from a source code related to the target component; determining at least one subcomponent corresponding to the at least one slot according to the state information; and generating the target component including the at least one subcomponent on the basis of a hierarchical structure of the target component.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for creating UI components

[0001] Embodiments of the present specification relate to a method and device for generating a UI component. Embodiments of the present specification relate to a method and device for generating a target component including at least one subcomponent based on a hierarchical structure of the target component.

[0002] A UI component can be a unit that constitutes a web page or mobile page. For example, a UI component corresponding to a widget included on a mobile page may be structured hierarchically, containing lower-level components.

[0003] Embodiments disclosed herein provide a method for generating a UI component and a device for doing so.

[0004] The technical tasks to be achieved by this embodiment are not limited to the technical tasks described above, and other technical tasks can be inferred from the following embodiments.

[0005] As a technical means for achieving the above-described task, a method for generating a UI component in an electronic device according to a first aspect of the present disclosure may include: a step of identifying a target component; a step of identifying at least one slot of the target component; a step of identifying state information related to at least one slot from source code related to the target component; a step of determining at least one subcomponent corresponding to at least one slot according to the state information; and a step of generating a target component including at least one subcomponent based on a hierarchical structure of the target component.

[0006] According to one embodiment, the step of identifying state information may include a step of determining a first type of state information among the state information as default state information of the first type using a first level API; and a step of identifying a second type of state information among the state information from source code using the first level API.

[0007] According to one embodiment, the source code may include a first field indicating that the first type of state information is set to default state information of the first type, and a second field indicating state information of the second type.

[0008] In one embodiment, the step of identifying state information may include the step of identifying a first type of state information and a second type of state information from source code using a second level API.

[0009] In one embodiment, a second level API may be an API utilized when the source code includes a third field indicating that at least some of the first type of state information is set to a first type of state information that is different from the first type of default state information.

[0010] According to one embodiment, a target component of a default version may include at least one default subcomponent corresponding to default state information associated with at least one slot.

[0011] According to one embodiment, when state information of a first slot among at least one slot is different from default state information of the first slot in a target component of a default version, and state information of a second slot among at least one slot is default state information of the second slot in the target component of the default version, the source code may include a first subfield indicating that the state information of the first slot is set to state information different from the default state information of the first slot, and a second subfield indicating that the state information of the second slot is set to the default state information of the second slot.

[0012] According to one embodiment, the step of identifying state information may further comprise the step of identifying state information associated with at least one slot via the interface.

[0013] According to one embodiment, the interface may include a first area for setting state information of a target component, and a second area for setting state information of each of at least one subcomponent.

[0014] According to one embodiment, the step of determining at least one subcomponent may include the step of identifying at least one subcomponent-specific data based on state information, and the step of generating the target component may include the step of generating the target component by rendering at least one subcomponent-specific data to satisfy a hierarchy based on the state information.

[0015] According to one embodiment, the source code may be either source code in xml format or source code in json format.

[0016] An electronic device for generating a UI component according to a second aspect of the present disclosure includes a transceiver; a storage for storing one or more commands; and one or more processors; and a storage for storing one or more commands to be executed by the one or more processors, wherein the one or more processors can, by executing the one or more commands, identify a target component, identify at least one slot of the target component, identify state information related to the at least one slot from source code related to the target component, determine at least one subcomponent corresponding to the at least one slot based on the state information, and generate a target component including the at least one subcomponent based on a hierarchical structure of the target component.

[0017] The recording medium according to the third aspect of the present disclosure may be a non-transitory computer-readable recording medium having recorded thereon a program for executing a method for generating a UI component on a computer.

[0018] According to an embodiment of the present disclosure, an electronic device can identify state information related to at least one slot of a target component from source code related to the target component. The electronic device can determine at least one subcomponent corresponding to at least one slot using the state information, and generate a target component including at least the subcomponent based on a hierarchical structure of the target component. Accordingly, when generating a target component of a different version from a default version of the target component and a specific subcomponent, even if only a field related to the specific subcomponent of the source code related to the target component is modified, the electronic device can efficiently generate a different version of the target component by reusing subcomponents other than the specific subcomponent.

[0019] The effects of the invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

[0020] Figure 1 is a flowchart illustrating how an electronic device creates a UI component.

[0021] Figure 2 is a drawing for explaining a target component according to one embodiment.

[0022] Following FIG. 2, FIG. 3 is a diagram for explaining a method for generating a target component including at least one subcomponent satisfying the hierarchical structure of the target component based on state information related to a slot according to one embodiment.

[0023] FIG. 4 is a diagram illustrating a method for identifying state information associated with at least one slot from source code according to one embodiment.

[0024] FIG. 5 is a diagram illustrating a method for identifying state information associated with at least one slot from source code according to one embodiment.

[0025] FIG. 6 may be a drawing for explaining a new version of a target component according to an embodiment of FIGS. 4 and 5.

[0026] FIG. 7 is a diagram illustrating a method for identifying state information associated with at least one slot from source code according to one embodiment.

[0027] Following FIG. 7, FIG. 8 may be a drawing for explaining a target component of a version according to one embodiment.

[0028] FIG. 9 is a diagram illustrating a method for identifying status information associated with at least one slot through an interface.

[0029] Following FIG. 9, FIG. 10 may be a drawing for explaining a target component according to one embodiment.

[0030] FIG. 11 is a block diagram schematically illustrating an electronic device for generating a UI component according to one embodiment.

[0031] The terms used in the embodiments have been selected from widely used and common terms, taking into account the functions of the present disclosure. However, these terms may vary depending on the intentions of those skilled in the art, precedents, the emergence of new technologies, etc. Furthermore, in certain cases, terms may be arbitrarily selected by the applicant, in which case their meanings will be described in detail in the relevant description. Therefore, the terms used in this disclosure should not be defined simply as names of terms, but rather based on the meanings of the terms and the overall content of the present disclosure.

[0032] When a part of the specification is said to "include" a component, this does not exclude other components, but rather implies the inclusion of other components, unless otherwise specifically stated. Furthermore, terms such as "part" and "module" used in the specification mean a unit that processes at least one function or operation, which may be implemented in hardware, software, or a combination of hardware and software.

[0033] The expression “at least one of a, b, and c” described throughout the specification may encompass ‘a alone’, ‘b alone’, ‘c alone’, ‘a and b’, ‘a and c’, ‘b and c’, or ‘all of a, b, and c’.

[0034] The "terminal" mentioned below may be implemented as a computer or portable terminal that can connect to a server or other terminal via a network. Here, the computer includes, for example, a notebook, desktop, laptop, etc. equipped with a web browser, and the portable terminal may include, for example, a wireless communication device that guarantees portability and mobility, and may include all types of handheld-based wireless communication devices such as communication-based terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), smartphones, tablet PCs, etc.

[0035] Below, embodiments of the present disclosure are described in detail with reference to the attached drawings so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

[0036] In describing the embodiments, descriptions of technical details that are well-known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to avoid obscuring the gist of the present invention by omitting unnecessary explanations and to convey it more clearly.

[0037] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0038] The advantages and features of the present invention, and the methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present invention is complete and to fully inform those skilled in the art of the scope of the invention, and the present invention is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0039] At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0040] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0041] Hereinafter, embodiments of the present invention will be described in detail with reference to the attached drawings.

[0042] Figure 1 is a flowchart illustrating how an electronic device creates a UI component.

[0043] Referring to FIG. 1, it can be clearly understood that some of the operations for generating UI components by an electronic device may be changed, substituted, or some of the order between operations may be changed within a scope clearly understood by a person having ordinary skill in the art to which the present invention pertains.

[0044] In step S110, the electronic device can identify the target component.

[0045] In this disclosure, a component may be a unit that constitutes a web page or mobile page. Components may be classified into atomic components and composite components. A component that is determined to have no lower-level components based on the component hierarchy may be classified as an atomic component. An atomic component may be the smallest unit that constitutes a web page or mobile page. Furthermore, a component that is determined to include lower-level components based on the component hierarchy may be identified as a composite component. In other words, a composite component may be a component hierarchically structured with each lower-level component as a single element. In this disclosure, lower-level components may be referred to as subcomponents.

[0046] In one embodiment, the electronic device can identify a target component that is the target of component creation. Here, the target component may be a composite component, hierarchically structured with each lower-level component as an element.

[0047] In step S120, the electronic device can identify at least one slot of the target component.

[0048] In this disclosure, a slot may be a placeholder for a subcomponent that constitutes a composite component. Whether a composite component has a slot may vary depending on whether user modification is supported when creating a UI component, and may be preset in the electronic device. A composite component that supports user modification may include a slot that is a placeholder for a subcomponent. A default subcomponent corresponding to an existing UI component may be positioned in each slot of the composite component. A composite component that includes a default subcomponent may be a default version of the composite component. However, only a default subcomponent may be positioned in a slot, and the components that can be positioned in a slot are not limited to the default subcomponent. For example, a subcomponent different from the default subcomponent may be positioned in a slot. Furthermore, a subcomponent may not be positioned in a slot. In this case, the corresponding slot of the composite component may be a void area.

[0049] According to one embodiment, the electronic device can identify at least one sub-slot, which is a placeholder of a target component, which is a composite component. More specifically, the electronic device can identify at least one sub-slot, which is a placeholder of the target component, based on the hierarchical structure of the target component. Here, each of the at least one slot may be an atomic component, but is not limited thereto. At least some of the at least one slot may be a composite component. That is, the sub-component of the target component may be a lower-level sub-component in a relationship with the target component, but may also be a composite component.

[0050] In step S130, the electronic device can identify state information associated with at least one slot from source code associated with the target component.

[0051] In the present invention, state information may be information for setting the features of a subcomponent located in a slot. More specifically, the features of the subcomponent may be detailed characteristics of a UI component displayed on a terminal in terms of the UI, and the state information may be parameter values ​​corresponding to features used to render the UI component. For example, the state information may include at least one of state information regarding the size of the component, state information regarding the color of the background and text of the component, state information regarding the alignment of text of the component, state information regarding the spacing between texts of the component, and state information regarding the corner radius of the component.

[0052] According to one embodiment, the state information related to at least one slot identified by the electronic device may be divided into a second type of state information that sets a feature from an overall perspective of a target component composed of at least one slot, and a first type of state information that sets a feature for at least one slot. The electronic device may identify the second type of state information that sets a feature of the target component itself from source code related to the target component, and the first type of state information that sets a feature for at least one slot constituting the target component. Here, the source code may be a source code in XML format or a source code in JSON format. According to another embodiment, the electronic device may identify the state information related to at least one slot based on a setting related to the target component identified through an interface. Here, the interface may be an interface for setting the state information related to at least one slot, and may be Figma. A specific method of identifying the state information related to at least one slot from the interface or the source code will be described in detail below.

[0053] In step S140, the electronic device can determine at least one subcomponent corresponding to at least one slot based on the status information.

[0054] According to one embodiment, the electronic device can identify at least one slot-specific subcomponent corresponding to a second type of state information that sets a feature of the target component itself and a first type of state information that sets at least one slot-specific feature that constitutes the target component.

[0055] When the identified state information is the default state information corresponding to the slot, the subcomponent located in the slot can be determined as the default component. However, only the default subcomponent can be located in the slot, and the components that can be located in the slot are not limited to the default subcomponent. In other words, when creating a new version of the target component according to a business decision, a subcomponent of a type other than the default subcomponent can be located in the slot. In this case, the electronic device can identify the state information of the slot as state information corresponding to a subcomponent of a type other than the default state information. The electronic device can determine the subcomponent corresponding to the slot as a subcomponent of a type other than the default subcomponent.

[0056] In step S150, the electronic device can generate a target component including at least one subcomponent based on the hierarchical structure of the target component.

[0057] According to one embodiment, an electronic device may generate a target component by combining or aggregating at least one subcomponent so as to satisfy the hierarchical structure of the target component. A default version of the target component may include a default subcomponent corresponding to default state information associated with at least one slot constituting the target component. In this regard, when a default subcomponent corresponding to each slot of the target component is positioned, the electronic device may identify a default version of the target component including the default subcomponent. The target component identified by the electronic device may be, but is not limited to, a target component of the default version. When generating a new version of the target component based on a business decision, a subcomponent of a different type than the default subcomponent may be positioned in the slot. In this case, the electronic device may identify a new version of the target component in which a subcomponent of a different type than the target component of the default version is positioned in the corresponding slot.

[0058] Figure 2 is a drawing for explaining a target component according to one embodiment.

[0059] The target component may correspond to one of the widgets that constitute a web page or mobile page. Referring to FIG. 2, the target component (200) may be a component related to a message box that conveys information or poses a question to a user using a computing device through a pop-up page. Furthermore, the target component (200) may be a default version of the target component. However, the target component is not limited to a message box-related component, and the target component may be a component of a UI element such as a text button or a container button.

[0060] The target component (200) is a component with a green background and can be divided into at least one sub-slot. Referring to FIG. 2, the target component (200) is a composite component and can include a first slot (210), a second slot (220), a third slot (230), and a fourth slot (240).

[0061] The first slot (210) may be a start slot including an image or an icon. More specifically, the default subcomponent corresponding to the first slot (210) may be an icon having the letter C engraved in a deep green circle. More specifically, the color of the letter C in the icon may be the same as the green background color of the target component (200). When the electronic device determines the default subcomponent corresponding to the first slot (210) from the source code, the default state information corresponding to the first slot (210) may be identified as state information for setting an icon having the letter C engraved in a deep green circle. However, the subcomponent corresponding to the first slot (210) of FIG. 2 is not limited to the default subcomponent, and the subcomponent corresponding to the first slot (210) may be a subcomponent of a different type than the default subcomponent. For example, the subcomponent corresponding to the first slot (210) may be a text-related subcomponent.

[0062] The second slot (220) may be a content slot including text. More specifically, the default subcomponent corresponding to the second slot (220) may include the text, "Message box v3 does not yet support development code. Please use V2 to use RDS code." When the electronic device determines the default subcomponent corresponding to the second slot (220) from the source code, the default status information corresponding to the second slot (220) may be identified as status information for setting the text, "Message box v3 does not yet support development code. Please use V2 to use RDS code." However, the subcomponent corresponding to the second slot (220) of FIG. 2 is not limited to the default subcomponent, and the subcomponent corresponding to the second slot (220) may be a subcomponent of a different type than the default subcomponent. For example, the subcomponent corresponding to the second slot (220) may be an image or icon-related subcomponent.

[0063] The third slot (230) may be a bottom slot containing text. More specifically, the default subcomponent corresponding to the third slot (230) may include the text "Button" and an icon related to the text. More specifically, the color of the text and the icon related to the text may be blue. When the electronic device determines the default subcomponent corresponding to the third slot (230) from the source code, the default state information corresponding to the third slot (230) may be identified as state information for setting the text "Button" and the icon related to the text. However, the subcomponent corresponding to the third slot (230) of FIG. 2 is not limited to the default subcomponent, and the subcomponent corresponding to the third slot (230) may be a subcomponent of a different type than the default subcomponent. For example, the subcomponent corresponding to the third slot (230) may be an image-related icon. Alternatively, the state information corresponding to the third slot (230) may not be set separately. At this time, the third slot (230) may be a void area.

[0064] The fourth slot (240) may be an end slot including a button. More specifically, the default subcomponent corresponding to the fourth slot (240) may include an arrow-shaped button icon in relation to the button. When the electronic device determines the default subcomponent corresponding to the fourth slot (240) from the source code, the default state information corresponding to the fourth slot (240) may be identified as state information for setting the arrow-shaped button icon. However, the subcomponent corresponding to the fourth slot (240) is not limited to the default subcomponent, and the subcomponent corresponding to the fourth slot (240) may be a subcomponent of a different type than the default subcomponent. For example, the subcomponent corresponding to the fourth slot (240) may be a text-related icon.

[0065] Following FIG. 2, FIG. 3 is a diagram for explaining a method for generating a target component including at least one subcomponent satisfying the hierarchical structure of the target component based on state information related to a slot according to one embodiment.

[0066] According to one embodiment, the electronic device can identify state information related to at least one slot constituting the target component from an interface related to setting source code or state information related to the target component. A state information tree (300) related to the target component can hierarchically represent state information related to the target component. The state information related to the target component displayed in the state information tree (300) can include a second type of state information (310) that sets features from an overall perspective of the target component and a first type of state information that sets features for at least one slot.

[0067] The second type of state information (310) is information for setting the features of the target component itself, and may include background color information of the target component and size information of the target component. Referring to Fig. 2, the background color information of the target component may be green, and the size information of the target component may be M.

[0068] The first type of status information is status information that sets at least one slot-specific feature, and may include status information (311) of the first slot (210), status information (312) of the second slot (220), status information (313) of the third slot (230), and status information (314) of the fourth slot (240).

[0069] The status information (311) of the first slot (210) is information for setting an icon having the alphabet C engraved on a circle of deep green color, and may include information on data related to the icon, size information of the circle as an icon, color information of the alphabet C, and font size information. The status information (312) of the second slot (220) is information for setting a text saying, 'Message box v3 does not yet support development code. Please use V2 to use RDS code.', and may include information on text data, font size information of the text, and font color information of the text. The status information (313) of the third slot (230) is information for setting a text called 'button' and an arrow-shaped icon related to the text, and may include data information related to the text, font size information of the text, and font color information of the text. In addition, the status information (313) of the third slot (230) may include data information related to the arrow-shaped icon, and color information of the icon. The status information (314) of the 4th slot (240) is information for setting an arrow-shaped button icon, and may include data information related to the icon, size information of the icon, and color information of the icon.

[0070] According to one embodiment, the electronic device can identify data corresponding to at least one slot according to the second type of state information (310) and the first type of state information, and can generate a first version of the target component by rendering data for at least one subcomponent so as to satisfy a hierarchy based on the state information related to the target component. More specifically, the electronic device can generate the target component by rendering data for at least one subcomponent through rendering logic.

[0071] Referring to the hierarchy (320) of the target component, an image-related subcomponent (321) corresponding to state information (311) may be located in the first slot (210) of the target component, a text-related subcomponent (322) corresponding to state information (312) may be located in the second slot (212) of the target component, a text-related subcomponent (323) corresponding to state information (313) may be located in the third slot (230) of the target component, and a button-related subcomponent (324) corresponding to state information (314) may be located in the fourth slot (240) of the target component. That is, the target component generated by the electronic device may be dependent on or oriented to the state information tree (300), and may have a one-to-one correspondence with the state information tree (300).

[0072] According to one embodiment, in order to create a target component of a different version from the default version of the target component (200) of FIG. 2 and a subcomponent located in a specific slot, the state information corresponding to the specific slot may be set differently from the state information tree (300), and the state information corresponding to slots excluding the specific slot may be set identically to the state information tree (300). That is, the subcomponents located in slots excluding the specific slot can be reused as is to create a target component of a different version. The developer can add fields related to the state information corresponding to the specific slot to the source code, and reuse fields related to the state information corresponding to slots excluding the specific slot. That is, redundant work such as writing unnecessary source code by the developer can be minimized. In addition, even if a subcomponent is updated by a designer, if there is no change in the state information of the slot in which the subcomponent is located, the developer can immediately use the updated subcomponent without additional work.

[0073] FIG. 4 is a diagram illustrating a method for identifying state information associated with at least one slot from source code according to one embodiment.

[0074] The source code (400) may include a first field (401) related to a first type of state information and a second field (402) related to a second type of state information. Here, the source code may be a source code for generating a target component of a different version from the default version of the target component of FIG. 2. The electronic device may identify state information related to at least one slot from the source code (400) using the first level API.

[0075] In this disclosure, the first-level API may be an API that reflects the design specifications of the target component and simplifies the creation of target components with predefined styles. In other words, the first-level API is an API for quickly providing target components with predefined styles, thereby preventing hard coding by developers. Here, the predefined style may mean that among the state information associated with at least one slot, the first type of state information is set as default state information.

[0076] The first field (401) may indicate that the first type of state information of at least one first sub-slot among at least one sub-slot included in the target component is the first type of default state information set. For example, the state information of at least one first slot excluding the third slot among at least one slot, which is the first slot, the second slot, the third slot, and the fourth slot, may be included in the first field (401). The first field (401) may indicate that the first type of state information of the first slot, which is the start slot, the second slot, which is the content slot, and the fourth slot, which is the end slot, is set as default state information through the Setstate(buildMessageBoxState) function that sets the state information. That is, the sub-components corresponding to the first slot, the second slot, and the fourth slot may be determined as default sub-components of a preset style.

[0077] According to one embodiment, the electronic device may determine the first type of state information of at least one first sub-slot as the first type of default state information set using the first level API from the source code. The first type of state information of the state information tree (410) may correspond to state information (413), state information (414), and state information (415), which are the first type of state information of the first slot, the second slot, and the fourth slot, respectively. The first slot, the second slot, and the fourth slot of the new version of the target component may have the same sub-components as the first slot (210), the second slot (220), and the fourth slot (240) of the default version of the target component (200). On the other hand, the electronic device may confirm that the state information corresponding to the third slot is not described in the source code (400). That is, the third slot of the new version of the target component may not have a sub-component, and thus the third slot of the new version of the target component may be a void area.

[0078] The second field (402) may indicate the second type of state information. More specifically, referring to FIG. 4, the second field (402) may indicate that the second type of state information is the second type of default state information that is set. The default color value, default size value, and default effect value of the target component may be preset as specifications related to the target component. For example, the background color information of the target component among the first type of state information may be the set default color value, Color, which may be green. In addition, the size information of the target component among the first type of state information may be the set default size value, Size, which may be M. The effect information of the target component among the first type of state information may be the set default effect value, effect, which may be tint. That is, the feature of the background of the target component may be determined as a light green color.

[0079] According to one embodiment, the electronic device can identify the second type of state information of the target component using the first level API from the source code. Referring to FIG. 4, the second type of state information (411) of the target component may be the set second type of default state information. That is, the size and background color of the new version of the target component may be the same as the size and background color of the default version of the target component (200). The new version of the target component generated based on the source code (400) may have the same design as the default version of the target component (200) except that the third slot (230) is a void area. Since the first type of state information for at least one first slot in the first field (401) is set as the default state information, the new version of the target component may be a target component of a predefined style.

[0080] In one embodiment, the electronic device may determine an API for analyzing state information by analyzing source code. More specifically, for each of at least one slot, when the first type of state information is set as default state information preset in the source code or the first type of state information is not included in the source code, the electronic device may use the first level API to identify state information associated with at least one slot from the source code.

[0081] Following FIG. 4, FIG. 5 is a diagram illustrating a method for identifying state information related to at least one slot from source code according to another embodiment.

[0082] The source code (500) may include a first field (501) related to a first type of state information and a second field (502) related to a second type of state information. Here, the source code may be a source code for generating a target component of a different version from the default version of the target component of FIG. 2. The electronic device may use the second level API to identify state information related to at least one slot from the source code (500).

[0083] In this disclosure, the second-level API may be an API for creating and assembling at least one subcomponent. More specifically, the second-level API may be an API used for creating a customized target component with a different style than a target component with a predefined style.

[0084] The first field (501) may indicate the first type of status information of at least one first sub-slot among at least one sub-slot included in the target component. For example, status information of at least one first slot excluding the third slot among at least one slot, which is the first slot, the second slot, the third slot, and the fourth slot, may be included in the first field (501). The sub-field (503) corresponding to the first slot in the first field (501) may include information on image data related to Logo, Icon, CircularImage, and SquareImage, information on the height and width of the image data, color information of the image data, and font color information of the text in the image data. The sub-field (504) corresponding to the second slot in the first field (501) may include information on text data, font size information of the text data, and font color information. The subfield (505) corresponding to the fourth slot within the first field (501) may include information on button-related icon data, information on the height and width of the icon data, and color information on the icon data. In addition, the subfield (505) may include a field for information on a text button; however, information on the text button with respect to the fourth slot may not be set within the subfield (505).

[0085] The second field (502) may indicate the second type of state information. More specifically, referring to FIG. 5, the second field (502) may indicate that the second type of state information is the second type of default state information that has been set. For example, the background color information of the target component among the first type of state information may be the set default color value, Color, which may be green. In addition, the size information of the target component among the first type of state information may be the set default size value, Size, which may be M. The effect information of the target component among the first type of state information may be the set default effect value, effect, which may be tint.

[0086] According to one embodiment, the electronic device can determine the first type of state information and the second type of state information using the second level API from the source code. The first type of state information of the state information tree (510) may correspond to the first type of state information, namely, state information (513), state information (514), and state information (515), of the first slot, the second slot, and the fourth slot, respectively. The first slot, the second slot, and the fourth slot of the new version of the target component may have the same subcomponents as the first slot (210), the second slot (220), and the fourth slot (240) of the default version of the target component (200). On the other hand, since the state information of the third slot is not in the first field (501), the electronic device can determine that there is no first type of state information corresponding to the third slot. That is, since the third slot of the new version of the target component may not have a subcomponent, the third slot of the new version of the target component may be a void area. Additionally, the second type of state information (511) of the target component may be the default state information of the second type that has been set. A new version of the target component generated based on the source code (500) may have the same design as the default version of the target component (200), except that the third slot is a void area.

[0087] FIG. 6 may be a drawing for explaining a new version of a target component according to an embodiment of FIGS. 4 and 5.

[0088] FIG. 6 illustrates a new version of a target component (600) that is different from the default version of the target component (200) generated based on the source code (400) of FIG. 4 or the source code (500) of FIG. 5. As described above, the subcomponents located in the first slot (610), the second slot (620), and the fourth slot (640) of the target component (600) may be identical to the subcomponents located in the first slot (210), the second slot (220), and the fourth slot (240) of the target component (200). On the other hand, the third slot (630) of the target component (600) may not have a subcomponent located therein, and thus the third slot (630) of the target component (600) may be a void area. That is, the third slot (630) of the target component (600) and the third slot (203) of the target component (200) may differ in whether a sub-component is located in the third slot.

[0089] Multiple versions of a target component may be stored on an electronic device. In this regard, when receiving source code related to a call to a target component, the electronic device may provide the terminal with a version of the target component corresponding to the field values ​​of variants within the source code. When providing a specific version of a target component to a terminal, such as during AB testing, the version of the target component provided to each user's terminal may be determined by the provider of the UI component.

[0090] Referring to FIGS. 4 and 5, the first type of state information of at least one first slot is set to the first type of default state information of at least one first slot, so that the new version of the target component (600) may not be completely identical to the default version of the target component (200), but may be a predefined style target component. That is, it may be more efficient for the electronic device to generate the target component from source code using the first level API among the first level API and the second level API.

[0091] However, if the target component is not a target component of a predefined style, the electronic device may generate the target component from the source code using a second-level API. That is, the second-level API may be an API used to identify state information when the source code includes a field indicating that at least some of the first-type state information is set to a first-type state information that is different from the first-type default state information.

[0092] FIG. 7 is a diagram illustrating a method for identifying state information associated with at least one slot from source code according to one embodiment.

[0093] According to one embodiment, when state information of a first slot among at least one slot is different from default state information of the first slot in a target component of a default version, and state information of a second slot among at least one slot is default state information of the second slot in the target component of the default version, the source code may include a first subfield indicating that the state information of the first slot is set to state information different from the default state information of the first slot, and a second subfield indicating that the state information of the second slot is set to the default state information of the second slot.

[0094] The first subfield (701) corresponding to the first slot of the source code (700) may be different from the subfield (503) corresponding to the first slot of the source code (500). More specifically, the first subfield (701) may indicate that the state information of the start slot, which is the first slot, is TwocircularImageState. That is, the first subfield (701) may indicate that the state information of the first slot is set to state information that is different from the state information (513), which is the default state information of the first slot. The image data related to TwocircularImage may be data pre-generated by the developer and may be set to data of TwocircularImageState. Information about the height and width of the image data related to TwocircularImage of the source code (700), the color information of the image data, and the font color information of the text in the image data may be set to be identical to the state information of the source code (500). On the other hand, the second subfield (702) corresponding to the second slot of the source code (700) may be identical to the subfield (504) corresponding to the second slot of the source code (500). That is, the second subfield (702) may indicate that the state information of the second slot is set identical to the state information (514), which is the default state information of the second slot.

[0095] Referring to the state information tree (710) corresponding to the source code (700), the state information (711) corresponding to the first slot among the state information of the first type may be different from the state information (513) corresponding to the first slot in the state information tree (510). On the other hand, the state information (712) corresponding to the second slot among the state information of the first type may be different from the state information (514) corresponding to the second slot in the state information tree (510).

[0096] Following FIG. 7, FIG. 8 may be a drawing for explaining a target component of a version according to one embodiment.

[0097] Fig. 8 illustrates a new version of a target component (800) that is different from the default version of the target component (200) generated based on the source code (700) of Fig. 7. The subcomponents located in the second slot (820) and the fourth slot (840) of the target component (800) may be identical to the subcomponents located in the second slot (620) and the fourth slot (640) of the target component (600). In addition, the third slot (830) of the target component (800) may be a void area, like the third slot (630) of the target component (600). On the other hand, the subcomponent located in the first slot (810) of the target component (800) may be displayed as in Fig. 8.

[0098] More specifically, the subcomponent located in the first slot (810) may be generated as image data related to TwocircularImage is rendered according to the status information in the first subfield (701). Referring to FIG. 8, the subcomponent located in the first slot (810) may be an icon having the letter C engraved inside two partially overlapping circles.

[0099] FIG. 9 is a diagram illustrating a method for identifying status information associated with at least one slot through an interface.

[0100] According to one embodiment, a developer or UI designer can set state information related to a target component by selecting settings in an interface. Here, the interface may be an interface for setting state information related to at least one slot, and may be Figma. More specifically, the interface may include a first area (901) for setting state information of the target component itself, and a second area (902) for setting state information of each of at least one subcomponent.

[0101] The first area (901) may be an area within the interface (900) that can set the second type of state information that sets the feature from the overall perspective of the target component. That is, the first area (901) may be an area that sets the state information of the target component itself. More specifically, the type of the first area (901) corresponds to the effect of the source code (400) and may be set to Tint. In addition, the size of the first area (901) corresponds to the size of the source code (400) and may be set to M. In addition, the color of the first area (901) corresponds to the color of the source code (400) and may be set to green.

[0102] The second area (902) may be an area within the interface (900) that can set at least one slot-specific status information. For example, with respect to the first slot, the start slot, the second area (902) may include a sub-area for selecting image data located in the first slot as one of an icon, a logo, a circular image, and a square image, and a sub-area for selecting one of a plurality of image data of the selected type. Referring to FIG. 9, the image data located in the first slot is set to an icon. In addition, the image data located in the first slot may correspond to an icon in the first slot (610) of FIG. 6 among icons. In addition, whether to activate the first slot, the start slot, may also be set through the second area (902).

[0103] The source code (910) may be a source code in which at least one slot-specific state information set in the interface (900) is transformed. Since the third slot, which is a bottom slot, is deactivated among the at least one slot-specific state information set in the interface (900), the first field (911) in the source code (910) may include only state information related to the start slot, which is the first slot, the content slot, which is the second slot, and the end slot, which is the fourth slot, and may not include state information of the bottom slot, which is the deactivated third slot.

[0104] Since the bottom slot, which is the third slot, and the end slot, which is the fourth slot, are deactivated among at least one slot-specific status information set in the interface (900), the first field (921) in the source code (920) may only include status information related to the start slot, which is the first slot, and the content slot, which is the second slot, and may not include status information of the bottom slot, which is the third slot, and the end slot, which is the fourth slot, which are deactivated.

[0105] Following FIG. 9, FIG. 10 may be a drawing for explaining a target component according to one embodiment.

[0106] The target component (1000) may be a version of the target component generated based on the source code (910). Referring to FIG. 9, the first field (911) may not include status information of the bottom slot, which is a disabled third slot, and thus the target component (1000) generated based on the source code (910) may be identical to the target component (600) of FIG. 6. The bottom slot, which is the third slot of the target component (1000), may be a void area.

[0107] The target component (1050) may be a target component of a version generated based on the source code (920). Referring to FIG. 9, the first field (921) may not include state information of the bottom slot, which is a third slot, and the end slot, which is a fourth slot, which are inactive. That is, subcomponents may not be located in the bottom slot, which is a third slot, and the end slot, which is a fourth slot, of the target component (1050) generated based on the source code (920), and thus the bottom slot, which is a third slot, and the end slot, which is a fourth slot, of the target component (1050) may be void areas. The subcomponents located in the start slot, which is a first slot, and the content slot, which is a second slot, of the target component (1050) may be the same as the subcomponents located in the start slot, which is a first slot, and the content slot, which is a second slot, of the target component (1000).

[0108] FIG. 11 is a block diagram schematically illustrating an electronic device for generating a UI component according to one embodiment.

[0109] The electronic device (1100) of FIG. 11 may correspond to the electronic device of the present specification. The electronic device (1100) of the present disclosure may include a processor (1110) and storage (1120), according to one embodiment. The components illustrated in FIG. 11 are not essential for implementing the electronic device, and thus, it will be understood by those skilled in the art related to the present embodiment that the electronic device (1100) described in the present specification may include more or fewer components than the components listed above. Meanwhile, in the embodiment, the processor (1110) may include at least one processor.

[0110] The processor (1110) can control the overall operation of the electronic device (1100) and process data and signals. The processor (1110) can perform one of the methods described above with reference to FIGS. 1 to 11 . The processor (1110) can control embodiments performed by the electronic device (1100) through interaction with the storage (1120) and further components that the electronic device (1100) may include.

[0111] One or more processors (1110) may control embodiments performed by the electronic device (1100) through interaction with the memory (1120) and further components that the electronic device (1100) may include. According to one embodiment, the one or more processors (1930) may execute one or more instructions to identify a target component, identify at least one slot of the target component, identify state information related to the at least one slot from source code related to the target component, determine at least one subcomponent corresponding to the at least one slot based on the state information, and generate a target component including the at least one subcomponent based on a hierarchical structure of the target component.

[0112] Storage (1120) can store information for performing at least one of the methods described above with reference to FIGS. 1 to 11 . Storage (1120) can be referred to as memory and can be volatile memory or non-volatile memory. In addition, storage (1120) can store one or more instructions required to perform the operation of processor (1110) and can temporarily store data stored on the platform or in external memory. Storage (1120) can store source code related to the target component, data for at least one sub-component, and information regarding the hierarchical structure of the target component. In addition, storage (1120) can store various versions of the target component, including a default version of the target component.

[0113] The electronic device (1100) may further include a transceiver (not shown). The transceiver may communicate with an external device using wired or wireless communication technology and may include a transceiver. The external device may be a client device, a terminal, an open source platform, or a server. Communication technologies used by the transceiver may include, but are not limited to, GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), LTE (Long Term Evolution), 5G, WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Bluetooth, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), ZigBee, NFC (Near Field Communication), etc.

[0114] Meanwhile, the present specification and drawings disclose preferred embodiments of the present invention. Although specific terms have been used, they are used in a general sense only to easily explain the technical contents of the present invention and to assist in understanding the invention, and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modified examples based on the technical concept of the present invention are possible in addition to the embodiments disclosed herein.

[0115] The electronic device or terminal according to the above-described embodiments may include a processor, a memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, a user interface device such as a touch panel, a key, an icon, etc. The methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable codes or program commands executable on the processor. Here, the computer-readable recording medium includes a magnetic storage medium (e.g., read-only memory (ROM), random-access memory (RAM), floppy disk, hard disk, etc.) and an optical reading medium (e.g., CD-ROM, DVD: Digital Versatile Disc)). The computer-readable recording medium may be distributed to computer systems connected to a network, so that the computer-readable code may be stored and executed in a distributed manner. The medium may be readable by a computer, stored in a memory, and executed by a processor.

[0116] The present embodiment may be represented by functional block configurations and various processing steps. These functional blocks may be implemented by various hardware and / or software configurations that perform specific functions. For example, the embodiment may employ direct circuit configurations such as memory, processing, logic, look-up tables, etc., which may perform various functions under the control of one or more microprocessors or other control devices. Similarly, the present embodiment may be implemented in a programming or scripting language such as C, C++, Java, assembler, Python, etc., including various algorithms implemented as a combination of data structures, processes, routines, or other programming configurations. Functional aspects may be implemented as algorithms that execute on one or more processors. Furthermore, the present embodiment may employ conventional techniques for electronic configuration, signal processing, and / or data processing. Terms like "mechanism," "element," "means," and "composition" can be used broadly and are not limited to mechanical or physical components. These terms can also encompass a series of software routines, such as those associated with a processor.

[0117] The above-described embodiments are merely examples, and other embodiments may be implemented within the scope of the claims set forth below.

Claims

1. A method for creating a UI component in an electronic device, Step to verify the target component; A step of checking at least one slot of the target component; A step of identifying state information related to at least one slot from source code related to the target component; A step of determining at least one subcomponent corresponding to at least one slot according to the above state information; and A step of generating the target component including at least one subcomponent based on the hierarchical structure of the target component, How to create a UI component.

2. In paragraph 1, The step of identifying the above status information is: A step of determining the first type of state information among the state information as the first type of default state information using the first level API; and A step of identifying a second type of state information among the state information from the source code using the API of the first level, How to create a UI component.

3. In paragraph 2, The above source code is, A first field indicating that the state information of the first type is set to the default state information of the first type set, and including a second field representing the second type of status information, How to create a UI component.

4. In paragraph 1, The step of identifying the above status information is: A step of identifying the first type of state information and the second type of state information from the source code using the second level API, How to create a UI component.

5. In paragraph 4, The above second level API is, When the source code includes a third field indicating that at least some of the state information of the first type is set to a first type of state information different from the default state information of the first type, the API being used is How to create a UI component.

6. In paragraph 1, The above target component in the default version is, comprising at least one default subcomponent corresponding to default state information associated with at least one slot; How to create a UI component.

7. In paragraph 5, When the state information of the first slot among the at least one slot is different from the default state information of the first slot in the target component of the default version, and the state information of the second slot among the at least one slot is the default state information of the second slot in the target component of the default version, the source code, A first subfield indicating that the status information of the first slot is set to status information different from the default status information of the first slot, and a second subfield indicating that the status information of the second slot is set to the default status information of the second slot. How to create a UI component.

8. In paragraph 1, The step of identifying the above status information is: Further comprising the step of identifying state information associated with said at least one slot through the interface; How to create a UI component.

9. In paragraph 8, The above interface is, A first area for setting the status information of the above target component, and A second area comprising a second region for setting state information of each of the at least one subcomponent, How to create a UI component.

10. In paragraph 1, The step of determining at least one subcomponent is: A step of identifying data for at least one sub-component based on the above state information, The steps for creating the above target component are: A step of generating the target component by rendering data for at least one subcomponent to satisfy the hierarchical structure based on the state information, How to create a UI component.

11. In paragraph 1, The above source code is, Either the source code in XML format or the source code in JSON format, How to create a UI component.

12. In an electronic device for creating a UI component, one or more processors; and comprising storage for storing one or more instructions executed by said one or more processors; The one or more processors, by executing the one or more instructions, Check the target component, Check at least one slot of the above target component, From the source code associated with the target component, identify state information associated with at least one slot, According to the above state information, at least one subcomponent corresponding to the at least one slot is determined, and Based on the hierarchical structure of the target component, generating the target component including at least one subcomponent. An electronic device for creating UI components.

13. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method of paragraph 1 on a computer.

Citation Information

Patent Citations

  • Hybrid application development system based on object relational mapping and the method thereof

    KR101588592B1

  • Interactive multimedia E-book authoring apparatus and method

    KR1020140096225A

  • Methods and systems for resolving conflicts in hierarchically-referenced data

    KR1020150079467A

  • Method and Apparatus for Re-Configuring Design Decisions after Developing Graphic User Interface

    KR1020150092880A

  • System and method for sharing software component

    KR102327083B1