CN113127010B - Application management method and device, electronic equipment and storage medium - Google Patents
Application management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113127010B CN113127010B CN201911414874.0A CN201911414874A CN113127010B CN 113127010 B CN113127010 B CN 113127010B CN 201911414874 A CN201911414874 A CN 201911414874A CN 113127010 B CN113127010 B CN 113127010B
- Authority
- CN
- China
- Prior art keywords
- target application
- global variable
- application
- target
- preset
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 63
- 244000035744 Hura crepitans Species 0.000 claims abstract description 74
- 238000000034 method Methods 0.000 claims abstract description 30
- 238000004590 computer program Methods 0.000 claims description 10
- 238000000605 extraction Methods 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000002347 injection Methods 0.000 description 2
- 239000007924 injection Substances 0.000 description 2
- 239000000243 solution Substances 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/62—Uninstallation
Abstract
The embodiment of the application provides an application management method, an application management device, electronic equipment and a storage medium, wherein the method comprises the following steps: acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application; extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information; determining the first global variable as a current global variable so as to mount the first target application; when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application. The application can effectively reduce the interference of each target application in the use process and is convenient to manage.
Description
Technical Field
The present application relates to the field of application management technologies, and in particular, to an application management method, an application management device, an electronic device, and a storage medium.
Background
The front-end engineering of many background management systems is currently based on SPA (Single Page Application, single page application program) application of a certain front-end framework, and has great defects in the following application scenarios: 1. integrating multiple applications into one application, which can only reconstruct applications of different frameworks, unifying the applications into one framework, has huge development time consumption, and all reconstructed functional details need secondary detailed test. 2. A large application needs to be developed, that is, the use frames of all developers need to be unified, and support staff or new recruiters crossing technical departments may not need to be provided with the frames, so that lead time and cost of learning, training and the like are brought, and project development time is prolonged. When integrating a plurality of applications developed by different frameworks into one application, the above-mentioned drawbacks can be solved, but after integrating a plurality of applications developed by different frameworks into one application in the existing integration technology, interference exists between each application in the use process and management is inconvenient.
Disclosure of Invention
The embodiment of the application provides an application management method, which can effectively reduce the interference of each target application in the use process and is convenient to manage.
In a first aspect, an embodiment of the present application provides an application management method, including:
acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
determining the first global variable as a current global variable so as to mount the first target application;
when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application.
Preferably, the method further comprises:
presetting a corresponding first preset sandbox for the first target application, wherein the first preset sandbox is used for storing the first global variable;
and presetting a corresponding second preset sandbox for the second target application, wherein the second preset sandbox is used for storing the second global variable.
Preferably, before the step of changing the first global variable to the second global variable to mount the second target application corresponding to the second global variable when the first target application is unloaded, the method includes:
judging whether second mounting request information for mounting a second target application is received or not, wherein the second mounting information comprises second target application information corresponding to the second target application;
when the second mounting request information is received, returning the first global variable to the first preset sandbox for storage so as to unload the first target application;
and extracting the second global variable from the second preset sandbox according to the second target application information.
Preferably, before the determining the first global variable as the current global variable to mount the first target application, the method further includes the following steps:
and calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information so as to apply the first style to the first target application.
Preferably, before the first global variable is changed to a second global variable to mount a second target application corresponding to the second global variable, the method further includes the following steps:
and calling a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
Preferably, the method further comprises the steps of:
presetting the corresponding first hypertext markup language and the first style corresponding to the first hypertext markup language for the first target application, and storing the first hypertext markup language and the first style;
and presetting the second hypertext markup language and the second style corresponding to the second hypertext markup language for the second target application, and storing the second hypertext markup language and the second style.
In a second aspect, an embodiment of the present application further provides an application management apparatus, where the application management apparatus includes:
the first acquisition module is used for acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
the first extraction module is used for extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
the first mounting module is used for determining the first global variable as a current global variable so as to mount the first target application;
and the second mounting module is used for changing the first global variable into a second global variable when the first target application is unloaded so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application.
Preferably, the application management device further includes:
the first preset module is used for presetting the corresponding first preset sandbox for the first target application, and the first preset sandbox is used for storing the first global variable;
the second preset module is configured to preset a corresponding second preset sandbox for the second target application, where the second preset sandbox is used to store the second global variable.
In a third aspect, an embodiment of the present application further provides an electronic device, including: the system comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the steps in the application management method provided in the embodiment when executing the computer program.
In a fourth aspect, an embodiment of the present application further provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the application management method provided in the above embodiment.
In the embodiment of the application, by acquiring the first mounting request information for mounting the first target application, the first mounting request information carries first target application information corresponding to the first target application; extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information; determining the first global variable as a current global variable so as to mount the first target application; when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application. Each target application is provided with a sandbox for storing the corresponding global variable, and the corresponding global variable can be extracted from the sandbox for use when the target application is mounted. When another target application needs to be mounted, the global variable of the currently mounted target application is directly replaced by another global variable corresponding to the other target application, and free switching between the two target applications can be achieved. In the switching process of two different global variables, no interference exists between the global variables, and the mounting and the unloading of the other party are not affected. And further, the interference of each target application in the use process can be effectively reduced, and the management is convenient.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a diagram of a system architecture according to an embodiment of the present application;
FIG. 2 is a flowchart of an application management method according to an embodiment of the present application;
FIG. 3 is a flowchart of another method for application management provided by an embodiment of the present application;
FIG. 4 is a flow chart of yet another method of application management provided by an embodiment of the present application;
FIG. 5 is a flowchart of another method for application management provided by an embodiment of the present application;
fig. 6 is a schematic structural diagram of an application management device according to an embodiment of the present application;
FIG. 7 is a schematic diagram of another application management device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of still another application management device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of another application management device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
For more clearly explaining the technical solution of the present application, as shown in fig. 1, fig. 1 is a system architecture diagram provided in an embodiment of the present application, where the system architecture 100 may include a browser 101; a host application 102; a first target application 103 and a second target application 104 integrated in the host application 102; a first service 105 corresponding to a first target application 103; and a second service 106 corresponding to the second target application 104. The host application 102 is configured to switch and manage between the first target application 103 and the second target application 104 according to the request information sent by the browser 101, and a user may access, through the browser 101, a first service 105 and a second service 106 provided by the first target application 103 and the second target application 104.
The first target application 103 and the second target application 104 may be provided in various electronic devices or terminals having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, electronic book readers, MP3 players (Moving Picture Experts Group Audio Layer III, dynamic video expert compression standard audio plane 3), MP4 (Moving Picture Experts Group Audio Layer IV, dynamic video expert compression standard audio plane 4) players, laptop and desktop computers, and the like. The first service 105 and the second service 106 may be set in servers corresponding to the electronic devices or terminals where the first target application 103 and the second target application 104 are located. Various communication client applications may be installed in an electronic device or terminal, such as a web browser application, a shopping class application, a search class application, an instant messaging tool, a mailbox client, social platform software, a management class application, and the like.
It should be noted that, the application management method provided in the embodiment of the present application is generally executed by the host application 102, and accordingly, the application management device corresponds to the host application 102.
It should be appreciated that browser 101 in FIG. 1; a host application 102; a first target application 103 and a second target application 104 integrated in the host application 102; the number of first services 105 corresponding to the first target application 103 and second services 106 corresponding to the second target application 104 is merely illustrative. Any number of browsers 101 may be present, as desired for implementation; a host application 102; a first target application 103 and a second target application 104 integrated in the host application 102; a first service 105 corresponding to the first target application 103 and a second service 106 corresponding to the second target application 104. In general, a target application corresponds to a service, that is, the target application corresponds to the service it provides one-to-one.
Note that, the application management apparatus, the first target application 103, and the second target application 104 mentioned in the following embodiments may each correspond to the host application 102, the first target application 103, and the second target application 104 in fig. 1.
The first target application 103 in the following embodiment is an application that the user currently wants to access, and the second target application 104 is an application that the user next wants to access, so in order to distinguish between accessing different applications, two different applications are called a first target application 103 and a second target application 104, respectively. However, if three different applications are accessed sequentially, the first accessed application is referred to as a first target application 103, the second accessed application is referred to as a second target application 104, the third accessed application is referred to as a third target application, and so on, if multiple applications are accessed sequentially, naming can be performed sequentially. But the first target application 103, the second target application 104, and the third target application may all be replaced with each other. The first target application 103 and the second target application 104 may be directly used to replace two different target applications, so the names of the respective target applications are not limited.
Referring to fig. 2, fig. 2 is a flowchart of an application management method according to an embodiment of the present application, as shown in fig. 2, including the following steps:
step 201, obtaining first mounting request information for mounting a first target application, where the first mounting request information carries first target application information corresponding to the first target application.
The above-mentioned mounting may be referred to as loading or mounting, and when a certain application is mounted, the application may be accessed by other users and the service of the application may be used. It may also be stated that the application may provide the service normally. The first target application may be an application that the user is currently accessing. The first mounting request information is used for requesting to mount request information of the first target application. The first target application information may include routing information, identification information, and the like of the first target application.
Specifically, when the user wants to access the service of the first target application, the user can edit the first mounting request information for mounting the first target application through the browser and send the first mounting request information to the main application, and at this time, the main application can receive the first mounting request information. After the host application receives the first mounting request information, it knows which application the user wants to access the service according to the first target application information, and step 102 may be performed subsequently.
Step 202, extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information.
The sandbox is used for creating a region in the main application to store global variables used by different target applications and is provided with identifications corresponding to the target applications. The first preset sandbox is preset, specifically, before step 201, a corresponding first preset sandbox is preset for the first target application, where the first preset sandbox carries the identifier of the first target application. The first preset sandbox is for storing a first global variable. The first global variable is a global variable used in the implementation process of the first target application. The first global variable is also preset. The global variable may be created by an object function of an application or may be created anywhere in the application program. A global variable is a function or object that can be referenced by all objects or functions of the application. To this end, each application is provided with its own global variable, and each global variable may be provided with its own name, e.g. the global variables used in the first target application may be denoted by a, b, c and/or d, etc., and the first global variable may comprise one or more variables. Of course, each application is also set with its own local variable (which may be referred to as a run variable), which may also be referred to as an internal variable, relative to the global variable. Variables created by an object or function of an application are typically local variables that can only be referenced internally and cannot be referenced by other objects or functions.
Specifically, after the host application receives the first mounting request information, the target application to be specifically accessed by the user can be determined according to the routing information, the identification information, or the like in the first target application information carried in the first mounting request information, that is, the target application to be accessed by the user is determined to be the first target application, for example, the routing information of the first target application is determined to be the routing 1, and when the routing information of the routing 1 is carried in the first mounting request information, the user can know that the user wants to access the first target application. At this time, the first target application should be installed, that is, the first global variable of the first target application is extracted from the first preset sandbox corresponding to the first target application.
Step 203, determining the first global variable as the current global variable to mount the first target application.
The current global variable is a global variable being mounted on the global, and may also be a global variable corresponding to the target application being mounted.
Specifically, to mount the first target application, only the first global variable corresponding to the first target application is hung on the global to be changed into the current variable. For example, if the second target application is to be installed, the second global variable corresponding to the second target application may be installed to be globally changed into the current global variable. If other target applications are in the mounting state, the global variable which is mounted on the global before the target application is mounted can be replaced.
And 204, when the first target application is unloaded, changing the first global variable into the second global variable so as to mount the second target application corresponding to the second global variable.
Wherein, the unloading may mean that the target application is not accessed and the target application is from the mounting to the off-line. The second preset sandbox is preset, and the second global variable is stored in the second preset sandbox corresponding to the second target application. Specifically, before step 201, a corresponding second preset sandbox is preset for the second target application, where the second preset sandbox carries the identifier of the second target application. The second preset sandbox is for storing a second global variable. The second global variable is a global variable used in the implementation process of the second target application. The second global variable is also preset, and may include one or more variables.
Specifically, in step 203, the first target application is being installed, and when the user wants to access the service of the second target application, the main application needs to switch the first target application being installed to the second target application for installation, at this time, the first target application needs to be unloaded, and at the same time, the second application needs to be installed. Therefore, the second target application can be mounted by replacing the first global variable which is being mounted on the global with the second global variable corresponding to the second target application.
It should be noted that, in the prior art, each target application has its own global variable, and when the number of target applications is multiple, or multiple target applications are developed in the same manner, or multiple target applications are developed for the same developer, the same identifier, such as the same letter, symbol, etc., is used when naming the global variable of each target application. There is no effect when each target application is used alone, but once multiple target applications are integrated together for use, global variable interference exists when multiple target applications are used due to the fact that the names of the global variables of each target application are identical.
In the embodiment of the application, by acquiring the first mounting request information for mounting the first target application, the first mounting request information carries first target application information corresponding to the first target application; extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information; determining a first global variable as a current global variable to mount a first target application; when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application. Each target application is provided with a sandbox for storing the corresponding global variable, and the corresponding global variable can be extracted from the sandbox for use when the target application is mounted. When another target application needs to be mounted, the global variable of the currently mounted target application is directly replaced by another global variable corresponding to the other target application, and free switching between the two target applications can be achieved. In the switching process of two different global variables, no interference exists between the global variables, and the mounting and the unloading of the other party are not affected. And further, the interference of each target application in the use process can be effectively reduced, and the management is convenient.
Optionally, referring to fig. 3, fig. 3 is a flowchart of another application management method provided in an embodiment of the present application, on the basis of fig. 2, before step 104, the application management method further includes the steps of:
step 301, determining whether second mounting request information for mounting a second target application is received, where the second mounting information includes second target application information corresponding to the second target application.
And 302, returning the first global variable to a first preset sandbox for storage when receiving the second mounting request information so as to unload the first target application.
And 303, extracting a second global variable from a second preset sandbox according to the second target application information.
The second mounting request information is used for requesting to mount request information of a second target application. The second target application information may include route information identification information of the second target application, and the like.
Specifically, when the first target application is in the mounting period, if the main application receives the second mounting request information, the target application to be specifically accessed by the user can be determined according to the routing information, the identification information, or the like in the second target application information carried in the second mounting request information, that is, the target application to be accessed by the user is determined to be the second target application, for example, the routing information of the second target application is determined to be the routing 2, and when the routing information of the routing 2 is carried in the second mounting request information, the user can know that the user wants to access the second target application. At this time, the first target application needs to be unloaded first, and then the first global variable corresponding to the first target application is unloaded globally and returned to the corresponding first preset sandbox for storage, so that when the first target application is mounted next time, the corresponding first global variable can be extracted from the first preset sandbox again, and further the re-mounting of the first target application is realized.
When the first target application is unloaded, a corresponding second global variable is extracted from a second preset sandbox corresponding to the second target application, so that the second global variable is convenient to be subsequently hung on the global to be changed into a current global variable, the second target application is mounted, and the user can conveniently access the second global variable.
When the second target application is unloaded, the corresponding second global variable can be returned to the corresponding second preset sandbox from the global to be stored, so that the corresponding second global variable can be extracted from the second preset sandbox again when the second target application is mounted next time, and further the second target application is mounted again.
In the embodiment of the application, the alternate mounting between two different target applications can be realized, and when each target application is unloaded, the corresponding global variable can be returned to the corresponding preset sandbox for storage, so that the subsequent extraction and use during re-mounting are facilitated.
Optionally, referring to fig. 4, fig. 4 is a flowchart of another application management method provided in an embodiment of the present application, and on the basis of fig. 2, before step 203, the application management method further includes the following steps:
step 401, calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information, so as to apply the first style to the first target application.
Wherein the hypertext markup language may be html (HyperText Markup Language). The first hypertext markup language is a hypertext markup language corresponding to a first target application. Each target application is provided with its own html. The style is an application style of the target application, and the first style is a style corresponding to the first target application. The style of each target application is injected through its corresponding html. And the html corresponding to each target application is unique.
Specifically, after determining that the target application to be accessed by the user is the first target application, the first hypertext markup language of the first target application pair can be directly called, and then the corresponding first mode is loaded on the first target application through the injection of the first hypertext markup language.
It should be noted that, the first hypertext markup language and the first format are both preset. Specifically, a corresponding first hypertext markup language and a first style corresponding to the first hypertext markup language are preset for a first target application, and the first hypertext markup language and the first style are stored.
In the prior art, each target application has its own style, and when the number of target applications is multiple, or multiple target applications are developed in the same manner, or multiple target applications are developed for the same developer, it is inevitable to use the same identifier, such as the same letter, symbol, etc., when naming the style of each target application. When each target application is used alone, there is no influence, but once a plurality of target applications are integrated together for use, pattern interference exists between patterns of each target application due to the same name or the like when a plurality of target applications are used.
In the embodiment of the application, the first hypertext markup language and the first mode of the first target application can be independently used, and the first mode is loaded onto the first target application through the first hypertext markup language. Since the hypertext markup language of each target application is unique, style interference among a plurality of target applications can be avoided, and global variable interference among a plurality of target applications can be avoided.
Preferably, referring to fig. 5, fig. 5 is a flowchart of another application management method provided in an embodiment of the present application, and on the basis of fig. 4, before step 204, the application management method further includes the following steps:
step 501, calling a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
Wherein the second hypertext markup language is a hypertext markup language corresponding to the second target application. The second pattern is a pattern corresponding to the second target application.
Specifically, after determining that the target application to be accessed by the user is the second target application, the second hypertext markup language of the second target application pair may be directly called, and then the second style corresponding to the second hypertext markup language is loaded onto the second target application through injection of the second hypertext markup language.
It should be noted that, the second hypertext markup language and the second style are both preset. Specifically, a second hypertext markup language and a second style corresponding to the second hypertext markup language are preset for a second target application, and the second hypertext markup language and the second style are saved.
In the embodiment of the application, the second hypertext markup language and the second style of the second target application can be independently used, and the second style is loaded onto the second target application through the second hypertext markup language. Since the hypertext markup language of each target application is unique, style interference between the first target application and the second target application can be avoided. Style interference of multiple target applications can be further avoided, and global variable interference among multiple target applications can be avoided.
Referring to fig. 6, fig. 6 is a schematic structural diagram of an application management device according to an embodiment of the present application, and as shown in fig. 6, the application management device 600 includes:
the first obtaining module 601 is configured to obtain first mounting request information for mounting a first target application, where the first mounting request information carries first target application information corresponding to the first target application.
The first extraction module 602 is configured to extract, according to the first target application information, a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application.
The first mounting module 603 is configured to determine the first global variable as a current global variable, so as to mount the first target application.
And the second mounting module 604 is configured to change the first global variable to a second global variable when the first target application is unloaded, so as to mount a second target application corresponding to the second global variable, where the second global variable is stored in a second preset sandbox corresponding to the second target application.
Optionally, on the basis of fig. 6, before the first acquisition module, the application management device 600 further includes:
the first preset module is used for presetting a corresponding first preset sandbox for the first target application, and the first preset sandbox is used for storing a first global variable;
the second preset module is used for presetting a corresponding second preset sandbox for the second target application, and the second preset sandbox is used for storing a second global variable.
Referring to fig. 7 and fig. 7, fig. 7 is a schematic structural diagram of another application management device according to an embodiment of the present application, on the basis of fig. 6, before the second mounting module 603, the application management device 600 further includes:
a judging module 605, configured to judge whether second mounting request information for mounting a second target application is received, where the second mounting information includes second target application information corresponding to the second target application;
the unloading module 606 is configured to return, when receiving the second mounting request information, the first global variable to the first preset sandbox for saving, so as to unload the first target application;
and a second extraction module 607, configured to extract a second global variable from a second preset sandbox according to the second target application information.
Referring to fig. 8, fig. 8 is a schematic structural diagram of another application management device according to an embodiment of the present application, on the basis of fig. 6, before the first mounting module 603, the application management device 600 further includes:
the first calling module 608 is configured to call a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information, so as to apply the first style to the first target application.
Referring to fig. 9, fig. 9 is a schematic structural diagram of another application management device according to an embodiment of the present application, on the basis of fig. 8, before the second mounting module, the application management device 600 further includes:
a second invoking module 609 is configured to invoke a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
Optionally, on the basis of fig. 9, the application management device 600 further includes:
the third preset module is used for presetting a corresponding first hypertext markup language and a first style corresponding to the first hypertext markup language for the first target application and storing the first hypertext markup language and the first style;
and the fourth preset module is used for presetting a corresponding second hypertext markup language and a second style corresponding to the second hypertext markup language for the second target application and storing the second hypertext markup language and the second style.
The application management device 600 provided in the embodiment of the present application can implement each implementation manner in the above method embodiment, and corresponding beneficial effects, and in order to avoid repetition, a detailed description is omitted here.
Referring to fig. 10, fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application, where the electronic device 700 includes: the memory 702, the processor 701 and the computer program stored in the memory 702 and executable on the processor 701, the processor 701 implements the steps in the application management method provided in the above embodiment when the processor 701 executes the computer program, and the processor 701 performs the following steps:
acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
determining a first global variable as a current global variable to mount a first target application;
when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application.
Optionally, the processor 701 further performs the steps of:
the method further comprises the steps of:
presetting a corresponding first preset sandbox for a first target application, wherein the first preset sandbox is used for storing a first global variable;
and presetting a corresponding second preset sandbox for the second target application, wherein the second preset sandbox is used for storing a second global variable.
Optionally, before the step executed by the processor 701 of changing the first global variable to the second global variable to mount the second target application corresponding to the second global variable when the first target application is uninstalled, the processor 701 further executes the following steps:
judging whether second mounting request information for mounting a second target application is received or not, wherein the second mounting information comprises second target application information corresponding to the second target application;
when receiving the second mounting request information, returning the first global variable to a first preset sandbox for storage so as to unload the first target application;
and extracting a second global variable from a second preset sandbox according to the second target application information.
Optionally, before the processor 701 determines the first global variable as the current global variable to mount the first target application, the processor 701 further performs the following steps:
and calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information so as to apply the first style to the first target application.
Optionally, before the processor 701 performs changing the first global variable to the second global variable to mount the second target application corresponding to the second global variable, the processor 701 further performs the following steps:
and calling a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
Optionally, the processor 701 further performs the steps of:
presetting a corresponding first hypertext markup language and a first style corresponding to the first hypertext markup language for a first target application, and storing the first hypertext markup language and the first style;
and presetting a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language, and storing the second hypertext markup language and the second style.
It should be noted that, the electronic device 700 may be a smart terminal, a mobile phone, a tablet computer, or other devices of an application management system.
The electronic device 700 provided in the embodiment of the present application can implement each implementation manner and corresponding beneficial effects in the foregoing method embodiment, and in order to avoid repetition, details are not repeated here.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements each process of the application management method provided by the embodiment of the application, and can achieve the same technical effects, so that repetition is avoided, and no further description is provided herein.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM) or the like.
The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.
Claims (10)
1. An application management method, characterized in that the method comprises the steps of:
acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
determining the first global variable as a current global variable so as to mount the first target application;
when the first target application is unloaded, changing the first global variable into a second global variable so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application.
2. The application management method according to claim 1, wherein the method further comprises the steps of:
presetting a corresponding first preset sandbox for the first target application, wherein the first preset sandbox is used for storing the first global variable;
and presetting a corresponding second preset sandbox for the second target application, wherein the second preset sandbox is used for storing the second global variable.
3. The application management method according to claim 2, wherein before the step of changing the first global variable to a second global variable to mount a second target application corresponding to the second global variable when the first target application is uninstalled, the method further comprises the steps of:
judging whether second mounting request information for mounting a second target application is received or not, wherein the second mounting request information comprises second target application information corresponding to the second target application;
when the second mounting request information is received, returning the first global variable to the first preset sandbox for storage so as to unload the first target application;
and extracting the second global variable from the second preset sandbox according to the second target application information.
4. The application management method of claim 1, wherein prior to said determining said first global variable as a current global variable for mounting a first target application, said method further comprises the steps of:
and calling a first hypertext markup language corresponding to the first target application and a first style corresponding to the first hypertext markup language according to the first target application information so as to apply the first style to the first target application.
5. The application management method according to claim 4, wherein before said changing the first global variable to a second global variable to mount a second target application corresponding to the second global variable, the method further comprises the steps of:
and calling a second hypertext markup language corresponding to the second target application and a second style corresponding to the second hypertext markup language to apply the second style to the second target application.
6. The application management method according to claim 5, wherein the method further comprises the steps of:
presetting the corresponding first hypertext markup language and the first style corresponding to the first hypertext markup language for the first target application, and storing the first hypertext markup language and the first style;
and presetting the second hypertext markup language and the second style corresponding to the second hypertext markup language for the second target application, and storing the second hypertext markup language and the second style.
7. An application management apparatus, characterized in that the application management apparatus comprises:
the first acquisition module is used for acquiring first mounting request information for mounting a first target application, wherein the first mounting request information carries first target application information corresponding to the first target application;
the first extraction module is used for extracting a first global variable corresponding to the first target application from a first preset sandbox corresponding to the first target application according to the first target application information;
the first mounting module is used for determining the first global variable as a current global variable so as to mount the first target application;
and the second mounting module is used for changing the first global variable into a second global variable when the first target application is unloaded so as to mount a second target application corresponding to the second global variable, wherein the second global variable is stored in a second preset sandbox corresponding to the second target application.
8. The application management apparatus according to claim 7, wherein the application management apparatus further comprises:
the first preset module is used for presetting the corresponding first preset sandbox for the first target application, and the first preset sandbox is used for storing the first global variable;
the second preset module is configured to preset a corresponding second preset sandbox for the second target application, where the second preset sandbox is used to store the second global variable.
9. An electronic device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps in the application management method according to any one of claims 1 to 6 when the computer program is executed.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps in the application management method according to any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911414874.0A CN113127010B (en) | 2019-12-31 | 2019-12-31 | Application management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911414874.0A CN113127010B (en) | 2019-12-31 | 2019-12-31 | Application management method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113127010A CN113127010A (en) | 2021-07-16 |
| CN113127010B true CN113127010B (en) | 2023-11-17 |
Family
ID=76770476
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911414874.0A Active CN113127010B (en) | 2019-12-31 | 2019-12-31 | Application management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113127010B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106874749A (en) * | 2017-02-15 | 2017-06-20 | 青岛海信移动通信技术股份有限公司 | A kind of method and apparatus for managing root authority |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8448255B2 (en) * | 2008-07-14 | 2013-05-21 | Apple Inc. | Secure file processing |
-
2019
- 2019-12-31 CN CN201911414874.0A patent/CN113127010B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106874749A (en) * | 2017-02-15 | 2017-06-20 | 青岛海信移动通信技术股份有限公司 | A kind of method and apparatus for managing root authority |
Non-Patent Citations (1)
| Title |
|---|
| 刘俊琦 ; 程虎 ; .基于J2EE的应用支撑平台的设计与实现.计算机工程与设计.2006,(15),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113127010A (en) | 2021-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104572278B (en) | The method, device and equipment of light application calling local side ability | |
| CN109325195B (en) | Rendering method and system for browser, computer device and computer storage medium | |
| CN104885055B (en) | Application data synchronization method and device | |
| CN104683386B (en) | The stake service implementing method and device of customizable response | |
| CN109445784B (en) | Method and device for processing structure data, storage medium and electronic equipment | |
| CN103106102A (en) | Running method of Web application program and mobile terminal | |
| CN111580879A (en) | Applet running method and device, electronic equipment and computer storage medium | |
| CN104756080A (en) | Augmenting capabilities of a host device | |
| CN104516885A (en) | Implementation method and device of browse program double-kernel assembly | |
| CN102323887A (en) | Browser engine-based method for dynamically loading Widget and mobile terminal | |
| CN104268472B (en) | Reduction is by the method and apparatus of third party's dynamic base Modification growth function address | |
| CN110968331A (en) | Method and device for running application program | |
| CN102130993A (en) | Mobile-terminal-based information-recording method and system | |
| CN105847319A (en) | Mobile terminal network request method and system | |
| CN112214250A (en) | Application program assembly loading method and device | |
| CN111679828B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN113220366A (en) | Sub-application starting method and device, terminal and server | |
| CN103379022B (en) | A kind of instant communication method based on Internet map search and system | |
| CN113127010B (en) | Application management method and device, electronic equipment and storage medium | |
| CN103354927A (en) | Method and apparatus for managing content in a processing device | |
| CN110728379A (en) | Configuration information management method and device, electronic equipment and non-transitory storage medium | |
| CN111488286B (en) | Method and device for independently developing Android modules | |
| CN111581578B (en) | Interface request processing method and device | |
| CN104866301B (en) | For calling and the method and device of assisted call local side ability | |
| CN110471708B (en) | Method and device for acquiring configuration items based on reusable components |
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 |