Fast application execution method and device and storage medium

Abstract

The invention relates to a fast application execution method and device and a storage medium. The fast application execution method comprises the steps of calling a fast application package management tool based on a plug-in function of a first integrated development environment, generating an application file for executing the operation based on the fast application package management tool, and executing the operation based on the application file. The fast-running application is developed in the first integrated development environment, developers are helped to concentrate on function development, and the development and debugging process is simplified.

Description

Technical Field

[0001] The present disclosure relates to software development, and more particularly to a quick application execution method, device, and storage medium. Background Art

[0002] The IDEA plug-in is a plug-in that can be installed in an integrated development environment (IDE) (such as IDEA and Android Studio) developed by JetBrains. It can enhance the functionality of the IDE or customize development requirements, thereby improving the development efficiency and code quality of developers.

[0003] Currently, IDEA plug-ins are a very popular technology, and there are already many mature plug-ins, covering many aspects such as code quality, build tools, framework support, etc. With the development of IDEA itself, new plug-ins are constantly emerging.

[0004] Quick App is a new type of application jointly developed by mobile phone manufacturers. It uses a lightweight framework and can be used directly without downloading and installing. With the participation of major mobile phone manufacturers and the gradual establishment of the ecological environment, Quick App has quickly gained widespread attention and recognition. At present, Quick App has become one of the leading application ecological service platforms in China, with many high-quality applications and users, and its development prospects are broad.

[0005] In the related art, there is a plug-in-based Android application packaging and distribution method, which can only package Android applications but not quick applications and has no visual interface. Summary of the invention

[0006] In order to overcome the problems existing in the related art, the present disclosure provides a quick application execution method, device and storage medium.

[0007] According to a first aspect of an embodiment of the present disclosure, a quick application execution method is provided, the method comprising calling a quick application package management tool based on a plug-in function of a first integrated development environment, generating an application file for executing the operation based on the quick application package management tool, and executing the operation based on the application file.

[0008] In one implementation, calling the quick application package management tool based on the plug-in function of the first integrated development environment includes: in response to determining that the first integrated development environment running on the first device executes a quick application operation, starting a first process based on the plug-in function of the first integrated development environment, the first process being used to execute a command to call the quick application package management tool; executing the command to call the quick application package management tool to call the quick application package management tool.

[0009] In one implementation, the command for calling the quick application package management tool is used to instruct the first device to detect a code runtime environment that supports the quick application operation, and to detect version information of the quick application package management tool supported in the code runtime environment; before calling the quick application package management tool, the method further includes: determining that the first device is detected to have the code runtime environment installed, and obtaining version information of the quick application package management tool to determine that the calling of the quick application package management tool is supported.

[0010] In one embodiment, the operation includes running a quick application; the operation is performed based on the application file, including: starting a second process, the second process is used to execute a monitoring service status command, the monitoring service status command is used to start a service corresponding to the quick application; executing the monitoring service status command to start the service, and pushing the application file to a second device based on the corresponding address of the service, so as to run the quick application in a quick application debugger of the second device.

[0011] In one embodiment, the operation includes quick application packaging; the operation is performed based on the application file, including: starting a third process, the third process is used to execute commands for creating a package and / or releasing a package; executing commands for creating a package and / or releasing a package to generate a debug version of the application file package and a release version of the application file package.

[0012] In one implementation, before generating the application file package of the release version, the method further includes: determining whether a signature file exists in the quick application project.

[0013] In one implementation, the method further includes: obtaining a metadata file in a quick application project, and obtaining quick application project information in the metadata file; and displaying the quick application project information.

[0014] In one embodiment, the determining to execute a quick application operation in a first integrated development environment running on a first device includes: in response to detecting manipulation of an operation control, determining to execute a quick application operation in the first integrated development environment running on the first device; the operation control is provided as a toolbar displayed in the first integrated development environment running on the first device.

[0015] In one embodiment, the method also includes: in response to detecting the presence of a second device set connected to the first device when the first device is running the first integrated development environment; obtaining information of each second device in the second device set, and displaying the information of each device in the second device set in a list form.

[0016] In one embodiment, the method further includes: in response to detecting that the target second device displayed in the list is selected, checking whether a quick app debugger and a quick app preview tool are installed in the target second device based on a check instruction.

[0017] According to a second aspect of an embodiment of the present disclosure, a quick application execution device is provided, the device comprising:

[0018] A calling unit, which calls a quick application package management tool based on a plug-in function of the first integrated development environment;

[0019] The execution unit generates a quick application program startup application file for executing the operation based on the quick application package management tool, and executes the operation based on the application file.

[0020] In one embodiment, the calling unit calls the quick application package management tool based on the plug-in function of the first integrated development environment in the following manner: in response to determining that the first integrated development environment running on the first device executes a quick application operation, based on the plug-in function of the first integrated development environment, starting a first process, the first process being used to execute a command to call the quick application package management tool; executing the command to call the quick application package management tool to call the quick application package management tool.

[0021] In one embodiment, the calling unit uses the following method to call the command of the quick application package management tool to instruct the first device to detect the code running environment that supports the quick application operation, and detect the version information of the quick application package management tool supported in the code running environment; before calling the quick application package management tool, the device is also used to: determine that the first device is detected to have the code running environment installed, and obtain the version information of the quick application package management tool to determine that the calling of the quick application package management tool is supported.

[0022] In one embodiment, the execution unit operates in the following manner including running a quick application; the operation is performed based on the application file, including: starting a second process, the second process is used to execute a monitoring service status command, the monitoring service status command is used to start a service corresponding to the quick application; executing the monitoring service status command to start the service, and pushing the application file to the second device based on the corresponding address of the service, so as to run the quick application in the quick application debugger of the second device.

[0023] In one embodiment, the execution unit operates in the following manner including quick application packaging; the operation is performed based on the application file, including: starting a third process, the third process is used to execute commands for creating a package and / or releasing a package; executing commands for creating a package and / or releasing a package to generate a debug version of the application file package and a release version of the application file package.

[0024] In one implementation, before the execution unit generates the application file package of the release version, the device is further used to: determine whether there is a signature file in the quick application project.

[0025] In one implementation, the execution unit is further used to: obtain a metadata file in a quick application project, and obtain quick application project information in the metadata file; and display the quick application project information.

[0026] In one embodiment, the execution unit determines that a quick application operation is executed in a first integrated development environment running on a first device in the following manner: in response to detecting manipulation of an operation control, determining that the quick application operation is executed in the first integrated development environment running on the first device; the operation control is provided as a toolbar displayed in the first integrated development environment running on the first device.

[0027] In one embodiment, the execution unit is also used to: in response to detecting the existence of a second device set connected to the first device when the first device is running the first integrated development environment; obtain information of each second device in the second device set, and display the information of each device in the second device set in a list form.

[0028] In one embodiment, the execution unit is further used for: in response to detecting that the target second device displayed in the list is selected, checking whether a quick app debugger and a quick app preview tool are installed in the target second device based on a check instruction.

[0029] According to a third aspect of an embodiment of the present disclosure, a quick application execution device is provided, comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute the quick application execution method described in the first aspect or any one of the implementations of the first aspect.

[0030] According to a fourth aspect of an embodiment of the present disclosure, a storage medium is provided, in which instructions are stored. When the instructions in the storage medium are executed by a processor of a first device, the first device is enabled to execute the quick application execution method described in the first aspect or any one of the embodiments of the first aspect.

[0031] The technical solution provided by the embodiment of the present disclosure may include the following beneficial effects: determining that a first integrated development environment running on a first device performs a quick application operation, calling a quick application package management tool based on a plug-in function of the first integrated development environment, and performing an operation based on the quick application package management tool. Through the present disclosure, it is possible to develop and run quick applications on the first integrated development environment, simplifying the development and debugging process.

[0032] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0034] Figure 1 The figure is a flowchart of a quick application execution method according to an exemplary embodiment.

[0035] Figure 2 The present invention is a flowchart showing a method for calling a quick application package management tool according to an exemplary embodiment.

[0036] Figure 3 The figure is a flowchart of a method for running a quick application according to an exemplary embodiment.

[0037] Figure 4 The figure is a flowchart of a quick application packaging method according to an exemplary embodiment.

[0038] Figure 5 The present invention is a flowchart showing project details according to an exemplary embodiment.

[0039] Figure 6 The present invention is a block diagram showing an interface for displaying project details according to an exemplary embodiment.

[0040] Figure 7 The present invention is a flowchart showing a method for a quick application to perform an operation according to an exemplary embodiment.

[0041] Figure 8 The figure is a flowchart of a method for obtaining a device list according to an exemplary embodiment.

[0042] Fig. 9 It is a block diagram showing a second device list interface according to an exemplary embodiment.

[0043] Fig.10 The figure is a flowchart of a general method for executing a quick application according to an exemplary embodiment.

[0044] Fig.11 The figure is a block diagram of a quick application execution device according to an exemplary embodiment.

[0045] Fig.12 The figure is a block diagram of a quick application execution device according to an exemplary embodiment.

[0046] Fig.13The figure is a block diagram of a quick application execution device according to an exemplary embodiment. DETAILED DESCRIPTION

[0047] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present disclosure.

[0048] In the related technology, there is currently a plug-in-based Android application packaging and distribution method, which obtains relevant configurations and parses relevant configuration parameters through a custom plug-in; determines whether to enable the plug-in, if enabled, continue, otherwise end; determines whether to enable reinforcement, if enabled, continue, otherwise execute the upload step; obtains the current compilation type, if it is a release package, then reinforces it; determines whether to enable multi-channel packaging, if enabled, continue, otherwise execute the upload step; inserts channel information in the multi-channel packaging module (Apk Signing Block) of the installation package, and outputs the channel package; determines whether to enable upload, if enabled, continue, otherwise execute the notification step; uploads the channel package to the intranet network disk; determines whether to enable application notification, if enabled, sends the application notification, otherwise end.

[0049] In view of this, the present disclosure proposes a quick application execution method, which realizes the development and operation of quick applications in the IDE of JetBrains, and has a visual operation interface, which can help quick application developers focus on function development.

[0050] The specific implementation process of the quick application execution is described below in the embodiments of the present disclosure.

[0051] Figure 1 is a flowchart of a quick application execution method according to an exemplary embodiment. Figure 1 As shown, the quick application execution method includes the following steps:

[0052] In step S11, a quick application package management tool is called based on a plug-in function of the first integrated development environment.

[0053] In the disclosed embodiment, the first integrated development environment may be IntelliJ IDEA or Android Studio of JetBrains, and the quick application package management tool includes aiot-toolkit and node environment, wherein aiot-toolkit is a quick application packaging tool, and the node environment is the operating environment of the front-end code. Based on this, quick application operations can be performed in IntelliJ IDEA, based on the plug-in function call of IntelliJ IDEA, and based on aiot-toolkit, application files can be generated, and the application files can be RPK files. Among them, the plug-in can be run on any IDE developed by JetBrains. For example, IntelliJ IDEA.

[0054] In step S12, an application file for executing the operation is generated based on the quick application package management tool, and the operation is executed based on the application file.

[0055] In the disclosed embodiment, based on the RPK file generated by calling aiot-toolkit, quick application operations can be performed in IntelliJ IDEA.

[0056] In the disclosed embodiment, it is possible to develop and run quick applications in the first integrated development environment, thereby expanding the functions of the integrated development environment.

[0057] The following is an explanation of the specific implementation process of calling the quick application package management tool in the embodiment of the present disclosure.

[0058] Figure 2 is a flowchart of a method for calling a quick application package management tool according to an exemplary embodiment. Figure 2 As shown, the method for calling the quick application package management tool includes the following steps:

[0059] In step S21, in response to determining that a quick application operation is performed in a first integrated development environment running on a first device, a first process is started based on a plug-in function of the first integrated development environment, and the first process is used to execute a command for calling a quick application package management tool.

[0060] In the disclosed embodiment, based on the first integrated development environment, it is detected whether the current quick application project has installed the quick application package management tool, namely, aiot-toolkit. First, the File(path).exist() interface is used to check whether the node_module under the project has installed the quick application package management tool, where node_module is a folder used to store packages downloaded and installed with the package management tool after node is installed. It can be understood that node is the operating environment of the front-end code. If the quick application package management tool is installed under the project, it means that it has been installed. If not, a pop-up window with an "Install (install forme)" button will pop up. When you click "install for me", the first process will be started to execute instructions to complete the installation, and it will be used for subsequent execution of commands that call the quick application package management tool.

[0061] In step S22, a command for calling a quick application package management tool is executed to call the quick application package management tool.

[0062] In the embodiment of the present disclosure, based on the first integrated development environment, a command for calling a quick application package management tool is executed, and the quick application package management tool can be called to perform subsequent operations of the quick application in the first integrated development environment.

[0063] In the disclosed embodiment, the quick application management tool is called based on the first integrated development environment without opening another command run box, which simplifies the operation process and helps developers focus on function development.

[0064] The following is an explanation of the specific implementation process of detecting the quick application running environment in the embodiment of the present disclosure.

[0065] The command for invoking the quick application package management tool is used to instruct the first device to detect a code running environment that supports quick application operations, and to detect version information of the quick application package management tool supported in the code running environment;

[0066] Before calling the quick app package management tool, the method also includes:

[0067] It is determined that the first device is detected to have a code execution environment installed, and version information of the quick application package management tool is obtained to determine that calling of the quick application package management tool is supported.

[0068] In the disclosed embodiment, the first device code running environment is detected, where the running environment is a node environment. The first process is started and a version check command is executed. If the version information of the quick application package management tool is output, the call of the quick application package management tool is supported. In one example, the first process is started to execute the "node--version" command, and the "v14.17.2" character is output, indicating that node is installed.

[0069] In the disclosed embodiment, the installation of the quick application package management tool is detected first to avoid the subsequent failure to execute the quick application operation, and there is no need to open another command run box, and the operation can be directly performed in the first integrated development environment, which simplifies the operation process.

[0070] The specific implementation process of running a quick application is described below in the embodiments of the present disclosure.

[0071] Figure 3 is a flowchart of a method for running a quick application according to an exemplary embodiment. Figure 3 As shown, the method for running a quick application includes the following steps:

[0072] In step S31, an operation is performed based on the application file.

[0073] In step S32, a second process is started, the second process is used to execute a monitoring service status command, and the monitoring service status command is used to start a service corresponding to the quick application.

[0074] In one example, the command for monitoring service status can be the "aiot server-watch" command, which is used to execute when starting the corresponding service of the quick application. Among them, the watch mode can realize the hot update of the quick application project. Hot update can be understood as when the project code is changed, the user interaction interface will be updated synchronously.

[0075] In step S33, the monitoring service status command is executed to start the service, and the application file is pushed to the second device based on the service corresponding address, so as to run the quick application in the quick application debugger of the second device.

[0076] In the disclosed embodiment, a monitoring service status command is executed to start the service, a service address is obtained according to the printed log, and an RPK file is pushed to the second device for execution based on the service corresponding address.

[0077] In one example, the command to monitor the service status can be the "aiot server-watch" command, with an address format similar to http: / / localhost:8000. Based on the obtained service address, execute the "adb am start-n'org.hapjs.debugger / MainActivity'-e path$address" command to push the RPK file in the dist directory to the second device to start and run. The dist directory is compiled or compressed code. If multiple devices are connected, the RPK file will be pushed to each device.

[0078] In the disclosed embodiment, in a first integrated development environment in which a quick application package management tool is installed, an RPK file can be pushed to a second device for execution, thereby realizing the development and execution of quick applications in the first integrated development environment, and the second device can directly execute the RPK file upon receiving the RPK file pushed by the first device, thereby expanding the functionality of the integrated development environment.

[0079] The specific implementation process of quick application packaging is described below in the embodiments of the present disclosure.

[0080] Figure 4 is a flowchart of a quick application packaging method according to an exemplary embodiment. Figure 1 As shown, the quick application packaging method includes the following steps:

[0081] In step S41, an operation is performed based on the application file.

[0082] In step S42, a third process is started, and the third process is used to execute commands for creating a package and / or releasing a package.

[0083] In the embodiment of the present disclosure, it is determined to execute the packaging operation and start the third process. The environment detection for executing the third process is similar to the second process, and the quick application package management tool also needs to be installed.

[0084] In step S43, a command for creating a package and / or releasing a package is executed to generate an application file package of a debug version and an application file package of a release version.

[0085] In the embodiment of the present disclosure, the third process is started to generate the RPK file package of the debug version and the RPK file package of the release version. The RPK file package of the debug version can be understood as the RPK of the debug version, and the RPK file package of the release version can be understood as the RPK of the release version.

[0086] In the disclosed embodiment, in a first integrated development environment in which a quick application package management tool is installed, RPK files can be packaged, thereby enabling the creation and / or release of quick application packages in the first integrated development environment, extending the functionality of the integrated development environment, and avoiding opening a window outside the first integrated development environment for packaging operations.

[0087] The specific implementation process of the quick application packaging conditions is described below in the embodiments of the present disclosure.

[0088] Before generating the RPK file package of the release version, the method also includes:

[0089] Make sure that the signature file exists in the quick app project.

[0090] In the disclosed embodiment, when packaging the RPK file package of the release version, it is necessary to ensure that there is a signature file in the project. The signature file can be detected through an interface. The interface can be File(path).exist(). If there is a signature file in the project, the packaging command is executed to generate the RPK file package of the release version. If there is no signature file package, the RPK file package of the debug version is generated.

[0091] In one example, the signature files are sign / release / private.pem and sign / release / certificate.pem. The process is started to execute the build and release commands of the quick application packaging tool, aiot-toolkit, namely "aiot build" and "aiot release", which will generate the corresponding RPK file package in the dist directory of the project.

[0092] In the embodiment of the present disclosure, quick application packaging is implemented in the first integrated development environment, so that the first integrated development environment has a quick application packaging function.

[0093] The specific implementation process of displaying project details is described below in the embodiment of the present disclosure.

[0094] Figure 5 is a flowchart showing project details according to an exemplary embodiment. Figure 5 As shown, the method for displaying project details includes the following steps:

[0095] In step S51, a metadata file in a quick application project is obtained, and quick application project information in the metadata file is obtained.

[0096] In the disclosed embodiment, the quick application project information is obtained by reading the metadata file in the source code (src) directory of the quick application project, wherein the metadata file may be a manifest.json file, which is an important file for configuring the quick application information.

[0097] In step S52, quick application project information is displayed.

[0098] In the disclosed embodiment, the package name, application name, version and other information of the quick application can be obtained. Figure 6 , Figure 6 is a block diagram showing an interface for displaying project details according to an exemplary embodiment. Figure 6As shown in the figure, the Quickapp project information includes: "package name (packageName)", "application name (appName)", "application version name (versionName)", "application version number (versionCode)", "minimum supported platform version number (minPlatformVersion)", and "project path (projectPath)". In addition to the project details, it also includes the model names of the three devices "X", "Y", and "Z". The Android version information and wireless LAN information of each device are displayed below the device, and the "Install Debugger (Install Debugger)" and "UnInstall Debugger (UnInstall Debugger)" buttons are displayed on the right side of the device.

[0099] In the disclosed embodiment, quick application project information can be directly displayed in the first integrated development environment, which is convenient for developers to view related quick application projects and simplifies the development and operation process.

[0100] The specific implementation process of the quick application execution operation is described below in the embodiment of the present disclosure.

[0101] Figure 7 is a flowchart of a method for a quick application to perform an operation according to an exemplary embodiment. Figure 7 As shown, the method for quick application to perform an operation includes the following steps:

[0102] In step S61, in response to detecting manipulation of an operating control, determining that a quick application operation is performed in a first integrated development environment running on a first device.

[0103] In step S62, the operation control is provided as a toolbar displayed on the first integrated development environment running on the first device.

[0104] In the disclosed embodiment, a tool window bar of a "Quickapp" is created based on a first integrated development environment and is placed on the right side of the first integrated development environment, wherein the first integrated development environment may be IntelliJ IDEA. Function buttons are placed at the top of the tool window bar, indicating all supported operations, including functions such as running, packaging, and viewing project details. The middle part of the toolbar displays a list of connected devices, and the bottom displays basic information of the currently opened quick app project according to the selected state of the "View Project Details" button.

[0105] In the disclosed embodiment, the toolbar window is implemented using toolwindow, and the function button is implemented using Action, both of which are components provided by the first integrated development environment plug-in. First, register toolwindow and Action in plugin.xml of the plug-in, and bind their corresponding class implementations. When initializing toolwindow, add all Actions at the top, create two lightweight containers (JPanels) for displaying the device list and project information respectively, and add these two JPanels to the toolbar window in turn to realize the creation of the toolbar.

[0106] In the disclosed embodiment, quick application operations are performed through the operation controls in the toolbar, which facilitates the operation of developers and simplifies the operation process.

[0107] The specific implementation process of obtaining the device list is described below in the embodiment of the present disclosure.

[0108] Figure 8 is a flowchart of a method for obtaining a device list according to an exemplary embodiment. Figure 8 As shown, the method for obtaining a device list includes the following steps:

[0109] In step S71 , in response to the first device running the first integrated development environment, it is detected that there is a second device set connected to the first device.

[0110] In the disclosed embodiment, a USB data cable is used to connect the first device and the second device, or an Android emulator is opened and a command is executed to view the connected device.

[0111] In one example, you can use the Android Debug Bridge (adb) to view the connected device. Start the process and execute the "adb devices" command to obtain the unique identity document (ID) of the connected device, and then use the "adb –s device ID shell getproup" command to obtain the device properties.

[0112] In step S72, information of each second device in the second device set is obtained, and the information of each device in the second device set is displayed in a list form.

[0113] In the present disclosure, Fig. 9 As shown, Fig. 9 is a block diagram showing a second device list interface according to an exemplary embodiment. Fig. 9As shown in the figure, there are three device model names "X", "Y" and "Z", and the Android version information and wireless LAN information of each device are displayed below the device. The "Install Debugger" and "UnInstall Debugger" buttons are displayed on the right side of the device.

[0114] In the disclosed embodiment, through the acquired devices, one or two devices can be selected in the toolbar window for operation, thereby realizing a visual operation interface, simplifying the operation process, and allowing developers to focus on the operation of the quick application.

[0115] The specific implementation process of the detection quick application tool is described below in the embodiment of the present disclosure.

[0116] In response to detecting that the target second device displayed in the list is selected, checking whether a quick app debugger and a quick app preview tool are installed in the target second device based on the checking instruction.

[0117] In the disclosed embodiment, since the operation of the quick app of the second device depends on the two applications, the quick app debugger and the quick app preview version, it is necessary to check whether the selected target second device has these two applications installed. In one example, start the process and execute the "adb-s$ device ID shell pm path org.hapjs.debugger" and "adb-s$ device ID shell pmpath org.hapjs.mockup" commands to check whether the two applications are installed on the device. Among them, org.hapjs.debugger and org.hapjs.mockup are the names of the quick app debugger and the preview version, respectively. According to the installation situation, decide whether to display the "Install Debugger" or "UnInstall Debugger" button on the right side of the corresponding device.

[0118] After clicking the "Install Debugger" button, the present invention downloads the apk packages of the two applications from the remote server to the Home directory of the local machine through the HttpURLConnect class, executes the "adb install" installation command, installs the application, and deletes the downloaded apk package after successful installation. After clicking the "UnInstall Debugger" button, executes the "adb uninstall" uninstall command to uninstall the application.

[0119] In the disclosed embodiment, it is detected on the first device whether the second device has the two applications, the quick app debugger and the quick app preview version, so as to facilitate direct debugging or running of the quick app on the second device, shorten the development time, and simplify the operation process of the developer.

[0120] Based on the above embodiments, the embodiments of the present disclosure are based on a method for executing a quick application based on a plug-in of a first integrated development environment, and the plug-in can be run on any IDE developed by JetBrains. All functions on the user interaction interface are implemented through the plug-in interface provided by the first integrated development environment. For example, the packaging and running functions are implemented by calling the command of the npm package of the quick application packaging tool aiot-toolkit in the plug-in code (Kotlin). Since the process execution command is started in Kotlin, cross-platform can be achieved by specifying terminal handlers for different platforms (mac / linux / windows), such as using the bash terminal for linux and the powershell terminal for windows.

[0121] Quick application execution operations such as Fig.10 As shown, Fig.10 It is a flowchart of a general method for executing a quick application according to an exemplary embodiment. First, determine whether the opened project is a quick application project. If so, start the plug-in, otherwise do not start the plug-in. First, create a quick application toolbar in the plug-in to display the operation buttons and device list. If the run function is selected, an RPK file is generated, the RPK file is automatically pushed to the terminal or simulator, and the run is started in the quick application debugger to view the running effect of the quick application. If the packaging function is selected, get the packaging type. If it is a release version package, package the RPK of the release version, otherwise generate the RPK of the debug version. If you are viewing the project details, the relevant basic information is displayed.

[0122] The disclosed embodiments can realize the ability to develop and run quick applications on software such as Intellij IDEA and Android Studio in a first integrated development environment, provide a visual interface for quick application developers, help developers focus on function development, and simplify the development and debugging process.

[0123] Based on the same concept, the embodiment of the present disclosure also provides a quick application execution device.

[0124] It is understandable that in order to realize the above functions, the quick application execution device provided by the embodiment of the present disclosure includes hardware structures and / or software modules corresponding to the execution of each function. In combination with the units and algorithm steps of each example disclosed in the embodiment of the present disclosure, the embodiment of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present disclosure.

[0125] Fig.11 FIG. 1 is a block diagram of a quick application execution device according to an exemplary embodiment. Fig.11 The device 100 includes a calling unit 101 and an execution unit 102.

[0126] The calling unit 101 is used to call the quick application package management tool application file based on the plug-in function of the first integrated development environment.

[0127] The execution unit 102 is used to generate a quick application startup application file for executing the operation based on the quick application package management tool, and execute the operation based on the application file.

[0128] In one implementation, the calling unit 101 calls the quick application package management tool based on the plug-in function of the first integrated development environment in the following manner: in response to determining that the first integrated development environment running on the first device executes a quick application operation, based on the plug-in function of the first integrated development environment, a first process is started, and the first process is used to execute a command to call the quick application package management tool; the instruction to call the quick application package management tool is executed to call the quick application package management tool.

[0129] In one embodiment, the calling unit 101 uses the following method to call the command of the quick application package management tool to instruct the first device to detect the code running environment that supports the quick application operation, and detect the version information of the quick application package management tool supported in the code running environment; before calling the quick application package management tool, the device is also used to: determine that the code running environment is detected to be installed on the first device, and obtain the version information of the quick application package management tool to determine that the calling of the quick application package management tool is supported.

[0130] In one embodiment, the execution unit 102 operates in the following manner, including running a quick application; based on the application file, performing operations, including: starting a second process, the second process is used to execute a monitoring service status command, the monitoring service status command is used to start a service corresponding to the quick application; executing the monitoring service status command to start the service, and pushing the application file to the second device based on the corresponding address of the service, so as to run the quick application in the quick application debugger of the second device.

[0131] In one embodiment, the execution unit 102 operates in the following manner including quick application packaging; based on the application file, performing operations including: starting a third process, the third process is used to execute commands for creating a package and / or releasing a package; executing commands for creating a package and / or releasing a package to generate a debug version of the application file package and a release version of the application file package.

[0132] In one implementation, before the execution unit 102 generates the application file package of the release version, the device is further configured to: determine whether a signature file exists in the quick application project.

[0133] In one implementation, the execution unit 102 is further configured to: obtain a metadata file in the quick application project, and obtain quick application project information in the metadata file; and display the quick application project information.

[0134] In one embodiment, the execution unit 102 determines that a quick application operation is executed in a first integrated development environment running on a first device in the following manner: in response to detecting manipulation of an operation control, determining that the quick application operation is executed in the first integrated development environment running on the first device; the operation control is provided as a toolbar displayed in the first integrated development environment running on the first device.

[0135] In one embodiment, the execution unit 102 is also used to: in response to detecting the existence of a second device set connected to the first device when the first device is running the first integrated development environment; obtain information of each second device in the second device set, and display the information of each device in the second device set in a list form.

[0136] In one implementation, the execution unit 102 is further configured to: in response to detecting that the target second device displayed in the list is selected, check whether the quick app debugger and the quick app preview tool are installed in the target second device based on the check instruction.

[0137] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0138] Fig.122 is a block diagram of a device 200 for executing a quick application according to an exemplary embodiment. For example, the device 200 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0139] Reference Fig.12 , the device 200 may include one or more of the following components: a processing component 202 , a memory 204 , a power component 206 , a multimedia component 208 , an audio component 210 , an input / output (I / O) interface 212 , a sensor component 214 , and a communication component 216 .

[0140] The processing component 202 generally controls the overall operation of the device 200, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 202 may include one or more processors 220 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 202 may include one or more modules to facilitate interaction between the processing component 202 and other components. For example, the processing component 202 may include a multimedia module to facilitate interaction between the multimedia component 208 and the processing component 202.

[0141] The memory 204 is configured to store various types of data to support operations on the device 200. Examples of such data include instructions for any application or method operating on the device 200, contact data, phone book data, messages, pictures, videos, etc. The memory 204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0142] The power component 206 provides power to the various components of the device 200. The power component 206 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 200.

[0143] The multimedia component 208 includes a screen that provides an output interface between the device 200 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 208 includes a front camera and / or a rear camera. When the device 200 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0144] The audio component 210 is configured to output and / or input audio signals. For example, the audio component 210 includes a microphone (MIC), and when the device 200 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 204 or sent via the communication component 216. In some embodiments, the audio component 210 also includes a speaker for outputting audio signals.

[0145] I / O interface 212 provides an interface between processing component 202 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0146] The sensor assembly 214 includes one or more sensors for providing various aspects of the status assessment of the device 200. For example, the sensor assembly 214 can detect the open / closed state of the device 200, the relative positioning of components, such as the display and keypad of the device 200, the sensor assembly 214 can also detect the position change of the device 200 or a component of the device 200, the presence or absence of user contact with the device 200, the orientation or acceleration / deceleration of the device 200 and the temperature change of the device 200. The sensor assembly 214 can include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 214 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 214 can also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

[0147] The communication component 216 is configured to facilitate wired or wireless communication between the device 200 and other devices. The device 200 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 216 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 216 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0148] In an exemplary embodiment, the apparatus 200 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0149] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 204 including instructions, and the instructions can be executed by the processor 220 of the device 200 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0150] Fig.13 3 is a block diagram of a device 300 for executing a quick application according to an exemplary embodiment. For example, the device 300 may be provided as a server. Fig.13 , the apparatus 300 includes a processing component 322, which further includes one or more processors, and a memory resource represented by a memory 332 for storing instructions, such as an application, that can be executed by the processing component 322. The application stored in the memory 332 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 322 is configured to execute the instructions to perform the above method.

[0151] The device 300 may also include a power supply component 326 configured to perform power management of the device 300, a wired or wireless network interface 350 configured to connect the device 300 to a network, and an input / output (I / O) interface 358. The device 300 may operate based on an operating system stored in the memory 332, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0152] It is to be understood that in the present disclosure, "plurality" refers to two or more than two, and other quantifiers are similar. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. The singular forms "a", "the" and "the" are also intended to include plural forms, unless the context clearly indicates other meanings.

[0153] It is further understood that the terms "first", "second", etc. are used to describe various information, but such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other, and do not indicate a specific order or degree of importance. In fact, the expressions "first", "second", etc. can be used interchangeably. For example, without departing from the scope of the present disclosure, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information.

[0154] It can be further understood that, unless otherwise specified, “connection” includes a direct connection without other components between the two, and also includes an indirect connection with other components between the two.

[0155] It is further understood that, although the operations are described in a specific order in the drawings in the embodiments of the present disclosure, it should not be understood as requiring the operations to be performed in the specific order shown or in a serial order, or requiring the execution of all the operations shown to obtain the desired results. In certain environments, multitasking and parallel processing may be advantageous.

[0156] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modifications, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure.

[0157] It should be understood that the present disclosure is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the scope of the appended claims.

Claims

1. A quick application execution method, characterized in that: include: A quick application package management tool is called based on the plug-in function of the first integrated development environment, an application file for executing the operation is generated based on the quick application package management tool, and the operation is executed based on the application file.

2. The method according to claim 1, characterized in that The plug-in function based on the first integrated development environment calls the quick application package management tool, including: In response to determining that a quick application operation is performed in a first integrated development environment running on the first device, starting a first process based on a plug-in function of the first integrated development environment, the first process being used to execute a command for invoking a quick application package management tool; Execute the command for calling the quick application package management tool to call the quick application package management tool.

3. The method according to claim 1, characterized in that The command for calling the quick application package management tool is used to instruct the first device to detect a code running environment that supports the quick application operation, and to detect version information of the quick application package management tool supported in the code running environment; Before calling the quick application package management tool, the method further includes: It is determined that the first device is detected to have the code execution environment installed, and version information of the quick application package management tool is obtained to determine that calling of the quick application package management tool is supported.

4. The method according to any one of claims 1 to 3, characterized in that The operation includes running a quick application; The performing the operation based on the application file includes: Starting a second process, where the second process is used to execute a monitoring service status command, where the monitoring service status command is used to start a service corresponding to the quick application; The monitoring service status command is executed to start the service, and the application file is pushed to the second device based on the service corresponding address, so as to run the quick application in the quick application debugger of the second device.

5. The method according to any one of claims 1 to 3, characterized in that: The operation includes quick application packaging; The performing the operation based on the application file includes: Starting a third process, wherein the third process is used to execute a command for creating a package and / or releasing a package; Execute the command to create a package and / or release a package to generate a debug version application file package and a release version application file package.

6. The method according to claim 5, characterized in that Before generating the application file package of the release version, the method further includes: Make sure that the signature file exists in the quick app project.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Obtaining a metadata file in a quick application project, and obtaining quick application project information in the metadata file; Display the quick application project information.

8. The method according to claim 1, characterized in that The determining to execute the quick application operation in the first integrated development environment running on the first device includes: In response to detecting manipulation of the operation control, determining to execute a quick application operation in a first integrated development environment running on the first device; The operation control is provided as a toolbar displayed on a first integrated development environment running on a first device.

9. The method according to claim 8, characterized in that The method further comprises: In response to detecting, when the first device runs the first integrated development environment, that there is a second set of devices connected to the first device; The information of each second device in the second device set is obtained, and the information of each device in the second device set is displayed in a list form.

10. The method according to claim 9, characterized in that The method further comprises: In response to detecting that the target second device displayed in the list is selected, checking whether a quick app debugger and a quick app preview tool are installed in the target second device based on a checking instruction.

11. A quick application execution device, characterized in that: include: A calling unit, which calls a quick application package management tool based on a plug-in function of the first integrated development environment; The execution unit generates a quick application program startup application file for executing an operation based on the quick application package management tool, and executes the operation based on the application file.

12. The device according to claim 11, characterized in that The calling unit calls the quick application package management tool based on the plug-in function of the first integrated development environment in the following manner: In response to determining that a quick application operation is performed in a first integrated development environment running on the first device, starting a first process based on a plug-in function of the first integrated development environment, the first process being used to execute a command for invoking a quick application package management tool; Execute the command for calling the quick application package management tool to call the quick application package management tool.

13. The device according to claim 11, characterized in that The calling unit calls the command of the quick application package management tool in the following manner to instruct the first device to detect a code running environment supporting the quick application operation, and detect version information of the quick application package management tool supported in the code running environment; Before calling the quick application package management tool, the device is further used to: It is determined that the first device is detected to have the code execution environment installed, and version information of the quick application package management tool is obtained to determine that calling of the quick application package management tool is supported.

14. The device according to any one of claims 11 to 13, characterized in that The execution unit operates in the following manner including running a quick application; The performing the operation based on the application file includes: Starting a second process, where the second process is used to execute a monitoring service status command, where the monitoring service status command is used to start a service corresponding to the quick application; The monitoring service status command is executed to start the service, and the application file is pushed to the second device based on the service corresponding address, so as to run the quick application in the quick application debugger of the second device.

15. The device according to any one of claims 11 to 13, characterized in that The execution unit operates in the following manner including quick application packaging; The performing the operation based on the application file includes: Starting a third process, wherein the third process is used to execute a command for creating a package and / or releasing a package; Execute the command to create a package and / or release a package to generate a debug version application file package and a release version application file package.

16. The device according to claim 15, characterized in that Before the execution unit generates the application file package of the release version, the device is further used to: Make sure that the signature file exists in the quick app project.

17. The device according to any one of claims 11 to 16, characterized in that The execution unit is also used for: Obtaining a metadata file in a quick application project, and obtaining quick application project information in the metadata file; Display the quick application project information.

18. The device according to claim 11, characterized in that The execution unit determines that the first integrated development environment running on the first device executes the quick application operation in the following manner: In response to detecting manipulation of the operation control, determining to execute a quick application operation in a first integrated development environment running on the first device; The operation control is provided as a toolbar displayed on a first integrated development environment running on a first device.

19. The device according to claim 18, characterized in that The execution unit is also used for: In response to detecting, when the first device runs the first integrated development environment, that there is a second set of devices connected to the first device; The information of each second device in the second device set is obtained, and the information of each device in the second device set is displayed in a list form.

20. The device according to claim 19, characterized in that The execution unit is also used for: In response to detecting that the target second device displayed in the list is selected, checking whether a quick app debugger and a quick app preview tool are installed in the target second device based on a checking instruction.

21. A quick application execution device, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to: execute the quick application execution method described in any one of claims 1-10.

22. A storage medium, characterized in that: The storage medium stores instructions, and when the instructions in the storage medium are executed by the processor of the terminal, the first device is enabled to execute the quick application execution method described in any one of claims 1-10.

Images