CN114115862A - Data processing method and device, electronic equipment and storage medium - Google Patents

Data processing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114115862A
CN114115862A CN202111427879.4A CN202111427879A CN114115862A CN 114115862 A CN114115862 A CN 114115862A CN 202111427879 A CN202111427879 A CN 202111427879A CN 114115862 A CN114115862 A CN 114115862A
Authority
CN
China
Prior art keywords
class
initialized
component
initialization
code
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.)
Pending
Application number
CN202111427879.4A
Other languages
Chinese (zh)
Inventor
凌日新
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wuba Co Ltd
Original Assignee
Wuba Co Ltd
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 Wuba Co Ltd filed Critical Wuba Co Ltd
Priority to CN202111427879.4A priority Critical patent/CN114115862A/en
Publication of CN114115862A publication Critical patent/CN114115862A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/36—Software reuse
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/40—Transformation of program code
    • G06F8/41—Compilation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
    • G06F9/44526—Plug-ins; Add-ons

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The application discloses a data processing method, a data processing device, electronic equipment and a storage medium. By the method and the device, when the initialized attribute and the attribute used for merging to the ContentProvider class are required to be set for the class to be initialized in each component in the application program in the development environment of the application program, codes of the initialized attribute for the class to be initialized in each component in the development environment of the application program do not need to be written for the class to be initialized in each component in the application program, and codes of the attribute used for merging to the ContentProvider class do not need to be written for the class to be initialized in each component in the application program. And only one initialization code template can be set in the development environment and the class name of the class to be initialized in the component can be set in the component, so that the code development amount can be reduced, and the labor cost is further reduced.

Description

Data processing method and device, electronic equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data processing method and apparatus, an electronic device, and a storage medium.
Background
In the process that a user uses an application program on a mobile phone, the application program may sometimes be switched to the background operation of an operating system of the mobile phone, so that the operating system may recycle threads of the application program, that is, the threads of the application program are closed to save system resources of the mobile phone, and then when the user switches the application program to the foreground operation of the operating system again, the operating system starts the threads for the application program to start the application program, and when the application program is started, the class to be initialized in each Library component in the application program is initialized, and a page displayed before the last background operation is displayed.
In order to initialize the class to be initialized in each Library component in the application program when the application program is started, when the source code of the application program is developed, in one mode, the code of the class to be initialized in each Library component may be written into an onCreate method in a ContentProvider class.
In this way, after the computer program code is compiled into the application program, in the process of starting the application program, in order to initialize the class to be initialized in each Library component in the application program, a ContentProvider class may be created, and the class to be initialized in each Library component is processed by using the ContentProvider class, so that the class to be initialized in each Library component is initialized respectively.
However, since the ContentProvider class needs to be used to complete initialization of the class to be initialized in each component, in the development environment of the application program, not only the code of the initialized attribute needs to be written for the class to be initialized in each component, but also the code of the attribute needs to be written for merging into the ContentProvider class for the class to be initialized in each component in the application program. Resulting in a large code development amount and thus high labor cost.
Disclosure of Invention
The application discloses a data processing method, a data processing device, electronic equipment and a storage medium.
In a first aspect, the present application shows a data processing method, which is applied to an electronic device, where the electronic device runs a development environment of an application program, the development environment includes at least one content provider ContentProvider class, an auxiliary plug-in, and at least one component of the application program, and each component includes at least one class to be initialized; the method comprises the following steps:
acquiring an initialization code template set in the auxiliary plug-in; the initialization code template includes a first code segment and a second code segment; the first code segment at least comprises a class name of the ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name; the second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that a class corresponding to the class name added on the class name adding bit needs to be initialized;
for any one of the at least one component, acquiring a class name of a class to be initialized in the component in an add-in file corresponding to the auxiliary add-in the component;
adding the class name of the class to be initialized in the component in the class name adding position in the initialization code template to obtain the initialization code of the class to be initialized in the component; the initialization code comprises a first code segment and a second code segment; the first code segment in the initialization code at least comprises the class name of the ContentProvider class and a preset merging tag used for indicating merging to the ContentProvider class according to the class name of the ContentProvider class; the second code segment in the initialization code at least comprises the class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized;
and storing the initialization code of the class to be initialized in the component in a sub-list file of the class to be initialized in the component.
In an optional implementation, the method further includes:
creating an auxiliary plug-in the development environment, and setting the initialization code template in the auxiliary plug-in;
and the number of the first and second groups,
and for any one of the at least one component, creating an add-in file corresponding to the auxiliary add-in the component, and setting the class name of the class to be initialized in the component in the add-in file.
In an optional implementation, the method further includes:
in the case where an executable file of the application program is generated from source code of the application program that has been developed in the development environment, the auxiliary plug-in is deleted or the initialization code template is deleted in the auxiliary plug-in.
In an optional implementation, the method further includes:
under the condition that the initialization code template needs to be updated, acquiring a new version of auxiliary plug-in, wherein the new version of auxiliary plug-in has the new version of initialization code template;
replacing existing auxiliary plug-ins in the development environment with new versions of auxiliary plug-ins.
In an optional implementation, the method further includes:
in the case of generating an executable file of the application program according to source codes of the application program developed in the development environment, respectively searching whether an initialization code with the preset initialization tag exists in sub-manifest files in various classes in the source code;
acquiring a class name of a class to be initialized recorded in a second code segment in the initialization code with the preset initialization tag, and acquiring a class name of the ContentProvider class and the preset merging tag recorded in a first code segment in the initialization code with the preset initialization tag;
generating a tag set in the ContentProvider class in the executable file;
and adding the acquired class name of each class to be initialized in the tag set according to the class name of the ContentProvider class and the preset merging tag.
In a second aspect, the present application shows a data processing apparatus, which is applied to an electronic device, where the electronic device runs a development environment of an application program, where the development environment includes at least one content provider ContentProvider class, an auxiliary plug-in, and at least one component of the application program, and each component includes at least one class to be initialized; the device comprises:
the first acquisition module is used for acquiring an initialization code template set in the auxiliary plug-in; the initialization code template includes a first code segment and a second code segment; the first code segment at least comprises a class name of the ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name; the second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that a class corresponding to the class name added on the class name adding bit needs to be initialized;
a second obtaining module, configured to, for any one of the at least one component, obtain, in an add-in file corresponding to the auxiliary add-in the component, a class name of a class to be initialized in the component;
a first adding module, configured to add a class name of a class to be initialized in the component to a class name adding bit in the initialization code template, so as to obtain an initialization code of the class to be initialized in the component; the initialization code comprises a first code segment and a second code segment; the first code segment in the initialization code at least comprises the class name of the ContentProvider class and a preset merging tag used for indicating merging to the ContentProvider class according to the class name of the ContentProvider class; the second code segment in the initialization code at least comprises the class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized;
and the storage module is used for storing the initialization code of the class to be initialized in the component in the sub-list file of the class to be initialized in the component.
In an optional implementation, the apparatus further comprises:
the first setting module is used for creating an auxiliary plug-in the development environment and setting the initialization code template in the auxiliary plug-in;
and the number of the first and second groups,
and the second setting module is used for creating an plugin file corresponding to the auxiliary plugin in the component for any one of the at least one component, and setting the class name of the class to be initialized in the component in the plugin file.
In an optional implementation, the apparatus further comprises:
a deletion module configured to delete the auxiliary plug-in or delete the initialization code template in the auxiliary plug-in when an executable file of the application is generated from source code of the application that has been developed in the development environment.
In an optional implementation, the apparatus further comprises:
the third acquisition module is used for acquiring a new version of auxiliary plug-in unit under the condition that the initialization code template needs to be updated, wherein the new version of auxiliary plug-in unit has a new version of initialization code template;
a replacement module for replacing an existing auxiliary plug-in the development environment with a new version of the auxiliary plug-in.
In an optional implementation, the apparatus further comprises:
the searching module is used for respectively searching whether the initialization code with the preset initialization tag exists in the sub-list files in each class in the source code under the condition that the executable file of the application program is generated according to the source code of the application program developed in the development environment;
a fourth obtaining module, configured to obtain a class name of a class to be initialized recorded in the second code segment in the initialization code stored in the preset initialization tag, and obtain a class name of the ContentProvider class and the preset merge tag recorded in the first code segment in the initialization code stored in the preset initialization tag;
a generating module, configured to generate a tag set in the ContentProvider class in the executable file;
and the second adding module is used for adding the acquired class name of each class to be initialized in the tag set according to the class name of the ContentProvider class and the preset merging tag.
In a third aspect, the present application shows an electronic device comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the data processing method of the first aspect.
In a fourth aspect, the present application shows a non-transitory computer readable storage medium having instructions which, when executed by a processor of an electronic device, enable the electronic device to perform the data processing method of the first aspect.
In a fifth aspect, the present application shows a computer program product, in which instructions, when executed by a processor of an electronic device, enable the electronic device to perform the data processing method according to the first aspect.
The technical scheme provided by the application can comprise the following beneficial effects:
in the present application, an initialization code template set in an auxiliary plug-in is obtained. For any one of the at least one component, the class name of the class to be initialized in the component is obtained in the plug-in file corresponding to the auxiliary plug-in the component. And adding the class name of the class to be initialized in the component in the class name adding bit in the initialization code template to obtain the initialization code of the class to be initialized in the component. And storing the initialization code of the class to be initialized in the component in a sub-list file of the class to be initialized in the component.
By the method and the device, when the initialized attribute and the attribute used for merging to the ContentProvider class are required to be set for the class to be initialized in each component in the application program in the development environment of the application program, codes of the initialized attribute for the class to be initialized in each component in the development environment of the application program do not need to be written for the class to be initialized in each component in the application program, and codes of the attribute used for merging to the ContentProvider class do not need to be written for the class to be initialized in each component in the application program. And only one initialization code template can be set in the development environment and the class name of the class to be initialized in the component can be set in the component, so that the code development amount can be reduced, and the labor cost is further reduced.
Drawings
FIG. 1 is a flow chart of the steps of a data processing method of the present application.
FIG. 2 is a flow chart of the steps of a data processing method of the present application.
Fig. 3 is a block diagram of a data processing apparatus according to the present application.
Fig. 4 is a block diagram of an electronic device of the present application.
FIG. 5 is a block diagram of an electronic device of the present application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description.
Referring to fig. 1, a flowchart of steps of a data processing method according to the present application is shown, and the method is applied to an electronic device, where the electronic device runs a development environment of an application, and the development environment includes a ContentProvider class, an auxiliary plug-in, and at least one component of the application, and each component includes at least one class to be initialized.
In the present application, a developer may start a development environment in an electronic device and develop source code of an application in the development environment.
In one embodiment, a developer has developed a part of source code of an application program in a development environment, the developed source code includes at least one component, each component includes at least one class to be initialized, and the component may include a Library component or the like.
In the application, different classes of functions developed for an application are different, some classes of components need to be initialized in an executable file during the starting process of the executable file of the application, and some classes of components need not be initialized in the executable file during the starting process of the executable file of the application, but are enabled or called only under specific requirements, services or scenes afterwards.
As such, it is desirable to set which classes of components need to be initialized during startup of the executable file and the manner of initialization in the development environment.
As for the initialization method, the class may be initialized by using a ContentProvider class.
In one example, during a development phase, a developer may enter a create request in a development environment of an application to create a ContentProvider class in the development environment of the application. The electronic device may receive the creation request and then create a ContentProvider class in the development environment of the application based on the creation request.
In one embodiment of the present application, part of classes in a component in an application program need to be initialized in an executable file during the starting process of the executable file of the application program, and therefore, which classes in the component need to be initialized during the starting process of the executable file of the application program needs to be set in the development environment of the application program.
Classes to be initialized may include classes in the Library component in the application, and so on.
In order to realize that which classes in the components need to be initialized in the process of starting the executable file of the application program are set in the development environment of the application program, the initialized attributes can be respectively set for the classes to be initialized in each component in the application program in the development environment.
In order to set the initialized property for the class to be initialized in each component in the application program in the development environment, at least two aspects of the following work need to be prepared in the present application.
In one aspect, an auxiliary plug-in is created in a development environment. The auxiliary plug-ins include gradle plug-ins, and the like.
For example, a developer may input a creation request for creating an auxiliary plug-in a development environment of an application program. The electronic device may receive the creation request and then create an auxiliary plug-in a development environment of the application according to the creation request.
In addition, an initialization code template may be set in the auxiliary plug-in.
For example, a developer may enter a setup request in the development environment of an application to set up a second code segment in an initialization code template in an auxiliary plug-in. The electronic device may receive the setup request and then set the second code segment in the initialization code template in the auxiliary plug-in according to the setup request.
The second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that the class corresponding to the class name added on the class name adding bit needs to be initialized.
The class name addition bit is used to add a class name or the like of a class that needs to be initialized.
The class name adding bit and the preset initialization tag can represent the attribute that the class corresponding to the class name added to the class name adding bit needs to be initialized in the process of starting the executable file of the application program.
On the other hand, in the present application, for any one of the at least one component, in the case that the component includes the class to be initialized, an add-in file corresponding to the auxiliary add-in, for example, a build.
For example, a developer may enter a creation request in a development environment of an application to create an add-in file corresponding to an auxiliary add-in the component. The electronic device can receive the creation request and then create an add-in file corresponding to the auxiliary add-in the component according to the creation request.
In addition, a developer can input a setting request for setting the class name of the class to be initialized in the component in the plug-in file corresponding to the auxiliary plug-in the component in the development environment of the application program, and the electronic device can receive the setting request and then set the class name of the class to be initialized in the component in the plug-in file corresponding to the auxiliary plug-in the component according to the setting request.
The same is true for each of the other at least one component.
In the application, since the ContentProvider class needs to be used to complete initialization of the class to be initialized in each component in the executable file of the application, the ContentProvider class and the class to be initialized in each component in the executable file of the application are independent from each other.
Therefore, the class names of the classes to be initialized in the components need to be merged into the ContentProvider class, so that the ContentProvider class can initialize the classes to be initialized in the components in the executable file of the application program according to the class names of the classes to be initialized in the components.
In order to merge the class names of the classes to be initialized in the components into the ContentProvider class, in the present application, it is also necessary to set attributes for merging into the ContentProvider class for the classes to be initialized in the components in the application in the development environment of the application.
In the application, attributes for merging to the ContentProvider class can be set for classes to be initialized in each component in the application program in the development environment of the application program by means of the auxiliary plug-in.
For example, a developer can enter a setup request in the development environment of an application to set up a first code segment in an initialization code template in an auxiliary plug-in. The electronic device may receive the setup request and then set the first code segment in the initialization code template in the auxiliary plug-in according to the setup request.
As such, the initialization code template in the present application includes a first code segment and a second code segment.
The first code segment at least comprises a class name of a ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name of the ContentProvider class.
Wherein, the class name of the ContentProvider class and the preset merge tag may embody the attribute for merging to the ContentProvider class.
Thus, referring to fig. 1, a specific process for setting initialized attributes and attributes for merging into a ContentProvider class for classes to be initialized in each component in an application program in a development environment of the application program may include:
in step S101, an initialization code template set in the auxiliary plug-in is acquired.
The initialization code template includes a first code segment and a second code segment.
The first code segment at least comprises a class name of a ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name of the ContentProvider class.
The second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that the class corresponding to the class name added on the class name adding bit needs to be initialized.
In step S102, for any one of the at least one component, in the plug-in file corresponding to the auxiliary plug-in the component, the class name of the class to be initialized in the component is acquired.
In this application, for any one component in at least one component, the flow of steps S102 to S104 may be executed to achieve the purpose of setting initialized attributes and attributes for merging to the ContentProvider class for the class to be initialized in the component respectively. The same is true for each of the other at least one component.
For any one of the at least one component, the component has an add-in file corresponding to the auxiliary add-in, since the add-in file in the component is the add-in file corresponding to the auxiliary add-in, that is, the add-in file in the component is associated with the auxiliary add-in, the auxiliary add-in has an initialization code template therein, and since the initialization code template includes a second code segment therein, the second code segment includes at least a class name addition bit and a preset initialization tag for indicating that a class corresponding to the class name added on the class name addition bit needs to be initialized. The class name adding bit and the preset initialization tag can reflect the attribute that the class corresponding to the class name added to the class name adding bit needs to be initialized in the process of starting the executable file of the application program.
Thus, it is often stated that the class corresponding to the class name in the component is the class to be initialized, that is, the class corresponding to the class name in the component needs to be initialized in the executable file in the process of starting the executable file of the application program.
In this way, in order to set the initialized attribute and the attribute for merging into the ContentProvider class for the class to be initialized in the component, the class name of the class to be initialized in the component may be obtained in the plug-in file corresponding to the auxiliary plug-in the component, and then step S103 is executed.
In step S103, the class name of the class to be initialized in the component is added to the class name adding bit in the initialization code template, and the initialization code of the class to be initialized in the component is obtained.
The initialization code includes a first code segment and a second code segment.
The first code segment in the initialization code at least comprises a class name of a ContentProvider class and a preset merging tag used for indicating merging to the ContentProvider class according to the class name of the ContentProvider class.
The second code segment in the initialization code at least comprises a class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized.
Through the application, the following association relationship can be realized: "auxiliary plug-in" - "initialization code template" - "plug-in file corresponding to auxiliary plug-in" - "class name of class to be initialized in component".
In this way, the auxiliary plug-in and the plug-in file corresponding to the auxiliary plug-in can associate the initialization code template with the class name of the class to be initialized in the component, that is, the electronic device can know that the class name of the class to be initialized in the component needs to be added to the class name adding bit in the second code segment in the initialization code template.
In this way, the electronic device may add the class name of the class to be initialized in the component in the class name adding bit in the second code segment in the initialization code template, and obtain the initialization code of the class to be initialized in the component.
The initialization code of the class to be initialized in the component may embody an initialized attribute of the class to be initialized in the component and an attribute for merging to the ContentProvider class. Therefore, the purpose of setting initialized attributes and the attributes for merging to the ContentProvider class in the component in the application program in the development environment of the application program is achieved.
In step S104, the initialization code of the class to be initialized in the component is stored in the sub-manifest file of the class to be initialized in the component.
In the present application, an initialization code template set in an auxiliary plug-in is obtained. For any one of the at least one component, the class name of the class to be initialized in the component is obtained in the plug-in file corresponding to the auxiliary plug-in the component. And adding the class name of the class to be initialized in the component in the class name adding bit in the initialization code template to obtain the initialization code of the class to be initialized in the component. And storing the initialization code of the class to be initialized in the component in a sub-list file of the class to be initialized in the component.
By the method and the device, when the initialized attribute and the attribute used for merging to the ContentProvider class are required to be set for the class to be initialized in each component in the application program in the development environment of the application program, codes of the initialized attribute for the class to be initialized in each component in the development environment of the application program do not need to be written for the class to be initialized in each component in the application program, and codes of the attribute used for merging to the ContentProvider class do not need to be written for the class to be initialized in each component in the application program. And only one initialization code template can be set in the development environment and the class name of the class to be initialized in the component can be set in the component, so that the code development amount can be reduced, and the labor cost is further reduced.
In another embodiment of the present application, after the initialization code of the class to be initialized in each component is stored in the sub-manifest file of the class to be initialized in each component, the developer may continue to write source code of other functions of the application program in the development environment.
After a developer writes source code of an application program in a development environment, the source code of the application program developed in the development environment can be compiled to obtain an executable file of the application program. Referring to fig. 2, the specific process is as follows:
in step S201, in a case where an executable file of an application is generated from source code of the application that has been developed in a development environment, whether or not there is initialization code having a preset initialization tag is respectively searched for in sub-manifest files in respective classes in the source code.
The source code of the application program developed in the development environment at least comprises a ContentProvider class, an auxiliary plug-in and at least one component of the application program, wherein each component comprises at least one class to be initialized and the like, and the auxiliary plug-in comprises an initialization code template. Each component comprises a plug-in file corresponding to the auxiliary plug-in, and the plug-in file comprises a class name and the like of a class to be initialized in the component. Of course, it is also possible to include code for other functions of the application, such as other classes that do not need to be initialized during the startup of the executable file of the application, and so on, and will not be described in detail herein.
In the application, after a developer writes source codes of an application program in a development environment, the developer may input a compilation request for compiling the source codes of the application program developed in the development environment into an electronic device, and the electronic device may receive the compilation request and compile the source codes of the application program developed in the development environment according to the compilation request to obtain an executable file of the application program.
The method comprises the steps that initialization codes of classes to be initialized are contained in a sub-list file of the classes to be initialized in the development environment. Which may embody initialized attributes, attributes for merging to the ContentProvider class, etc.
The initialization code of the class to be initialized comprises: a first code segment and a second code segment.
The first code segment at least comprises a class name of a ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name of the ContentProvider class.
The second code segment at least comprises a class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized.
In this way, in the case where the electronic device compiles the source code of the application program that has been developed in the development environment, the classes to be initialized may be looked up in the source code, for example, whether the initialization code having the preset initialization tag exists in the sub-manifest files in the respective classes in the source code, respectively.
For example, for any class in each component in the application program, if an initialization code with a preset initialization tag exists in a sub-manifest file of the class, the class is often a class to be initialized, and if an initialization code with a preset initialization tag does not exist in a sub-manifest file of the class, the class is often not a class to be initialized. The same is true for every other class in the various components in the application.
Therefore, in this step, the electronic device may respectively search whether the initialization code having the preset initialization tag exists in the sub-manifest files in the classes in the source code of the application program developed in the development environment. Then step S202 is performed.
In step S202, a class name of the class to be initialized recorded in the second code segment in the initialization code having the preset initialization tag is obtained, and a class name of the ContentProvider class and a preset merge tag recorded in the first code segment in the initialization code having the preset initialization tag are obtained.
In this application, for any to-be-initialized class in each component in the application program, the class name and the preset merge tag of the ContentProvider class recorded in the first code segment of the initialization code in the sub-manifest file of the to-be-initialized class may be obtained, and the class name of the to-be-initialized class in the second code segment may be obtained.
The above operation is also performed for each other class to be initialized in the respective component in the application.
In step S203, a tag set is generated in the ContentProvider class in the executable file.
In step S204, the obtained class name of each class to be initialized is added to the tag set according to the class name of the ContentProvider class and the preset merge tag.
In this application, for any to-be-initialized class in each component in an application program, it can be known that the class name of the to-be-initialized class needs to be merged into the ContentProvider class corresponding to the class name of the ContentProvider class according to the class name of the ContentProvider class and the preset merge tag recorded in the first code segment of the initialization code in the sub-manifest file of the to-be-initialized class, so that a tag set in the ContentProvider class can be searched according to the class name of the ContentProvider class, and then the class name of the to-be-initialized class is added in the tag set according to the preset merge tag.
The above operation is also performed for each other class to be initialized in the respective component in the application.
Therefore, the tag set of the ContentProvider class has the class name of the class to be initialized in each component in the application program, so that when the executable file of the application program is started and needs to be initialized, the tag set in the ContentProvider class in the executable file can be obtained, the class name of the class to be initialized in each component is obtained in the tag set in the ContentProvider class, the class to be initialized in each component is obtained in the executable file according to the class name of the class to be initialized in each component in the tag set, and the class to be initialized in each component obtained in the executable file is initialized based on the ContentProvider class. Therefore, the tasks of each class to be initialized in the components in the executable file are initialized based on the contentProvider class.
In another embodiment of the present application, in a case where an executable file of an application program is generated from source code of the application program that has been developed in a development environment of the application program, since the executable file is already obtained, an initialization code template set in the development environment of the application program is often no longer effective, and thus, in order to save memory space, at least an auxiliary plug-in may be deleted or an initialization code template may be deleted in the auxiliary plug-in.
In another embodiment of the present application, sometimes the initialization code template may need to be upgraded according to actual requirements, for example, information related to the initialized property needs to be changed, and thus, the code in the initialization code template may be modified.
And under the condition that the initialization code template needs to be upgraded, acquiring a new version of auxiliary plug-in, wherein the new version of auxiliary plug-in has the new version of initialization code template. The new version of the auxiliary plug-in may be entered or downloaded by the user in the electronic device. The new version of the auxiliary plug-in is then used to replace the existing auxiliary plug-in the development environment.
Therefore, the auxiliary plug-in is updated, the initialization code template is updated, a large amount of manual modification is avoided, and therefore efficiency can be improved and labor cost can be reduced.
In another embodiment of the present application, an electronic device runs a development environment of an application, where the development environment includes at least two ContentProvider classes, an auxiliary plug-in, and at least one component of the application, and each component includes at least one class to be initialized; at least two initialization code templates are arranged in the auxiliary plug-in. Different ContentProvider classes correspond to different initialization code templates.
Initializing a code template for any one of the auxiliary plug-ins set; the initialization code template includes a first code segment and a second code segment; the first code segment at least comprises class names of ContentProvider classes corresponding to the initialization code template in at least two ContentProvider classes and preset merging labels used for indicating merging to the ContentProvider classes corresponding to the initialization code template according to the class names of the ContentProvider classes corresponding to the initialization code template; the second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that a class corresponding to the class name added on the class name adding bit needs to be initialized; the same is true for every other initialization code template set in the auxiliary plug-in.
Wherein, the class names of the ContentProvider class in the first code segment in different initialization code templates are different.
For any one component, in the plug-in file corresponding to the auxiliary plug-in the component, the class name of the class to be initialized in the component is obtained, and for each other component, the same is true, so that the class names of a plurality of initialization classes are obtained in total.
The class names of the plurality of initialization classes are divided into more than two class name sets. Each class name set comprises more than two class names respectively, and the class names in different class name sets are not overlapped.
Different types of ContentProvider corresponding to different class name sets are different, and different initialization code templates corresponding to different class name sets are different.
For any one class name set in more than two class name sets, a ContentProvider class corresponding to the class name set and an initialization code template corresponding to the class name set can be determined.
For any class name of a class to be initialized in the class name set, adding the class name of the class to be initialized in a class name adding position in the initialization code template to obtain an initialization code of the class to be initialized; the initialization code of the class to be initialized comprises a first code segment and a second code segment; the first code segment in the initialization code at least comprises class names of the ContentProvider classes corresponding to the class name set and preset merging labels used for indicating merging of the ContentProvider classes corresponding to the class name set according to the class names of the ContentProvider classes corresponding to the class name set; the second code segment in the initialization code at least comprises the class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized; and then storing the initialization code of the class to be initialized in the sub-list file of the class to be initialized. The above operation is also performed for each other class name of the class to be initialized in the class name set.
The above operation is also performed for each of the other two or more sets of class names.
It is noted that, for simplicity of explanation, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will appreciate that the present application is not limited by the order of acts, as some steps may, in accordance with the present application, occur in other orders and concurrently. Further, those skilled in the art will also appreciate that the embodiments described in the specification are exemplary and that no action is necessarily required in this application.
Referring to fig. 3, a block diagram of a data processing apparatus according to the present application is shown, and is applied to an electronic device, where the electronic device runs a development environment of an application program, where the development environment includes at least one content provider ContentProvider class, an auxiliary plug-in, and at least one component of the application program, and each component includes at least one class to be initialized; the device comprises:
a first obtaining module 11, configured to obtain an initialization code template set in the auxiliary plug-in; the initialization code template includes a first code segment and a second code segment; the first code segment at least comprises a class name of the ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name; the second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that a class corresponding to the class name added on the class name adding bit needs to be initialized;
a second obtaining module 12, configured to, for any one of the at least one component, obtain, in an add-in file corresponding to the auxiliary add-in the component, a class name of a class to be initialized in the component;
a first adding module 13, configured to add a class name of a class to be initialized in the component to a class name adding bit in the initialization code template, so as to obtain an initialization code of the class to be initialized in the component; the initialization code comprises a first code segment and a second code segment; the first code segment in the initialization code at least comprises the class name of the ContentProvider class and a preset merging tag used for indicating merging to the ContentProvider class according to the class name of the ContentProvider class; the second code segment in the initialization code at least comprises the class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized;
a storage module 14, configured to store the initialization code of the class to be initialized in the component in the sub-manifest file of the class to be initialized in the component.
In an optional implementation, the apparatus further comprises:
the first setting module is used for creating an auxiliary plug-in the development environment and setting the initialization code template in the auxiliary plug-in;
and the number of the first and second groups,
and the second setting module is used for creating an plugin file corresponding to the auxiliary plugin in the component for any one of the at least one component, and setting the class name of the class to be initialized in the component in the plugin file.
In an optional implementation, the apparatus further comprises:
a deletion module configured to delete the auxiliary plug-in or delete the initialization code template in the auxiliary plug-in when an executable file of the application is generated from source code of the application that has been developed in the development environment.
In an optional implementation, the apparatus further comprises:
the third acquisition module is used for acquiring a new version of auxiliary plug-in unit under the condition that the initialization code template needs to be updated, wherein the new version of auxiliary plug-in unit has a new version of initialization code template;
a replacement module for replacing an existing auxiliary plug-in the development environment with a new version of the auxiliary plug-in.
In an optional implementation, the apparatus further comprises:
the searching module is used for respectively searching whether the initialization code with the preset initialization tag exists in the sub-list files in each class in the source code under the condition that the executable file of the application program is generated according to the source code of the application program developed in the development environment;
a fourth obtaining module, configured to obtain a class name of a class to be initialized recorded in the second code segment in the initialization code stored in the preset initialization tag, and obtain a class name of the ContentProvider class and the preset merge tag recorded in the first code segment in the initialization code stored in the preset initialization tag;
a generating module, configured to generate a tag set in the ContentProvider class in the executable file;
and the second adding module is used for adding the acquired class name of each class to be initialized in the tag set according to the class name of the ContentProvider class and the preset merging tag.
In the present application, an initialization code template set in an auxiliary plug-in is obtained. For any one of the at least one component, the class name of the class to be initialized in the component is obtained in the plug-in file corresponding to the auxiliary plug-in the component. And adding the class name of the class to be initialized in the component in the class name adding bit in the initialization code template to obtain the initialization code of the class to be initialized in the component. And storing the initialization code of the class to be initialized in the component in a sub-list file of the class to be initialized in the component.
By the method and the device, when the initialized attribute and the attribute used for merging to the ContentProvider class are required to be set for the class to be initialized in each component in the application program in the development environment of the application program, codes of the initialized attribute for the class to be initialized in each component in the development environment of the application program do not need to be written for the class to be initialized in each component in the application program, and codes of the attribute used for merging to the ContentProvider class do not need to be written for the class to be initialized in each component in the application program. And only one initialization code template can be set in the development environment and the class name of the class to be initialized in the component can be set in the component, so that the code development amount can be reduced, and the labor cost is further reduced.
For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
Fig. 4 is a block diagram of an electronic device 800 shown in the present application. For example, the electronic device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.
Referring to fig. 4, electronic device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and a communication component 816.
The processing component 802 generally controls overall operation of the electronic device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.
The memory 804 is configured to store various types of data to support operation at the device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, images, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The power supply component 806 provides power to the various components of the electronic device 800. The power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the electronic device 800.
The multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the rear-facing camera may receive external multimedia data when the device 800 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.
The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the electronic device 800. For example, the sensor assembly 814 may detect an open/closed state of the device 800, the relative positioning of components, such as a display and keypad of the electronic device 800, the sensor assembly 814 may also detect a change in the position of the electronic device 800 or a component of the electronic device 800, the presence or absence of user contact with the electronic device 800, orientation or acceleration/deceleration of the electronic device 800, and a change in the temperature of the electronic device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 816 is configured to facilitate wired or wireless communication between the electronic device 800 and other devices. The electronic device 800 may access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives broadcast signals or broadcast operation information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the electronic device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the electronic device 800 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Fig. 5 is a block diagram of an electronic device 1900 shown in the present application. For example, the electronic device 1900 may be provided as a server.
Referring to fig. 5, electronic device 1900 includes a processing component 1922 further including one or more processors and memory resources, represented by memory 1932, for storing instructions, e.g., applications, executable by processing component 1922. The application programs stored in memory 1932 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1922 is configured to execute instructions to perform the above-described method.
The electronic device 1900 may also include a power component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input/output (I/O) interface 1958. The electronic device 1900 may operate based on an operating system stored in memory 1932, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, or the like.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The foregoing detailed description is directed to a data processing method, an apparatus, an electronic device, and a storage medium provided by the present application, and specific examples are applied in the present application to explain the principles and implementations of the present application, and the descriptions of the foregoing examples are only used to help understand the method and the core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims (12)

1. A data processing method is characterized in that the method is applied to electronic equipment, the electronic equipment runs a development environment of an application program, the development environment comprises at least one content provider ContentProvider class, an auxiliary plug-in and at least one component of the application program, and each component comprises at least one class to be initialized; the method comprises the following steps:
acquiring an initialization code template set in the auxiliary plug-in; the initialization code template includes a first code segment and a second code segment; the first code segment at least comprises a class name of the ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name; the second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that a class corresponding to the class name added on the class name adding bit needs to be initialized;
for any one of the at least one component, acquiring a class name of a class to be initialized in the component in an add-in file corresponding to the auxiliary add-in the component;
adding the class name of the class to be initialized in the component in the class name adding position in the initialization code template to obtain the initialization code of the class to be initialized in the component; the initialization code comprises a first code segment and a second code segment; the first code segment in the initialization code at least comprises the class name of the ContentProvider class and a preset merging tag used for indicating merging to the ContentProvider class according to the class name of the ContentProvider class; the second code segment in the initialization code at least comprises the class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized;
and storing the initialization code of the class to be initialized in the component in a sub-list file of the class to be initialized in the component.
2. The method of claim 1, further comprising:
creating an auxiliary plug-in the development environment, and setting the initialization code template in the auxiliary plug-in;
and the number of the first and second groups,
and for any one of the at least one component, creating an add-in file corresponding to the auxiliary add-in the component, and setting the class name of the class to be initialized in the component in the add-in file.
3. The method of claim 1, further comprising:
in the case where an executable file of the application program is generated from source code of the application program that has been developed in the development environment, the auxiliary plug-in is deleted or the initialization code template is deleted in the auxiliary plug-in.
4. The method of claim 1, further comprising:
under the condition that the initialization code template needs to be updated, acquiring a new version of auxiliary plug-in, wherein the new version of auxiliary plug-in has the new version of initialization code template;
replacing existing auxiliary plug-ins in the development environment with new versions of auxiliary plug-ins.
5. The method of claim 1, further comprising:
in the case of generating an executable file of the application program according to source codes of the application program developed in the development environment, respectively searching whether an initialization code with the preset initialization tag exists in sub-manifest files in various classes in the source code;
acquiring a class name of a class to be initialized recorded in a second code segment in the initialization code with the preset initialization tag, and acquiring a class name of the ContentProvider class and the preset merging tag recorded in a first code segment in the initialization code with the preset initialization tag;
generating a tag set in the ContentProvider class in the executable file;
and adding the acquired class name of each class to be initialized in the tag set according to the class name of the ContentProvider class and the preset merging tag.
6. A data processing device is characterized in that the data processing device is applied to electronic equipment, the electronic equipment runs a development environment of an application program, the development environment comprises at least one content provider ContentProvider class, an auxiliary plug-in and at least one component of the application program, and each component comprises at least one class to be initialized; the device comprises:
the first acquisition module is used for acquiring an initialization code template set in the auxiliary plug-in; the initialization code template includes a first code segment and a second code segment; the first code segment at least comprises a class name of the ContentProvider class and a preset merging label for indicating merging to the ContentProvider class according to the class name; the second code segment at least comprises a class name adding bit and a preset initialization tag used for indicating that a class corresponding to the class name added on the class name adding bit needs to be initialized;
a second obtaining module, configured to, for any one of the at least one component, obtain, in an add-in file corresponding to the auxiliary add-in the component, a class name of a class to be initialized in the component;
a first adding module, configured to add a class name of a class to be initialized in the component to a class name adding bit in the initialization code template, so as to obtain an initialization code of the class to be initialized in the component; the initialization code comprises a first code segment and a second code segment; the first code segment in the initialization code at least comprises the class name of the ContentProvider class and a preset merging tag used for indicating merging to the ContentProvider class according to the class name of the ContentProvider class; the second code segment in the initialization code at least comprises the class name of the class to be initialized and a preset initialization tag used for indicating that the class corresponding to the class name of the class to be initialized needs to be initialized;
and the storage module is used for storing the initialization code of the class to be initialized in the component in the sub-list file of the class to be initialized in the component.
7. The apparatus of claim 6, further comprising:
the first setting module is used for creating an auxiliary plug-in the development environment and setting the initialization code template in the auxiliary plug-in;
and the number of the first and second groups,
and the second setting module is used for creating an plugin file corresponding to the auxiliary plugin in the component for any one of the at least one component, and setting the class name of the class to be initialized in the component in the plugin file.
8. The apparatus of claim 6, further comprising:
a deletion module configured to delete the auxiliary plug-in or delete the initialization code template in the auxiliary plug-in when an executable file of the application is generated from source code of the application that has been developed in the development environment.
9. The apparatus of claim 6, further comprising:
the third acquisition module is used for acquiring a new version of auxiliary plug-in unit under the condition that the initialization code template needs to be updated, wherein the new version of auxiliary plug-in unit has a new version of initialization code template;
a replacement module for replacing an existing auxiliary plug-in the development environment with a new version of the auxiliary plug-in.
10. The apparatus of claim 6, further comprising:
the searching module is used for respectively searching whether the initialization code with the preset initialization tag exists in the sub-list files in each class in the source code under the condition that the executable file of the application program is generated according to the source code of the application program developed in the development environment;
a fourth obtaining module, configured to obtain a class name of a class to be initialized recorded in the second code segment in the initialization code stored in the preset initialization tag, and obtain a class name of the ContentProvider class and the preset merge tag recorded in the first code segment in the initialization code stored in the preset initialization tag;
a generating module, configured to generate a tag set in the ContentProvider class in the executable file;
and the second adding module is used for adding the acquired class name of each class to be initialized in the tag set according to the class name of the ContentProvider class and the preset merging tag.
11. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to perform the data processing method of any one of claims 1-5.
12. A non-transitory computer readable storage medium, instructions in which, when executed by a processor of an electronic device, enable the electronic device to perform the data processing method of any one of claims 1-5.
CN202111427879.4A 2021-11-26 2021-11-26 Data processing method and device, electronic equipment and storage medium Pending CN114115862A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111427879.4A CN114115862A (en) 2021-11-26 2021-11-26 Data processing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111427879.4A CN114115862A (en) 2021-11-26 2021-11-26 Data processing method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN114115862A true CN114115862A (en) 2022-03-01

Family

ID=80370667

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111427879.4A Pending CN114115862A (en) 2021-11-26 2021-11-26 Data processing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114115862A (en)

Similar Documents

Publication Publication Date Title
CN109032606B (en) Native application compiling method and device and terminal
CN110704053B (en) Style information processing method and device
CN111221613A (en) Program calling method and device and storage medium
CN107368562B (en) Page display method and device and terminal
CN113128181B (en) Information processing method and device
CN113590091A (en) Data processing method and device, electronic equipment and storage medium
CN110457084B (en) Loading method and device
CN114115862A (en) Data processing method and device, electronic equipment and storage medium
CN108549570B (en) User interface updating method and device
CN108427568B (en) User interface updating method and device
CN111596949B (en) Method and device for developing application program
CN113934452B (en) Data processing method and device, electronic equipment and storage medium
CN110673850A (en) Method and device for obtaining size of static library
CN114115863A (en) Data processing method and device, electronic equipment and storage medium
CN114020504B (en) Data processing method and device, electronic equipment and storage medium
CN111625251B (en) Method and device for processing application instance
CN113946346B (en) Data processing method and device, electronic equipment and storage medium
CN116126320B (en) Data processing method and device, electronic equipment and storage medium
CN111273910B (en) Method, device and storage medium for acquiring resource number identifier
CN113778440B (en) Data processing method and device, electronic equipment and storage medium
CN114528037B (en) Application starting method and device, electronic equipment and storage medium
CN111241097B (en) Method for processing object, device for processing object and storage medium
CN115809054A (en) Data processing method and device, electronic equipment and storage medium
CN114416085A (en) Data processing method and device, electronic equipment and storage medium
CN116400925A (en) Data processing method and device, electronic 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