Patent Application
20240362149
The present disclosure relates to the field of data processing, and in particular, relates to a component debugging method, apparatus, device, and storage medium.
Components in an application program refer to various types of controls displayed on an interactive interface of the application program, such as a button control, an input box control and so on. In a practical application, the same component often has multiple forms. For example, for a button control, there is at least a pressed form and a non-pressed form. Before developing an application based on components, developers need to know the form and capability of each component in advance, so as to apply each component accurately and efficiently in the process of application development, and improve the overall efficiency of application development.
At present, the way to exhibit the forms and capabilities of components for users is relatively simple, as shown in
In order to solve or at least partially solve the above technical problem, the present disclosure may provide a component debugging method, apparatus, device, and storage medium, which can fully exhibit various forms of a target component for a user, so that the user can fully understand the capability of the target component, and the efficiency of application development based on the target component can be further improved.
In a first aspect, the present disclosure may provide a component debugging method, which may include:
In an embodiment of the present disclosure, the debugging panel may further exhibit an attribute value range corresponding to the attribute of the target component.
In an embodiment of the present disclosure, before the exhibiting a debugging page for a target component, the method may further include:
In an embodiment of the present disclosure, the configuration file may include the correspondence among attributes, attribute value types and attribute value ranges, and the debugging panel is used to exhibit the attribute based on the preset debugging mode and attribute value range corresponding to the attribute.
In an embodiment of the present disclosure, the debugged attribute value is a limit value of the target attribute, and the exhibiting the form of the target component in the form exhibition window based on the debugged attribute value, may include:
In an embodiment of the present disclosure, the component debugging method is applied to a component test acceptance scenario.
In an embodiment of the present disclosure, the debugging panel is provided with a displacement control widget, and the method may further include:
In an embodiment of the present disclosure, the target component may include an interactive component, and after the exhibiting the form of the target component in the form exhibition window based on the debugged attribute value, the method may further include:
In an embodiment of the present disclosure, the target component may include a preset type of component, which may include a page type of component and a to-be-triggered effect component;
In a second aspect, the present disclosure provides a component debugging apparatus, which may include:
In a third aspect, the present disclosure provides a computer-readable storage medium storing instructions therein, the instructions, when running on a terminal device, cause the terminal device to implement the method as described above.
In a fourth aspect, the present disclosure provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor, when executing the computer program, implements the method as described above.
In a fifth aspect, the present disclosure provides a computer program product comprising computer programs/instructions which, when executed by a processor, implement the method as described above.
In a sixth aspect, the present disclosure provides a computer program, program codes included in the computer program, when executed by a computer, cause the computer to implement the method as described above.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the present disclosure.
In order to explain a technical scheme in an embodiment of the present disclosure or in the prior art more clearly, the drawings needed in the description of the embodiment or the prior art will be briefly introduced below. Obviously, for those ordinary skilled in the field, other drawings can be obtained according to these drawings without requiring any creative work.
In order to understand the above objects, features and advantages of the present disclosure more clearly, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.
In the following description, many specific details are set forth in order to fully understand the present disclosure, but the present disclosure may be practiced in other ways than those described herein; obviously, the embodiments in the specification are only part of the embodiments of the present disclosure, not all of them.
A component in an application program usually has various forms, and it is an urgent technical problem that how to fully and comprehensively exhibit various forms of the component for users so that the user can fully understand the capability of the target component.
Furthermore, how to fully and comprehensively exhibit various forms of components for users so as to improve the overall efficiency of component-based application development is an technical problem.
In an application scenario, before developing an application program based on components, developers need to know the capability of each component in advance, so as to implement application of each component accurately and efficiently in the process of application program development, and improve the overall development efficiency of application finally.
In another application scenario, after the component development is completed, it is often necessary to perform test acceptance for the component to determine whether the developed component meets expectations. Therefore, in the process of performing the test acceptance for the component, the premise for ensuring the result of test acceptance is to exhibit various forms of the component for users fully and comprehensively.
Based on the above-mentioned at least two application scenarios, how to fully and comprehensively exhibit various forms and capabilities of a component is a technical problem to be solved by an embodiment of this disclosure.
Therefore, the embodiment of the present disclosure provides a component debugging method, firstly, a debugging page for a target component is exhibited, wherein the debugging page may include a debugging panel and a form exhibition window, the debugging panel is used for exhibiting an attribute of a target component in a preset debugging mode which is used for indicating a debugging operation for the attribute, and the form exhibition window is used for exhibiting the form of the target component. Then, in response to the debugging operation for a target attribute on the debugging page, a debugged attribute value of the target attribute is acquired, and the form of the target component is exhibited in the form exhibition window based on the debugged attribute value.
The embodiment of the present disclosure can exhibit the form of the target component in the form exhibition window in real time based on a debugging operation for the attribute of the target component. Therefore, the embodiment of the present disclosure can fully and comprehensively exhibit various forms of the target component for a user, so that the user can fully understand the capability of the target component, and the efficiency of application development based on the target component can be further improved.
In addition, the embodiment of the present disclosure can exhibit the form of the target component in real time by a debugging operation for the attribute of the target component, to determine whether the target component meets the expectations based on the form of the target component when the test acceptance is performed for the target component, so as to complete the test acceptance of the target component.
On this basis, an embodiment of the present disclosure provides a component debugging method, referring to
Wherein the debugging page may include a debugging panel and a form exhibition window, the debugging panel is used for exhibiting an attribute of a target component in a preset debugging mode, the preset debugging mode is used for indicating a debugging operation for the attribute, and the form exhibition window is used for exhibiting the form of the target component.
In an embodiment of the present disclosure, a component may include various types of controls displayed on an interactive interface of the application program, such as a button control, an input box control and so on. Among them, a target component can be any type of control, such as a button control.
In an embodiment of the present disclosure, optionally, before the debugging page for the target component is exhibited, a configuration file for the target component may be received first, wherein the configuration file may include correspondence between attributes and attribute value types of the target component. Specifically, an attribute of the target component may be used to characterize a display feature of the target component, which may include, but not limited to, color, size, location information, etc. It should note that different components usually have different attributes.
In addition, an attribute value type may be used to characterize the type of an available attribute value of an attribute, for example, assuming that the available attribute value of an attribute is any value between 0 and 80, the attribute value type corresponding to the attribute is a continuous numerical type; assuming that the available attribute values of an attribute are “black”, “red” and “green” respectively, the attribute value type corresponding to the attribute is enumerated numerical type, assuming that the available attribute values of the attribute are “open” and “close” respectively, the attribute value type corresponding to the attribute is Boolean numerical type. Embodiments of that present disclosure do not limit the types of attribute value.
After receiving the configuration file for the target component, an embodiment of the present disclosure can obtain the correspondence between the attributes and the attribute value types of the target component by analyzing the configuration file. Then, based on the attribute value type corresponding to the attribute, the preset debugging mode corresponding to the attribute can be determined. Wherein, the preset debugging mode is used for indicating the debugging operation for the attribute.
It should note that the above step is not necessary. In particular, the above step can be included in the method according to embodiments of the present disclosure, and can also be performed outside the method according to embodiments of the present disclosure. Even if the above step is not performed, the scheme of the present disclosure is still complete and can achieve advantageous technical effects, so it is shown by dotted lines in
In an embodiment of the present disclosure, after the preset debugging mode corresponding to the attribute of the target component is determined, a debugging tool corresponding to the preset debugging mode is determined. Among them, the debugging tool can include, but not limited to, a slider debugging tools, a click debugging tool, an input debugging tool, a switch debugging tool, etc. For example, the preset debugging mode for an attribute corresponding to the above continuous numerical type can be implemented based on the slider debugging tool.
In an embodiment of the present disclosure, based on an attribute value type corresponding to an attribute, the determined preset debugging mode corresponding to the attribute may include one or more modes. Assuming that the attribute value type corresponding to an attribute is a continuous numerical type, the preset debugging mode corresponding to the attribute can include a debugging mode based on the slider debugging tool and a debugging mode based on the input debugging tool, that is to say, the attribute valude of a continuous numerical type of attribute can be debugged by the slider debugging, or the attribute value of a continuous numerical type of attribute can be debugged by the input debugging.
In an embodiment of the present disclosure, after a preset debugging mode corresponding to an attribute of a target component is determined, the corresponding attribute is exhibited on a debugging panel of a debugging page for the target component in the preset debugging mode. Referring to
In an embodiment of the present disclosure, the debugging panel 320 can also exhibit an attribute value range corresponding to an attribute of the target component for controlling the attribute value debugging range for the attribute. As shown in
In a practical application, the configuration file for the target component can include correspondence between the attribute, the attribute value type and the attribute value range. Specifically, the attribute is exhibited on the debugging panel 320 of the debugging page of the target component by displaying the preset debugging mode and the attribute value range corresponding to the attribute.
In addition, the debugging panel can also be provided with a displacement control widget, such as the displacement control widget 330 shown in
In an embodiment of the present disclosure, the preset trigger operation for the displacement control widget may include a long press and drag operation for the displacement control widget, and the user can adjust the display height of the debugging panel by long pressing and dragging the displacement control widget up and down.
In a practical application, assuming the target component exhibited in the form exhibition window is large, the display height of the debugging panel can be adjusted by the displacement control widget to avoid the debugging panel covering the target component exhibited in the form exhibition window, thus avoiding the form exhibit effect of the target component being affected.
In an embodiment of the present disclosure, after the debugging page for the target component is exhibited, the user can trigger the debugging operation for a target attribute on the debugging page, wherein the target attribute can be any attribute exhibited on the debugging page. Specifically, after the debugging operation for the target attribute on the debugging page is received, a debugged attribute value of the target attribute is first acquired, for example, if the user debugs the attribute value corresponding to attribute 2 in
Referring to
In an embodiment of the present disclosure, the target component may include an interactive component, such as a clickable button control, etc., after the form of the target component is exhibited in the form exhibition window, the user can trigger a preset interactive operation for the target component in the form exhibition window, For example, a click operation, a drag operation and so on are triggered for the button component.
In an embodiment of the present disclosure, optionally, when a preset interactive operation triggered for the target component exhibited in the form exhibition window is received, the interactive form of the target component is exhibited in the form exhibition window. For example, when a click operation triggered for a button component is received, the clicked form of the button component is exhibited in the form exhibition window. It should note that the above step is not necessary. In particular, the above step can be included in the method according to embodiments of the present disclosure, and can also be performed outside the method according to embodiments of the present disclosure. Even if the above step is not performed, the scheme of the present disclosure is still complete and can achieve advantageous technical effects, so it is shown by dotted lines in
In an embodiment of the present disclosure, the interactive forms of various types of target components are exhibited by the form exhibition window, users can fully understand the capabilities of the target components, and the efficiency of application development based on the target components can be further improved.
In an embodiment of the present disclosure, the target component may also include a preset type of component, wherein the preset type of component may include a page type of component and a to-be-triggered effect component.
Specifically, a page type of component can include a page component with specific functions such as a page loading component, a video playback page component and so on, and can be directly called by different applications. However, because the exhibition of the page type of component needs to occupy the whole display page of the device, the preset control can serve as an entrance to trigger exhibition of the form of the component, so as to switch to the whole display page of the device for exhibiting the form of the page type of component. Among them, the preset control in the embodiment of the present disclosure can be any control with interactive function, for example, the preset control can be a button control, etc., the preset control is usually exhibited in the center of the form exhibition window, and it can also be exhibited at other positions in the form exhibition window as required. The embodiment of the present disclosure does not limit the exhibition position of the preset control.
In addition, the to-be-triggered effect component can include a component that requires active triggering by a user for exhibition, such as a pop-up type of component, toast message prompt box type of component, and so on. In order to reflect the characteristics of this class of components, the preset control can serve as an entrance to trigger exhibition of the forms of the class of components, and the preset control can be triggered for switching to exhibition of this class of components.
In addition, the to-be-triggered effect component can also include a component that needs to exhibit dynamic effects, such as a component that need to exhibit the staying time of the component or the page entry and exit effects. In order to dynamically exhibit the effects of such components, the preset control can serve as an entrance to trigger exhibition of the forms of such components, and the preset control can be triggered for switching to exhibition of such components.
In an embodiment of the present disclosure, assuming that the target component includes a preset type of component, after a debugging operation for a target attribute on the debugging page is received and a debugged attribute value of the target attribute is acquired, firstly, a preset control is exhibited in the form exhibition window; wherein, the preset control is used for triggering exhibition of the form of the target component. Then, when a preset trigger operation for the preset control is received, the form of the target component is exhibited in the form exhibition window based on the debugged attribute value. It should note that the above steps are not necessary. In particular, the above steps can be included in the method according to embodiments of the present disclosure, and can also be performed outside the method according to embodiments of the present disclosure. Even if the above steps are not performed, the scheme of the present disclosure is still complete and can achieve advantageous technical effects, so it is shown by dotted lines in
In the component debugging method provided by embodiments of the present disclosure, firstly, a debugging page for a target component is exhibited, wherein the debugging page may include a debugging panel and a form exhibition window, the debugging panel is used for exhibiting an attribute of a target component in a preset debugging mode which is used for indicating a debugging operation for the attribute, and the form exhibition window is used for exhibiting the form of the target component. Then, in response to the debugging operation for a target attribute on the debugging page, a debugged attribute value of the target attribute is acquired, and the form of the target component is exhibited in the form exhibition window based on the debugged attribute value. The embodiment of the present disclosure can exhibit the form of the target component in the form exhibition window in real time based on a debugging operation for the attribute of the target component. Therefore, the embodiment of the present disclosure can fully and comprehensively exhibit various forms of the target component for a user, so that the user can fully understand the capability of the target component, and the efficiency of application development based on the target component can be further improved.
In a practical application, the form of a component in a limit state is a component form that application developers and component test and acceptance person pay close attention to. Therefore, an embodiment of the present disclosure can exhibit the user the form of a target component in a limit state corresponding to the target attribute in the form exhibition window, so that the user can fully understand various forms and capabilities of the target component.
In an embodiment of the present disclosure, when a debugging operation for a target attribute of a target component on the debugging page is received, a debugged attribute value of the target attribute is acquired. If it is determined that the debugged attribute value is the limit value of the target attribute, then in the form exhibition window, the form of a target component in a limit state corresponding to the target attribute is exhibited based on the limit value.
For example, taking the target attribute being the height as an example, after the attribute value of the height becomes the limit value of 80 by slider debugging, the form of the target component in the limit state that the height is the limit value of 80 is exhibited in the form exhibition window of the target component.
In the component debugging method provided by embodiments of the present disclosure, by exhibiting the form of the target component in the limit state corresponding to the target attribute, the user can fully understand various forms and capabilities of the target component.
Based on embodiments of the above method, the present disclosure also provides a component debugging apparatus, referring to
In an embodiment of the present disclosure, the debugging panel may further exhibit an attribute value range corresponding to the attribute of the target component.
In an embodiment of the present disclosure, the apparatus may further include: a receiving module configured to receive a configuration file for the target component; wherein, the configuration file may include correspondence between attributes and attribute value types;
In an embodiment of the present disclosure, the configuration file may include the correspondence among attributes, attribute value types and attribute value ranges, and the debugging panel is used to exhibit the attribute based on the preset debugging mode and attribute value range corresponding to the attribute.
In an embodiment of the present disclosure, the debugged attribute value is a limit value of the target attribute, and the second exhibition module is specifically configured to:
In an embodiment of the present disclosure, the component debugging method is applied to a component test acceptance scenario.
In an embodiment of the present disclosure, the debugging panel is provided with a displacement control widget, and the apparatus may further include:
In an embodiment of the present disclosure, the target component may include an interactive component, and the apparatus may further include:
In an embodiment of the present disclosure, the target component may include a preset type of component, which may include a page type of component and a to-be-triggered effect component;
The apparatus may further include:
It should be pointed out that the above-mentioned receiving module, determination module, adjustment module, third exhibition module and fourth exhibition module are not necessarily included in the component debugging apparatus according to embodiments of the present disclosure, in particular, they may be included in the component debugging apparatus, or they may be located outside the component debugging apparatus to communicate with the component debugging apparatus, so they are shown by dotted lines in the drawings.
It should be noted that the above modules are only divided according to their specific functions, instead of being used to limit their specific implementations, for example, they can be implemented in software, hardware or a combination of software and hardware. In actual implementation, the above modules can be realized as independent physical entities, or can also be realized by a single entity (for example, a processor (CPU or DSP, etc.), an integrated circuit, etc.).
In addition, although not shown, the apparatus may also include a memory, which may store various information generated by the apparatus and various modules included in the apparatus during operation, programs and data used for operation, data to be transmitted by the communication unit, and the like. The memory may be a volatile memory and/or a nonvolatile memory. For example, the memory may include, but not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), and flash memory. Of course, the memory may also be located outside the apparatus. Alternatively, although not shown, the apparatus may also include a communication unit, which may be used to communicate with other apparatuses. In one example, the communication apparatus can be implemented in an appropriate manner known in the art, and will not be described in detail here.
In the component debugging apparatus provided by embodiments of the present disclosure, firstly, a debugging page for a target component is exhibited, wherein the debugging page may include a debugging panel and a form exhibition window, the debugging panel is used for exhibiting an attribute of a target component in a preset debugging mode which is used for indicating a debugging operation for the attribute, and the form exhibition window is used for exhibiting the form of the target component. Then, in response to the debugging operation for a target attribute on the debugging page, a debugged attribute value of the target attribute is acquired, and the form of the target component is exhibited in the form exhibition window based on the debugged attribute value. The embodiment of the present disclosure can exhibit the form of the target component in the form exhibition window in real time based on a debugging operation for the attribute of the target component. Therefore, the embodiment of the present disclosure can fully exhibit various forms of the target component for a user, so that the user can fully understand the capability of the target component, and the efficiency of application development based on the target component can be further improved.
In addition to the above method and apparatus, the embodiments of the present disclosure also provides a computer-readable storage medium in which instructions are stored, the instructions, when running on a terminal device, cause the terminal device to implement the component debugging method according to embodiments of the present disclosure.
The embodiments of the present disclosure also provides a computer program product, including computer programs/instructions, which, when executed by a processor, implement the component debugging method according to the embodiments of the present disclosure.
The embodiments of the present disclosure also provides a computer program, and the computer program includes program codes which, when executed by a computer, cause the computer to implement the component debugging method according to the embodiments of the present disclosure.
In addition, an embodiment of the present disclosure also provides a component debugging device, as shown in
a processor 601, a memory 602, an input device 603 and an output device 604. The number of processors 601 in the component debugging device can be one or more, and one processor is shown as an example in
The memory 602 can be used to store software programs and modules, and the processor 601 executes various functional applications and data processing of the component debugging device by running the software programs and modules stored in the memory 602. The memory 602 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, application programs required by at least one function, and the like. In addition, the memory 602 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk memory device, flash memory device, or other volatile solid-state memory devices. The input device 603 can be used to receive input digital or character information, and generate signal input related to user settings and function control for the component debugging device.
Specifically, in this embodiment, the processor 601 will load executable files corresponding to the processes of one or more application programs into the memory 602, and the processor 601 will run the application programs stored in the memory 602, so that various functions of the above-mentioned component debugging device can be implemented.
It should be noted that in this paper, relational terms such as “first” and “second” are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there exists any such actual relationship or order between these entities or operations. Moreover, the terms “include”, “comprise” or any other variation thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article or device. Without further restrictions, an element defined by the phrase “including one” does not exclude the existence of other identical elements in the process, method, article or device including the element.
What has been described above is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or realize the present disclosure. Many modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but can be accorded the widest scope consistent with the principles and novel features disclosed herein.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202110772731.8 | Jul 2021 | CN | national |
This application is a national stage of International Application No. PCT/CN2022/091022, filed on May 5, 2022, which claims the priority of a Chinese patent application No. 202110772731.8 filed in China Patent Office on Jul. 8, 2021, both of the aforementioned applications are hereby incorporated by reference in their entireties.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2022/091022 | 5/5/2022 | WO |
