Application program processing method and device, equipment, medium and program product

Abstract

The embodiment of the invention discloses an application program processing method and device, equipment, a medium and a program product. The method comprises the following steps: displaying an application identifier of an application program; in response to a function arousing operation on the application identifier, displaying one or more application function components of the application program; and in response to a trigger operation on the target application function component, displaying a function execution interface corresponding to the target application function component. By adopting the embodiment of the invention, the convenient triggering of the application function can be realized in a cross-platform manner, and the calling efficiency of the application function on the computer equipment is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, in particular to the field of application programs, and specifically to a method for processing an application program, a device for processing an application program, a computer device, a computer-readable storage medium, and a computer program product. Background Art

[0002] An emulator is software or hardware that can simulate one computer operating system on another computer operating system; for example, an emulator deployed on a Windows system device is used to simulate a mobile operating system and run mobile applications in the simulated mobile operating system.

[0003] Currently, there is a problem of inconsistent operation experience when users operate mobile applications on desktop devices (such as Windows system devices) and when users directly operate the mobile applications on mobile devices (such as Android system devices). For example, some interactive operations that users can perform on mobile applications on mobile devices are not supported on desktop devices. This not only hinders the cross-platform compatibility of mobile applications, but also reduces the efficiency of using mobile applications on desktop devices. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, device, medium and program product for processing an application program, which can quickly call the application function of the application program in the simulator on a computer device, not only realizing convenient triggering of the application function across platforms, but also improving the efficiency of calling the application function on the computer device.

[0005] On the one hand, an embodiment of the present application provides a method for processing an application, the method comprising:

[0006] Displaying an application identifier of an application; the application is run in a simulator of a computer device, the simulator is used to simulate a first operating system in the computer device, the computer device is deployed with a second operating system, and the first operating system and the second operating system are different;

[0007] In response to a function invoking operation on an application identifier, displaying one or more application function components of the application, each application function component being used to trigger an application function of the application;

[0008] In response to a triggering operation on a target application function component, a function execution interface corresponding to the target application function component is displayed; the function execution interface is used to execute a target application function triggered by the target application function component; the target application function component is one of one or more application function components.

[0009] On the other hand, an embodiment of the present application provides a device for processing an application program, the device comprising:

[0010] A display unit, used to display an application identifier of an application; the application runs in a simulator of a computer device, the simulator is used to simulate a first operating system in the computer device, the computer device is deployed with a second operating system, and the first operating system and the second operating system are different;

[0011] A processing unit, configured to display one or more application function components of the application program in response to a function invoking operation on the application identifier, each application function component being configured to trigger an application function of the application program;

[0012] The processing unit is also used to display a function execution interface corresponding to the target application function component in response to a triggering operation on the target application function component; the function execution interface is used to execute the target application function triggered by the target application function component; the target application function component is one of one or more application function components.

[0013] In one implementation, the function-awakening operation includes at least one of the following: a key operation on an input device, the input device being a device that establishes a communication connection with a computer device; a pressing operation on an application identifier; and a triggering operation on a specified display position in a display area where the application identifier is located;

[0014] The application function component includes at least one of the following: a scanning function component, a payment function component, a playback function component, an information viewing function component and a search function component.

[0015] In one implementation, the processing unit is configured to, in response to a function invoking operation on an application identifier, display one or more application function components of an application program, specifically:

[0016] In response to a function invoking operation on the application identifier, outputting a shortcut menu window;

[0017] Display one or more application function components of the application in the shortcut menu window.

[0018] In one implementation, the shortcut menu window includes a first display area and a second display area; and the processing unit is configured to display one or more application function components of the application in the shortcut menu window, specifically configured to:

[0019] Displaying one or more preset menu components in the first display area; the preset menu components are provided by the second operating system or the simulator;

[0020] One or more application function components of the application are displayed in the second display area.

[0021] In one implementation, the shortcut menu window includes an application function trigger option; the processing unit is used to display one or more application function components of the application in the shortcut menu window, specifically to:

[0022] If the application function trigger option is triggered, the function display window is output;

[0023] One or more application function components of the application are displayed in the function display window.

[0024] In one implementation, the processing unit is further configured to:

[0025] Displaying at least one candidate application function component to be controlled to be displayed according to the display control operation performed on one or more application function components;

[0026] The display control operation includes at least one of the following: a scrolling operation on one or more application function components through an input device; a sliding operation on one or more application function components; and an expansion operation on one or more application function components.

[0027] In one implementation, the display unit, when used to display the application identifier of the application, is specifically used to:

[0028] Displaying an application recommendation interface of the simulator, wherein the application identifier is displayed in the application recommendation interface;

[0029] The processing unit is configured to, in response to a function invoking operation on an application identifier, display one or more application function components of an application program, specifically to:

[0030] In response to a function invocation operation for an application identifier in the application recommendation interface, one or more application function components of the application program are displayed.

[0031] In one implementation, the display unit, when used to display the application identifier of the application, is specifically used to:

[0032] Displaying a desktop interface of the computer device, and displaying an application identifier of the application program in the desktop interface;

[0033] Displaying an indication mark in the display area where the application mark is located; the indication mark is used to indicate that: the application corresponding to the application mark is running in the first operating system simulated by the simulator;

[0034] The processing unit is configured to, in response to a function invoking operation on an application identifier, display one or more application function components of an application program, specifically to:

[0035] In response to a function invoking operation for an application identifier in a desktop interface, one or more application function components of the application program are displayed.

[0036] In one implementation, the processing unit is further configured to:

[0037] If there is an identification creation operation for the application in the simulator, a step of displaying the application identification of the application in the desktop interface is triggered.

[0038] In one implementation, the processing unit is configured to trigger the step of displaying the application identification of the application in the desktop interface if there is an identification creation operation for the application in the simulator, specifically to:

[0039] When the application is installed in the simulator, an identification prompt information is output, where the identification prompt information is used to prompt: creating an application identification of the application in the desktop interface of the computer device;

[0040] In response to a confirmation operation performed on the identification prompt information, a step of displaying the application identification of the application program in the desktop interface is triggered.

[0041] In one implementation, the processing unit, when used to display one or more application function components of an application, is specifically used to:

[0042] Acquire target menu data of the application, where the target menu data is used to define display rules for displaying application function components of the application in the second operating system;

[0043] Displaying one or more application function components of the application according to the target menu data;

[0044] Among them, the process of generating target menu data includes: obtaining the menu resource file of the application, the menu resource file includes extended menu data, and the extended menu data defines the component attributes of each application function component in one or more application function components; obtaining the menu data template of the second operating system, the menu data template is used to standardize the component display rules in the second operating system; extracting the extended menu data from the menu resource file, and filling the extended menu data into the menu data template to obtain the target menu data.

[0045] In one implementation, the simulator includes a function mapping table, in which function data required to be called when each application function component is triggered is stored; a processing unit, which is used to respond to the triggering operation of the target application function component and display the function execution interface corresponding to the target application function component, is specifically used to:

[0046] In response to a triggering operation on a target application functional component, obtaining an application identifier of the application program;

[0047] Obtaining target function data required to be called when the target application function component is triggered from the function mapping table; the target function data includes jump path data of the target function interface corresponding to the target application function component;

[0048] splicing the application identifier and the target function data to obtain function jump data;

[0049] The function execution interface corresponding to the target application function component is displayed based on the function jump data.

[0050] In another aspect, an embodiment of the present application provides a computer device, the computer device comprising:

[0051] a processor adapted to execute a computer program;

[0052] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processing method of the above application program is implemented.

[0053] On the other hand, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program is suitable for being loaded by a processor and executing the processing method of the above-mentioned application.

[0054] On the other hand, an embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the processing method of the above-mentioned application program.

[0055] In an embodiment of the present application, a simulator is deployed in a computer device, and the simulator can be used to simulate a first operating system in the computer device, and the first operating system is different from the second operating system deployed in the computer device; in this way, the computer device can use the simulator as an intermediate medium to run an application that only runs on the first operating system. In the case where a simulator is deployed in the computer device, an embodiment of the present application supports displaying the application identifier of the application in the computer device; if the user wants to quickly trigger the application function of the application, the user can directly perform a function call operation on the application identifier of the application to trigger the display of one or more application function components of the application, each application function component is used to trigger an application function of the application. This ability to quickly call up the application function component by directly performing a function call operation on the application identifier in the computer device is equivalent to the ability to quickly call up the application function of the application by long pressing the application identifier in the mobile device that deploys the first operating system, so that the user can perform the same or similar interactive operations in the computer device and the mobile device to quickly call up the application function, achieving better compatibility of cross-platform applications and broadening the use scenarios of applications. Furthermore, if the user wants to execute an application function of an application, the user can trigger an application function component in one or more application function components in the computer device. At this time, the function execution interface corresponding to the target application function component is displayed, so that the user can execute the target application function in the function execution interface. Compared with the need to enter the application to perform a series of interactive operations to open the function execution interface, the operation process of triggering application functions in the computer device is simplified, and the efficiency of the user's calling application functions in the computer device is greatly improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0057] Figure 1 is a schematic diagram of a cross-platform system architecture provided by an exemplary embodiment of the present application;

[0058] Figure 2 It is a flowchart of a method for processing an application provided by an exemplary embodiment of the present application;

[0059] Figure 3 is a schematic diagram of an application recommendation interface of a simulator provided by an exemplary embodiment of the present application;

[0060] Figure 4 It is a schematic diagram of displaying a shortcut of an application on a desktop interface provided by an exemplary embodiment of the present application;

[0061] Figure 5 It is a flowchart of creating a shortcut on a desktop interface provided by an exemplary embodiment of the present application;

[0062] Figure 6a It is another flowchart of creating a shortcut on a desktop interface provided by an exemplary embodiment of the present application;

[0063] Figure 6b It is another flowchart of creating a shortcut on a desktop interface provided by an exemplary embodiment of the present application;

[0064] Figure 6c It is a schematic diagram of another process of creating a shortcut on a desktop interface provided by an exemplary embodiment of the present application;

[0065] Figure 7a It is a schematic diagram of right-clicking an application logo in an application recommendation interface of a simulator provided by an exemplary embodiment of the present application;

[0066] Figure 7b It is a schematic diagram of right-clicking an application logo in a desktop interface of a computer device provided by an exemplary embodiment of the present application;

[0067] Figure 8a is a schematic diagram of pressing an application logo with two fingers in an application recommendation interface of a simulator provided by an exemplary embodiment of the present application;

[0068] Figure 8b is a schematic diagram of pressing an application logo with two fingers in a desktop interface of a computer device provided by an exemplary embodiment of the present application;

[0069] Figure 9a It is a schematic diagram of performing a trigger operation on an application representation in an application recommendation interface of a simulator provided by an exemplary embodiment of the present application;

[0070] Figure 9b It is a schematic diagram of performing a trigger operation on an application identifier in a desktop interface of a computer device provided by an exemplary embodiment of the present application;

[0071] Fig.10 is a schematic diagram of a shortcut menu window provided by an exemplary embodiment of the present application;

[0072] Fig.11 is a schematic diagram of another shortcut menu window provided by an exemplary embodiment of the present application;

[0073] Fig.12a It is a schematic diagram of display control of application function components provided by an exemplary embodiment of the present application;

[0074] Figure 12b is a schematic diagram of another display control of application function components provided by an exemplary embodiment of the present application;

[0075] Fig.12c It is a schematic diagram of another display control of application function components provided by an exemplary embodiment of the present application;

[0076] Fig.13 is a schematic diagram of a function execution interface provided by an exemplary embodiment of the present application;

[0077] Fig.14 It is a background process diagram of a method for processing an application provided by an exemplary embodiment of the present application;

[0078] Fig.15 is a flowchart of another method for processing an application program provided by an exemplary embodiment of the present application;

[0079] Fig.16 is a structural diagram of a processing device for an application provided by an exemplary embodiment of the present application;

[0080] Fig.17 It is a structural diagram of a computer device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0081] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0082] The embodiment of the present application provides a processing solution for an application program, which mainly involves technical contents such as an application program, a platform, and a simulator. The following is a brief introduction to the technical terms and related concepts involved in the processing solution for the application program, wherein:

[0083] 1. Platform.

[0084] A platform refers to an operating environment built through the hardware resources (such as CPU (Central Processing Unit), memory and interfaces, etc.) and software resources (such as program code, interfaces, etc.) of a computer device; this operating environment provides an operating environment and necessary physical support for applications deployed on the platform. Among them, the operating system can be regarded as a platform. The operating system is a computer program that manages and controls the hardware resources and software resources of a computer device. It is also the most basic system software that runs directly on a computer device. The operating system provides an operating environment and management functions for other software resources on a computer device. Any software resource on a computer device must be supported by the operating system to run.

[0085] According to the operating environment of the operating system, the operating system may include but is not limited to: desktop operating system, mobile operating system and embedded operating system, etc. Among them:

[0086] (1) Desktop operating systems are mainly designed for desktop devices. Desktop operating systems can adapt to the hardware configuration of desktop devices and help run more complex software resources on desktop devices. Among them, desktop devices refer to electronic devices that are larger and heavier, such as personal computers (PC). PC devices include desktop computers, tablet computers, personal computers, portable personal computers and mobile Internet devices (MID). PC devices have larger display screens, more powerful processing capabilities and higher storage capacity. The desktop operating system deployed on desktop devices can be Windows operating system or macOS operating system. Windows operating system and macOS operating system have different developers, and the desktop devices they are used in are also different. For example, macOS operating system is mainly deployed in Mac series smart computers.

[0087] (2) Mobile operating systems are mainly designed for mobile devices. Mobile operating systems can adapt to the hardware configuration of mobile devices, organize the entrance to software resources using icon grids, and use gesture navigation to achieve page jumps in software resources, thereby helping to run software resources on mobile devices. Compared with desktop devices, mobile devices refer to electronic devices that are smaller and lighter in weight, such as smartphones and smart watches. Mobile operating systems deployed on mobile devices may include Android operating system, IOS operating system, and Hongmeng operating system.

[0088] (3) Embedded operating system is an operating system designed for embedded devices. Embedded operating system can be applied to some resource-constrained embedded devices to realize the intelligence of embedded devices. Among them, embedded devices can include smart TVs, car-mounted devices, head-mounted devices, smart TVs or smart homes, etc.

[0089] It should be noted that operating systems can also include server operating systems, etc. The above takes desktop operating systems, mobile operating systems, and embedded operating systems as examples to introduce the classification of operating systems. For the sake of convenience, the following will take the Windows operating system under the desktop operating system and the Android operating system under the mobile operating system as examples to introduce the processing solution for application programs, which is specially explained here.

[0090] 2. Application.

[0091] An application is a software resource that runs on a computer device through an operating system. Specifically, an application is a computer program designed to complete one or more specific tasks. Applications are classified according to different classification dimensions, including:

[0092] (1) According to the classification of the operation mode of the application, the application may include but is not limited to: ① Client, also known as application client, client (APPlication, APP), refers to the application that downloads the installation package and installs and runs in the computer device through the installation package. ② Mini program, refers to the application that does not require installation; compared with the client, the mini program is an application that can be used without downloading the installation package, and it usually runs as a subprogram in the client. ③ World Wide Web (world wide web, web), refers to the web version of the application opened through the browser in the computer device; etc.

[0093] (2) According to the classification of the application's operating environment, the application may include but is not limited to: ① Mobile application, which is a software resource running in a mobile operating system and mobile device; such as a mobile client running on a smartphone with an Android operating system / iOS operating system / Hongmeng operating system. Mobile client corresponds to the server and is a program that provides services to users, including a client that provides services directly through the local (i.e., mobile device) or a client that is installed locally but needs to cooperate with the server to run. ② Desktop application, which is a software resource running in a desktop operating system and desktop device; such as a desktop client running on a smart computer with a Windows operating system / macOS operating system; a desktop client is also called a PC client, a computer client, etc. ③ Embedded application, which is a software resource running in an embedded operating system and embedded device; such as a vehicle-mounted client running on a vehicle-mounted device with an embedded operating system, and a home client running on a smart home with an embedded operating system, etc.

[0094] It should be noted that applications can also be classified according to other classification standards. For example, applications can be classified according to their functions. Applications can include social applications, music applications, game applications, etc.

[0095] Considering that the hardware characteristics, screen size, programming language and screen resolution of computer devices adapted by different operating systems are different; for example, mobile applications run on mobile devices deployed with Android operating systems, while desktop applications run on desktop devices deployed with Windows operating systems; this makes it difficult to use applications across platforms. The so-called cross-platform application means that the same application can provide roughly the same user experience when running on different system devices (i.e. computer devices deployed with operating systems); not only does it include the interface content and interface style of the application's service interface to be unified on different platforms, but it also tries to maintain the user's daily operating habits of operating applications on different platforms to avoid introducing new interactive operations.

[0096] In order to achieve cross-platform application, the simulator is used to solve the problem of incompatible applications between different system devices. The simulator is software or hardware that can simulate another system device on one system device; that is, the simulator supports simulating the hardware architecture (such as the hardware configuration of a computer device), operating system and software environment of another system device in one system device, so that applications designed for other system devices can be run on the original system device without changing the original system device. For example, the Android simulator is deployed on a Windows system device, and the hardware architecture, Android operating system and software environment of the Android system device can be simulated in the Windows system device, so that mobile applications can run on the Android system device through the Android simulator.

[0097] Currently, the cross-platform effect achieved through simulators is not good. For example, mobile devices have the ability to trigger the application function of a mobile application based on the user's long press operation on the application icon of the mobile application, while the simulator deployed in the desktop device does not support the quick triggering of the application function of the mobile application. This defect of not being able to achieve the quick triggering of the application function of the mobile application in a compatible / synchronous manner between multiple platforms not only hinders the cross-platform compatibility of the application, but also reduces the efficiency of users calling the application function of the mobile application on the desktop device.

[0098] The processing scheme of the application provided in the embodiment of the present application is specifically a cross-platform application capability quick trigger mechanism. Among them, the application capability of the application refers to the application function that the application can realize; such as the scanning function, payment function, audio and video playback function, information viewing function and search function of the application. The application functions possessed by different applications are different. For the convenience of explanation, a quick control menu is usually used to represent the various application functions possessed by the application; the quick control menu includes application function components corresponding to each of the various application functions possessed by the application, and each application function component is used to trigger an application function. The cross-platform application capability quick trigger mechanism aims to: seamlessly map the ability to quickly trigger the display of the quick control menu through the application identifier of the application on the first system device to the simulator interaction operation on the second system device, so that the simulator based on the second system device can also quickly trigger the display of the quick control menu through the application identifier of the application in the second system device. For example, the ability to quickly trigger the quick control menu of the mobile application by long pressing the application identifier of the mobile application on the mobile device is seamlessly mapped to the simulator operation interaction on the desktop device; so that the interactive operation supported by the desktop device can also be performed on the desktop device, triggering the mobile application to quickly display the quick control menu triggered by the mobile application on the mobile device on the desktop device. In this way, through the cross-platform application capability quick trigger mechanism, the quick call capability of the quick control menu of the corresponding application of the first system device can be integrated in the second system device, thereby improving the cross-platform compatibility of the application and broadening the application scenario. Among them, the first system device and the second system device are different. The embodiment of this application is described by taking the first system device as a mobile device deploying the first operating system - Android operating system, and the second system device as a desktop device deploying the second operating system - Windows operating system as an example, and in the subsequent embodiments, the second system device is referred to as a computer device, which is specially explained here.

[0099] Among them, the cross-platform scenario of the processing scheme of the application provided by the embodiment of the present application includes: deploying an emulator in a computer device, the emulator is used to simulate a first operating system in the computer device, and a second operating system is deployed in the computer device, and the second operating system is different from the first operating system; in this way, the application developed for the first operating system can be run in the emulator of the computer device to realize the cross-platform operation of the application. In this cross-platform scenario, the application identifier of the application can be displayed in the computer device; if the user wants to quickly use the application function of the application in the process of using the computer device, then the user can perform a similar function call operation for the application identifier of the application in the computer device according to the trigger operation of quickly calling the shortcut control menu of the application on the first system device to trigger the shortcut control menu. At this time, the computer device displays the shortcut control menu of the application through the emulator, specifically one or more application function components provided by the application. Further, if the user wants to use the target application function, the user can perform a trigger operation on the target application function component in one or more application function components displayed in the computer device; at this time, the computer device responds to the trigger operation and displays the function execution interface corresponding to the target application function component through the emulator, and the function execution interface is used to execute the application function triggered by the target application function component.

[0100] It can be seen that, on the one hand, the embodiment of the present application can realize the quick triggering of the application capability of the application across platforms, and realize the cross-platform compatibility of the application. At the same time, the user can use the corresponding daily user operation on different system devices to quickly trigger the quick control menu of the application, reduce the user's perceived experience of triggering the application on the system device, and improve the user's experience. On the other hand, the user can quickly call up the quick control menu through the simulator in the computer device, and jump to the corresponding function execution interface by directly triggering the application function component in the quick control menu. Compared with the need to enter the application and perform a series of interactive operations to open the function execution interface, the opening operation process of the function execution interface is shortened, and the execution efficiency / calling efficiency of the application function is improved.

[0101] The processing scheme of the application provided in the embodiment of the present application is a solution for quick triggering of the application capability of a cross-platform, and can be applied to a variety of cross-platform scenarios that require quick calling of the application capability of the application. According to different scenarios of the cross-platform scenario, the computer device, simulator, first operating system, second operating system and application mentioned in the embodiment of the present application are different. Exemplarily, the cross-platform scenario may include: ① The cross-platform scenario is to simulate the mobile operating system in the simulator of the desktop device to run the mobile application scenario. For example, the android operating system is simulated in the android simulator deployed in the windows system device to run the android application scenario; in this cross-platform scenario, the second operating system is the windows operating system, the computer device is a desktop device, the simulator is the android simulator, the first operating system simulated by the Android simulator in the desktop device is the android operating system, and the application running in the Android simulator is a mobile application-android application. For another example, the IOS operating system is simulated in the IOS simulator deployed in the windows system device to run the IOS application scenario; in this cross-platform scenario, the second operating system is the windows operating system, the computer device is a desktop device, the simulator is the IOS simulator, the first operating system simulated by the IOS simulator in the desktop device is the IOS operating system, and the application running in the IOS simulator is a mobile application-IOS application. ② The cross-platform scenario is a scenario where another mobile operating system is simulated in an emulator deployed in a mobile device that deploys a mobile operating system to run a mobile application. For example, the IOS operating system is simulated in an IOS emulator deployed in an Android system device to run an IOS application; in this cross-platform scenario, the second operating system is the Android operating system, the computer device is the mobile device, the emulator is the IOS emulator, the first operating system simulated by the IOS emulator in the mobile device is the IOS operating system, and the application running in the Android emulator is a mobile application - the Android application.

[0102] It should be understood that the above description is only an exemplary cross-platform scenario given in the embodiment of the present application, and does not limit the product performance and cross-platform scenario of the application processing solution provided in the embodiment of the present application. The application processing solution provided in the embodiment of the present application can provide efficient, accurate and convenient application capability quick triggering services in various cross-platform scenarios, showing high value and practicality in various cross-platform scenarios, and helping to improve user experience and satisfaction.

[0103] The processing scheme of the application provided in the embodiment of the present application can be integrated into the simulator. Taking the cross-platform scenario of the application of the embodiment of the present application as simulating the Android operating system in the Android simulator deployed in the Windows system device, the scenario of running the Android application is taken as an example. In this cross-platform scenario, the processing scheme of the application provided in the embodiment of the present application can be integrated into the Android simulator, so as to realize the application function of the mobile application being quickly called on the desktop device through the Android simulator.

[0104] Among them, the android simulator mentioned in the embodiment of the present application can be called a mobile phone simulator application (or simply a mobile phone simulator), which is a software tool used to simulate the operating environment of a smartphone on a desktop device, that is, to simulate the operating environment of the android operating system; thereby allowing users to experience mobile applications on smartphones on desktop devices without actually owning a smartphone. The mobile phone simulator application is mainly divided into an application market program, a mobile phone simulator Host end, and a mobile phone simulator Guest end. Among them: ① The application market program can be understood as an application mall, which is a software program that can realize the search and download of applications. In the application market program, the management of the operating status of the mobile phone simulator Host end and the mobile phone simulator Guest end can be realized. ② The mobile phone simulator Host end refers to the android simulator itself running on the desktop device, as well as the hardware abstraction layer, android operating system and user interface components that are matched therewith; the mobile phone simulator Host end is responsible for creating and managing a virtual mobile phone environment (i.e., the mobile phone simulator Guest end), and provides a series of tools and interfaces so that users can interact with the virtual mobile phone environment; in the embodiment of the present application, the mobile phone simulator Host is a PC software implemented based on a windows system device. ③ Mobile simulator guest refers to a virtual mobile environment created by the android simulator on a desktop device for mobile applications (or android applications); one mobile application corresponds to one virtual mobile environment. Mobile applications can be installed and run in the mobile simulator guest, and various interactive operations and experiences can be performed, providing users with the same operating experience as operating mobile applications on mobile devices.

[0105] The process of running mobile applications in Windows system devices through the above three mobile simulator applications includes: downloading the installation package of the mobile application in the application. When the user triggers the installation of the downloaded installation package, the mobile simulator Host creates a mobile simulator Guest for the mobile application, and the mobile simulator Guest is a vdi (Virtual Disk Image) file; the mobile simulator Host specifically loads the vdi file to create the mobile simulator Guest and run the mobile application in the mobile simulator Guest. The vdi file is a virtual disk image file format, which can be regarded as a digital copy of a physical disk. It contains all the data of a virtual disk, including partitions, file systems, files and directories.

[0106] For example, a schematic diagram of an exemplary cross-platform scenario provided in an embodiment of the present application can be found in Figure 1 .like Figure 1 As shown, it is assumed that the computer device on which the simulator is deployed is a Windows system device 101, and the simulator is an Android simulator. The Android simulator is used to simulate the Android operating system in the Windows system device 101, so that a mobile application can be run in the Android simulator in the Windows system device 101; the mobile application was originally an application running in the Android system device 102, such as the mobile application is a mobile client running in the Android system device 102.

[0107] exist Figure 1In the cross-platform scenario of the Windows system device 101 and the Android system device 102 shown, the user can open the Android emulator in the Windows system device 101, and the Android emulator displays the application identifiers of the installed mobile applications and the application identifiers of the mobile applications to be downloaded; at the same time, the application identifiers of the installed mobile applications can also be directly displayed as shortcuts in the desktop interface of the Windows system device 101. If the user wants to quickly trigger the shortcut control menu of the application directly from the application identifier, the user can perform a function call operation on the application identifier of the application displayed in the computer device (such as displayed in the Android emulator or displayed in the desktop interface of the computer device). At this time, after the Windows system device 101 detects the function call operation, it forwards the function call operation to the Android emulator, so that the Android emulator can respond to the function call operation (specifically, the mobile phone emulator Host sends the function call operation to the mobile phone emulator Guest for running the mobile application, so that the mobile phone emulator Guest returns the shortcut control menu of the mobile application to the mobile phone emulator Host), and passes the shortcut control menu of the mobile application to the Windows system device 101, so that the Windows system device 101 can display the shortcut control menu of the mobile application according to the original display format requirements.

[0108] Furthermore, the user can perform a trigger operation on the target application function component in the shortcut control menu displayed in the windows system device 101. After the windows system device 101 detects the trigger operation, it forwards the trigger operation to the android emulator, so that the android emulator responds. The android emulator passes the interface data of the function execution interface corresponding to the target application function component to the windows system device 101, so that the windows system device 101 can output the function execution interface corresponding to the target application function component according to its own display format requirements.

[0109] It can be seen that the Android simulator deployed in the Windows system device 101, as an intermediate bridge between the Windows system device 101 and the mobile application, can ensure that the mobile application can realize the cross-platform application capability quick triggering between the Windows operating system and the Android operating system. In this way, the ability to trigger the quick control menu by long pressing the application logo on the Android system device 102 can be seamlessly mapped to the operation interaction of the Android simulator in the Windows system device 101; so that the user can quickly call the application capability of the mobile application through the application logo whether on the Android system device 102 or the Windows system device 101, realizing better compatibility of the cross-platform application capability quick triggering, and at the same time improving the user's calling efficiency of triggering the application function of the mobile application in the Windows system device 101.

[0110] Based on the above brief introduction to the processing solution and system architecture of the application provided in the embodiment of the present application, it is also necessary to explain that:

[0111] ① Figure 1 The scenario architecture shown is an example of running a mobile application in an Android emulator deployed on a Windows system device to introduce the cross-platform application capability quick trigger mechanism provided by the embodiment of the present application. As mentioned above, the cross-platform scenarios applicable to the embodiment of the present application may also include other scenarios, so Figure 1 The scenario architecture shown is to more clearly illustrate the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided by the embodiment of the present application. It is known to those skilled in the art that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present application is also applicable to similar technical problems.

[0112] ② The collection and processing of relevant data in the embodiments of this application should be strictly in accordance with the requirements of relevant laws and regulations. The acquisition of personal information requires the knowledge or consent of the individual subject (or the legal basis for obtaining the information), and the subsequent use and processing of data shall be carried out within the scope of authorization of laws and regulations and the subject of personal information. For example, when the embodiments of this application are applied to specific products or technologies, such as when invoking the application function components of an application, the user's permission or consent is required, and the collection, use and processing of relevant data shall comply with the relevant laws, regulations and standards of the relevant regions.

[0113] Based on the above-described application processing solution, the embodiment of the present application proposes a more detailed application processing method. The application processing method proposed in the embodiment of the present application will be described in detail below in conjunction with the accompanying drawings.

[0114] See also Figure 2 , Figure 2 A schematic flow chart of a method for processing an application program provided by an exemplary embodiment of the present application is shown; Figure 2 The application processing method shown in the figure can be executed by a computer device, such as the computer device as described above. Figure 1 The windows system device 101 shown. The processing method may include but is not limited to steps S201-S203:

[0115] S201: Display the application ID of the application program.

[0116] The application here refers to an application running on a computer device through an emulator, such as an Android client running on a Windows system device through an Android emulator. The application identifier of an application is information used to uniquely identify the application; the application identifier can be expressed as at least one of the following: an icon, text, a number (ID), and a card, etc. For example, the application identifier of the application consists of an icon and text, or the application identifier of the application consists of a card, an icon, and text; the embodiment of the present application does not limit the form of expression of the application identifier of the application.

[0117] The embodiment of the present application supports displaying the application identifier of an application through a simulator of a computer device. In other words, the service interface provided by the simulator is displayed with the help of the display screen of the computer device, and the application identifier of the application is displayed in the service interface. Since the simulator is deployed in the computer device to simulate the first operating system that can run the application; for the user, the operation process of actively opening the service interface provided by the simulator in the computer device is in line with the user's daily operating habits of running the application using the simulator, and there is no need to learn new interactive operations to trigger the display of the application identifier of the application in the computer device, thereby avoiding increasing the learning cost and improving the user experience.

[0118] In a specific implementation, when a user wants to use an application running in a simulator of a computer device, the user can open and display the service interface of the simulator in the computer device. In the embodiment of the present application, the service interface is referred to as an application recommendation interface, and the application identification of the application is displayed in the application recommendation interface. It is worth noting that the application recommendation interface can be understood as the main page of the simulator, and the application identification of the application that has been installed in the simulator can be displayed in the application recommendation interface, and the application identification of the application that has not been downloaded to the simulator can also be displayed, and the application recommendation interface also allows operations such as searching and downloading applications.

[0119] A schematic diagram of an exemplary display of an application recommendation interface of a simulator on a display screen of a computer device can be found in Figure 3.like Figure 3 As shown, the simulator is deployed in the computer device in the form of a software tool. The software tool may be a simulator application (such as the mobile phone simulator application mentioned above), and a simulator logo 302 of the simulator application is displayed on the desktop interface 301 of the computer device. The simulator logo 302 is used to indicate the simulator application. When a user wants to use the simulator, the user can perform a trigger operation on the simulator logo 302 of the simulator. At this time, after the computer device detects the trigger operation, it calls the simulator to output the simulator's application recommendation interface 303. Among them, the application recommendation interface 303 includes application logos of installed applications and application logos of applications that have not been downloaded; such as application logos 3031 and 3032 of installed applications, application logos 3033 and 3034 of applications that have not been downloaded, etc. As Figure 3 As shown, the application identification of the application program on the application recommendation interface 303 is composed of a card, an icon and text, and the icon and text are displayed on the card.

[0120] Furthermore, the user can perform a function call operation on the application identifier (such as application identifier 3031) of the installed application in the application recommendation interface 303, so that the computer device can quickly trigger the application's shortcut control menu in response to the function call operation; wherein, the specific implementation process of performing the function call operation on the application identifier and quickly triggering the shortcut control menu is described in detail in the specific implementation process shown in the following step S202. In addition, the simulator's application recommendation interface 303 is displayed in the form of a window on the desktop interface of the computer device; the embodiment of the present application supports the application recommendation interface 303 to be reduced or enlarged in accordance with the window display rules of the computer device, which meets the user's personalized requirements for adjusting the display position and actual area of ​​the window on the desktop interface.

[0121] The embodiment of the present application also supports directly displaying the application ID of the application through the desktop interface of the computer device. That is to say, after the application is successfully installed in the simulator, the application ID of the application can be directly displayed on the desktop interface of the computer device in the form of a shortcut of the computer device; for the user, the application running in the simulator can be accessed directly in the desktop interface through the shortcut, which simplifies the operation process of accessing the application in the simulator and makes the interaction between the user and the application in the simulator simpler and more convenient.

[0122] In a specific implementation, a desktop interface is displayed on the display screen of a computer device, and the desktop interface can be understood as the main interface of the computer device; the application identifier of the application is displayed in the desktop interface, and the application identifier is in the form of a shortcut at this time, supporting the quick launch of the application through the shortcut. In order to distinguish the application identifier of the application running on the first operating system and the application identifier of the application running on the second operating system in the desktop interface, the embodiment of the present application supports displaying an indication mark in the display area where the application identifier of the application running on the first operating system is located, and the indication mark is used to indicate that the application corresponding to the corresponding application identifier runs in the first operating system simulated by the simulator. In this way, the application identifier of the application running on the first operating system and the application identifier of the application running on the second operating system are displayed in the form of shortcuts on the desktop interface of the computer device at the same time; on the one hand, it is convenient for users to interact with the application running on the first operating system according to the daily operating habits of using the computer device, and enhance the user's operating experience of operating the application running on the first operating system in the computer device. On the other hand, the indication mark is conducive to users to effectively distinguish between applications running on different operating systems on the desktop interface.

[0123] An exemplary schematic diagram of displaying an application identifier of an application program in the form of a shortcut in a desktop interface of a computer device can be seen in Figure 4 .like Figure 4 As shown, the desktop interface of the computer device displays application identifiers of applications running on the second operating system, such as application identifier 401; application identifiers of applications running on the first operating system, such as application identifier 402 and application identifier 403; Figure 4 As shown in the desktop interface, the application logo is composed of an icon and text. For an application running on the first operating system, an indicator logo is also displayed in the display area where the application logo is located, such as an indicator logo 404 is displayed in the display area where the application logo 402 is located; the indicator logo 404 can be displayed as a simulator logo (such as an icon) of the simulator, so as to inform the user that the application logo 402 is an application downloaded from the simulator and running in the simulated first operating system. Of course, the indicator logo can also be displayed in other styles, such as text style, animation style, etc., which is not limited in the embodiments of the present application.

[0124] Furthermore, the user can directly perform a function-wake-up operation on the application identifier (such as application identifier 402) of the application running in the simulator in the desktop interface of the computer device, so that the computer device can quickly trigger the shortcut control menu of the application in response to the function-wake-up operation; among them, the specific implementation process of performing the function-wake-up operation on the application identifier and quickly triggering the shortcut control menu is detailed in the relevant description of the specific implementation process shown in the following step S202.

[0125] In an embodiment of the present application, if the computer device detects the existence of an identification creation operation for an application in the simulator, a shortcut is created for the application in the simulator, and the step of displaying the application identification of the application in the desktop interface is triggered, that is, the shortcut is displayed on the desktop interface of the computer device. Among them, the identification creation operation is an operation performed by the user to trigger the creation of a shortcut; the embodiment of the present application supports the user to create a shortcut on the desktop interface of the computer device for the application running on the first operating system through a variety of identification creation operations. For the user, he can choose any identification creation operation to create a shortcut for the application running on the first operating system according to business needs, thereby increasing the flexibility of shortcut creation and improving the user experience.

[0126] The following takes the specific operation process of two identification creation operations as an example to introduce the process of creating a shortcut of an application running on the first operating system on the desktop interface of a computer device, wherein:

[0127] In one implementation, when the application is installed in the simulator of the computer device, a shortcut is created for the application on the desktop interface of the computer device. In other words, the installation of the application in the simulator and the creation of the shortcut are continuous actions; when the application is installed, a shortcut can be created for the application.

[0128] Specifically, the application identifier of the application that has not been downloaded is displayed in the application recommendation interface of the simulator, and the application identifier is displayed as not downloaded at this time; wherein, the application identifier of the application that has not been downloaded is directly recommended and displayed by the simulator or searched and displayed by the user in the application recommendation interface. When the user performs a download operation on the application that has not been downloaded, the simulator starts to download the installation package of the application and installs the downloaded installation package; taking the simulator as a mobile phone simulator Host end as an example, when the user performs a download operation on the application that has not been downloaded, the mobile phone simulator application starts the built-in mobile phone simulator Host end to download the installation package of the application, and after the installation package is successfully downloaded, the mobile phone simulator Host end creates a mobile phone simulator Guest end to run the installation package to install the application. After the application is successfully installed, the application identifier of the application is displayed as installed in the application recommendation interface of the simulator, so that the user can intuitively perceive the installation status of the application corresponding to each application identifier from the application recommendation interface. Among them, the application identifier being displayed as a non-downloaded state may include: an installation option is displayed in the display area where the application identifier is located, and the installation option is used to trigger the installation of the application corresponding to the application identifier; in this way, the user can know through the installation option that the application corresponding to the application identifier can be installed, and thus the application is an application that has not been downloaded. Correspondingly, the application identifier being displayed as an installed state may include: an open option is displayed in the display area where the application identifier is located, and the open option is used to trigger the startup / interface opening of the application corresponding to the application identifier; it is convenient for the user to know through the open option that the application corresponding to the application identifier is an application that has been downloaded and successfully installed. Of course, the expression form of the application identifier being displayed as a non-downloaded state and an installed state can also be other; for example, when the application identifier is displayed as a non-downloaded state, the transparency of the application identifier is greater than the transparency when the application identifier is displayed as an installed state, so that the user can intuitively distinguish between installed applications and non-downloaded applications in the application recommendation interface.

[0129] Then, when the application is installed in the simulator, the simulator outputs identification prompt information through the computer device, and the identification prompt information is used to prompt: create an application identification of the application in the desktop interface of the computer device, specifically, create a shortcut to the application. If the user wants to create a shortcut to the application, the user can perform a confirmation operation on the identification prompt information, and the computer device triggers the creation of a shortcut to the application on the desktop interface in response to the user's confirmation operation on the prompt information; wherein the shortcut to the application displayed on the desktop interface is the application identification of the application.

[0130] For example, when the application is installed in the simulator of the computer device, the process of creating a shortcut for the application on the desktop interface of the computer device can be seen in Figure 5 .like Figure 5 As shown, an application identifier 501 of an application that has not been downloaded is displayed in the application recommendation interface of the simulator, and the application identifier 501 is displayed as not downloaded, such as the application identifier 501 includes an installation option 502. When the installation option 502 is triggered, it indicates that the user wants to download and install the application corresponding to the application identifier 501; at this time, the simulator starts to download the installation package of the application, and installs the application into the simulator based on the installation package. Considering that the download of the installation package of the application and the installation of the application based on the installation package often require a waiting time, the embodiment of the present application supports the display of a waiting prompt 503 during the waiting time, such as the waiting prompt 503 is displayed in the display area where the application identifier 501 is located, or displayed in other display areas; not only is the waiting prompt 503 convenient for users to intuitively perceive the download and installation progress of the installation package of the application, but also the waiting prompt 503 is enriched by the expression form (such as animation, video, etc.) to improve the fun, thereby alleviating the anxiety of users during the waiting time.

[0131] Then, after the simulator successfully installs the application based on the downloaded installation package, on the one hand, the application identification 502 of the application is displayed as installed in the application recommendation interface, such as the installation option 502 in the application identification 502 is updated to be displayed as the open option 504. On the other hand, the simulator pops up the identification prompt information 505, which can be displayed on the application recommendation interface in the form of a floating window, and the display area of ​​the floating window is smaller than the display area of ​​the application recommendation interface. The identification prompt information 505 includes a creation control 5051 and a cancel control 5052; if the user wants to create a shortcut, the creation control 5051 is triggered, and the simulator generates a shortcut of the application on the desktop interface through the computer device in response to the trigger operation performed on the creation control 5051; on the contrary, if the user does not want to create a shortcut, the cancel control 5052 is triggered, and the simulator closes the identification prompt information 505 in response to the trigger operation on the cancel control 5052.

[0132] In other implementations, users are supported to create shortcuts for installed applications in the simulator of a computer device. That is, the installation of applications and the creation of shortcuts in the simulator may not be consecutive actions, and users can actively initiate an identification creation operation for installed applications in the simulator at any time, thereby realizing autonomous creation of shortcuts for applications; this method of allowing users to create shortcuts for installed applications at any time improves the flexibility of shortcut creation.

[0133] Specifically, the application identification of the installed application is displayed in the application recommendation interface of the simulator, and an identification creation component is also displayed in the display area where the application identification is located; if the user wants to create a shortcut for the application, the user can click the identification creation component to trigger the creation of a shortcut to the application in the desktop interface of the computer device. Figure 6a As shown, the application recommendation interface of the simulator includes an application identifier 601 of an installed application, and an identifier creation component 602 is displayed in the display area where the application identifier 601 is located; in response to the user's triggering operation on the identifier creation component 602, a shortcut to the application is displayed in the desktop interface of the computer device.

[0134] Of course, the logo creation operations performed by users for installed applications in the simulator's application recommendation interface are not limited to the above Figure 6a For example, a user can perform a shortcut operation (such as inputting a shortcut key through the input keyboard of a computer device, which is a virtual keyboard or an external physical keyboard of the computer device) or double-click an installed application in the application recommendation interface of the simulator. At this time, the simulator responds to the shortcut operation or double-click operation and triggers the display of a shortcut of the application in the desktop interface of the computer device. See the schematic diagram of the user performing a shortcut operation in FIG. Figure 6b , the user controls the cursor on the display screen through the input device of the computer device (such as a mouse externally connected to the computer device, which is a position indicator for indicating the vertical and horizontal coordinate positions of the display screen of the computer device) and selects the application identifier of the installed application in the application recommendation interface of the simulator. Then, the user inputs the shortcut key P through the input keyboard of the computer device. At this time, the simulator responds to the shortcut key P input by the input keyboard and triggers the display of the shortcut of the application in the desktop interface of the computer device. Similarly, the schematic diagram of the user performing a double-click operation can be seen in Figure 6c The user controls the cursor on the display screen through the input device of the computer device and clicks twice in succession in the display area where the application logo of the application is located. At this time, the simulator responds to the operation of the cursor position being triggered twice in succession, triggering the display of a shortcut to the application in the desktop interface of the computer device.

[0135] S202: In response to a function invoking operation on an application identifier, display one or more application function components of the application program.

[0136] Among them: ① Each application function component can be used to trigger an application function of the application, that is, one application function component corresponds to one application function, and the corresponding application function provided by the application can be called through the application function component. The application function component includes at least one of the following: a scanning function component, a payment function component, a playback function component, an information viewing function component, and a search function component. When the scanning function component is triggered, the scanning function of the application can be quickly called up; when the payment function component is triggered, the payment function of the application can be quickly called up; when the playback function component is triggered, the audio and video playback function of the application can be quickly called up; when the information viewing function component is triggered, the new message viewing function of the application can be quickly called up; and when the search function component is triggered, the search function of the application can be quickly called up. It should be understood that the application functions of the application are not the same depending on the type of application; for example, the payment application has a scanning function, a payment function, and an information viewing function, etc., and the audio application has a scanning function, a playback function, and a search function, etc.; the embodiment of the present application does not limit the type and number of the application functions of the application.

[0137] ② The function-awakening operation is a user operation used to trigger the display of a shortcut control menu of an application, which includes one or more application function components of the application. The function-awakening operation performed on the application identifier may include at least one of the following: a key operation on an input device, which is a device that establishes a communication connection with a computer device, such as the aforementioned mouse externally connected to a computer device; a pressing operation on an application; and a triggering operation on a specified display position in the display area where the application identifier is located; etc.

[0138] As can be seen from the description of the aforementioned step S201, the application identifier of the application can be directly displayed in the application recommendation interface of the simulator, and can also be displayed on the desktop interface of the computer device in the form of a shortcut; therefore, the embodiment of the present application does not limit the display position of the application identifier of the application when the user performs a function call operation. In other words, the embodiment of the present application supports the user to perform a function call operation on the application identifier of the application in the application recommendation interface of the simulator, triggering the display of the shortcut control menu of the application; and also supports the user to perform a function call operation on the application identifier of the application on the desktop interface of the computer device, triggering the display of the shortcut control menu of the application.

[0139] In a specific implementation, if a user wants to quickly call up an application's shortcut control menu, the user can perform a function call operation on the application's application identifier (such as performing the function call operation in the simulator's application recommendation interface, or performing the function call operation in the computer device's desktop interface). At this time, the computer device responds to the function call operation on the application, outputs a shortcut menu window, and displays the application's shortcut control menu in the shortcut menu window, specifically displaying one or more application function components. In this way, the application's shortcut control menu can be quickly triggered on the computer device, greatly facilitating the user's call to the application function and improving the efficiency of calling the application function.

[0140] The following is an introduction to the specific implementation process of performing a function-awakening operation on an application logo to trigger the display of an application function component in two display positions of the application logo in conjunction with the accompanying drawings, wherein:

[0141] (1) The function invoking operation performed on the application identifier is: a key operation on the input device.

[0142] Taking the input device as an external mouse of a computer device as an example, the user controls the mouse to move the cursor on the display screen of the computer device, and selects or operates the interface element pointed by the cursor by left-clicking or right-clicking the mouse. In the embodiment of the present application, after controlling the input device to move the cursor to the display area where the application logo of the application is located, the user performs a right-click operation on the input device (such as clicking the right button of the mouse) to trigger the display of a shortcut menu window; the shortcut control menu of the application is displayed in the shortcut menu window.

[0143] For a schematic diagram of the application logo of an application when a user right-clicks it in the application recommendation interface of the simulator, see Figure 7a .like Figure 7a As shown, if the user wants to quickly trigger the application function of the application, the user can control the input device - mouse, and move the cursor 701 in the display screen of the computer device to the display area where the application identifier 702 of the application in the application recommendation interface of the simulator is located, and the cursor 701 now points to the application identifier 702. Then, the user can perform a key operation (or a press operation) on the right button of the input device - mouse, and the computer device detects that the right button of the input device - mouse is triggered, and the cursor 701 points to the application identifier 702, then the shortcut menu window 703 corresponding to the application identifier 702 is output in the application recommendation interface of the simulator; the shortcut menu window 703 displays the shortcut control menu of the application corresponding to the application identifier 702, and the shortcut control menu includes one or more application function components, such as application function component 7031, application function component 7032 and application function component 7033.

[0144] A schematic diagram of the application logo of a user right-clicking an application in the desktop interface of a computer device can be seen in Figure 7b .like Figure 7b As shown, if the user wants to quickly trigger the application function of the application, the user can control the input device, the mouse, to move the cursor 701 in the display screen of the computer device to the display area where the application identifier 702 of the application is located on the desktop interface of the computer device, and the cursor 701 now points to the application identifier 702. Then, the user can press the right button of the input device, the mouse, and the computer device detects that the right button of the input device, the mouse, is triggered and the cursor 701 points to the application identifier 702, and outputs a shortcut menu window 703 corresponding to the application identifier 702 in the desktop interface; the shortcut menu window 703 displays a shortcut control menu of the application corresponding to the application identifier 702, and the shortcut control menu includes one or more application function components, such as application function component 7031, application function component 7032, and application function component 7033.

[0145] (2) The function invoking operation performed on the application identifier is: a pressing operation on the application identifier.

[0146] If the display screen of the computer device is a touch screen that supports touch screen operations; the embodiment of the present application supports the user to quickly trigger the application capability by directly pressing the application logo on the display screen of the computer device with a finger. Among them, the pressing operation includes: a single-finger pressing operation or a multi-finger pressing operation (such as a double-finger pressing operation), etc., and can also include a pressing operation on the application logo using a physical device, such as the physical device is an electronic pen, etc. The following is an illustrative explanation using a pressing operation as a multi-finger pressing operation, specifically a double-finger pressing operation; a double-finger pressing operation refers to an operation in which two fingers of the user (such as the index finger and middle finger of the right hand) simultaneously press two display positions in the display area where the application logo is located.

[0147] For a diagram of a user pressing the application logo of an application with two fingers in the application recommendation interface of the simulator, see Figure 8a .like Figure 8a As shown, if the user wants to quickly trigger the application function of an application and the display screen of the computer device is a touch screen, the user can directly perform a two-finger press operation on the application identifier of the application in the application recommendation interface of the simulator; at this time, a shortcut menu window corresponding to the application identifier is output in the application recommendation interface of the simulator, and the shortcut menu window displays a shortcut control menu of the application corresponding to the application identifier.

[0148] A schematic diagram of a user pressing an application logo of an application with two fingers in a desktop interface of a computer device can be seen in Figure 8b .like Figure 8bAs shown, if the user wants to quickly trigger the application function of an application and the display screen of the computer device is a touch screen, the user can perform a two-finger press operation on the shortcut of the application on the desktop interface of the computer device; at this time, a shortcut menu window corresponding to the application identifier is output in the application recommendation interface of the simulator; the shortcut menu window displays a shortcut control menu of the application corresponding to the application identifier.

[0149] (3) The function invoking operation performed on the application identifier is: a triggering operation on a specified display position in the display area where the application identifier is located.

[0150] The designated display position in the display area where the application logo is located may include: the right position or the left position in the display area where the application logo is located, the lower right corner position in the display area where the application logo is located, etc. The embodiment of the present application does not limit the specific position of the designated display position in the display area where the application logo is located.

[0151] A schematic diagram of a user performing a trigger operation on a specified display position in a display area where an application logo of an application is located in an application recommendation interface of a simulator can be seen in Figure 9a .like Figure 9a As shown, it is assumed that the designated display position in the display area where the application identifier is located is the lower right corner position 901 in the display area where the application identifier is located. In this case, if the user wants to quickly trigger the application function of the application, the user can perform a trigger operation (such as controlling a cursor to perform a click operation, or performing a click operation with a finger) on the lower right corner position 901 in the display area where the application identifier of the application is located in the application recommendation interface of the simulator. At this time, a shortcut menu window corresponding to the application identifier is output in the application recommendation interface of the simulator, and the shortcut menu window displays a shortcut control menu of the application corresponding to the application identifier.

[0152] A schematic diagram of a user performing a trigger operation on a specified display position in a display area where an application logo of an application is located in an application recommendation interface of a simulator can be seen in Figure 9b .like Figure 9b As shown, it is assumed that the designated display position in the display area where the application identifier is located is the lower right corner position in the display area where the application identifier is located. In this case, if the user wants to quickly trigger the application function of the application, the user can perform a trigger operation (such as controlling a cursor to perform a click operation, or performing a click operation with a finger) on the lower right corner position in the display area where the application identifier of the application is located in the desktop interface of the computer device; at this time, a shortcut menu window corresponding to the application identifier is output in the desktop interface, and one or more application function components of the application corresponding to the application identifier are displayed in the shortcut menu window.

[0153] It should be noted that the embodiment of the present application emphasizes that the application function of the application is quickly triggered in the second operating system through the application identifier of the application running in the first operating system; Figure 7a , Figure 7b , Figure 8a , Figure 8b , Figure 9a and Figure 9b The function invoking operations shown are exemplary and do not limit the specific operations of triggering the application functions of the application program.

[0154] It should also be noted that the function-awakening operation performed on the application identifier can be different from the daily user operation of the computer device; for example, the function-awakening operation is a triggering operation on a specified display position in the display area where the application identifier is located. In this way, when the user performs the function-awakening operation on the application identifier, only the application function component of the application program is triggered and displayed, which is not easy for the user to confuse the daily user operation performed on the computer device.

[0155] The embodiment of the present application also supports the use of daily user operations that users usually use on computer devices as function-evoking operations that evoke application functions of applications; for example, the key operation performed by the user on the input device is used - the right-click operation of the mouse, and for example, the pressing operation performed by the user on the touch screen is used. The user can quickly trigger the application function of the application by performing daily user operations, which does not increase the learning cost of the user on the computer device for the function-evoking operation, while improving the efficiency of calling the application function. In the case of using daily user operations as function-evoking operations that evoke application functions of applications, when the user performs the function-evoking operation in the computer device, the shortcut control menu of the application can be triggered at the same time, as well as the preset functions that can be triggered by the daily execution of the function-evoking operation in the computer device. For example, when the right-click operation (i.e., the key operation for the input device) is performed on the application identifier of the application in the desktop interface of the computer device, the preset function triggered is the system function preset by the second operating system for the application, and the preset function may include but is not limited to: open function, cut function, delete function, compress function, rename function and attribute function, etc. For another example, when a right-click operation is performed on an application identifier of an application in the application recommendation interface of the simulator, the preset function triggered is the function preset by the simulator for the application, and the preset function may include but is not limited to: an uninstall function and an update function, etc.

[0156] Based on this, in response to the function invoking operation for the application identifier, the computer device not only outputs the shortcut control menu of the application, but also outputs the preset menu component corresponding to the preset function (preset by the computer device or preset by the simulator), and one of the preset menu components is used to trigger a preset function, and the preset menu component can be provided by the second operating system or the simulator. In other words, when the user performs a function invoking operation for the application identifier of the application, the shortcut menu window triggered to be displayed is not only used to display the shortcut control menu of the application, but also used to display the preset menu component corresponding to the predicted function preset by the computer device or the simulator; the user can trigger the application function related to the application, or trigger the preset function in the shortcut menu window according to his actual needs.

[0157] In one implementation, a preset menu component and a shortcut control menu are simultaneously displayed in a shortcut menu window. That is, in the output shortcut menu window, not only can the preset menu component corresponding to the computer device or simulator be directly displayed, but also the shortcut control menu of the application can be directly displayed. In a specific implementation, the shortcut menu window includes a first display area and a second display area, and the first display area and the second display area are separated by a separator bar. One or more preset menu components provided by the computer device or simulator are displayed in the first display area in the shortcut menu window, and the shortcut control menu of the application, that is, one or more application function components, is displayed in the second display area in the shortcut menu window. This method of displaying preset menu components and application function components in different areas makes it easy for users to intuitively distinguish between the two types of components from the shortcut menu window, thereby improving the user experience.

[0158] like Fig.10 As shown, when a user right-clicks an application identifier of an application on a desktop interface of a computer device, a shortcut menu window 1001 is displayed; the shortcut menu window 1001 includes a first display area 1002 and a second display area 1003. The first display area 1002 displays a preset menu component provided by the computer device or the second operating system, such as a copy menu component 10021 corresponding to a copy function and a compression menu component 10022 corresponding to a compression function. The second display area 1003 displays a shortcut control menu of the application, such as a scan function component 10031 corresponding to a scan function and an add friend function component 10032 corresponding to an add friend function.

[0159] In other implementations, only the preset menu component and the entry for triggering the display of the shortcut control menu are displayed in the shortcut menu window. That is to say, the entry for triggering the shortcut control menu is set in the shortcut menu window, and the shortcut menu window is still triggered and displayed by daily user operations (such as right-click operations); while ensuring that the user can quickly trigger the shortcut control menu in the computer device, the window content of the shortcut menu window triggered by the right-click operation will not be greatly changed. In a specific implementation, when the application identifier of the application running in the first operating system is right-clicked, a shortcut menu window is output, and the shortcut menu window includes an application function trigger option, and the entry for triggering the application function component is set in the application function trigger option. If the application function trigger option in the shortcut menu window is triggered, a function display window is output, and the shortcut control menu of the application, that is, one or more application function components, is displayed in the function display window.

[0160] like Fig.11 As shown, when a user right-clicks an application identifier of an application on a desktop interface of a computer device, a shortcut menu window is displayed; the shortcut menu window includes an application function trigger option 1101, and the application function trigger option 1101 is used to invoke the application function of the application. When the user performs a trigger operation on the application function trigger option 1101, it indicates that the user wants to quickly trigger the application function of the application, and a function display window 1102 is displayed at this time, and one or more application function components of the application are displayed in the function display window 1102.

[0161] It can be seen that the embodiments of the present application support the use of daily user operations originally supported by the computer device to trigger the application capabilities of the application, such as using the right-click operation to trigger the application of the application, so that the user can quickly perform the function call operation according to the operating habits, improve efficiency, and increase user satisfaction with the simulator, thereby improving user retention. In other words, the embodiments of the present application can seamlessly map the ability of long pressing the application logo on the mobile device to trigger the application function to the operation interaction of the simulator, specifically, through the right mouse button on the second operating system and other interactive operations equivalent to the right-click response, to trigger the mobile application on the computer device of the second operating system to display the application capabilities of the mobile application on the first operating system.

[0162] In addition, when there are many application function components of an application, considering that the display area of ​​the shortcut menu window (or function display window) is limited, the embodiment of the present application supports users to flexibly control the display status of one or more application function components of the application according to their own viewing needs. Among them, the display status of the application function component includes a visible state and a hidden state. When the application function component is in the visible state, the application function component is displayed in the shortcut menu window (or function display window); when the application function component is in the hidden state, the application function component is not displayed in the shortcut menu window (or function display window).

[0163] Specifically, the process of the user flexibly controlling the display state of the application function component may include: the user performs a display control operation on one or more application function components of the application in the shortcut menu window, and the computing device displays at least one candidate application function component controlled to be displayed according to the display control operation performed by the user on the one or more application function components. The candidate application function component is a candidate application function component that needs to be displayed by the user operation among the one or more application function components, that is, the candidate application function component is in a displayed state, and other application function components except the candidate application function component among the one or more application function components are in a hidden state.

[0164] The specific operation process of the display control operation of the application function component in the embodiment of the present application is not limited. Exemplarily, the display control operation includes at least one of the following: ① Scrolling operation of one or more application function components through an input device. Fig.12a As shown, the user can control the input device - the cursor corresponding to the mouse is in the shortcut menu window, specifically in the display area where one or more application function components are located; then, control the mouse to perform a scrolling operation, at which time one or more application function components are dynamically displayed in the shortcut menu window by scrolling, and the application function components displayed on the display screen are candidate application function components. ② Slide operation for one or more application function components. As shown Figure 12b As shown, a slide bar 1201 is displayed in the shortcut menu window; when the display screen of the computer device is a touch screen, the user can control the slide bar 1201 with a finger to slide, or control the cursor on the display screen to slide the slide bar 1201 through an input device to dynamically control the appearance or hiding of one or more application function components in the shortcut menu window. ③ Expand operation for one or more application function components. Fig.12cAs shown, a view option 1202 is displayed adjacent to each application function component in the shortcut menu window; when the application function component is in a visible state, a trigger operation is performed on the corresponding view option 1202, and the application function component is hidden; when the application function component is in a hidden state, a trigger operation is performed on the corresponding view option 1202, and the application function component is visible.

[0165] S203: In response to the triggering operation on the target application function component, displaying a function execution interface corresponding to the target application function component.

[0166] Among them, the target application function component is the application function component corresponding to the target application function that the user wants to use in one or more application function components of the application. Specifically, the user performs a trigger operation on the target application function component in the shortcut menu window, and the computer device responds to the user's trigger operation on the target application function component by starting the function execution interface corresponding to the target application function in the application through the simulator; the function execution interface can be understood as a service interface for executing the target application function triggered by the target application function component. For example, if the target application function is a scanning function, then the function execution interface corresponding to the scanning function component is a service interface for scanning; for another example, if the target application function is an information viewing function, then the function execution interface corresponding to the information viewing function component is a service interface for viewing new information. Taking the target application function as the scanning function as an example, the schematic diagram of the function execution interface corresponding to the scanning function can be seen in Fig.13 ;like Fig.13 As shown, when the scanning function component 1301 in the shortcut menu window is triggered, a function execution interface 1302 corresponding to the scanning function is displayed, and the function execution interface 1302 can implement scanning.

[0167] In summary, the embodiment of the present application supports the user to directly perform a function call operation on the application identifier of the displayed application, triggering one or more application function components of the displayed application. In other words, the ability to quickly call up the application function component by directly performing a function call operation on the application identifier in a computer device is equivalent to the ability to quickly call up the application function of the application by long pressing the application identifier in a mobile device, so that the user can quickly call up the application function by performing the same or similar interactive operations in the computer device and the mobile device, achieving better compatibility of cross-platform applications and broadening the use scenarios of the application. Furthermore, if the user wants to execute an application function of an application, the user can perform a trigger operation on the target application function component in one or more application function components, and the function execution interface corresponding to the target application function component is displayed, so that the user can execute the corresponding application function in the function execution interface; compared with the need to enter the application to perform a series of interactive operations to open the function execution interface, the operation process of the application function is simplified, and the user's call efficiency for the application function is greatly improved.

[0168] The foregoing Figure 2 The embodiment shown mainly introduces the processing method of the application provided by the embodiment of the present application from the interface dimension. The following introduces the processing method from the background dimension. The background technical logic involved in the embodiment of the present application is as follows: Fig.14 As shown, it mainly includes shortcut creation, application function component integration and function synchronization. Among them, shortcut creation refers to the process of creating a shortcut on the desktop interface of the first operating system for an application running on the first operating system. Application function component integration refers to the process of integrating the shortcut control menu of the application into the original shortcut menu window of the computer device, that is, displaying the application function component and the preset function component of the computer device in the same window. Function synchronization refers to the process of quickly calling up the target application function corresponding to the target application function in the application in the computer device by triggering the target application function component.

[0169] Combine the following Fig.15 The flowchart of another processing method of an application is shown, which introduces the above three background logics. Fig.15 The application processing method shown in the figure can be executed by a computer device, which can be the aforementioned Figure 1 The windows system device 101 shown. The processing method may include but is not limited to steps S1501-S1503:

[0170] S1501: Display the application ID of the application.

[0171] As mentioned above, the display method of displaying the application identifier of the application in the computer device may include displaying the application identifier of the application as a shortcut on the desktop interface of the computer device, or displaying the application identifier of the application in the application recommendation interface of the simulator. The specific implementation process of displaying the application identifier of the application on the desktop interface or the application recommendation interface can be referred to the above Figure 2 The relevant description of the specific implementation process shown in step S201 in the illustrated embodiment is not repeated here.

[0172] The following is an example of a computer device that deploys a Windows operating system, and the background technology implementation of displaying the application identifier of an application in a computer device as a shortcut is introduced. Specifically, the embodiment of the present application supports using the interface (API) provided by the Windows operating system to create a desktop shortcut for an application running in a simulator, and associates the application path of the application in the simulator with the created shortcut; in this way, when the shortcut is triggered on the desktop interface of the computer device, the application can be quickly linked to the application through the application path. In detail, the embodiment of the present application can specifically use the ShellLink interface of the Windows operating system to create a shortcut, and the ShellLink interface is an interface for processing shortcuts in the Windows operating system. In the embodiment of the present application, the IShellLink interface and the IPersistFile interface are mainly used to create shortcuts. Among them, the IShellLink interface provides information reading and writing functions for shortcuts, and various attribute information of shortcuts can be obtained and set through the IShellLink interface. The IPersistFile interface provides a continuous file reading and writing function for shortcuts; through the IPersistFile interface, the created shortcut can be saved to the file system of the computer device.

[0173] For example, using the programming language C++, the IShellLink interface and the IPersistFile interface of the Windows operating system, the process of creating a shortcut for an application can be seen as follows:

[0174] ① Create an IShellLink object: Create an IShellLink object through the CoCreateInstance function; the IShellLink object is an object used to create and manage shortcuts in the Windows operating system, and can be understood as a shortcut object for an application.

[0175] ② Set the property information of the application's shortcut through the IShellLink object: Use the methods of the IShellLink interface to set the properties of the application's shortcut, such as the application path of the application, the interface path of the function execution interface corresponding to the application function of the application, the working directory and description information, etc.

[0176] ③Get IPersistFile interface: Get IPersistFile interface by querying IShellLink object.

[0177] ④ Save shortcut: Use the Save method of the IPersistFile interface (or expressed as the IPersistFile::Save method) to save the shortcut (that is, the IShellLink object with set property information, specifically a shortcut file) to the file system of the computer device.

[0178] After creating a shortcut file for the application based on the above process, when the desktop interface is rendered and displayed in the computer device or the application recommendation interface is rendered and displayed in the simulator, the shortcut file of the application will be called from the file system of the computer device, and the application identifier of the application will be displayed in the desktop interface or the application recommendation interface according to the shortcut file.

[0179] S1502: In response to a function invoking operation on an application identifier, display one or more application function components of the application according to target menu data of the application.

[0180] It should be noted that, in response to the function invoking operation of the application program, the interface implementation process of displaying one or more application functions of the application program can be referred to the aforementioned Figure 2 The relevant description of the specific implementation process shown in step S202 of the illustrated embodiment will not be repeated here. The background process corresponding to the interface implementation process is introduced below: When the user performs a trigger operation on the target application function component of the application in the shortcut menu window, the computer device obtains the target menu data of the application through the simulator, and realizes the display of one or more application function components of the application on the display screen of the computer device. Among them, the target menu data defines the display rules for displaying the application function components of the application in the second operating system; for example, the display rules are: the scanning function component in the mobile client displays the function icon and function name on the display screen, and the function icon is displayed on the left side of the function name.

[0181] In a specific implementation, when the shortcut of an application is displayed in a computer device, the target menu data of the application will be constructed so that when the shortcut is triggered, the application function components of the application can be displayed based on the target menu data. The target menu data generation process includes: obtaining the menu resource file of the application; the menu resource file includes extended menu data, and the extended menu data is the component properties of the application function components that can be quickly invoked by the function invocation operation customized by the developer; that is, the component properties of each application function component in one or more application function components are defined in the extended menu data. As mentioned above, a working directory is set in the shortcut file of the application, and the menu resource file of the application is usually stored under the working project, such as the menu resource file is stored in an XML file under the res / menu directory with the file name main_menu.xml, and the main_menu.xml file includes the extended menu data of the application function components customized by the developer. The exemplary code of the main_menu.xml file is as follows:

[0182]

[0183] Furthermore, the computer device obtains a menu data template of the second operating system of the computer device, and the menu data template is used to standardize the display rules for displaying the application function components of the application running in the first operating system in the second operating system. Then, the customized extended menu data is extracted from the menu resource file of the application, and the extended menu data is filled into the menu data template to obtain the target menu data; that is, the extended menu data related to the application function components that can be quickly triggered by the application is filled into the menu data template that meets the display requirements of the second operating system, which can ensure that when there is a function call operation for the application identifier, one or more application function components of the application can be output according to the target menu data and the display requirements or rules of the second operating system, thereby realizing the rapid triggering and display of the application function components of the application running in the first operating system in the second operating system.

[0184] Among them, the general process of building the extended menu data of the application and adding it to the menu resource file of the application can include: the simulator analyzes the application characteristics of the application, extracts the application functions that the application can quickly evoke (such as scanning functions or information viewing functions, etc.); designs corresponding Windows-compatible operation instructions for each application function, and generates extended menu data; associates the extended menu data with the shortcut file of the application (such as adding the extended menu data to the menu resource file under the working directory of the shortcut file), and when generating or displaying the shortcut of the application, generates target menu data based on the extended menu data, so as to integrate the application function components into the shortcut menu window, such as integrating the application function components into the right-click menu of the Windows operating system.

[0185] Taking the Windows operating system as an example, the second operating system deployed in the computer device supports the use of the Windows operating system's Shell extension technology to add extended menu data to the application's shortcut to achieve the purpose of quickly triggering the application's application function components through shortcuts. Specifically, the application's extended menu data is generated through Shell extension technology, and the extended menu data can also be called a Shell file; Shell extension technology allows developers to extend the functions of the file explorer (an important tool for managing files or folders in a computer device), including adding customized application function components to the application's menu resource file. Exemplarily, the process of customizing an application's Shell file (i.e., extended menu data) based on Shell extension technology can generally include:

[0186] ① Create a DLL (Dynamic Link Library) project; it contains a set of functions, variables, and classes that can be called by other programs, can be shared by multiple programs, and provide modularization and resource sharing functions for multiple programs.

[0187] ②Implement the IContextMenu interface, which can be used to implement a custom shortcut control menu. Through the IContextMenu interface, developers can add custom right-click menu items for specific files or folders (such as shortcut files), thereby providing more abundant operation options.

[0188] ③ Modify the registry, such as creating a .reg file (registry file), and by setting the key value in the registry file, when there is a function call operation for the application identifier, specify which files or folders can use the right-click menu items that can be set through the IContextMenu interface. Exemplarily, the .reg file may include: [HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\MyContextMenu]@="{your CLSID}", indicating that shellex\ContextMenuHandlers\MyContextMenu specifies that these files or folders can use the right-click menu items set through the IContextMenu interface.

[0189] S1503: In response to the triggering operation on the target application function component, display the function execution interface corresponding to the target application function component based on the function jump data.

[0190] In order to achieve functional synchronization, such as triggering the application function component of the Android application in the Windows system device to call the application function, and directly triggering the application function component of the Android application in the Android system device to call the application function. On the one hand, the embodiment of the present application supports the jump between the shortcut menu window and the function execution interface through the scheme mechanism; the scheme mechanism is an extension of the Uniform Resource Locator (URL), similar to a link, which can be used to design interaction with the application to display the function execution interface of the application function in the application. On the other hand, a function mapping table is maintained in the simulator, that is, the simulator includes a function mapping table, and the function mapping table stores the function data required to be called when each application function component of the application is triggered, such as the interface path of the function execution interface corresponding to the application function component and other data.

[0191] Based on this, when the user performs a trigger operation on the target application function component of the application in the shortcut menu window, the computer device responds to the user's trigger operation on the target application function component, obtains the application identification of the application, and performs subsequent operations through the simulator interface. Specifically, the simulator obtains the target function data required to be called when the target application function component is triggered from the function mapping table, and the target function data includes the jump path data of the target function interface corresponding to the target application function component (that is, the interface path mentioned above). Then, based on the jump path data and the application identification of the application, and the user's trigger operation on the target application function component, the function jump data is spliced; the spliced ​​jump data is the link data that conforms to the scheme mechanism. For example, the spliced ​​jump data is represented as: yourapp: / / yourdomain.com / path(action), yourapp is the application identification of the application, yourdomain.com is the jump path data of the function execution interface of the target application function, and path(action) represents the user's trigger operation on the target application function component. Then, based on the spliced ​​jump data, it is possible to jump to the function execution interface designed by the application for the target application function, that is, to display the function execution interface corresponding to the target application function component.

[0192] In summary, on the one hand, the embodiment of the present application supports displaying the application identifier of the application as a shortcut on the desktop interface of the computer device, so that the user can directly access the application running in the first operating system on the desktop interface, simplifying the operation process, and improving the user experience and convenience. On the other hand, the embodiment of the present application maps the ability of the application identifier to quickly trigger the application function to the computer device across platforms, so that the user can use the daily user operation in the computer device to quickly call up the application function component of the application, achieve better compatibility of cross-platform applications, broaden the use scenarios of the application, and improve the calling efficiency of the application function. On the other hand, the application function is called directly on the desktop interface for the shortcut of the application, and the interactivity of the desktop environment of the computer device is improved, which can increase the user's dependence and satisfaction on the simulator in the computer device and improve the user's retention rate in the simulator.

[0193] The method of the embodiment of the present application is described in detail above. In order to facilitate the above-mentioned scheme of the embodiment of the present application to be better implemented, the device of the embodiment of the present application is provided below accordingly. In the embodiment of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of an overall module or unit that includes the module or unit function.

[0194] Fig.16 A schematic diagram of a processing device for an application program provided by an exemplary embodiment of the present application is shown; the processing device can be used to execute Figure 2 and Fig.15 Some or all of the steps in the method embodiment shown. Fig.16 , the device comprises the following units:

[0195] The display unit 1601 is used to display the application identification of the application; the application is run in a simulator of a computer device, the simulator is used to simulate a first operating system in the computer device, the computer device is deployed with a second operating system, and the first operating system and the second operating system are different;

[0196] The processing unit 1602 is used to display one or more application function components of the application program in response to a function invoking operation on the application identifier, each application function component being used to trigger an application function of the application program;

[0197] Processing unit 1602 is also used to display a function execution interface corresponding to the target application function component in response to a triggering operation on the target application function component; the function execution interface is used to execute the target application function triggered by the target application function component; the target application function component is one of one or more application function components.

[0198] In one implementation, the function-awakening operation includes at least one of the following: a key operation on an input device, the input device being a device that establishes a communication connection with a computer device; a pressing operation on an application identifier; and a triggering operation on a specified display position in a display area where the application identifier is located;

[0199] The application function component includes at least one of the following: a scanning function component, a payment function component, a playback function component, an information viewing function component and a search function component.

[0200] In one implementation, the processing unit 1602 is configured to, in response to a function invoking operation on an application identifier, display one or more application function components of an application program, specifically to:

[0201] In response to a function invoking operation on the application identifier, outputting a shortcut menu window;

[0202] Display one or more application function components of the application in the shortcut menu window.

[0203] In one implementation, the shortcut menu window includes a first display area and a second display area; the processing unit 1602 is configured to display one or more application function components of the application in the shortcut menu window, specifically to:

[0204] Displaying one or more preset menu components in the first display area; the preset menu components are provided by the second operating system or the simulator;

[0205] One or more application function components of the application are displayed in the second display area.

[0206] In one implementation, the shortcut menu window includes an application function trigger option; the processing unit 1602 is configured to display one or more application function components of the application in the shortcut menu window, specifically to:

[0207] If the application function trigger option is triggered, the function display window is output;

[0208] One or more application function components of the application are displayed in the function display window.

[0209] In one implementation, the processing unit 1602 is further configured to:

[0210] Displaying at least one candidate application function component to be controlled to be displayed according to the display control operation performed on one or more application function components;

[0211] The display control operation includes at least one of the following: a scrolling operation on one or more application function components through an input device; a sliding operation on one or more application function components; and an expansion operation on one or more application function components.

[0212] In one implementation, the display unit, when used to display the application identifier of the application, is specifically used to:

[0213] Displaying an application recommendation interface of the simulator, wherein the application identifier is displayed in the application recommendation interface;

[0214] The processing unit 1602 is configured to, in response to a function invoking operation on an application identifier, display one or more application function components of an application program, specifically to:

[0215] In response to a function invocation operation for an application identifier in the application recommendation interface, one or more application function components of the application program are displayed.

[0216] In one implementation, the display unit, when used to display the application identifier of the application, is specifically used to:

[0217] Displaying a desktop interface of the computer device, and displaying an application identifier of the application program in the desktop interface;

[0218] Displaying an indication mark in the display area where the application mark is located; the indication mark is used to indicate that: the application corresponding to the application mark is running in the first operating system simulated by the simulator;

[0219] The processing unit 1602 is configured to, in response to a function invoking operation on an application identifier, display one or more application function components of an application program, specifically to:

[0220] In response to a function invoking operation for an application identifier in a desktop interface, one or more application function components of the application program are displayed.

[0221] In one implementation, the processing unit 1602 is further configured to:

[0222] If there is an identification creation operation for the application in the simulator, a step of displaying the application identification of the application in the desktop interface is triggered.

[0223] In one implementation, the processing unit 1602 is configured to trigger the step of displaying the application identification of the application in the desktop interface if there is an identification creation operation for the application in the simulator, specifically to:

[0224] When the application is installed in the simulator, an identification prompt information is output, where the identification prompt information is used to prompt: creating an application identification of the application in the desktop interface of the computer device;

[0225] In response to a confirmation operation performed on the identification prompt information, a step of displaying the application identification of the application program in the desktop interface is triggered.

[0226] In one implementation, the processing unit 1602, when used to display one or more application function components of the application, is specifically used to:

[0227] Acquire target menu data of the application, where the target menu data is used to define display rules for displaying application function components of the application in the second operating system;

[0228] Displaying one or more application function components of the application according to the target menu data;

[0229] Among them, the process of generating target menu data includes: obtaining the menu resource file of the application, the menu resource file includes extended menu data, and the extended menu data defines the component attributes of each application function component in one or more application function components; obtaining the menu data template of the second operating system, the menu data template is used to standardize the component display rules in the second operating system; extracting the extended menu data from the menu resource file, and filling the extended menu data into the menu data template to obtain the target menu data.

[0230] In one implementation, the simulator includes a function mapping table, in which function data required to be called when each application function component is triggered is stored; the processing unit 1602 is used to respond to the triggering operation of the target application function component and display the function execution interface corresponding to the target application function component, specifically for:

[0231] In response to a triggering operation on a target application functional component, obtaining an application identifier of the application program;

[0232] Obtaining target function data required to be called when the target application function component is triggered from the function mapping table; the target function data includes jump path data of the target function interface corresponding to the target application function component;

[0233] splicing the application identifier and the target function data to obtain function jump data;

[0234] The function execution interface corresponding to the target application function component is displayed based on the function jump data.

[0235] According to one embodiment of the present application, Fig.16The various units in the processing device of the application shown can be separately or completely combined into one or several other units to form, or one (some) of the units can be further divided into multiple functionally smaller units to form, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application. The above-mentioned units are divided based on logical functions. In practical applications, the function of one unit can also be implemented by multiple units, or the functions of multiple units can be implemented by one unit. In other embodiments of the present application, the processing device of the application can also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented by the collaboration of multiple units. According to another embodiment of the present application, it can be executed by running on a general computing device such as a computer including processing elements and storage elements such as a central processing unit (CPU), a random access memory (RAM), and a read-only memory (ROM). Figure 2 and Fig.15 A computer program for each step of the corresponding method shown in FIG. Fig.16 The processing device based on media application shown in and the processing method of the application program of the embodiment of the present application are implemented. The computer program can be recorded on, for example, a computer readable recording medium, and loaded into the above-mentioned computing device through the computer readable recording medium and run therein.

[0236] In the embodiment of the present application, it is supported to directly perform a function call operation on the application identifier in the computer device to quickly call up the application function component, which is equivalent to the ability to quickly call up the application function of the application program by long pressing the application identifier in the mobile device deployed with the first operating system, so that the user can perform the same or similar interactive operations in the computer device as in the mobile device to quickly call up the application function, thereby achieving better compatibility of cross-platform applications and broadening the application usage scenarios. In addition, if the user wants to execute an application function of the application, the user can perform a trigger operation on the target application function component in one or more application function components in the computer device, and the function execution interface corresponding to the target application function component is displayed at this time, so that the user can execute the target application function in the function execution interface; compared with the need to enter the application to perform a series of interactive operations to open the function execution interface, the operation process of the user triggering the application function in the computer device is simplified, and the efficiency of the user calling the application function in the computer device is greatly improved.

[0237] Fig.17 FIG. 1 shows a schematic diagram of a computer device provided by an exemplary embodiment of the present application. Fig.17, the computer device includes a processor 1701, a communication interface 1702 and a computer-readable storage medium 1703. The processor 1701, the communication interface 1702 and the computer-readable storage medium 1703 may be connected via a bus or other means. The communication interface 1702 is used to receive and send data. The computer-readable storage medium 1703 may be stored in the memory of the computer device, the computer-readable storage medium 1703 is used to store computer programs, and the processor 1701 is used to execute the computer programs stored in the computer-readable storage medium 1703. The processor 1701 (or CPU) is the computing core and control core of the computer device, which is suitable for implementing one or more computer programs, and is specifically suitable for loading and executing one or more computer programs to implement corresponding method flows or corresponding functions.

[0238] The embodiment of the present application also provides a computer-readable storage medium (Memory), which is a memory device in a computer device for storing programs and data. It is understandable that the computer-readable storage medium here can include both built-in storage media in the computer device and, of course, extended storage media supported by the computer device. The computer-readable storage medium provides a storage space that stores the processing system of the computer device. In addition, one or more computer programs suitable for being loaded and executed by the processor 1701 are also stored in the storage space, and these computer programs can be one or more computer programs. It should be noted that the computer-readable storage medium here can be a high-speed RAM memory, or a non-volatile memory, such as at least one disk storage; optionally, it can also be at least one computer-readable storage medium located away from the aforementioned processor.

[0239] In one embodiment, the computer device may be the desktop device, mobile device or embedded device mentioned in the aforementioned embodiment; one or more computer programs are stored in the computer-readable storage medium; the processor 1701 loads and executes the one or more computer programs stored in the computer-readable storage medium to implement the corresponding steps in the above-mentioned application processing method embodiment; in a specific implementation, the one or more computer programs in the computer-readable storage medium are loaded and executed by the processor 1701 to execute the steps of each embodiment of the present application; wherein, the steps of each embodiment of the present application can refer to the relevant description of the aforementioned embodiments, and will not be repeated here.

[0240] Based on the same inventive concept, the principles and beneficial effects of solving the problems by the computer device provided in the embodiment of the present application are similar to the principles and beneficial effects of solving the problems by the processing method of the application in the method embodiment of the present application. Please refer to the principles and beneficial effects of the implementation of the method. For the sake of concise description, they will not be repeated here.

[0241] An embodiment of the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the processing method of the above-mentioned application is implemented.

[0242] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0243] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs (one or more). When loading and executing a computer program on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer program can be stored in a computer-readable storage medium or transmitted by a computer-readable storage medium. The computer program can be transmitted from a website site, a computer, a server or a data center by wired (for example, coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (for example, infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrations. Available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, digital video disks (DVDs)), or semiconductor media (eg, solid state disks (SSDs)).

[0244] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for processing an application, characterized in that: include: Displaying an application identifier of the application; The application is run in a simulator of a computer device, the simulator is used to simulate a first operating system in the computer device, the computer device is deployed with a second operating system, the first operating system and the second operating system are different; In response to a function invoking operation on the application identifier, displaying one or more application function components of the application, each of the application function components being used to trigger an application function of the application; In response to a triggering operation on a target application functional component, displaying a function execution interface corresponding to the target application functional component; The function execution interface is used to execute the target application function triggered by the target application function component; the target application function component is one of the one or more application function components.

2. The method according to claim 1, characterized in that The function-awakening operation includes at least one of the following: a key operation on an input device, the input device being a device that establishes a communication connection with the computer device; a pressing operation on the application identifier; and a triggering operation on a designated display position in the display area where the application identifier is located; The application function component includes at least one of the following: a scanning function component, a payment function component, a playing function component, an information viewing function component and a search function component.

3. The method according to claim 1 or 2, characterized in that The step of displaying one or more application function components of the application program in response to the function invoking operation on the application identifier includes: In response to a function invoking operation on the application identifier, outputting a shortcut menu window; One or more application function components of the application are displayed in the shortcut menu window.

4. The method according to claim 3, characterized in that The shortcut menu window includes a first display area and a second display area; and displaying one or more application function components of the application in the shortcut menu window includes: Displaying one or more preset menu components in the first display area; the preset menu components are provided by the second operating system or the simulator; One or more application function components of the application are displayed in the second display area.

5. The method according to claim 3, characterized in that The shortcut menu window includes an application function trigger option; the one or more application function components of the application program are displayed in the shortcut menu window, including: If the application function trigger option is triggered, a function display window is output; One or more application function components of the application are displayed in the function display window.

6. The method according to claim 1, characterized in that The method further comprises: Displaying at least one candidate application function component to be controlled to be displayed according to the display control operation performed on one or more of the application function components; The display control operation includes at least one of the following: a scrolling operation on one or more of the application function components through an input device; a sliding operation on one or more of the application function components; and an expansion operation on one or more of the application function components.

7. The method according to claim 1, characterized in that The displaying of the application identification of the application program includes: Displaying an application recommendation interface of the simulator, wherein the application identifier is displayed in the application recommendation interface; The step of displaying one or more application function components of the application program in response to the function invoking operation on the application identifier includes: In response to a function invoking operation for the application identifier in the application recommendation interface, one or more application function components of the application program are displayed.

8. The method according to claim 1, characterized in that The displaying of the application identification of the application program includes: Displaying a desktop interface of the computer device, and displaying an application identifier of the application program in the desktop interface; Displaying an indication mark in the display area where the application mark is located; the indication mark is used to indicate that: the application corresponding to the application mark is running in the first operating system simulated by the simulator; The step of displaying one or more application function components of the application program in response to the function invoking operation on the application identifier includes: In response to a function invoking operation for the application identifier in the desktop interface, one or more application function components of the application program are displayed.

9. The method according to claim 8, characterized in that Before displaying the application identifier of the application program in the desktop interface, the method further includes: If there is an identification creation operation for the application in the simulator, the step of displaying the application identification of the application in the desktop interface is triggered.

10. The method according to claim 9, characterized in that If there is an identification creation operation for the application in the simulator, triggering the step of displaying the application identification of the application in the desktop interface includes: When the installation of the application program in the simulator is completed, an identification prompt information is output, wherein the identification prompt information is used to prompt: creating an application identification of the application program in the desktop interface of the computer device; In response to a confirmation operation performed on the identification prompt information, the step of displaying the application identification of the application program in the desktop interface is triggered.

11. The method according to claim 1, characterized in that The display of one or more application function components of the application program includes: Acquire target menu data of the application, where the target menu data is used to define a display rule for displaying application function components of the application in the second operating system; Displaying one or more application function components of the application according to the target menu data; Among them, the generation process of the target menu data includes: obtaining the menu resource file of the application, the menu resource file includes extended menu data, and the extended menu data defines the component attributes of each of the one or more application function components; obtaining the menu data template of the second operating system, the menu data template is used to standardize the component display rules in the second operating system; extracting the extended menu data from the menu resource file, and filling the extended menu data into the menu data template to obtain the target menu data.

12. The method according to claim 1, characterized in that The simulator includes a function mapping table, in which function data required to be called when each application function component is triggered is stored; The step of displaying a function execution interface corresponding to the target application function component in response to a triggering operation on the target application function component includes: In response to a triggering operation on a target application functional component, obtaining an application identifier of the application program; Acquire the target function data required to be called when the target application function component is triggered from the function mapping table; the target function data includes the jump path data of the target function interface corresponding to the target application function component; splicing the application identifier and the target function data to obtain function jump data; The function execution interface corresponding to the target application function component is displayed based on the function jump data.

13. A device for processing an application, characterized in that: include: A display unit, used to display the application identification of the application program; The application is run in a simulator of a computer device, the simulator is used to simulate a first operating system in the computer device, the computer device is deployed with a second operating system, the first operating system and the second operating system are different; a processing unit, configured to display one or more application function components of the application program in response to a function invoking operation on the application identifier, each of the application function components being configured to trigger an application function of the application program; The processing unit is further configured to display a function execution interface corresponding to the target application function component in response to a triggering operation on the target application function component; The function execution interface is used to execute the target application function triggered by the target application function component; the target application function component is one of the one or more application function components.

14. A computer device, characterized in that: a processor adapted to execute a computer program; A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by the processor, the processing method of the application program according to any one of claims 1 to 12 is implemented.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is suitable for being loaded by a processor and executing the processing method of the application program according to any one of claims 1 to 12.

16. A computer program product, characterized in that The computer program product includes a computer program, and when the computer program is executed by a processor, the computer program implements the method for processing an application according to any one of claims 1 to 12.

Images