CN111008132B - Application debugging method and device for Android system, computer equipment and storage medium - Google Patents
Application debugging method and device for Android system, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111008132B CN111008132B CN201911199350.4A CN201911199350A CN111008132B CN 111008132 B CN111008132 B CN 111008132B CN 201911199350 A CN201911199350 A CN 201911199350A CN 111008132 B CN111008132 B CN 111008132B
- Authority
- CN
- China
- Prior art keywords
- debugging
- plug
- application
- application information
- menu
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
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/3636—Software debugging by tracing the execution of the program
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to an application debugging method and device of an Android system, computer equipment and a storage medium. The method comprises the following steps: packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page; and responding to the clicking operation of the plug-in on the debugging menu view, and triggering the corresponding plug-in behavior to debug the corresponding application information. According to the visual debugging method brought by the plug-in, the debugging can be completed at the mobile terminal without connecting a computer or installing any software tool, the learning cost of the debugging is reduced, and the debugging efficiency is greatly improved. In addition, when a new application debugging requirement exists, a new plug-in is directly registered, the plug-in can be used for completing the application debugging, and the source code of the application does not need to be modified, so that the stability and the safety of the application are not influenced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an application debugging method and apparatus for an Android system, a computer device, and a storage medium.
Background
With the development of various mobile terminal development technologies, especially the continuous iteration of software, the functions and requirements of various applications are diversified. In the development and testing stage of mobile software, developers, testers, or product managers often need to debug some information of applications, such as: the method comprises the steps of obtaining a certain request sent by an application, obtaining a page jump link, obtaining a running log, or needing to modify the execution environment of the application, and the like.
The existing methods for debugging application information in the Android system mainly comprise the following two methods: one is to assist in debugging the application by installing computer software. The general method of the debugging method is that the capturing and modifying of the network request information are carried out by opening the capturing software on the computer and simultaneously ensuring that the mobile phone and the computer are connected to the same network; or an Android development environment is installed on the computer, the computer is connected through a data line, and the running log of the application is checked. Some computer software is used for assisting debugging application, a computer is required to be used, and specific computer software is installed, so that the learning cost is high, and the debugging efficiency is low.
The other is that the developer modifies the source code of the application to assist in debugging the application. For example, switching of the application execution environment is achieved by modifying the environment code, or debugging information is output to a log or page for viewing or modification by modifying the source code. The modified source codes need to be changed before the application is on-line, so that the debugging efficiency is low due to frequent code modification, and the stability of the application can be influenced, so that certain potential safety hazards are caused.
Therefore, the existing application debugging method of the Android system has the problems of low debugging efficiency and possibility of influencing the stability of the application.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method, an apparatus, a computer device, and a storage medium for debugging an application of an Android system, which are efficient and stable.
An application debugging method of an Android system comprises the following steps:
packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
and responding to the plug-in clicking operation on the debugging menu view, and triggering the corresponding plug-in behavior to debug the corresponding application information.
In one embodiment, the step of encapsulating all the debugging methods of the application information to be debugged, registering the encapsulated application information into a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page includes the following steps:
when the application is started, initializing the debugging center and creating the debugging menu view;
initializing an application information provider, wherein all debugging methods of application information needing debugging are packaged in the application information provider;
according to application information needing debugging, registering a plug-in a debugging menu of the debugging center, and binding the debugging menu view with a data source of the registered plug-in; the data source of the registered plug-in comes from the application information provider.
In one embodiment, the method further comprises the steps of:
and when the application is started, generating a floating ball inlet for entering the debugging menu view on a mobile terminal page.
In one embodiment, the method further comprises the steps of:
and setting a monitor when the application is started, and triggering corresponding plug-in behaviors when the monitor monitors that the plug-ins in the debugging menu view are clicked.
In one embodiment, when a plurality of plug-ins are registered in a debugging menu of the debugging center, a plug-in queue is generated, and the debugging menu view is bound with data sources of the plug-ins in the plug-in queue.
In one embodiment, the method further comprises the steps of:
responding to the plug-in clicking operation on the debugging menu view, and entering a visual page of a corresponding plug-in; the visual page of the plug-in is a page of the application or a dialog box of the application.
In one embodiment, the application information provider includes one or more of a network information provider, a log provider, an environment provider, and a page information provider.
An application debugging device of an Android system comprises a plug-in registration module and a trigger debugging module;
the plug-in registration module is used for packaging all debugging methods of the application information needing debugging, registering the debugging methods into a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
and the triggering debugging module is used for responding to the plug-in clicking operation on the debugging menu view and triggering the corresponding plug-in behavior so as to debug the corresponding application information.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
and responding to the plug-in clicking operation on the debugging menu view, and triggering the corresponding plug-in behavior to debug the corresponding application information.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
and responding to the plug-in clicking operation on the debugging menu view, and triggering the corresponding plug-in behavior to debug the corresponding application information.
According to the application debugging method and device of the Android system, the computer equipment and the storage medium, all debugging methods of application information needing debugging are packaged and registered in a debugging menu of a debugging center in a plug-in mode, and a debugging menu view is generated on a mobile terminal page, so that the plug-in provides different debugging functions in a visual mode. Developers, testers or product managers can open a debugging menu view on any page of the mobile terminal, and can enter a visual page corresponding to the plug-in by clicking different plug-ins on the debugging menu, trigger corresponding plug-in behaviors and debug corresponding application information. The visual debugging method brought by the plug-in unit can finish debugging at the mobile terminal without connecting a computer and installing any software tool, so that the learning cost of debugging is reduced, and the debugging efficiency is greatly improved. In addition, when a new application debugging requirement exists, a new plug-in is directly registered, the plug-in can be used for completing the application debugging, and the source code of the application does not need to be modified, so that the stability and the safety of the application are not influenced.
Drawings
Fig. 1 is an application environment diagram of an application debugging method of an Android system in an embodiment;
fig. 2 is a schematic flowchart illustrating an application debugging method of an Android system in an embodiment;
fig. 3 is a schematic flowchart illustrating an application debugging method of an Android system in another embodiment;
fig. 4 is a block diagram illustrating an application debugging apparatus of an Android system according to an embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The application debugging method of the Android system can be applied to the application environment shown in fig. 1. The mobile terminal 102, as a terminal device, communicates with the server 104 through the network to complete the plug-in registration. The mobile terminal 102 may be, but not limited to, various notebook computers, smart phones, tablet computers and portable wearable devices that can be installed with an Android system, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In an embodiment, as shown in fig. 2, an application debugging method for an Android system is provided, which is described by taking the application method applied to the terminal in fig. 1 as an example, and includes the following steps:
s202, packaging all debugging methods of the application information needing debugging, registering the application information into a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page.
The debugging center referred to in this application is located in the server. The process of registering the plug-in to the debugging menu of the debugging center needs the mobile terminal to complete communication with the server.
The plug-in the application can be a page of the application or a dialog box of the application. All debugging methods of the application information needing debugging are packaged and registered in the form of plug-ins, so that the plug-ins can provide different debugging functions in a visual form. Such as: debugging a plug-in of a network request sent in an application, acquiring a plug-in of a page jump link, acquiring a plug-in of a running log, or modifying a plug-in of an application execution environment, and the like.
Each plug-in is a Java object and realizes an interface IPlogic together, and the IPlogic comprises the following callback methods:
a, acquiring information (), such as plug-in names and the like;
b plug-in is initialized ();
c plug-in clicked ();
and d, calling back () from the life cycle of the application page where the plug-in is positioned.
The debugging menu view can be realized through a RecylerView, a plug-in data source can be bound, information such as a plug-in name can be acquired through a callback method a of the plug-in, and finally the information is displayed on the debugging menu view.
One or more corresponding plug-ins may be registered according to information that the application needs to debug. If a plurality of plug-ins are registered, a plug-in queue is generated in a debugging menu of a debugging center. And registering the plug-in, triggering a callback method b of the plug-in, and adding the newly registered plug-in to a plug-in queue of the debugging center.
And S204, responding to the plug-in clicking operation on the debugging menu view, and triggering corresponding plug-in behaviors to debug corresponding application information.
Developers, testers or product managers can open a debugging menu view on any page of the mobile terminal, and enter a visual page of a corresponding plug-in by clicking different plug-ins on the debugging menu, so as to debug corresponding application information. Once the view content is clicked, the callback method c of the corresponding plug-in is triggered to trigger the corresponding plug-in behavior.
The lifecycle of Activity in the application can be monitored through a register Activity lifecycle callback method provided by Android, and once the lifecycle is recalled, the callback method d of all plug-ins is triggered.
According to the debugging method and the debugging device, all debugging methods of the application information needing debugging are packaged and registered in the debugging menu of the debugging center in the form of the plug-in, and the debugging menu view is generated on the mobile terminal page, so that the plug-in can provide different debugging functions in a visual form. Developers, testers or product managers can open a debugging menu view on any page of the mobile terminal, and can enter a visual page corresponding to the plug-in by clicking different plug-ins on the debugging menu, trigger corresponding plug-in behaviors and debug corresponding application information. The visual debugging method brought by the plug-in unit can finish debugging at the mobile terminal without connecting a computer or installing any software tool, thereby reducing the learning cost of debugging and greatly improving the debugging efficiency. In addition, when a new application debugging requirement exists, a new plug-in is directly registered, the plug-in can be used for completing the application debugging, and the source code of the application does not need to be modified, so that the stability and the safety of the application are not influenced.
In an embodiment, as shown in fig. 3, an application debugging method for an Android system is provided, which includes the following steps:
s302, when the application is started, initializing a debugging center and creating a debugging menu view.
Further, when the application is started, a hover ball entry entering the debugging menu view can be generated on the mobile terminal page. By means of the suspension ball, the application can be directly debugged on any page.
As an implementable way, the suspension ball can be made to be suspendable at any one interface by adding a view of type WindowManager. The touch method of rewriting the view can be used to support the dragging behavior, and a click view is set to open the debugging menu view.
The debug menu view may be implemented by a RecylerView and bound to the data source of the plug-in queue. Through the callback method a of the plug-in, information such as the name of the plug-in can be obtained and finally displayed on the debugging menu view.
S304, initializing an application information provider, wherein all debugging methods of the application information needing debugging are packaged in the application information provider.
The application information provider includes a network information provider, a log provider, an environment provider, a page information provider, and the like. The application information provider is a bridge that provides plug-ins to obtain or modify application information.
Each application information provider is implemented by a different Java class encapsulating all methods that the application information provider has to debug certain information inside the application. For example, a network information provider provides an interceptor (such as an OkHttp direct support interceptor) of a network framework to expose network requested information on a plug-in page through the provider or to provide a function of modifying network requested information.
S306, according to application information needing debugging, registering a plug-in a debugging menu of a debugging center, and binding a debugging menu view with a data source of the registered plug-in; the data source of the registered plug-in comes from the application information provider.
One or more corresponding plug-ins may be registered according to information that the application needs to debug. If a plurality of plug-ins are registered, a plug-in queue is generated in a debugging menu of a debugging center. And registering the plug-in, triggering a callback method b of the plug-in, and adding the newly registered plug-in to a plug-in queue of the debugging center.
For the case that a plurality of registered plug-ins are provided, as an implementable mode, when the application is started and in the process of initializing the debugging center, a plug-in queue can be further constructed, and the debugging menu view is bound with the data source of the plug-in queue.
S308, responding to the plug-in clicking operation on the debugging menu view, and triggering the corresponding plug-in behavior to debug the corresponding application information.
Developers, testers or product managers can open a debugging menu view by clicking the floating ball on any page of the mobile terminal, and further enter a visual page corresponding to the plug-in by clicking different plug-ins on the debugging menu, so as to debug corresponding application information. Once the view content is clicked, the callback method c of the corresponding plug-in is triggered to trigger the corresponding plug-in behavior.
As an implementable manner, when the application is started, a listener can be further set, and when the listener hears that the plug-in the debugging menu view is clicked, the corresponding plug-in behavior is triggered. Once the contents of the debugging menu view are clicked, a callback method c of the corresponding plug-in is triggered to trigger the corresponding plug-in behavior.
The lifecycle of Activity in the application can be monitored through a register Activity lifecycle callback method provided by Android, and once the lifecycle is recalled, the callback method d of all plug-ins is triggered.
Further, responding to a plug-in clicking operation on the debugging menu view, and entering a visual page of a corresponding plug-in; the visual page of the plug-in is a page of the application or a dialog box of the application.
According to the application debugging method of the Android system, the debugging can be completed at the mobile terminal without connecting a computer or installing any software tool through a visual debugging method brought by a plug-in. In addition, the method can be used for directly debugging and applying any page in a floating ball mode, the debugging process is visual, the learning cost is low, the efficiency is high, application source codes do not need to be modified in the debugging process, and the stability and the safety of application are guaranteed.
It should be understood that although the various steps in the flow charts of fig. 2-3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 4, an application debugging apparatus of the Android system is provided, which includes a plug-in registration module 402 and a trigger debugging module 404.
The plug-in registration module 402 is configured to encapsulate all debugging methods of application information to be debugged, register the encapsulated debugging methods in a debugging menu of a debugging center in a plug-in manner, and generate a debugging menu view on a mobile terminal page;
the trigger debugging module 404 is configured to trigger a corresponding plug-in behavior in response to a plug-in click operation on the debugging menu view, so as to debug corresponding application information.
In one embodiment, the plug-in registration module 402 module includes a first initialization unit, a second initialization unit, and a plug-in registration unit;
the first initialization unit is used for initializing a debugging center and creating a debugging menu view when the application is started;
the second initialization unit is used for initializing an application information provider, and all debugging methods of the application information needing debugging are packaged in the application information provider;
the plug-in registration unit is used for registering the plug-in a debugging menu of the debugging center according to the application information needing debugging and binding a debugging menu view with a data source of the registered plug-in; the data source of the registered plug-in comes from the application information provider.
In one embodiment, the plug-in registration module 402 is further configured to generate a hover ball entry into the debug menu view at the mobile end page when the application is launched.
In one embodiment, the plug-in registration module 402 is further configured to set a listener at the start of the application, and when the listener hears that a plug-in the debugging menu view is clicked, trigger a corresponding plug-in behavior.
In one embodiment, the plug-in registration module 402 is further configured to generate a plug-in queue when a plurality of plug-ins are registered in a debugging menu of the debugging center, and bind the debugging menu view with data sources of the plug-ins in the plug-in queue.
The trigger debugging module 404 is further configured to respond to a plug-in clicking operation on the debugging menu view, and enter a visual page of a corresponding plug-in; the visual page of the plug-in is a page of the application or a dialog box of the application.
In one embodiment, the application information provider includes one or more of a network information provider, a log provider, an environment provider, and a page information provider.
For specific limitations of the application debugging device of the Android system, reference may be made to the above limitations of the application debugging method of the Android system, which are not described herein again. All or part of the modules in the application debugging device of the Android system can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a mobile terminal, and its internal structure diagram may be as shown in fig. 5. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to realize an application debugging method of an Android system. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
and responding to the clicking operation of the plug-in on the debugging menu view, and triggering the corresponding plug-in behavior to debug the corresponding application information.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
when the application is started, initializing a debugging center and creating a debugging menu view;
initializing an application information provider, wherein all debugging methods of application information needing debugging are packaged in the application information provider;
according to application information needing debugging, registering a plug-in a debugging menu of a debugging center, and binding a debugging menu view with a data source of the registered plug-in; the data source of the registered plug-in comes from the application information provider.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and when the application is started, generating a floating ball inlet for entering the debugging menu view on the mobile terminal page.
In one embodiment, the processor, when executing the computer program, further performs the steps of: and setting a monitor when the application is started, and triggering corresponding plug-in behaviors when the monitor monitors that the plug-ins in the debugging menu view are clicked.
In one embodiment, the processor, when executing the computer program, further performs the steps of: when a plurality of plug-ins are registered in a debugging menu of a debugging center, a plug-in queue is generated, and a debugging menu view is bound with data sources of the plug-ins in the plug-in queue.
In one embodiment, the processor, when executing the computer program, further performs the steps of: responding to a plug-in clicking operation on the debugging menu view, and entering a visual page of a corresponding plug-in; the visual page of the plug-in is a page of the application or a dialog box of the application.
In one embodiment, the application information provider includes one or more of a network information provider, a log provider, an environment provider, and a page information provider.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
and responding to the clicking operation of the plug-in on the debugging menu view, and triggering the corresponding plug-in behavior to debug the corresponding application information.
In one embodiment, the computer program when executed by the processor further performs the steps of:
when the application is started, initializing a debugging center and creating a debugging menu view;
initializing an application information provider, wherein all debugging methods of application information needing debugging are packaged in the application information provider;
according to application information needing debugging, registering a plug-in a debugging menu of a debugging center, and binding a debugging menu view with a data source of the registered plug-in; the data source of the registered plug-in comes from the application information provider.
In one embodiment, the computer program when executed by the processor further performs the steps of: and when the application is started, generating a floating ball inlet for entering the debugging menu view on the mobile terminal page.
In one embodiment, the computer program when executed by the processor further performs the steps of: and setting a monitor when the application is started, and triggering corresponding plug-in behaviors when the monitor monitors that the plug-ins in the debugging menu view are clicked.
In one embodiment, the computer program when executed by the processor further performs the steps of: when a plurality of plug-ins are registered in a debugging menu of a debugging center, a plug-in queue is generated, and a debugging menu view is bound with data sources of the plug-ins in the plug-in queue.
In one embodiment, the computer program when executed by the processor further performs the steps of: responding to a plug-in clicking operation on the debugging menu view, and entering a visual page of a corresponding plug-in; the visual page of the plug-in is a page of the application or a dialog box of the application.
In one embodiment, the application information provider includes one or more of a network information provider, a log provider, an environment provider, and a page information provider.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (9)
1. An application debugging method of an Android system is characterized by comprising the following steps:
packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
responding to the plug-in clicking operation on the debugging menu view, and triggering corresponding plug-in behaviors to debug corresponding application information;
the method comprises the following steps of packaging all debugging methods of application information to be debugged, registering the application information to a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page, wherein the debugging menu view comprises the following steps:
when the application is started, initializing the debugging center and creating the debugging menu view;
initializing an application information provider, wherein all debugging methods of application information needing debugging are packaged in the application information provider;
according to application information needing debugging, registering a plug-in a debugging menu of the debugging center, and binding the debugging menu view with a data source of the registered plug-in; the data source of the registered plug-in comes from the application information provider.
2. The method of claim 1, further comprising the steps of:
and when the application is started, generating a floating ball inlet for entering the debugging menu view on a mobile terminal page.
3. The method of claim 1, further comprising the steps of:
and setting a monitor when the application is started, and triggering corresponding plug-in behaviors when the monitor monitors that the plug-ins in the debugging menu view are clicked.
4. The method of claim 1, wherein when a plurality of plug-ins are registered in a debug menu of the debug center, generating a plug-in queue and binding the debug menu view with data sources of the plug-ins in the plug-in queue.
5. The method of claim 1, further comprising the steps of:
responding to the plug-in clicking operation on the debugging menu view, and entering a visual page of a corresponding plug-in; the visual page of the plug-in is a page of the application or a dialog box of the application.
6. The method of claim 1, wherein the application information provider comprises one or more of a network information provider, a log provider, an environment provider, and a page information provider.
7. An application debugging device of an Android system is characterized by comprising a plug-in registration module and a trigger debugging module;
the plug-in registration module is used for packaging all debugging methods of the application information needing debugging, registering the debugging methods into a debugging menu of a debugging center in a plug-in mode, and generating a debugging menu view on a mobile terminal page;
the plug-in registration module also comprises a first initialization unit, a second initialization unit and a plug-in registration unit; the first initialization unit is used for initializing the debugging center and creating the debugging menu view when an application is started; the second initialization unit is used for initializing an application information provider, and all debugging methods of the application information needing debugging are packaged in the application information provider; the plug-in registration unit is used for registering a plug-in the debugging menu of the debugging center according to application information needing debugging and binding the debugging menu view with a data source of the registered plug-in; the data source of the registered plug-in comes from the application information provider;
and the triggering debugging module is used for responding to the plug-in clicking operation on the debugging menu view and triggering the corresponding plug-in behavior so as to debug the corresponding application information.
8. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 6 when executing the computer program.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911199350.4A CN111008132B (en) | 2019-11-29 | 2019-11-29 | Application debugging method and device for Android system, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911199350.4A CN111008132B (en) | 2019-11-29 | 2019-11-29 | Application debugging method and device for Android system, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111008132A CN111008132A (en) | 2020-04-14 |
| CN111008132B true CN111008132B (en) | 2021-11-16 |
Family
ID=70112060
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911199350.4A Active CN111008132B (en) | 2019-11-29 | 2019-11-29 | Application debugging method and device for Android system, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008132B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626109A (en) * | 2021-09-17 | 2021-11-09 | 平安普惠企业管理有限公司 | Report path acquisition method and device, intelligent terminal and storage medium |
| CN113867834A (en) * | 2021-09-17 | 2021-12-31 | 北京顺达同行科技有限公司 | Debugging plug-in calling method and device and computer readable storage medium |
| CN113867598A (en) * | 2021-09-30 | 2021-12-31 | 挂号网（杭州）科技有限公司 | Opening method, device, equipment and storage medium of in-application debugging tool |
| CN114780195B (en) * | 2022-04-29 | 2024-02-13 | 济南浪潮数据技术有限公司 | Operation visualization method, device, equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105117339A (en) * | 2015-08-27 | 2015-12-02 | 广州市百果园网络科技有限公司 | Method and apparatus for debugging native command debugging program by utilizing plugin |
| CN106406877A (en) * | 2016-09-09 | 2017-02-15 | 浪潮软件股份有限公司 | Implementation method for on-line development and publishing of light application |
| CN109002334A (en) * | 2017-06-05 | 2018-12-14 | 阿里巴巴集团控股有限公司 | A kind of operation platform and its data processing method |
-
2019
- 2019-11-29 CN CN201911199350.4A patent/CN111008132B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105117339A (en) * | 2015-08-27 | 2015-12-02 | 广州市百果园网络科技有限公司 | Method and apparatus for debugging native command debugging program by utilizing plugin |
| CN106406877A (en) * | 2016-09-09 | 2017-02-15 | 浪潮软件股份有限公司 | Implementation method for on-line development and publishing of light application |
| CN109002334A (en) * | 2017-06-05 | 2018-12-14 | 阿里巴巴集团控股有限公司 | A kind of operation platform and its data processing method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111008132A (en) | 2020-04-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111008132B (en) | Application debugging method and device for Android system, computer equipment and storage medium | |
| CN109901834B (en) | Document page generation method, device, computer equipment and storage medium | |
| JP7106001B2 (en) | SUB-APPLICATION DEVELOPMENT METHOD, APPARATUS, COMPUTER DEVICE, AND COMPUTER PROGRAM | |
| CN113238850A (en) | RPA implementation method, device, equipment and medium based on browser | |
| CN110597564A (en) | Installation package construction and service component loading method, device and terminal equipment | |
| CN111459541A (en) | Application program packaging method and device, computer equipment and storage medium | |
| CN112416458A (en) | Preloading method and device based on ReactNative, computer equipment and storage medium | |
| CN111045707B (en) | Method, apparatus, computer device and storage medium for updating applet | |
| CN108121650B (en) | Method and device for testing page user interface | |
| CN112965731B (en) | Method, device, equipment and storage medium for Flutter hot update based on Tinker | |
| CN112882769B (en) | Skill pack data processing method, skill pack data processing device, computer equipment and storage medium | |
| CN112764836A (en) | Method and device for running fast application and electronic equipment | |
| CN112527416A (en) | Task processing method and device, computer equipment and storage medium | |
| CN111949529A (en) | System debugging method and device, computer equipment and storage medium | |
| CN111176986A (en) | Thread script debugging method and device, computer equipment and storage medium | |
| CN110597552A (en) | Configuration method, device and equipment of project continuous integration pipeline and storage medium | |
| CN113868127A (en) | Online debugging method and device, computer equipment and storage medium | |
| CN113282363A (en) | Method and device for optimizing hybrid APP | |
| CN112214213A (en) | Linux kernel development and management method and device, computer equipment and storage medium | |
| CN112714148A (en) | Interface configuration method, device, equipment and medium | |
| CN112162743A (en) | Driver generation method, device, computer equipment and storage medium | |
| CN111857782A (en) | Interface updating method and device, computer equipment and storage medium | |
| CN110990078B (en) | Application initialization method and device, storage medium and mobile terminal | |
| CN115543486B (en) | Server-free computing oriented cold start delay optimization method, device and equipment | |
| CN112491799B (en) | Remote repair method and device for communication module, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |