WO2023245368A1 - Application control method and apparatus, electronic device, and storage medium - Google Patents

Abstract

An application control method and apparatus, an electronic device, and a storage medium. The method comprises: in response to detecting a redirection from the current page object to a first page object in an application program, obtaining pre-cached configuration data of the first page object (S210); and generating the first page object according to the configuration data (S220). The present method can achieve a quick page object redirection, and caching of a plurality of page objects can also be achieved for a small memory device, without reinitializing the configuration of a historical page object, such that the use fluency of an application program is improved.

Description

Application control methods, devices, electronic devices and storage media Technical field

The present disclosure relates to the technical field of application control, and specifically relates to an application control method, device, electronic device and storage medium.

Background technique

With the development of computer application technology, various electronic devices are becoming more and more popular, and applications based on electronic devices are becoming more and more abundant. In related technologies, an application can often include multiple page objects, and each page object includes multiple component resources, such as background images, widgets and other components.

For lightweight electronic devices such as wearable devices, due to the limited memory space of the device itself, the functionality and stability of the application are poor, which reduces the user experience of using the application.

Contents of the invention

In order to improve the application control effect of wearable devices, embodiments of the present disclosure provide an application control method, device, electronic device and storage medium.

In a first aspect, an embodiment of the present disclosure provides an application control method, including:

In response to detecting that the current page object jumps to the first page object in the application program, obtain the pre-cached configuration data of the first page object;

The first page object is generated according to the configuration data.

In some implementations, the process of pre-caching the configuration data of the first page object includes:

In response to detecting that the application program jumps from the first page object to other page objects, the current configuration data of the first page object is cached in the application program memory.

In some implementations, the process of controlling page object jumps in the application program includes:

Obtain the jump instruction of the page object to be jumped, where the jump instruction includes the page identifier of the page object to be jumped;

According to the page identifier, determine whether the configuration data of the page object to be jumped is cached in the current application memory;

In response to the configuration data of the page object to be jumped being cached in the current application memory, the page object to be jumped is generated according to the configuration data.

In some embodiments, the method described in the embodiments of the present disclosure further includes:

In response to the fact that the configuration data of the page to be jumped is not cached in the current application memory, the page to be jumped is initialized and configured according to the obtained initialization data of the page to be jumped, and the page to be jumped is generated. object.

In some implementations, the process of pre-caching the configuration data of the first page object includes:

In response to the amount of cached configuration data in the memory of the application program not reaching the preset threshold, cache the current configuration data of the first page object in the memory of the application program;

and / or,

In response to the amount of cached configuration data in the memory of the application reaching the preset threshold, the configuration data of the earliest cached page object is deleted, and the current configuration data of the first page object is cached in the application. in memory.

In some implementations, caching the current configuration data of the first page object in the application memory includes:

Caching the configuration data of the first page object at the top level of the routing stack of the configuration data of the previous page object of the application program;

or,

The configuration data of the previous page object located at the top of the routing stack is replaced with the configuration data of the first page object.

In a second aspect, an embodiment of the present disclosure provides an application control device, including:

An acquisition module configured to acquire the pre-cached configuration data of the first page object in response to detecting a jump from the current page object to the first page object in the application;

A generating module configured to generate the first page object according to the configuration data.

In some embodiments, the device described in the embodiments of the present disclosure further includes a cache module, and the cache module is configured to:

In response to detecting that the application program jumps from the first page object to other page objects, the current configuration data of the first page object is cached in the application program memory.

In some embodiments, the device described in the embodiments of the present disclosure also includes a page jump module, and the page jump module is configured to:

Obtain the jump instruction of the page object to be jumped, where the jump instruction includes the page identifier of the page to be jumped;

According to the page identifier, determine whether the configuration data of the page object to be jumped is cached in the current application memory;

In response to the configuration data of the page object to be jumped being cached in the current application memory, the page object to be jumped is generated according to the configuration data.

In some implementations, the page jump module is configured to:

In response to the fact that the configuration data of the page to be jumped is not cached in the current application memory, the page to be jumped is initialized and configured according to the obtained initialization data of the page to be jumped, and the page to be jumped is generated. object.

In some implementations, the cache module is configured to:

In response to the amount of cached configuration data in the memory of the application program not reaching the preset threshold, cache the current configuration data of the first page object in the memory of the application program;

and / or,

In response to the amount of cached configuration data in the memory of the application reaching the preset threshold, the configuration data of the earliest cached page object is deleted, and the current configuration data of the first page object is cached in the application. in memory.

In some implementations, the cache module is configured to:

Caching the configuration data of the first page object at the top level of the routing stack of the configuration data of the previous page object of the application program;

or,

The configuration data of the previous page object located at the top of the routing stack is replaced with the configuration data of the first page object.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including:

processor; and

A memory stores computer instructions for causing the processor to execute the method according to any implementation manner of the first aspect.

In a fourth aspect, an embodiment of the present disclosure provides a storage medium that stores computer instructions, and the computer instructions are used to cause a computer to execute the method according to any embodiment of the first aspect.

The application control method in the embodiment of the present disclosure includes, in response to detecting a jump from the current page object to the first page object in the application program, obtaining the pre-cached configuration data of the first page object, and generating the first page object according to the configuration data. . In the embodiment of the present disclosure, when the page object jumps, by caching the configuration data of the page object, the page object can be quickly jumped, and multiple page objects can also be cached for small memory devices without re-initialization. Historical page objects enable fast jumps to page objects, improve application fluency, and improve user experience.

Description of the drawings

In order to more clearly explain the specific embodiments of the present disclosure or the technical solutions in the prior art, the drawings that need to be used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description The drawings illustrate some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

FIG. 1 is an architectural diagram of an operating system of an electronic device according to some embodiments of the present disclosure.

Figure 2 is a flowchart of an application control method in some embodiments of the present disclosure.

Figure 3 is a flowchart of an application control method in some embodiments of the present disclosure.

Figure 4 is a schematic diagram of an application control method in some embodiments of the present disclosure.

Figure 5 is a schematic diagram of an application control method according to some embodiments of the present disclosure.

Figure 6 is a structural block diagram of an application control device according to some embodiments of the present disclosure.

Figure 7 is a structural block diagram of an electronic device according to some embodiments of the present disclosure.

Detailed ways

The technical solution of the present disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present disclosure, but not all of them. Based on the embodiments in this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this disclosure. In addition, the technical features involved in different embodiments of the present disclosure described below can be combined with each other as long as they do not conflict with each other.

With the development of computer application technology, various electronic devices are becoming more and more popular, and applications based on electronic devices are becoming more and more abundant. Taking mobile phone applications as an example, they may include shopping applications, instant messaging applications, map navigation applications, audio and video playback applications, etc.

An application often includes multiple page objects. Users can automatically jump to another page by clicking a button on a page, return to historical pages by pressing the return button, etc. Nowadays, as applications can implement more and more functions, the page objects of applications also include more and more component resources, such as background images, links, widgets and other component resources.

In related technologies, for terminal devices such as smartphones and tablets, the hardware performance and memory space are relatively good. When an application is started, the page objects that have been visited in the history can be completely cached in the memory, so that the user can return from the current page. When viewing the history page, the history page can be displayed directly without waiting for initial configuration and rendering.

However, for wearable devices such as smart watches and smart bracelets, the processing performance and memory space of the device are poor. When the wearable device starts an application, if it caches the rendered page objects that have been visited in the past in the memory , the memory space allocated to the application by the wearable device is limited, and it may only be able to cache the page object most recently accessed in history. If the user wants to return an earlier page object, he needs to re-initialize, configure and render the page object, causing the application to use the lag. Pause, reducing user experience.

Based on the above defects, embodiments of the present disclosure provide an application control method, device, electronic device and storage medium, aiming to manage and control the page objects of the application, realize rapid jump of multiple page objects, and improve the application running effect.

Figure 1 shows a schematic architectural diagram of an operating system of an electronic device in some embodiments of the present disclosure.

As shown in Figure 1, the system software architecture can be divided into four layers, namely the Applications layer, Application Framework layer, Libraries layer and Linux Kernel layer.

1. Application layer

The application layer is the layer in the Android system that interacts with users. The application layer includes various applications of the mobile phone, such as system applications such as settings, contacts, text messages, calls, gallery, calendar, browser, or third-party applications such as WeChat. The application layer can access the services provided by the application framework layer according to different applications. Generally speaking, applications are developed using the Java language and are completed by calling the application programming interface (application programming interface, API) provided by the application framework layer. For example, when a developer sets a page jump task, he or she can access the interface management service provided by the application framework layer at the application layer for setting a page jump task.

2. Application framework layer

The application framework layer mainly provides developers with access to various APIs used by applications. For different applications, the application framework layer provides different APIs and services to the application layer. For example, when setting page object management tasks, the application framework layer can provide the application layer with an API for setting page jump tasks, and provide relevant interface management services for the application layer to achieve management control of page objects.

Specifically, developers can interact with the underlying layer of the operating system (such as function libraries, Linux kernel, etc.) through the application framework to develop their own applications. The application framework can be a series of services and management systems of the operating system. The application framework mainly includes the following basic services:

Page management (Window Manager) module: used to manage graphical user page resources used on the screen, specifically including: creation and destruction of page objects, display and hiding of page objects, page layout, focus management, and input methods and wallpapers Management etc.

Activity Manager (Activity Manager) module: used to manage the life cycle of each application. Applications usually run in the operating system in the form of Activity. For each Activity, there will be a corresponding application record (Activity Record) in the activity manager. This Activity Record records the status of the application's Activity. The activity manager can use this Activity Record as an identifier to schedule the application's Activity process.

View: A rich and extensible view collection that can be used to build an application, including List, Grid, TextBox, Button, and embeddable web browser device.

Notification Manager module: used to control applications to display prompt information (such as Alerts, Notifications, etc.) to users in the status bar, lock screen interface, etc.

3. Function library layer

The function library layer is the support of the application framework and an important link between the application framework layer and the Linux kernel layer. The function library layer includes some function libraries compiled from the computer program C language or C++ language. These function libraries can be used by different components in the operating system. They provide services to developers through the application framework layer. Specifically, the function library can include the libc function library, which is specially customized for embedded Linux-based devices; the function library can also include the multimedia library (Media Framework), which supports the playback and recording of audio or video in multiple encoding formats. , while supporting still image files, as well as common audio or video encoding formats. The function library also includes the interface management library (Surface Manager), which is mainly responsible for managing access to the display system. It is specifically used to manage the interaction between display and access operations when executing multiple applications. It is also responsible for 2D drawing and 3D Drawing for display composition.

The function library layer can also include other function libraries used to implement various functions of electronic devices, such as: scalable graphics library (SGL): 2D graphics based on extensible markup language (XML) files Image processing engine; secure sockets layer (SSL): located between TVP/IP protocol and various application layer protocols, providing support for data communication; 3D graphics processing library (OpenGL/ES): support for 3D effects; Lightweight database (SQLite): relational database engine; Webkit: Web browser engine; FreeType: bitmap and vector font support; etc.

Android Runtime is a running environment on the operating system and a new virtual machine used by the operating system. In Android Runtime, AOT (Ahead-Of-Time) technology is used. When an application is installed for the first time, the bytecode of the application will be pre-compiled into machine code, making the application a truly local application. , and then run it again, the compilation step will be omitted, and startup and execution will become faster.

In some other embodiments of the present disclosure, Android Runtime can also be replaced by Core Libraries and Dalvik Virtual Machine. The core function library provides most functions in the Java language API, mainly through the Java native interface (java native interface, JNI) to provide the application framework layer with an interface for calling the underlying program library. It also includes some core APIs of the operating system, such as android.os, android.net, android.media, etc. The Dalvik virtual machine uses a JIT (Just-in-Time) runtime compilation mechanism. Every time a process is started, the virtual machine needs to recompile the bytecode in the background, which will have a certain impact on the startup speed. Each application runs in an instance of the Dalvik virtual machine, and each Dalvik virtual machine instance is an independent process space. The Dalvik virtual machine is designed to efficiently run multiple virtual machines on a single device. The Dalvik virtual machine executable file format is .dex. The dex format is a compression format specially designed for Dalvik and is suitable for systems with limited memory and processor speed. What needs to be mentioned is that the Dalvik virtual machine relies on the Linux kernel to provide basic functions (threads, underlying memory management). It can be understood that Android Runtime and Dalvik belong to different types of virtual machines, and those skilled in the art can choose different forms of virtual machines in different situations.

4. Linux kernel layer

The Linux kernel layer provides core system services of the operating system, such as security, memory management, process management, network protocol stack and driver model, all based on the Linux kernel. The Linux kernel also serves as an abstraction layer between the hardware and software stacks. This layer has many drivers related to electronic devices. The main drivers are: display driver; Linux-based frame buffer driver; keyboard driver as an input device; Flash driver based on memory technology equipment; camera driver; audio driver; Bluetooth driver ; Wi-Fi driver, etc.

Based on the above system, embodiments of the present disclosure provide an application control method, which can be applied to electronic devices. In the embodiments of the present disclosure, the electronic device can be any device type suitable for implementation, such as smart phones, tablet computers, wearable devices, etc. In addition, it can be understood that the method of the embodiments of the present disclosure is more effective for electronic devices with small memory. Electronic devices with small memory can be, for example, wearable devices such as smart watches, smart bracelets, and smart glasses, which are not limited in this disclosure. Moreover, the application described in the present disclosure can be any application type suitable for deployment in electronic devices, such as instant messaging applications, map navigation applications, audio and video playback applications, etc., and the present disclosure is not limited to this.

As shown in Figure 2, in some implementations, the application control method of the present disclosure includes:

S210. In response to detecting that the current page object jumps to the first page object in the application program, obtain the pre-cached configuration data of the first page object.

S220. Generate a first page object according to the configuration data.

It can be understood that the application may include multiple page objects, and the user can jump between each page object through operations such as touching or pressing keys. For example, in an example, the application is a music playing application. When the application is started, it is located on the home page object. The user can click the music name on the home page through touch operation to jump to the page object of the music playing interface from the currently displayed home page object. . In this embodiment, the application program may be an application in a lightweight electronic device. The lightweight electronic device may be a smart watch, a smart bracelet, etc. The memory space of the lightweight electronic device is small and the hardware performance is limited. , often only one process can exist at the same time.

In the embodiment of the present disclosure, the page object to be jumped and displayed can be defined as the first page object. That is, the first page object can be any page object in the application program and is not limited to a fixed page object.

The current page object refers to the page object currently being displayed in the application, that is, the current page object can be any page object except the first page object, and is not limited to a fixed page object.

When it is detected that the current page object jumps to the first page object in the application, it means that the currently displayed current page object needs to be hidden in the background, and the first page object needs to be displayed and switched in the foreground. For example, in one example, the user jumps to the first page object from the second page object currently running in the application through touch or click operations. At this time, the second page object will be hidden in the background, and the first page object will be in the background. Foreground rendering display.

In the embodiment of the present disclosure, the first page object may be a page object that has been started before the second page object is displayed, that is, the first page object is switched to running in the background. In this case, when the first page object is switched to the background, the system will cache the configuration data of the first page object in the application memory, so that when the first page object is switched to the foreground again, the configuration data will be cached in the application memory. The configuration data of the first page object has been cached in advance.

In the embodiment of the present disclosure, considering that for some small memory devices, when the first page object is hidden in the background, the rendering interface of the first page object does not need to be presented to the user, and therefore there is no need to display all the data of the first page object. are cached in memory. Therefore, in the embodiment of the present disclosure, the component resources in the first page object can be deleted, thereby freeing up memory space, and only the configuration data of the first page object is cached in the application memory.

It can be understood that when rendering and displaying page objects, a corresponding display interface needs to be generated based on various component resources. For example, component resources may include background images, button icons, layer widgets, etc. These component resources will occupy a large amount of memory space. At the same time, at the bottom of the system, the application environment needs to be configured based on the configuration data of the page object. The configuration data may include, for example, the global variable information required to configure the application, such as system capability interface information, application timer information, etc. Therefore, in the embodiment of the present disclosure, when the first page object is hidden in the background, the component resources of the first page object can be deleted, thereby freeing up memory space, and only the configuration data is cached in the memory.

For example, in some embodiments, when the first page object is switched to the second page object, the component resources of the first page object can be cleared, including the background images, button icons and other data required for rendering the first page object. Cleared from memory. The relevant configuration data required to initialize the first page object is cached in the application memory.

It can be understood that since the component resources of the first page object are not cached, compared with the component resource data, the configuration data of the page object only occupies a small amount of memory space. Therefore, caching of the first page object can be achieved by occupying only a small amount of memory space. Especially for low-memory devices such as wearable devices, multiple page objects can be cached at the same time.

In the embodiment of the present disclosure, when jumping back to the first page object from the current page object, since the configuration data of the first page object is already cached in the application memory, the configuration of the first page object can be read directly from the memory. data, render the page according to the configuration data, obtain the first page object, and realize the jump from the current page object to the first page object.

In the embodiment of the present disclosure, when jumping from the current page object back to the first page object, since there is no need to re-initialize the configuration of the first page object, that is, the first page object does not need to be restarted, saving the initialization process of the first page object. During the occupied time, the device can quickly return to the first page object from the current page object, improving the smoothness of the application and the efficiency of page jumps.

In addition, it can be understood that the first page object in the embodiment of the present disclosure is not specifically limited to a certain page object in the application program. That is, for each page object, when the current page object is jumped to other page objects, The configuration data of the current page object can be cached in the memory of the application in sequence. Since only configuration data is cached, it takes up very little memory space. Compared with the solution of caching all data of page objects, a larger number of page objects can be cached in the same memory space.

For example, in one example, the system jumps from the first page object to the second page object, and the configuration data of the first page object can be cached in the application memory. Then the system jumps from the second page object to the third page object, and the configuration data of the second page object can also be cached in the application memory. When the system rolls back from the third page object to the second page object, the configuration data of the second page object can be read from the memory and rendered to generate the second page object in real time. When the system rolls back from the second page object to the first page object, the configuration data of the first page object can be read from the memory and rendered in real time to generate the first page object.

It can be seen from the above that in the embodiments of the present disclosure, when the page object jumps, by caching the configuration data of the page object, the page object can be quickly jumped, and multiple page objects can also be cached for small memory devices. , there is no need to re-initialize the configuration of historical page objects, realize rapid jump of page objects, improve the smoothness of application use, and improve user experience.

As shown in Figure 3, in some implementations, in the application control method of this disclosure example, the process of controlling page object jump includes:

S310. Obtain the jump instruction of the page object to be jumped.

S320. According to the page identifier, determine whether the configuration data of the page object to be jumped is cached in the current application memory.

S330. In response to the configuration data of the page object to be jumped being cached in the current application memory, generate the page to be jumped based on the configuration data.

S340. In response to the fact that the configuration data of the page to be jumped is not cached in the current application memory, initialize the configuration of the page to be jumped based on the obtained initialization data of the page to be jumped, and generate the page to be jumped.

In the embodiment of the present disclosure, the page object to be jumped refers to the target page object that is expected to be jumped to. For example, in an example, the currently displayed page is the first page object, the page object that needs to be jumped is the second page object, and the second page object is the page object to be jumped.

Jump instructions refer to instruction data that trigger page object jumps, which can be set in advance when developing applications. For example, in one example, in a scene where a first page object jumps to a second page object, the first page object has preset function keys, and the user can trigger the preset function keys in the first page object through touch operations. Thus, a jump instruction for jumping from the first page object to the second page object can be generated.

In some implementations, the jump instruction may include the application identifier of the page object to be jumped, the page identifier of the page object to be jumped, and related page parameters. The application identifier of the page object to be jumped refers to the identifier of the application program to which the page object to be jumped belongs. For example, for two different page objects using one application, the application identifiers of the two should be the same. The page identifier of the page object to be jumped refers to the unique identification information of the page object, such as page name, etc. Different page objects of the same application have different page identifiers, so the page that needs to be jumped can be determined by identifying the page identifier. The page object to be jumped. Page parameters refer to the relevant configuration parameters of the page to be jumped, such as system capability interface, page plug-in initialization parameters, language setting parameters, etc. This parameter is not required.

In the embodiment of the present disclosure, taking the jump of different page objects in the same application as an example, when a page jump is triggered, a jump instruction of the page object to be jumped can be generated, so that the system can obtain by parsing the jump instruction. The page identifier of the page object to be jumped.

Based on the foregoing, it can be known that if the page object to be jumped is a historical page object, the configuration data of the page object may have been cached in the application memory. Therefore, based on the page identifier of the page to be jumped, it is determined whether the configuration data corresponding to the page identifier has been cached in the current application memory. If the configuration data of the page object to be jumped has been cached in the application memory, S330 is executed; conversely, if the configuration data of the page object to be jumped is not cached in the application memory, S340 is executed.

Specifically, for S330, if the configuration data of the page object to be jumped has been cached in the application memory, it means that the page object to be jumped is a page object that has been visited in history, and the page object is currently in the background retention state. This You can directly read the configuration data of the page object from the memory, and render and generate the page to be jumped corresponding to the page object to be jumped based on the configuration data. There is no need to re-initialize the page object, which improves the page jump efficiency of the application.

For S340, if the configuration data of the page object to be jumped is not cached in the application memory, the following two situations may exist:

First, the page object to be jumped is not a page object that has been visited in history. At this time, the configuration folder of the page object to be jumped can be read to obtain the initialization data of the page object to be jumped, and initialization configuration and rendering are performed based on the initialization data. , the page to be jumped corresponding to the page object to be jumped can be generated. Initialization data refers to the data required when the page object to be jumped is started for the first time, which includes the above-mentioned component resources and configuration data required to render the page object.

Second, although the page object to be jumped is a page object that has been visited in history, due to limited memory space, the configuration data of the page to be jumped has been overwritten and deleted. At this time, the page object to be jumped can also be read. The configuration folder obtains the initialization data of the page object to be jumped, and performs initial configuration and rendering based on the initialization data to generate the page to be jumped corresponding to the page object to be jumped. This will be described in the following embodiments of the present disclosure and will not be described in detail here.

It can be seen from the above that in the embodiments of the present disclosure, when the page object jumps, by caching the configuration data of the page object, the page object can be quickly jumped, and multiple page objects can also be cached for small memory devices. , there is no need to re-initialize the configuration of historical page objects, realize rapid jump of page objects, improve the smoothness of application use, and improve user experience.

Combined with the system architecture shown in Figure 1, in the embodiment of the present disclosure, the application framework layer can provide developers with three APIs for page object management, which are push interface, replace interface and back interface.

In the field of application development, routing is the abstraction of the page object of the application. The routing stack can be understood as the rules for managing page objects. It enables each page object to jump and switch to each other according to predetermined rules. The principle is shown below in conjunction with Figure 4. Be explained.

First, take the push interface as an example. The push interface is the API interface for creating a new page object. When the developer needs to create a new page object, the push interface can be called to push the page data of the page object into the routing stack and notify the underlying rendering to display the page object. Page object. The page data of the page object includes the above-mentioned configuration data of the page object and the component resources for rendering the page object.

For example, as shown in Figure 4, the page data of the newly created page object page1 is pushed into the stack. At this time, the page of page1 is displayed on the wearable device. The developer calls the push interface to create a new page object page2. The page data of page2 is pushed into the routing stack and is located at the top level of page1. The page of page2 is rendered and displayed through the page data of page2. In the same way, the developer calls the push interface to create a new page object page3. The page data of page3 is pushed into the routing stack and is located on the top level of page2. The page of page3 is rendered and displayed through the page data of page3.

The back interface refers to the API interface for going back to the previous historical page. When the developer needs to go back to a historical page object, the back interface can be called to delete the page data from the top of the stack until it reaches the page that needs to be rolled back. object.

For example, as shown in Figure 4, when it is necessary to go back from page3 to page2, the developer calls the back interface to delete the page3 data on the top of the stack. At this time, page2 is the top of the stack, and is then rendered according to the configuration data of page2. Generate page2 page. In the same way, when it is necessary to go back from page2 to page1, the developer calls the back interface to delete the page2 data on the top of the stack. At this time, page1 is the top of the stack, and then the page1 page is generated based on the configuration data of page1.

The replace interface refers to the API interface for replacing the page object on the top of the stack. When the developer needs to replace the current page object, the replace interface can be called to push the page data of the page object into the routing stack and replace the page data on the top of the current stack. , and at the same time render the replaced page object.

For example, as shown in Figure 5, when page 4 needs to replace the current page 3, the developer calls the replace interface, pushes the page 4 data to the top of the routing stack to overwrite the page 3 data, and renders and displays the page 4 through the page data of page 4.

Based on the above, it can be seen that in the embodiment of the present disclosure, when the current page object jumps to other page objects, the configuration data of the current page object needs to be cached. In some implementations, as shown in Figure 4, the configuration data of the current page object can be cached on the top layer of the routing stack of the configuration data of the previous page object in sequence. In other embodiments, the configuration data of the previous page object located at the top of the routing stack can be replaced with the configuration data of the current page object according to the principle shown in Figure 5 . This disclosure does not limit this.

In the embodiment of the present disclosure, when caching the configuration data of the first page object, the application program has limited memory space and cannot cache the configuration data of all historical pages. Therefore, in some implementations, the amount of cacheable configuration data can be preset according to the memory space of the application program, and this data is also the preset threshold described in this disclosure. The number of preset thresholds can be selected according to specific scenarios. For example, the preset threshold can be any value such as 4, 6, 8, 10, etc.

Taking the example in Figure 4 as an example, the configuration data of up to four page objects can be cached in the application memory. Therefore, when caching the configuration data of the first page object, the configuration of the cached page object in the current application memory can first be determined. Whether the amount of data reaches the preset threshold 4.

If the number of cached configuration data in the current application is 4, it means that the cached configuration data in the current application memory has reached the upper limit, so the earliest cached configuration data can be deleted, and then the configuration data of the first page object can be deleted. The cache is at the top of the routing stack.

If the number of cached configuration data in the current application is less than 4, it means that the cached configuration data in the current application memory has not reached the upper limit. Therefore, there is no need to delete the cached configuration data, and the configuration data of the first page object is directly cached in Just go to the top of the routing stack.

It can be seen from the above that in the embodiments of the present disclosure, when the page object jumps, by caching the configuration data of the page object, the page object can be quickly jumped, and multiple page objects can also be cached for small memory devices. , there is no need to re-initialize the configuration of historical page objects, realize rapid jump of page objects, improve the smoothness of application use, and improve user experience. When the cached data reaches the upper memory limit, the cached data can be dynamically updated, which is beneficial to the deployment of low-memory wearable devices.

In some embodiments, examples of the present disclosure provide an application control device, which can be applied to wearable devices. In the embodiments of the present disclosure, the wearable device can be any suitable type for implementation, such as smart watches, smart bracelets, smart glasses, etc., and the present disclosure is not limited to this. Moreover, the application program described in the present disclosure can be any application type suitable for deployment in wearable devices, such as instant messaging applications, map navigation applications, audio and video playback applications, etc., and the present disclosure is not limited to this.

As shown in Figure 6, in some implementations, the application control device of the example of the present disclosure includes:

The acquisition module 10 is configured to acquire the pre-cached configuration data of the first page object in response to detecting a jump from the current page object to the first page object in the application;

The generation module 20 is configured to generate the first page object according to the configuration data.

It can be seen from the above that in the embodiments of the present disclosure, when the page object jumps, by caching the configuration data of the page object, the page object can be quickly jumped, and multiple page objects can also be cached for small memory devices. , there is no need to re-initialize the configuration of historical page objects, realize quick jump of page objects, improve the smoothness of application use, and improve user experience.

In some embodiments, the device described in the embodiments of the present disclosure further includes a cache module, and the cache module is configured to:

In response to detecting that the application program jumps from the first page object to other page objects, the current configuration data of the first page object is cached in the application program memory.

In some embodiments, the device described in the embodiments of the present disclosure also includes a page jump module, and the page jump module is configured to:

Obtain the jump instruction of the page object to be jumped, where the jump instruction includes the page identifier of the page to be jumped;

According to the page identifier, determine whether the configuration data of the page object to be jumped is cached in the current application memory;

In response to the configuration data of the page object to be jumped being cached in the current application memory, the page object to be jumped is generated according to the configuration data.

In some implementations, the page jump module is configured to:

In response to the fact that the configuration data of the page to be jumped is not cached in the current application memory, the page to be jumped is initialized and configured according to the obtained initialization data of the page to be jumped, and the page to be jumped is generated. object.

In some implementations, the cache module is configured to:

In response to the amount of cached configuration data in the memory of the application program not reaching the preset threshold, cache the current configuration data of the first page object in the memory of the application program;

and / or,

In response to the amount of cached configuration data in the memory of the application reaching the preset threshold, the configuration data of the earliest cached page object is deleted, and the current configuration data of the first page object is cached in the application. in memory.

In some implementations, the cache module is configured to:

Caching the configuration data of the first page object at the top level of the routing stack of the configuration data of the previous page object in the application program;

or,

The configuration data of the previous page object located at the top of the routing stack is replaced with the configuration data of the first page object.

It can be seen from the above that in the embodiments of the present disclosure, when the page object jumps, by caching the configuration data of the page object, the page object can be quickly jumped, and multiple page objects can also be cached for small memory devices. , there is no need to re-initialize the configuration of historical page objects, realize quick jump of page objects, improve the smoothness of application use, and improve user experience. When the cached data reaches the upper memory limit, the cached data can be dynamically updated, which is beneficial to the deployment of low-memory wearable devices.

In some embodiments, embodiments of the present disclosure provide an electronic device, including:

processor; and

The memory stores computer instructions, and the computer instructions are used to cause the processor to execute the method according to any of the above embodiments.

As can be seen from the above, the embodiments of the present disclosure do not limit the type of electronic equipment, and it can be any type of equipment suitable for implementation. However, the implementation method of the present disclosure can also implement caching of multiple page objects for small memory devices, thereby having better implementation effects for small memory devices such as wearable devices.

In some embodiments, embodiments of the present disclosure provide a storage medium storing computer instructions. The computer instructions are used to cause the computer to execute the method of any of the above embodiments.

Figure 7 shows a structural block diagram of an electronic device in some embodiments of the present disclosure. The relevant principles of electronic devices and storage media in some embodiments of the present disclosure will be described below with reference to Fig. 7 .

Referring to Figure 7, electronic device 1800 may include one or more of the following components: processing component 1802, memory 1804, power supply component 1806, multimedia component 1808, audio component 1810, input/output (I/O) interface 1812, sensor component 1816, and Communication component 1818.

Processing component 1802 generally controls the overall operations of electronic device 1800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. Processing component 1802 may include one or more processors 1820 to execute instructions. Additionally, processing component 1802 may include one or more modules that facilitate interaction between processing component 1802 and other components. For example, processing component 1802 may include a multimedia module to facilitate interaction between multimedia component 1808 and processing component 1802. As another example, the processing component 1802 can read executable instructions from the memory to implement electronic device-related functions.

Memory 1804 is configured to store various types of data to support operations at electronic device 1800 . Examples of such data include instructions for any application or method operating on electronic device 1800, contact data, phonebook data, messages, pictures, videos, etc. Memory 1804 may be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EEPROM), Programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk.

Power supply component 1806 provides power to various components of electronic device 1800 . Power supply components 1806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 1800 .

Multimedia component 1808 includes a display screen that provides an output interface between the electronic device 1800 and the user. In some embodiments, multimedia component 1808 includes a front-facing camera and/or a rear-facing camera. When the electronic device 1800 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

Audio component 1810 is configured to output and/or input audio signals. For example, audio component 1810 includes a microphone (MIC) configured to receive external audio signals when electronic device 1800 is in operating modes, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1804 or sent via communications component 1818 . In some embodiments, audio component 1810 includes a speaker for outputting audio signals.

The I/O interface 1812 provides an interface between the processing component 1802 and a peripheral interface module. The peripheral interface module may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.

Sensor component 1816 includes one or more sensors for providing various aspects of status assessment for electronic device 1800 . For example, the sensor component 1816 can detect the open/closed state of the electronic device 1800, the relative positioning of components, such as the display and keypad of the electronic device 1800, the sensor component 1816 can detect the electronic device 1800 or a component of the electronic device 1800. changes in position, the presence or absence of user contact with the electronic device 1800 , the orientation or acceleration/deceleration of the electronic device 1800 and changes in the temperature of the electronic device 1800 . Sensor component 1816 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor component 1816 may include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 1816 may include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

Communication component 1818 is configured to facilitate wired or wireless communication between electronic device 1800 and other devices. The electronic device 1800 may access a wireless network based on a communication standard, such as Wi-Fi, 2G, 3G, 4G, 5G or 6G, or a combination thereof. In one exemplary embodiment, communication component 1818 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communications component 1818 includes a near field communications (NFC) module to facilitate short-range communications. For example, the NFC module can 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, electronic device 1800 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Programmed gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation.

Obviously, the above-mentioned embodiments are only examples for clear explanation and are not limitations of the embodiments. For those of ordinary skill in the art, other different forms of changes or modifications can be made based on the above description. An exhaustive list of all implementations is neither necessary nor possible. The obvious changes or modifications derived therefrom are still within the protection scope of the present invention.

Claims (12)

An application control method, characterized by including: In response to detecting that the current page object jumps to the first page object in the application program, obtain the pre-cached configuration data of the first page object; The first page object is generated according to the configuration data. The method according to claim 1, characterized in that the process of pre-caching the configuration data of the first page object includes: In response to detecting that the application program jumps from the first page object to other page objects, the current configuration data of the first page object is cached in the application program memory. The method of claim 2, wherein caching the current configuration data of the first page object in the application memory includes: Caching the configuration data of the first page object at the top level of the routing stack of the configuration data of the previous page object of the application program; or, The configuration data of the previous page object located at the top of the routing stack is replaced with the configuration data of the first page object. The method according to claim 1, characterized in that the process of controlling page object jump in the application program includes: Obtain the jump instruction of the page object to be jumped, where the jump instruction includes the page identifier of the page object to be jumped; According to the page identifier, determine whether the configuration data of the page object to be jumped is cached in the current application memory; In response to the configuration data of the page object to be jumped being cached in the current application memory, the page object to be jumped is generated according to the configuration data. The method according to claim 4, further comprising: In response to the fact that the configuration data of the page to be jumped is not cached in the current application memory, the page to be jumped is initialized and configured according to the obtained initialization data of the page to be jumped, and the page to be jumped is generated. object. The method according to claim 1, characterized in that the process of pre-caching the configuration data of the first page object includes: In response to the amount of cached configuration data in the memory of the application program not reaching the preset threshold, cache the current configuration data of the first page object in the memory of the application program; and / or, In response to the amount of cached configuration data in the memory of the application reaching the preset threshold, the configuration data of the earliest cached page object is deleted, and the current configuration data of the first page object is cached in the application. in memory. An application control device, characterized by including: An acquisition module configured to acquire the pre-cached configuration data of the first page object in response to detecting a jump from the current page object to the first page object in the application; A generating module configured to generate the first page object according to the configuration data. The device according to claim 7, further comprising a cache module configured to: In response to detecting that the application program jumps from the first page object to other page objects, the current configuration data of the first page object is cached in the application program memory. The device according to claim 7, further comprising a page jump module configured to: Obtain the jump instruction of the page object to be jumped, where the jump instruction includes the page identifier of the page to be jumped; According to the page identifier, determine whether the configuration data of the page object to be jumped is cached in the current application memory; In response to the configuration data of the page object to be jumped being cached in the current application memory, the page object to be jumped is generated according to the configuration data. The device according to claim 7, wherein the cache module is configured to: In response to the amount of cached configuration data in the memory of the application program not reaching the preset threshold, cache the current configuration data of the first page object in the memory of the application program; and / or, In response to the amount of cached configuration data in the memory of the application reaching the preset threshold, the configuration data of the earliest cached page object is deleted, and the current configuration data of the first page object is cached in the application. in memory. An electronic device, characterized by including: processor; and A memory storing computer instructions for causing the processor to execute the method according to any one of claims 1 to 6. A storage medium, characterized in that computer instructions are stored, and the computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 6.

Images