WO2018149190A1 - 组件调试方法、装置、设备和计算机可读存储介质 - Google Patents

组件调试方法、装置、设备和计算机可读存储介质 Download PDF

Info

Publication number
WO2018149190A1
WO2018149190A1 PCT/CN2017/111886 CN2017111886W WO2018149190A1 WO 2018149190 A1 WO2018149190 A1 WO 2018149190A1 CN 2017111886 W CN2017111886 W CN 2017111886W WO 2018149190 A1 WO2018149190 A1 WO 2018149190A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
debugging
debug
browser
instruction
Prior art date
Application number
PCT/CN2017/111886
Other languages
English (en)
French (fr)
Inventor
钟大康
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2018149190A1 publication Critical patent/WO2018149190A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/362—Software debugging
    • G06F11/3648—Software debugging using additional hardware
    • G06F11/3656—Software debugging using additional hardware using a specific debug interface

Definitions

  • the present application relates to the field of computer technology, and in particular, to a component debugging method, apparatus, device, and computer readable storage medium.
  • Traditional component debugging is generally implemented in a mobile terminal with an IOS operating system or an Android operating system.
  • the debugging process needs to be connected to a mobile terminal. If the mobile terminal is not connected, debugging cannot be performed, and the limitation of component debugging is large; Moreover, when the component is debugged in the mobile terminal, the visual operation process cannot be presented, and the user cannot intuitively understand the debugging situation, which leads to inaccurate and intelligent debugging of the component.
  • the main purpose of the present application is to provide a component debugging method, device, device and computer readable storage medium, which are intended to solve the existing component debugging mode, the limitation of component debugging is large, and the component debugging is not accurate and intelligent. technical problem.
  • the present application provides a component debugging method, which is applied to a browser, where the browser is installed with a debugging plug-in, and the component debugging method includes:
  • the present application further provides a component debugging apparatus, which is applied to a browser, where the browser is installed with a debugging plug-in, and the component debugging apparatus includes:
  • a determining module configured to determine, according to the component debugging instruction, a component to be debugged corresponding to the debugging instruction
  • a debugging module configured to perform a debugging operation on the component to be debugged on a preset page of the browser based on the API of the call.
  • the present application further provides a component debugging device, which includes a processor and a memory storing a component debugging program; the processor is configured to execute the component debugging program to implement as above The steps of the component debugging method described.
  • the present application further provides a computer readable storage medium storing a component debugger, the component debugger being executed by a processor to implement a component as described above The steps of the debugging method.
  • the component debugging method proposed in the application is applied to a browser, and when receiving a component debugging instruction, first determining a component to be debugged corresponding to the debugging instruction, and then calling the browser API by using the debugging plugin installed Finally, based on the called API, a debugging operation is performed on the component to be debugged on a preset page of the browser.
  • the component debugging can be implemented in the preset page of the browser, and the debugging of the component can be performed even if the mobile terminal is not connected, and the debugging of the component is more convenient.
  • the debugging process can be displayed in the preset page, which is convenient for intuitively understanding the debugging situation, and the debugging of the component is more accurate and intelligent.
  • FIG. 1 is a schematic flow chart of a first embodiment of a component debugging method according to the present application
  • FIG. 2 is a schematic diagram of a first refinement process of step S10 in FIG. 1;
  • step S10 in FIG. 1 is a schematic diagram of a second refinement process of step S10 in FIG. 1;
  • FIG. 4 is a schematic flow chart of a second embodiment of a component debugging method according to the present application.
  • FIG. 5 is a schematic flowchart diagram of a third embodiment of a component debugging method according to the present application
  • FIG. 6 is a schematic diagram of functional modules of a first embodiment of a component debugging apparatus of the present application
  • FIG. 7 is a schematic diagram of a first refinement function module of the determination module 10 of FIG. 6;
  • FIG. 8 is a schematic diagram of a second refinement function module of the determination module 10 of FIG. 6;
  • FIG. 9 is a schematic diagram of functional modules of a second embodiment of a component debugging apparatus of the present application.
  • FIG. 10 is a schematic diagram of functional modules of a third embodiment of a component debugging apparatus of the present application.
  • FIG. 11 is a schematic structural diagram of a device in a hardware operating environment according to an embodiment of the present application.
  • the solution of the embodiment of the present application is: when receiving the component debugging instruction, determining the component to be debugged corresponding to the debugging instruction; and calling the browser application interface API (Application) by using the debugging plugin installed Programming Interface, an application programming interface); performing a debugging operation on the component to be debugged on a preset page of the browser based on the API of the call.
  • the limitation of component debugging is large, and the component debugging is not accurate and intelligent.
  • the debugging of the prior art components requires not only the connection of the mobile terminal but also the debugging of the component, and the debugging process is not visible; and, in the debugging process, if the debugging data is to be modified, the original installation package is also required to be original. The code is modified to regenerate the installation package, and then compile and load the installation package, which takes a long time, resulting in lower debugging efficiency of the component.
  • the present application provides a component debugging method.
  • FIG. 1 is a schematic flowchart of a first embodiment of a component debugging method according to the present application.
  • the component debugging method is applied to a browser, and the browser is installed with a debugging plug-in, and the component debugging method includes:
  • the preset page performs a debugging operation on the component to be debugged.
  • the debugging plug-in is first installed in the browser, and the type of the browser is not limited, and may be a browser using a traditional IE kernel, such as an IE browser, a TT browser, or a dual-core CPU.
  • Browsers such as the QQ high-speed browser, Sogou high-speed browser, can also be a Google Chrome browser using Chromium (the engine behind Google Chrome) and so on. Since the Google browser supports the javascript, the Html5, and the like, the rendering page is fast. Therefore, in this embodiment, the browser may preferably be a Google browser.
  • Installing the debugging plug-in in the browser is actually adding a debugging plug-in program in the browser, and the debugging plug-in program is written according to the actual situation, which is not limited herein, so as to be subsequently called based on the debugging plug-in program.
  • the API of the browser is actually adding a debugging plug-in program in the browser, and the debugging plug-in program is written according to the actual situation, which is not limited herein, so as to be subsequently called based on the debugging plug-in program.
  • the API of the browser is actually adding a debugging plug-in program in the browser, and the debugging plug-in program is written according to the actual situation, which is not limited herein, so as to be subsequently called based on the debugging plug-in program.
  • the components include, but are not limited to, the Hybird component, the Activity component, and the Service component.
  • the Hybird component is preferably taken as an example for explanation. It should be noted that there is only one debug plugin in this embodiment, but the component contains multiple.
  • Step S10 when receiving the component debugging instruction, determining a component to be debugged corresponding to the debugging instruction;
  • the receiving manner of the component debugging instruction includes: displaying a preset page of the browser first, and then displaying a component debugging control in the preset page, and receiving a click based on the component debugging control When an operation or touch operation is performed, confirm that the component debug command is received.
  • the preset page is preferably H5 (ie, HTML5, Hyper).
  • the Text Markup Language 5, 5th Generation Hypertext Markup Language page, where the default page is to be exemplified, is explained by taking the H5 page as an example.
  • the component to be debugged corresponding to the debugging instruction is further determined.
  • the implementation manner of the step S10 includes:
  • Method 1 referring to FIG. 2, the step S10 includes:
  • Step S11 when receiving the component debugging instruction, determining whether a component is selected in the preset debugger;
  • step S12 if a component is selected in the debugger, the selected component is used as a component to be debugged corresponding to the debugging instruction.
  • a component when receiving the component debugging instruction, it is first determined whether a component is selected in the debugger associated with the browser. It can be understood that the user can check the component in the debugger in advance, specifically: display each component option in the debugger, and when the user selects the corresponding component based on each component option displayed by the debugger, the selected component can be selected.
  • the component acts as a component to be debugged. If a component is selected in the debugger in advance, the selected component can be directly used as the component to be debugged corresponding to the debug instruction.
  • the user selects a component in the debugger in advance, it is equivalent to debugging the selected component, and then, when receiving the debug command, performs a debugging operation based on the previously selected component.
  • the component when the component is checked, it can be set according to actual needs.
  • Step S10 further includes:
  • Step S13 if the component is not selected in the debugger, the component selection window is displayed in the debugging interface of the debug plugin;
  • Step S14 the component selected by the outside world based on the component selection window is used as the component to be debugged corresponding to the debugging instruction.
  • the component selection window can be directly displayed in the debug interface of the debug plugin, so that the user selects the corresponding component based on the component selection window, and selects the selected component as The component to be debugged.
  • the component selection window may be displayed in the debugging interface of the browser debugging plugin for debugging, and the selected component is selected during debugging.
  • Step S20 calling the browser application interface API by using the debug plugin installed
  • Step S30 performing a debugging operation on the component to be debugged on a preset page of the browser based on the invoked API.
  • the browser application interface API can be invoked through the installed debug plugin, and then based on the invoked API, the preset in the browser.
  • the debugging operation is performed on the component to be debugged in the page.
  • the debugging operations include, but are not limited to, http cross-domain request, modification of current non-domain name cookies, cross-domain setting, or browser pop-up function.
  • the manner of determining the component to be debugged includes two types, one is to select a component in the debugger, and the other is to select a component in the debug interface of the debug plugin. Therefore, the preset page in the browser is There are also two types of debugging operations performed on the component to be debugged:
  • One is to capture the function corresponding to the selected component from the debugger. If the corresponding function is selected in the selected component, the component to be debugged may be directly on the preset page of the browser.
  • the debugging operation corresponding to the selected function is performed. For example, if the function selected in advance is an http cross-domain request, the http cross-domain request operation is performed on the component to be debugged on the preset page of the browser.
  • the second is to capture the function corresponding to the selected component from the debugging interface of the debugging plug-in. If the corresponding function is selected in the selected component in advance, the to-be-tuned can be directly performed on the preset page of the browser.
  • the component performs the debugging operation corresponding to the selected function. For example, if the function selected in advance is the http cross-domain request, the http cross-domain request operation is performed on the component to be debugged on the preset page of the browser.
  • the data in the selected component can be changed later, and the data fed back to the H5 page for debugging is also different. If the component is not checked, the data in the component is not subsequently performed. Change, directly feed the raw data of the component to the H5 page for debugging.
  • the Native environment is simulated, and the Hybird component successfully performs a debugging operation on the H5 page of the browser to implement various debugging functions, which facilitates development and debugging, and is performed by debugging the plug-in.
  • Visual debugging makes component debugging more accurate. Even if there is no mobile terminal, you can run the Hybird project directly on the browser and develop debugging.
  • the component debugging method in the embodiment is applied to a browser, and when receiving the component debugging instruction, first determining a component to be debugged corresponding to the debugging instruction, and then calling the browser through the installed debugging plugin.
  • the API based on the called API, performs a debugging operation on the component to be debugged on a preset page of the browser.
  • Implementing the debugging plug-in calling API based on the installation in the browser the component debugging can be implemented in the preset page of the browser, and the debugging of the component can be performed even if the mobile terminal is not connected, and the debugging of the component is more convenient. And the debugging process can be displayed in the preset page, which is convenient for intuitively understanding the debugging situation, and the debugging of the component is more accurate and intelligent.
  • the component debugging method further includes:
  • Step S40 when receiving the debug data update instruction of the component, displaying a debug interface of the debug plugin, so that the outside world updates the debug data of the component in the debug interface;
  • Step S50 Acquire debug data updated based on the debugging interface.
  • Step S60 transmitting the updated debug data to the preset page of the browser, to perform a debugging operation based on the updated debug data in the preset page.
  • step S40 to step S60 in this embodiment may be an operation performed after step S30, that is, after performing the debugging operation, the debugging data of the component is updated and re-commissioned; of course, it may also be in step S30.
  • the debugging data of the component is updated to implement the debugging operation.
  • the specific manner is determined according to the actual situation, and is not limited herein.
  • the debug interface of the debug plugin is first displayed in the browser.
  • the debugging interface of the debugging plug-in and the preset page of the browser are two mutually independent pages, and the H5 page is a front-end page of the browser, and the debugging page of the debugging plug-in It is a page displayed on the upper layer of the H5 page and is not covered by the H5 page.
  • the debugging interface is also a different interface from the component selection window described above, and the component selection window is equivalent to a sub-window of the debugging interface.
  • the first embodiment uses the data already in the system for debugging, so there is no need to display the interface.
  • the debugging interface corresponding to the debugging plug-in is displayed, so that the user updates the debugging data of the component in the debugging interface, where the debugging data refers to the debugging process of the component.
  • the data involved after detecting that the user inputs the updated debug data based on the debug interface, acquiring debug data updated by the user based on the debug interface, and transmitting the updated debug data to the browser Presetting a page to perform a debugging operation based on the updated debug data in the preset page.
  • a big difference between the present application and the prior art is that when the data is updated, the user can directly input data for updating in the debugging interface, and the original data in the installation package is not updated, so that the data updating manner is more convenient.
  • This implementation is equivalent to directly skipping the steps of compiling the installation package by Android and IOS operating system, directly seeing the page effect, dynamically modifying the data in the debugging page of the debugging plug-in, without changing the original code, improving the working efficiency of debugging.
  • a third embodiment of the component debugging method of the present application is proposed based on the first or second embodiment.
  • the component The debugging method also includes:
  • Step S70 setting a communication mechanism to the preset page of the browser
  • Step S80 setting the debug plugin of the browser as a communication object.
  • the debugging of the component is performed in the browser, and before the debugging of the component, the communication mechanism is set to the preset page of the browser, which specifically includes:
  • the preset page is bound to the debugging plug-in; of course, if the component is to be debugged according to the Android and IOS operating systems of the mobile terminal, the preset page of the browser needs to be performed with the operating system of the mobile terminal. Bind.
  • the debug plugin of the browser is set as the communication object.
  • the communication target is the operating system of the mobile terminal
  • the communication connection relationship between the preset page and the Native interface of the operating system is established, that is, the operating system of the mobile terminal is set as the communication object.
  • a communication mechanism is set on the preset page of the browser, and then the component can be debugged based on the set communication mechanism, so that the debugging of the component is very convenient.
  • the above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the application further provides a component debugging device.
  • FIG. 6 is a schematic diagram of functional modules of a first embodiment of a component debugging apparatus 100 of the present application.
  • the functional block diagram shown in FIG. 6 is merely an exemplary diagram of a preferred embodiment, and those skilled in the art will surround the functional modules of the component debugging apparatus 100 shown in FIG.
  • the function modules of the present application can be easily supplemented by the new function modules.
  • the core is the function that each functional module of the defined name has to achieve.
  • the component debugging device is applied to a browser, and the browser is installed with a debugging plug-in, and the component debugging device includes:
  • the determining module 10 is configured to determine, when the component debugging instruction is received, the component to be debugged corresponding to the debugging instruction;
  • the calling module 20 is configured to invoke an application interface API of the browser by using the debug plugin installed;
  • the debugging module 30 is configured to perform a debugging operation on the component to be debugged on a preset page of the browser based on the API that is invoked.
  • the debugging plug-in is first installed in the browser, and the type of the browser is not limited, and may be a browser using a traditional IE kernel, such as an IE browser, a TT browser, or a dual-core CPU.
  • Browsers such as the QQ high-speed browser, Sogou high-speed browser, can also be a Google Chrome browser using Chromium (the engine behind Google Chrome) and so on. Since the Google browser supports the javascript, the Html5, and the like, the rendering page is fast. Therefore, in this embodiment, the browser may preferably be a Google browser.
  • Installing the debugging plug-in in the browser is actually adding a debugging plug-in program in the browser, and the debugging plug-in program is written according to the actual situation, which is not limited herein, so as to be subsequently called based on the debugging plug-in program.
  • the API of the browser is actually adding a debugging plug-in program in the browser, and the debugging plug-in program is written according to the actual situation, which is not limited herein, so as to be subsequently called based on the debugging plug-in program.
  • the API of the browser is actually adding a debugging plug-in program in the browser, and the debugging plug-in program is written according to the actual situation, which is not limited herein, so as to be subsequently called based on the debugging plug-in program.
  • the components include, but are not limited to, the Hybird component, the Activity component, and the Service component.
  • the Hybird component is preferably taken as an example for explanation. It should be noted that there is only one debug plugin in this embodiment, but the component contains multiple.
  • the determining module 10 is configured to determine, when the component debugging instruction is received, the component to be debugged corresponding to the debugging instruction;
  • the receiving manner of the component debugging instruction includes: displaying a preset page of the browser first, and then displaying a component debugging control in the preset page, and receiving a click based on the component debugging control
  • the determining module 10 confirms receipt of the component debug command upon operation or touch operation.
  • the preset page is preferably H5 (HTML5, Hyper) Text Markup Language 5, the 5th generation hypertext markup language page, where the example of the preset page is required, is explained by taking the H5 page as an example.
  • the determining module 10 When the component debugging instruction is received, the determining module 10 further determines the component to be debugged corresponding to the debugging instruction. Specifically, the implementation manner of the determining module 10 includes:
  • Method 1 Referring to FIG. 7, the determining module 10 includes:
  • the determining unit 11 is configured to determine, when the component debugging instruction is received, whether a component is selected in the preset debugger;
  • the determining unit 12 is configured to: if the component is selected in the debugger, use the checked component as the component to be debugged corresponding to the debugging instruction.
  • the determining unit 11 upon receiving the component debug command, the determining unit 11 first determines whether a component is selected in the debugger associated with the browser. It can be understood that the user can check the component in the debugger in advance, specifically: display each component option in the debugger, and when the user selects the corresponding component based on each component option displayed by the debugger, the selected component can be selected. The component acts as a component to be debugged. If the component is checked in the debugger in advance, the determining unit 12 can directly use the selected component as the component to be debugged corresponding to the debugging instruction.
  • the user selects a component in the debugger in advance, it is equivalent to debugging the selected component, and then, when receiving the debug command, performs a debugging operation based on the previously selected component.
  • the component when the component is checked, it can be set according to actual needs.
  • Method 2 Referring to FIG. 8, the determining module 10 further includes:
  • a display unit 13 is configured to display a component selection window in a debugging interface of the debug plugin if the component is not selected in the debugger;
  • the determining unit 12 is further configured to use a component selected by the outside world based on the component selection window as a component to be debugged corresponding to the debugging instruction.
  • the display unit 13 can directly display the component selection window in the debug interface of the debug plugin, so that the user selects the corresponding component based on the component selection window, and the The determining unit 12 regards the selected component as a component to be debugged.
  • the component selection window may be displayed in the debugging interface of the browser debugging plugin for debugging, and the selected component is selected during debugging.
  • the calling module 20 is configured to invoke an application interface API of the browser by using the debug plugin installed;
  • the debugging module 30 is configured to perform a debugging operation on the component to be debugged on a preset page of the browser based on the invoked API.
  • the calling module 20 may invoke the application interface API of the browser through the installed debugging plugin, and then the debugging module 30 is based on the invoked
  • the API performs a debugging operation on the component to be debugged in a preset page of the browser.
  • the debugging operations include, but are not limited to, http cross-domain request, modification of current non-domain name cookies, cross-domain setting, or browser pop-up function.
  • the manner of determining the component to be debugged includes two types, one is to select a component in the debugger, and the other is to select a component in a debug interface of the debug plugin. Therefore, the debug module 30 is in the browser.
  • the preset page also performs two debugging operations on the component to be debugged:
  • the debugging operation corresponding to the selected function is performed. For example, if the function selected in advance is an http cross-domain request, the http cross-domain request operation is performed on the component to be debugged on the preset page of the browser.
  • the functions of the component to be debugged may be sequentially executed in a preset order.
  • the second is to capture the function corresponding to the selected component from the debugging interface of the debugging plug-in. If the corresponding function is selected in the selected component in advance, the to-be-tuned can be directly performed on the preset page of the browser.
  • the component performs the debugging operation corresponding to the selected function. For example, if the function selected in advance is the http cross-domain request, the http cross-domain request operation is performed on the component to be debugged on the preset page of the browser. Similarly, if the function is not selected in advance, the functions of the component to be debugged can be sequentially executed in a preset order.
  • the data in the selected component can be changed later, and the data fed back to the H5 page for debugging is also different. If the component is not checked, the data in the component is not subsequently performed. Change, directly feed the raw data of the component to the H5 page for debugging.
  • the Native environment is simulated, and the Hybird component successfully performs a debugging operation on the H5 page of the browser to implement various debugging functions, which facilitates development and debugging, and is performed by debugging the plug-in.
  • Visual debugging makes component debugging more accurate. Even if there is no mobile terminal, you can run the Hybird project directly on the browser and develop debugging.
  • the component debugging apparatus 100 of the present embodiment is applied to a browser, and when receiving a component debugging instruction, first determines a component to be debugged corresponding to the debugging instruction, and then invokes the browser through the installed debugging plugin.
  • the API and finally, based on the called API, performs a debugging operation on the component to be debugged on a preset page of the browser.
  • Implementing the debugging plug-in calling API based on the installation in the browser the component debugging can be implemented in the preset page of the browser, and the debugging of the component can be performed even if the mobile terminal is not connected, and the debugging of the component is more convenient. And the debugging process can be displayed in the preset page, which is convenient for intuitively understanding the debugging situation, and the debugging of the component is more accurate and intelligent.
  • the component debugging device further includes:
  • the display module 40 is configured to: when receiving the debug data update instruction of the component, display a debug interface of the debug plugin, so that the outside world updates the debug data of the component in the debug interface;
  • the obtaining module 50 is configured to obtain debugging data updated based on the debugging interface
  • the transmission module 60 is configured to transmit the updated debug data to the preset page of the browser to perform a debugging operation based on the updated debug data in the preset page.
  • the operations performed by the display module 40 to the transmission module 60 in this embodiment may be operations performed after the debugging module 30, that is, after the debugging operation is performed, the debugging data of the component is updated and re-commissioned; It may also be an operation performed during the debugging operation performed by the debugging module 30, that is, during the debugging operation, the debugging data of the component is updated to implement the debugging operation, and the specific manner is determined according to the actual situation, and is not Make a limit.
  • the display module 40 first displays the debug interface of the debug plugin in the browser.
  • the debugging interface of the debugging plug-in and the preset page of the browser are two mutually independent pages, and the H5 page is a front-end page of the browser, and the debugging page of the debugging plug-in It is a page displayed on the upper layer of the H5 page and is not covered by the H5 page.
  • the debugging interface is also a different interface from the component selection window described above, and the component selection window is equivalent to a sub-window of the debugging interface.
  • the first embodiment uses the data already in the system for debugging, so there is no need to display the interface.
  • the display module 40 displays the debugging interface corresponding to the debugging plug-in, so that the user updates the debugging data of the component in the debugging interface, where the debugging data refers to
  • the transmission module 60 acquires the debugging data updated by the user based on the debugging interface, and transmits the updated debugging data to the The preset page of the browser performs a debugging operation based on the updated debug data in the preset page.
  • a big difference between the present application and the prior art is that when the data is updated, the user can directly input data for updating in the debugging interface, and the original data in the installation package is not updated, so that the data updating manner is more convenient.
  • This implementation is equivalent to directly skipping the steps of compiling the installation package by Android and IOS operating system, directly seeing the page effect, dynamically modifying the data in the debugging page of the debugging plug-in, without changing the original code, improving the working efficiency of debugging.
  • the component debugging device further includes:
  • a setting module 70 configured to set a communication mechanism to the preset page of the browser
  • the setting module 70 is further configured to set the debug plugin of the browser as a communication object.
  • the setting module 70 sets a communication mechanism to the preset page of the browser, which specifically includes:
  • the preset page of the browser is bound to the debugging plug-in; of course, if the component is to be debugged according to the Android and IOS operating systems of the mobile terminal, the preset page of the browser needs to be combined with the mobile terminal.
  • the operating system is bound.
  • the setting module 70 sets the debug plugin of the browser as a communication object.
  • the communication target is the operating system of the mobile terminal
  • the communication connection relationship between the preset page and the Native interface of the operating system is established, that is, the operating system of the mobile terminal is set as the communication object.
  • a communication mechanism is set on the preset page of the browser, and then the component can be debugged based on the set communication mechanism, so that the debugging of the component is very convenient.
  • the above determining module 10, the calling module 20, the debugging module 30, and the like may be embedded in or independent of the component debugging device in hardware, or may be stored in software in the memory of the component debugging device.
  • the processor can be a central processing unit (CPU), a microprocessor, a microcontroller, or the like.
  • FIG. 11 is a schematic structural diagram of a device in a hardware operating environment according to an embodiment of the present application.
  • the component debugging device in the embodiment of the present application may be a PC, or may be a terminal device having a display function, such as a smart phone, a tablet computer, or a portable computer.
  • the component debugging device may include a processor 1001, such as a CPU, a network interface 1002, a user interface 1003, and a memory 1004. Connection communication between these components can be achieved via a communication bus.
  • the network interface 1002 may optionally include a standard wired interface (for connecting to a wired network), a wireless interface (such as a WI-FI interface, a Bluetooth interface, an infrared interface, etc. for connecting to a wireless network).
  • the user interface 1003 may include a display, an input unit such as a keyboard, and the optional user interface 1003 may also include a standard wired interface (eg, for connecting a wired keyboard, a wired mouse, etc.), a wireless interface (eg, for Connect a wireless keyboard, wireless mouse).
  • the memory 1004 may be a high speed RAM memory or a stable memory (non-volatile) Memory), such as disk storage.
  • the memory 1004 can also optionally be a storage device independent of the aforementioned processor 1001.
  • the component debugging device may further include a camera, RF (Radio) Frequency, RF) circuits, sensors, audio circuits, WiFi modules, and more.
  • RF Radio
  • RF Radio
  • component debugging device structure shown in FIG. 11 does not constitute a limitation of the component debugging device, and may include more or less components than those illustrated, or combine some components, or different components. Arrangement.
  • an operating system may be included in the memory 1004 as a computer storage medium.
  • the operating system is a program for managing and controlling components to debug device hardware and software resources, and supports operation of a network communication module, a user interface module, a component debugger, and other programs or software;
  • the network communication module is used to manage and control the network interface 1002;
  • the user interface module is used to manage and control the user interface 1003.
  • the processor 1001 can be used to execute a component debugger stored in the memory 1004 to implement the steps of the component debug method as described above.
  • the application provides a computer readable storage medium storing a component debugger that is executed by a processor to implement the steps of the component debug method as described above.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

一种组件调试方法以及一种组件调试装置、设备和计算机可读存储介质，应用于浏览器中，所述浏览器安装有调试插件，所述组件调试方法包括：在接收到组件调试指令时，确定所述调试指令对应的待调试组件（S10）；通过安装的所述调试插件，调用所述浏览器的应用程序接口API（S20）；基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作（S30）。在浏览器中基于安装的调试插件调用API，即可在所述浏览器的预设页面中实现组件的调试，对组件的调试更加方便，并且调试过程可在所述预设页面中显示，以便于直观了解调试的情况，对组件的调试更加准确和智能。

Description

组件调试方法、装置、设备和计算机可读存储介质
本申请要求于2017年02月20日提交中国专利局、申请号为201710091768.8、发明名称为“组件调试方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种组件调试方法、装置、设备和计算机可读存储介质。
背景技术
传统的组件调试，一般是在安装IOS操作系统或Android操作系统的移动终端中实现调试，该调试过程需要连接移动终端，若是没有连接移动终端，则无法进行调试，组件调试的局限性较大；并且，在移动终端中进行组件的调试时，无法呈现可视化操作过程，用户无法直观了解调试的情况，导致组件的调试不够准确和智能。
发明内容
本申请的主要目的在于提供一种组件调试方法、装置、设备和计算机可读存储介质，旨在解决现有的组件调试方式，组件调试的局限性较大，并且组件的调试不够准确和智能的技术问题。
为实现上述目的，本申请提供一种组件调试方法，应用于浏览器中，所述浏览器安装有调试插件，所述组件调试方法包括：
在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
此外，为实现上述目的，本申请还提供一种组件调试装置，应用于浏览器中，所述浏览器安装有调试插件，所述组件调试装置包括：
确定模块，用于在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
调用模块，用于通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
调试模块，用于基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
此外，为实现上述目的，本申请还提供一种组件调试设备，所述组件调试设备包括处理器以及存储有组件调试程序的存储器；所述处理器用于执行所述组件调试程序，以实现如上文所述的组件调试方法的步骤。
此外，为实现上述目的，本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有组件调试程序，所述组件调试程序被处理器执行，以实现如上文所述的组件调试方法的步骤。
本申请提出的组件调试方法，应用于浏览器中，在接收到组件调试指令时，先确定所述调试指令对应的待调试组件，然后通过安装的所述调试插件，调用所述浏览器的API，最终基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。实现了在浏览器中基于安装的调试插件调用API，即可在所述浏览器的预设页面中实现组件的调试，即使不连接移动终端，也可进行组件的调试，对组件的调试更加方便，并且调试过程可在所述预设页面中显示，便于直观了解调试的情况，对组件的调试更加准确和智能。
附图说明
图1为本申请组件调试方法第一实施例的流程示意图；
图2为图1中步骤S10的第一细化流程示意图；
图3为图1中步骤S10的第二细化流程示意图；
图4为本申请组件调试方法第二实施例的流程示意图；
图5为本申请组件调试方法第三实施例的流程示意图
图6为本申请组件调试装置第一实施例的功能模块示意图；
图7为图6中确定模块10的第一细化功能模块示意图；
图8为图6中确定模块10的第二细化功能模块示意图；
图9为本申请组件调试装置第二实施例的功能模块示意图；
图10为本申请组件调试装置第三实施例的功能模块示意图；
图11是本申请实施例方案涉及的硬件运行环境的设备结构示意图。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请实施例的解决方案主要是：在接收到组件调试指令时，确定所述调试指令对应的待调试组件；通过安装的所述调试插件，调用所述浏览器的应用程序接口API（Application Programming Interface，应用程序编程接口）；基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。以解决了现有的组件调试，对组件调试的局限性较大，且组件调试不够准确智能的问题。
应当注意的是，现有技术的组件调试，不仅要连接移动终端才能实现组件的调试，以及调试过程不可视；而且，在调试过程中，若是要修改调试数据，还需要对原始安装包的原始代码进行修改，以重新生成安装包，再对安装包进行编译和加载，花费的时间较长，导致组件的调试效率较低。
正是由于现有技术中，通过移动终端进行组件调试的方式，存在许多缺陷，因此，考虑将组件调试转移到浏览器中进行调试。
但是，现有的组件在浏览器中进行调试时，由于组件脱离Native环境（即Android和IOS操作系统环境），在安全性和能力有限的情况下，只能在浏览器中输入脚本程序代码，执行简单的功能。但对于一些高级点的功能，如http（Hyper Text Transfer Protocol，超文本传输协议）跨域请求、修改当前非域名的cookies（一种让网站服务器把少量数据储存到客户端的硬盘或内存，或是从客户端的硬盘读取数据的一种技术，在计算机上以小文本文件存储信息）、跨域设置，或者是实现浏览器的弹窗功能等等，由于组件内部没有调试代码，无法调用到浏览器的API，导致无法实现，即如果使用的是模拟native环境的纯JS（JavaScript，直译式脚本语言）脚本，由于安全性问题和能力有限导致无法模拟。
基于现有技术存在的缺陷，本申请提供一种组件调试方法。
参照图1，图1为本申请组件调试方法第一实施例的流程示意图。
在本实施例中，所述组件调试方法应用于浏览器中，所述浏览器安装有调试插件，所述组件调试方法包括：
在接收到组件调试指令时，确定所述调试指令对应的待调试组件；通过安装的所述调试插件，调用所述浏览器的应用程序接口API；基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
在本实施例中，先在浏览器中安装调试插件，所述浏览器的类型不做限定，可以是使用传统IE内核的浏览器，如IE浏览器、TT浏览器，也可以是使用双核CPU的浏览器，如QQ高速浏览器、搜狗高速浏览器，还可以是使用Chromium（谷歌浏览器背后的引擎）内核的谷歌浏览器等等。由于谷歌浏览器对javascript，Html5等的支持都比较好，渲染页面速度快，因此，本实施例中，所述浏览器可优选为谷歌浏览器。在浏览器中安装调试插件，实际上就是在浏览器中添加一个调试插件程序，所述调试插件程序根据实际情况进行编写设置，此处不做限定，以便后续基于所述调试插件程序，调用所述浏览器的API。
在本实施例中，所述组件包括但不限于Hybird组件，Activity组件，Service组件，为更好理解本实施，下文需要进行举例的地方，优选以Hybird组件为例进行解释。值得注意的是，本实施例中的调试插件只有一个，但是组件包含多个。
以下是本实施例中逐步实现组件调试的具体步骤：
步骤S10，在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
在本实施例中，所述组件调试指令的接收方式包括：先显示所述浏览器的预设页面，然后在所述预设页面中显示组件调试控件，接收到基于所述组件调试控件的点击操作或触摸操作时，确认接收到组件调试指令。本实施例中，所述预设页面优选为H5（即HTML5，Hyper Text Markup Language 5，第5代超级文本标记语言）页面，下文需要对预设页面进行举例的地方，均以H5页面为例进行解释。
在接收组件调试指令时，进一步确定所述调试指令对应的待调试组件，具体地，所述步骤S10的实施方式包括：
1）方式一、参照图2，所述步骤S10包括：
步骤S11，在接收到组件调试指令时，判断预设的调试器中是否勾选有组件；
步骤S12，若所述调试器中勾选有组件，则将勾选的组件作为所述调试指令对应的待调试组件。
在本实施方式中，在接收到组件调试指令时，先判断是否在所述浏览器关联的调试器中勾选有组件。可以理解，用户可以事先在所述调试器中勾选组件，具体地：调试器中显示各个组件选项，当用户基于所述调试器显示的各个组件选项选择相应的组件时，即可将选择的组件作为待续的待调试组件。若事先在所述调试器中勾选有组件，则可直接将勾选的组件作为所述调试指令对应的待调试组件。
在本实施方式中，若用户事先在调试器中勾选组件，相当于是针对勾选的所述组件进行调试，后续即可在接收到调试指令时，基于之前勾选的组件执行调试操作。具体在何时进行组件的勾选，可根据实际需要进行设置。
2）方式二、参照图3，所述步骤S12之后，所述步骤S10还包括：
步骤S13，若所述调试器中未勾选组件，则在所述调试插件的调试界面中显示组件选择窗口；
步骤S14，将外界基于所述组件选择窗口选择的组件，作为所述调试指令对应的待调试组件。
当然，若事先未在所述调试器中勾选组件，则可直接在调试插件的调试界面中显示组件选择窗口，以供用户基于所述组件选择窗口选择相应的组件，并将选择的组件作为待调试组件。
在本实施方式中，若事先未在调试器中勾选组件，则可在调试时，先在浏览器的调试插件所在调试界面中显示组件选择窗口，以供用户进行选择，并将选择的组件作为待调试组件，即使之前未勾选，也可在当前的情况下选择，提高了待调试组件选择的灵活性。
步骤S20，通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
步骤S30，基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
在本实施例中，在确定待调试组件之后，即可通过安装的所述调试插件，调用所述浏览器的应用程序接口API，然后基于调用的所述API，在所述浏览器的预设页面中对所述待调试组件执行调试操作。其中，所述调试操作包括但不限于：http跨域请求、修改当前非域名的cookies、跨域设置，或者是浏览器的弹窗功能等等。
由于上述确定待调试组件的方式包括两种，一种是在调试器中勾选组件，另一种是在调试插件的调试界面中选择组件，因此，所述在所述浏览器的预设页面对所述待调试组件执行调试操作也同样包括两种：
一是从所述调试器中，捕捉勾选的组件所对应的功能，若事先在勾选的组件中选择相应的功能，则可直接在所述浏览器的预设页面对所述待调试组件执行已选择的功能所对应的调试操作，例如，事先选择的功能是http跨域请求，则在所述浏览器的预设页面对所述待调试组件执行http跨域请求的操作。
二是从所述调试插件的调试界面中，捕捉选择的组件所对应的功能，若事先在选择的组件中选择相应的功能，则可直接在所述浏览器的预设页面对所述待调试组件执行已选择的功能所对应的调试操作，例如，事先选择的功能是http跨域请求，则在所述浏览器的预设页面对所述待调试组件执行http跨域请求的操作。
应当理解，在勾选组件之后，后续才可对勾选的组件中的数据进行更改，最终反馈至H5页面进行调试的数据也有所不同，若是不勾选组件，后续就不对组件中的数据进行更改，就直接将组件的原始数据反馈至H5页面中进行调试。
在本实施例中，相应于是通过安装的调试插件，模拟Native环境，让Hybird组件成功在浏览器的H5页面上执行调试操作，以实现各种调试功能，利于开发调试，并且，通过调试插件进行可视化调试，使得组件调试更加准确，即使缺少移动终端时，也可以直接在浏览器上运行Hybird项目并开发调试。
本实施例提出的组件调试方法，应用于浏览器中，在接收到组件调试指令时，先确定所述调试指令对应的待调试组件，然后通过安装的所述调试插件，调用所述浏览器的API，最终基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。实现了在浏览器中基于安装的调试插件调用API，即可在所述浏览器的预设页面中实现组件的调试，即使不连接移动终端，也可进行组件的调试，对组件的调试更加方便，并且调试过程可在所述预设页面中显示，便于直观了解调试的情况，对组件的调试更加准确和智能。
进一步地，为了提高组件调试的灵活性，基于第一实施例提出本申请组件调试方法的第二实施例，在本实施例中，参照图4，所述组件调试方法还包括：
步骤S40，在接收到组件的调试数据更新指令时，显示所述调试插件的调试界面，以供外界在所述调试界面中更新组件的调试数据；
步骤S50，获取基于所述调试界面更新的调试数据；
步骤S60，将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。
应当注意的是，本实施例中步骤S40至步骤S60可以是在步骤S30之后执行的操作，即执行调试操作之后，对组件的调试数据进行更新并重新调试；当然，也可以是在步骤S30的过程中所执行的操作，即在执行调试操作过程中，对组件的调试数据进行更新以实现调试操作，具体的方式根据实际情况而定，此处不做限定。
在本实施例中，若接收到组件的调试数据更新指令，先在所述浏览器中显示所述调试插件的调试界面。
本实施例中，所述调试插件的调试界面与所述浏览器的预设页面如H5页面是两个相互独立的页面，所述H5页面即浏览器的前端页面，所述调试插件的调试页面是显示在所述H5页面上层的页面，不会被所述H5页面所覆盖。并且，所述调试界面与上述的组件选择窗口也是不同的界面，组件选择窗口相当于是调试界面的一个子窗口。
应当理解，现有的组件调试过程中，由于调试数据在代码文件中写死了，相应于一个调试数据都是生成安装包，每次要更改调试数据，都需要对安装包中的原始代码进行修改，对代码修改之后，会生成新的安装包，再对新的安装包进行编译、加载运行，以重新进行调试，导致组件的调试过程所花费的时长，调试效率较低。
应当理解，第一实施例是采用系统已有的数据进行调试，因此无须显示界面。而在本实施例中，需要更新数据时，显示所述调试插件对应的调试界面，以便用户在所述调试界面中更新组件的调试数据，其中，所述调试数据指的是对组件进行调试过程所涉及到的数据，在检测到用户基于所述调试界面中输入更新的调试数据之后，获取用户基于所述调试界面更新的调试数据，并将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。本申请与现有技术一个较大的不同，就是在更新数据时，可以直接在调试界面中让用户输入数据进行更新，不用对安装包中的原始数据进行更新，使得数据的更新方式更加便捷。
本实施相当于是直接跳过Android和IOS操作系统编译生成安装包的步骤，直接看到页面效果，在调试插件的调试页面中动态修改数据，不改动原始代码，提高了调试的工作效率。
进一步地，为了提高组件调试的灵活性，基于第一或第二实施例提出本申请组件调试方法的第三实施例，在本实施例中，参照图5，所述步骤S10之前，所述组件调试方法还包括：
步骤S70，对所述浏览器的所述预设页面设置通信机制；
步骤S80，将所述浏览器的调试插件设置为通信对象。
在本实施例中，要实现在浏览器中进行组件的调试，则在进行组件的调试之前，先对所述浏览器的所述预设页面设置通信机制，具体包括：将所述浏览器的所述预设页面与调试插件进行绑定；当然，若是要根据移动终端的Android和IOS操作系统进行组件的调试，则需要将所述浏览器的所述预设页面与移动终端的操作系统进行绑定。
由于本实施例主要是针对浏览器，因此，在设置好通信机制之后，将所述浏览器的调试插件设置为通信对象。当然，若待通信对象是移动终端的操作系统，则建立所述预设页面与所述操作系统的Native接口的通信连接关系，即将移动终端的操作系统设置为通信对象。
在本实施例中，在进行组件的调试之前，先对所述浏览器的所述预设页面设置通信机制，后续即可基于设置好的通信机制，进行组件的调试，使得组件的调试非常便捷。
需要说明的是，本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
本申请进一步提供一种组件调试装置。
参照图6，图6为本申请组件调试装置100第一实施例的功能模块示意图。
需要强调的是，对本领域的技术人员来说，图6所示功能模块图仅仅是一个较佳实施例的示例图，本领域的技术人员围绕图6所示的组件调试装置100的功能模块，可轻易进行新的功能模块的补充；各功能模块的名称是自定义名称，仅用于辅助理解该组件调试装置100的各个程序功能块，不用于限定本申请的技术方案，本申请技术方案的核心是，各自定义名称的功能模块所要达成的功能。
在本实施例中，所述组件调试装置应用于浏览器中，所述浏览器安装有调试插件，所述组件调试装置包括：
确定模块10，用于在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
调用模块20，用于通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
调试模块30，用于基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
在本实施例中，先在浏览器中安装调试插件，所述浏览器的类型不做限定，可以是使用传统IE内核的浏览器，如IE浏览器、TT浏览器，也可以是使用双核CPU的浏览器，如QQ高速浏览器、搜狗高速浏览器，还可以是使用Chromium（谷歌浏览器背后的引擎）内核的谷歌浏览器等等。由于谷歌浏览器对javascript，Html5等的支持都比较好，渲染页面速度快，因此，本实施例中，所述浏览器可优选为谷歌浏览器。在浏览器中安装调试插件，实际上就是在浏览器中添加一个调试插件程序，所述调试插件程序根据实际情况进行编写设置，此处不做限定，以便后续基于所述调试插件程序，调用所述浏览器的API。
在本实施例中，所述组件包括但不限于Hybird组件，Activity组件，Service组件，为更好理解本实施，下文需要进行举例的地方，优选以Hybird组件为例进行解释。值得注意的是，本实施例中的调试插件只有一个，但是组件包含多个。
以下是本实施例中逐步实现组件调试的各个模块的具体描述：
其中，所述确定模块10，用于在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
在本实施例中，所述组件调试指令的接收方式包括：先显示所述浏览器的预设页面，然后在所述预设页面中显示组件调试控件，接收到基于所述组件调试控件的点击操作或触摸操作时，所述确定模块10确认接收到组件调试指令。本实施例中，所述预设页面优选为H5（HTML5，Hyper Text Markup Language 5，即第5代超级文本标记语言）页面，下文需要对预设页面进行举例的地方，均以H5页面为例进行解释。
在接收组件调试指令时，所述确定模块10进一步确定所述调试指令对应的待调试组件，具体地，所述确定模块10的实施方式包括：
1）方式一、参照图7，所述确定模块10包括：
判断单元11，用于在接收到组件调试指令时，判断预设的调试器中是否勾选有组件；
确定单元12，用于若所述调试器中勾选有组件，则将勾选的组件作为所述调试指令对应的待调试组件。
在本实施方式中，在接收到组件调试指令时，判断单元11先判断是否在所述浏览器关联的调试器中勾选有组件。可以理解，用户可以事先在所述调试器中勾选组件，具体地：调试器中显示各个组件选项，当用户基于所述调试器显示的各个组件选项选择相应的组件时，即可将选择的组件作为待续的待调试组件。若事先在所述调试器中勾选有组件，则确定单元12可直接将勾选的组件作为所述调试指令对应的待调试组件。
在本实施方式中，若用户事先在调试器中勾选组件，相当于是针对勾选的所述组件进行调试，后续即可在接收到调试指令时，基于之前勾选的组件执行调试操作。具体在何时进行组件的勾选，可根据实际需要进行设置。
2）方式二、参照图8，所述确定模块10还包括：
显示单元13，用于若所述调试器中未勾选组件，则在所述调试插件的调试界面中显示组件选择窗口；
所述确定单元12，还用于将外界基于所述组件选择窗口选择的组件，作为所述调试指令对应的待调试组件。
当然，若事先未在所述调试器中勾选组件，则显示单元13可直接在调试插件的调试界面中显示组件选择窗口，以供用户基于所述组件选择窗口选择相应的组件，并且所述确定单元12将选择的组件作为待调试组件。
在本实施方式中，若事先未在调试器中勾选组件，则可在调试时，先在浏览器的调试插件所在调试界面中显示组件选择窗口，以供用户进行选择，并将选择的组件作为待调试组件，即使之前未勾选，也可在当前的情况下选择，提高了待调试组件选择的灵活性。
其中，所述调用模块20，用于通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
所述调试模块30，用于基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
在本实施例中，在确定待调试组件之后，所述调用模块20即可通过安装的所述调试插件，调用所述浏览器的应用程序接口API，然后所述调试模块30基于调用的所述API，在所述浏览器的预设页面中对所述待调试组件执行调试操作。其中，所述调试操作包括但不限于：http跨域请求、修改当前非域名的cookies、跨域设置，或者是浏览器的弹窗功能等等。
由于上述确定待调试组件的方式包括两种，一种是在调试器中勾选组件，另一种是在调试插件的调试界面中选择组件，因此，所述调试模块30在所述浏览器的预设页面对所述待调试组件执行调试操作也同样包括两种：
一是从所述调试器中，捕捉勾选的组件所对应的功能，若事先在勾选的组件中选择相应的功能，则可直接在所述浏览器的预设页面对所述待调试组件执行已选择的功能所对应的调试操作，例如，事先选择的功能是http跨域请求，则在所述浏览器的预设页面对所述待调试组件执行http跨域请求的操作。当然，若事先未选择功能，则可按照预设顺序，依次执行待调试组件的各个功能。
二是从所述调试插件的调试界面中，捕捉选择的组件所对应的功能，若事先在选择的组件中选择相应的功能，则可直接在所述浏览器的预设页面对所述待调试组件执行已选择的功能所对应的调试操作，例如，事先选择的功能是http跨域请求，则在所述浏览器的预设页面对所述待调试组件执行http跨域请求的操作。同理，若事先未选择功能，可按照预设顺序，依次执行待调试组件的各个功能。
应当理解，在勾选组件之后，后续才可对勾选的组件中的数据进行更改，最终反馈至H5页面进行调试的数据也有所不同，若是不勾选组件，后续就不对组件中的数据进行更改，就直接将组件的原始数据反馈至H5页面中进行调试。
在本实施例中，相应于是通过安装的调试插件，模拟Native环境，让Hybird组件成功在浏览器的H5页面上执行调试操作，以实现各种调试功能，利于开发调试，并且，通过调试插件进行可视化调试，使得组件调试更加准确，即使缺少移动终端时，也可以直接在浏览器上运行Hybird项目并开发调试。
本实施例提出的组件调试装置100，应用于浏览器中，在接收到组件调试指令时，先确定所述调试指令对应的待调试组件，然后通过安装的所述调试插件，调用所述浏览器的API，最终基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。实现了在浏览器中基于安装的调试插件调用API，即可在所述浏览器的预设页面中实现组件的调试，即使不连接移动终端，也可进行组件的调试，对组件的调试更加方便，并且调试过程可在所述预设页面中显示，便于直观了解调试的情况，对组件的调试更加准确和智能。
进一步地，为了提高组件调试的灵活性，基于第一实施例提出本申请组件调试装置的第二实施例，在本实施例中，参照图9，所述组件调试装置还包括：
显示模块40，用于在接收到组件的调试数据更新指令时，显示所述调试插件的调试界面，以供外界在所述调试界面中更新组件的调试数据；
获取模块50，用于获取基于所述调试界面更新的调试数据；
传输模块60，用于将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。
应当注意的是，本实施例中显示模块40至传输模块60所执行的操作可以是在调试模块30之后执行的操作，即执行调试操作之后，对组件的调试数据进行更新并重新调试；当然，也可以是在调试模块30执行调试操作的过程中所执行的操作，即在执行调试操作过程中，对组件的调试数据进行更新以实现调试操作，具体的方式根据实际情况而定，此处不做限定。
在本实施例中，若接收到组件的调试数据更新指令，显示模块40先在所述浏览器中显示所述调试插件的调试界面。
本实施例中，所述调试插件的调试界面与所述浏览器的预设页面如H5页面是两个相互独立的页面，所述H5页面即浏览器的前端页面，所述调试插件的调试页面是显示在所述H5页面上层的页面，不会被所述H5页面所覆盖。并且，所述调试界面与上述的组件选择窗口也是不同的界面，组件选择窗口相当于是调试界面的一个子窗口。
应当理解，现有的组件调试过程中，由于调试数据在代码文件中写死了，相应于一个调试数据都是生成安装包，每次要更改调试数据，都需要对安装包中的原始代码进行修改，对代码修改之后，会生成新的安装包，再对新的安装包进行编译、加载运行，以重新进行调试，导致组件的调试过程所花费的时长，调试效率较低。
应当理解，第一实施例是采用系统已有的数据进行调试，因此无须显示界面。而在本实施例中，需要更新数据时，显示模块40显示所述调试插件对应的调试界面之后，以便用户在所述调试界面中更新组件的调试数据，其中，所述调试数据指的是对组件进行调试过程所涉及到的数据，在检测到用户基于所述调试界面中输入更新的调试数据之后，传输模块60获取用户基于所述调试界面更新的调试数据，并将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。本申请与现有技术一个较大的不同，就是在更新数据时，可以直接在调试界面中让用户输入数据进行更新，不用对安装包中的原始数据进行更新，使得数据的更新方式更加便捷。
本实施相当于是直接跳过Android和IOS操作系统编译生成安装包的步骤，直接看到页面效果，在调试插件的调试页面中动态修改数据，不改动原始代码，提高了调试的工作效率。
进一步地，为了提高组件调试的灵活性，基于第一或第二实施例提出本申请组件调试装置的第三实施例，在本实施例中，参照图10，所述组件调试装置还包括：
设置模块70，用于对所述浏览器的所述预设页面设置通信机制；
所述设置模块70，还用于将所述浏览器的调试插件设置为通信对象。
在本实施例中，要实现在浏览器中进行组件的调试，则在进行组件的调试之前，先由设置模块70对所述浏览器的所述预设页面设置通信机制，具体包括：将所述浏览器的所述预设页面与调试插件进行绑定；当然，若是要根据移动终端的Android和IOS操作系统进行组件的调试，则需要将所述浏览器的所述预设页面与移动终端的操作系统进行绑定。
由于本实施例主要是针对浏览器，因此，在设置好通信机制之后，所述设置模块70将所述浏览器的调试插件设置为通信对象。当然，若待通信对象是移动终端的操作系统，则建立所述预设页面与所述操作系统的Native接口的通信连接关系，即将移动终端的操作系统设置为通信对象。
在本实施例中，在进行组件的调试之前，先对所述浏览器的所述预设页面设置通信机制，后续即可基于设置好的通信机制，进行组件的调试，使得组件的调试非常便捷。
需要说明的是，在硬件实现上，以上确定模块10、调用模块20及调试模块30等可以以硬件形式内嵌于或独立于组件调试装置中，也可以以软件形式存储于组件调试装置的存储器中，以便于处理器调用执行以上各个模块对应的操作。该处理器可以为中央处理单元（CPU)、微处理器、单片机等。
参照图11，图11是本申请实施例方案涉及的硬件运行环境的设备结构示意图。
本申请实施例组件调试设备可以是PC，也可以是智能手机、平板电脑、便携计算机等具有显示功能的终端设备。
如图11所示，该组件调试设备可以包括：处理器1001，例如CPU，网络接口1002，用户接口1003，存储器1004。这些组件之间的连接通信可以通过通信总线实现。网络接口1002可选的可以包括标准的有线接口（用于连接有线网络）、无线接口（如WI-FI接口、蓝牙接口、红外线接口等，用于连接无线网络）。用户接口1003可以包括显示屏（Display）、输入单元比如键盘（Keyboard），可选用户接口1003还可以包括标准的有线接口（例如用于连接有线键盘、有线鼠标等）、无线接口（例如用于连接无线键盘、无线鼠标）。存储器1004可以是高速RAM存储器，也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。存储器1004可选的还可以是独立于前述处理器1001的存储装置。
可选地，该组件调试设备还可以包括摄像头、RF（Radio Frequency，射频）电路，传感器、音频电路、WiFi模块等等。
本领域技术人员可以理解，图11中示出的组件调试设备结构并不构成对组件调试设备的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图11所示，作为一种计算机存储介质的存储器1004中可以包括操作系统、网络通信模块、用户接口模块以及组件调试程序。其中，操作系统是管理和控制组件调试设备硬件与软件资源的程序，支持网络通信模块、用户接口模块、组件调试程序以及其他程序或软件的运行；网络通信模块用于管理和控制网络接口1002；用户接口模块用于管理和控制用户接口1003。
在图11所示的组件调试设备中，处理器1001可以用于执行存储器1004中存储的组件调试程序，以实现如上文所述的组件调试方法的步骤。
本申请提供了一种计算机可读存储介质，所述计算机可读存储介质存储有组件调试程序，所述组件调试程序被处理器执行，以实现如上文所述的组件调试方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其它变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其它要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质（如ROM/RAM、磁碟、光盘）中，包括若干指令用以使得一台终端设备（可以是手机，计算机，服务器，空调器，或者网络设备等）执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其它相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种组件调试方法，其特征在于，应用于浏览器中，所述浏览器安装有调试插件，所述组件调试方法包括：
    在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
    通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
    基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
  2. 如权利要求1所述的组件调试方法，其特征在于，所述在接收到组件调试指令时，确定所述调试指令对应的待调试组件的步骤包括：
    在接收到组件调试指令时，判断预设的调试器中是否勾选有组件；
    若所述调试器中勾选有组件，则将勾选的组件作为所述调试指令对应的待调试组件。
  3. 如权利要求2所述的组件调试方法，其特征在于，所述在接收到组件调试指令时，判断预设的调试器中是否勾选有组件的步骤之后，所述组件调试方法还包括：
    若所述调试器中未勾选组件，则在所述调试插件的调试界面中显示组件选择窗口；
    将外界基于所述组件选择窗口选择的组件，作为所述调试指令对应的待调试组件。
  4. 如权利要求1所述的组件调试方法，其特征在于，所述组件调试方法还包括：
    在接收到组件的调试数据更新指令时，显示所述调试插件的调试界面，以供外界在所述调试界面中更新组件的调试数据；
    获取基于所述调试界面更新的调试数据；
    将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。
  5. 如权利要求1所述的组件调试方法，其特征在于，所述在接收到组件调试指令时，确定所述调试指令对应的待调试组件的步骤之前，所述组件调试方法还包括：
    对所述浏览器的所述预设页面设置通信机制；
    将所述浏览器的调试插件设置为通信对象。
  6. 一种组件调试装置，其特征在于，应用于浏览器中，所述浏览器安装有调试插件，所述组件调试装置包括：
    确定模块，用于在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
    调用模块，用于通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
    调试模块，用于基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
  7. 如权利要求6所述的组件调试装置，其特征在于，所述确定模块包括：
    判断单元，用于在接收到组件调试指令时，判断预设的调试器中是否勾选有组件；
    确定单元，用于若所述调试器中勾选有组件，则将勾选的组件作为所述调试指令对应的待调试组件。
  8. 如权利要求7所述的组件调试装置，其特征在于，所述确定模块还包括：
    显示单元，用于若所述调试器中未勾选组件，则在所述调试插件的调试界面中显示组件选择窗口；
    所述确定单元，还用于将外界基于所述组件选择窗口选择的组件，作为所述调试指令对应的待调试组件。
  9. 如权利要求6所述的组件调试装置，其特征在于，所述组件调试装置还包括：
    显示模块，用于在接收到组件的调试数据更新指令时，显示所述调试插件的调试界面，以供外界在所述调试界面中更新组件的调试数据；
    获取模块，用于获取基于所述调试界面更新的调试数据；
    传输模块，用于将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。
  10. 如权利要求6所述的组件调试装置，其特征在于，所述组件调试装置还包括：
    设置模块，用于对所述浏览器的所述预设页面设置通信机制；
    所述设置模块，还用于将所述浏览器的调试插件设置为通信对象。
  11. 一种组件调试设备，其特征在于，所述组件调试设备包括处理器、以及存储有组件调试程序的存储器；所述处理器用于执行所述组件调试程序，以实现以下步骤：
    在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
    通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
    基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
  12. 如权利要求11所述的组件调试设备，其特征在于，在接收到组件调试指令时，所述处理器还用于执行所述组件调试程序，以实现确定所述调试指令对应的待调试组件的步骤：
    在接收到组件调试指令时，判断预设的调试器中是否勾选有组件；
    若所述调试器中勾选有组件，则将勾选的组件作为所述调试指令对应的待调试组件。
  13. 如权利要求12所述的组件调试设备，其特征在于，所述在接收到组件调试指令时，判断预设的调试器中是否勾选有组件的步骤之后，所述处理器还用于执行所述组件调试程序，以实现以下步骤：
    若所述调试器中未勾选组件，则在所述调试插件的调试界面中显示组件选择窗口；
    将外界基于所述组件选择窗口选择的组件，作为所述调试指令对应的待调试组件。
  14. 如权利要求11所述的组件调试设备，其特征在于，所述处理器还用于执行所述组件调试程序，以实现以下步骤：
    在接收到组件的调试数据更新指令时，显示所述调试插件的调试界面，以供外界在所述调试界面中更新组件的调试数据；
    获取基于所述调试界面更新的调试数据；
    将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。
  15. 如权利要求11所述的组件调试设备，其特征在于，所述在接收到组件调试指令时，确定所述调试指令对应的待调试组件的步骤之前，所述处理器还用于执行所述组件调试程序，以实现以下步骤：
    对所述浏览器的所述预设页面设置通信机制；
    将所述浏览器的调试插件设置为通信对象。
  16. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有组件调试程序，所述组件调试程序被处理器执行，以实现以下步骤：
    在接收到组件调试指令时，确定所述调试指令对应的待调试组件；
    通过安装的所述调试插件，调用所述浏览器的应用程序接口API；
    基于调用的所述API，在所述浏览器的预设页面对所述待调试组件执行调试操作。
  17. 如权利要求16所述的计算机可读存储介质，其特征在于，在接收到组件调试指令时，所述组件调试程序被处理器执行，还实现确定所述调试指令对应的待调试组件的步骤：
    在接收到组件调试指令时，判断预设的调试器中是否勾选有组件；
    若所述调试器中勾选有组件，则将勾选的组件作为所述调试指令对应的待调试组件。
  18. 如权利要求17所述的计算机可读存储介质，其特征在于，所述在接收到组件调试指令时，判断预设的调试器中是否勾选有组件的步骤之后，所述组件调试程序被处理器执行，还实现以下步骤：
    若所述调试器中未勾选组件，则在所述调试插件的调试界面中显示组件选择窗口；
    将外界基于所述组件选择窗口选择的组件，作为所述调试指令对应的待调试组件。
  19. 如权利要求16所述的计算机可读存储介质，其特征在于，所述组件调试程序被处理器执行，还实现以下步骤：
    在接收到组件的调试数据更新指令时，显示所述调试插件的调试界面，以供外界在所述调试界面中更新组件的调试数据；
    获取基于所述调试界面更新的调试数据；
    将更新的调试数据传输至所述浏览器的所述预设页面，以在所述预设页面中基于更新的调试数据，执行调试操作。
  20. 如权利要求16所述的计算机可读存储介质，其特征在于，所述在接收到组件调试指令时，确定所述调试指令对应的待调试组件的步骤之前，所述组件调试程序被处理器执行，还实现以下步骤：
    对所述浏览器的所述预设页面设置通信机制；
    将所述浏览器的调试插件设置为通信对象。
PCT/CN2017/111886 2017-02-20 2017-11-20 组件调试方法、装置、设备和计算机可读存储介质 WO2018149190A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710091768.8 2017-02-20
CN201710091768.8A CN107688529B (zh) 2017-02-20 2017-02-20 组件调试方法和装置

Publications (1)

Publication Number Publication Date
WO2018149190A1 true WO2018149190A1 (zh) 2018-08-23

Family

ID=61152420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/111886 WO2018149190A1 (zh) 2017-02-20 2017-11-20 组件调试方法、装置、设备和计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN107688529B (zh)
WO (1) WO2018149190A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108415844B (zh) * 2018-03-22 2022-03-08 北京奇虎科技有限公司 插件化调试方法及装置
CN109726109A (zh) * 2018-06-04 2019-05-07 平安普惠企业管理有限公司 代码调试方法、装置、设备和计算机存储介质
CN108897531B (zh) * 2018-06-29 2021-11-16 播思通讯技术（北京）有限公司 一种Carplay开发和调试方法
CN109144497B (zh) * 2018-07-06 2021-07-20 中科星图股份有限公司 一种基于安卓的地理空间浏览器平台及构建方法
CN109189663B (zh) * 2018-07-12 2021-10-29 武汉精测电子集团股份有限公司 一种插件调试方法、测试方法及微内核架构系统
CN109992485B (zh) * 2019-03-20 2023-02-03 郑州阿帕斯科技有限公司 一种调试日志提供方法、终端设备及服务器
CN111831538B (zh) * 2019-04-18 2024-03-26 腾讯科技（深圳）有限公司 调试方法、装置以及存储介质
CN110633220A (zh) * 2019-09-25 2019-12-31 北京明略软件系统有限公司 调试信息显示方法、装置、存储介质及电子设备
CN110990078B (zh) * 2019-11-29 2021-05-11 浙江大搜车软件技术有限公司 应用的初始化方法、装置、存储介质及移动终端

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1310868A2 (en) * 2001-10-24 2003-05-14 Sun Microsystems, Inc. Method and apparatus for a platform independent plug-in
CN104461855A (zh) * 2013-09-22 2015-03-25 腾讯科技（北京）有限公司 一种Web自动化测试方法、系统及装置
CN105117339A (zh) * 2015-08-27 2015-12-02 广州市百果园网络科技有限公司 一种利用插件调试原生命令调试程序的方法和装置
CN105138451A (zh) * 2015-07-31 2015-12-09 百度在线网络技术（北京）有限公司 一种用于测试插件的功能的方法、装置和系统
CN105404504A (zh) * 2015-11-02 2016-03-16 北京锐安科技有限公司 一种Web组件的调试方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103684899B (zh) * 2012-09-17 2019-01-08 腾讯科技（深圳）有限公司 远程调试方法和装置
US9135145B2 (en) * 2013-01-28 2015-09-15 Rackspace Us, Inc. Methods and systems of distributed tracing
CN104778121B (zh) * 2015-03-25 2018-09-18 网易（杭州）网络有限公司 游戏程序的测试方法、装置及系统
CN105357323B (zh) * 2015-12-11 2019-01-25 北京京东尚科信息技术有限公司 一种app中html5页面调试方法及装置
CN106228071B (zh) * 2016-07-20 2019-02-22 北京奇虎科技有限公司 一种测试编解码组件的方法和装置
CN106383785B (zh) * 2016-09-21 2018-11-27 网易（杭州）网络有限公司 移动应用的调试方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1310868A2 (en) * 2001-10-24 2003-05-14 Sun Microsystems, Inc. Method and apparatus for a platform independent plug-in
CN104461855A (zh) * 2013-09-22 2015-03-25 腾讯科技（北京）有限公司 一种Web自动化测试方法、系统及装置
CN105138451A (zh) * 2015-07-31 2015-12-09 百度在线网络技术（北京）有限公司 一种用于测试插件的功能的方法、装置和系统
CN105117339A (zh) * 2015-08-27 2015-12-02 广州市百果园网络科技有限公司 一种利用插件调试原生命令调试程序的方法和装置
CN105404504A (zh) * 2015-11-02 2016-03-16 北京锐安科技有限公司 一种Web组件的调试方法及装置

Also Published As

Publication number Publication date
CN107688529A (zh) 2018-02-13
CN107688529B (zh) 2020-07-21

Similar Documents

Publication Publication Date Title
WO2018149190A1 (zh) 组件调试方法、装置、设备和计算机可读存储介质
WO2018120429A1 (zh) 一种资源更新的方法、终端、计算机可读存储介质及资源更新设备
WO2014082500A1 (zh) 页面加载方法及其系统、计算机存储介质
WO2019205280A1 (zh) 服务器的测试方法、装置、设备及计算机可读存储介质
WO2019114262A1 (zh) 加载用户界面的方法、智能电视及计算机可读存储介质
WO2018107610A1 (zh) 业务数据处理方法、系统、设备及计算机可读存储介质
WO2019100638A1 (zh) 数据同步方法、装置、设备及存储介质
WO2017039321A1 (en) Foldable electronic device including hidden display and information display method thereof
WO2018120457A1 (zh) 数据处理方法、装置、设备及计算机可读存储介质
WO2015167165A1 (en) Method and electronic device for managing display objects
WO2017010803A1 (en) Method for operating electronic device, and electronic device
WO2019174375A1 (zh) 接口测试方法、装置、设备及计算机可读存储介质
WO2018188342A1 (zh) 脚本文件生成方法、装置、设备和计算机可读存储介质
WO2015158219A1 (en) Remote debugging method and apparatus for mobile terminal
WO2017054592A1 (zh) 一种界面显示的方法及终端
WO2016167620A1 (en) Apparatus and method for providing information via portion of display
WO2019104876A1 (zh) 保险产品的推送方法、系统、终端、客户终端及存储介质
WO2019024219A1 (zh) 文档自动生成方法、装置、文档自动生成器及介质
WO2019000801A1 (zh) 数据同步方法、装置、设备及计算机可读存储介质
WO2017095203A2 (en) Electronic device and method for displaying a notification object
WO2017219663A1 (zh) 移动终端、及其应用程序的查找方法与查找系统
WO2019080247A1 (zh) 产生保单批文的方法、装置、设备及计算机可读存储介质
WO2016000560A1 (en) File transmission method, file transmission apparatus, and file transmission system
WO2017206377A1 (zh) 同步播放节目的方法和装置
WO2017036208A1 (zh) 显示界面中的信息提取方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17896760

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17896760

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 12.02.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17896760

Country of ref document: EP

Kind code of ref document: A1