CN115103116A - Camera data acquisition method, device, equipment, storage medium and program product - Google Patents
Camera data acquisition method, device, equipment, storage medium and program product Download PDFInfo
- Publication number
- CN115103116A CN115103116A CN202210689278.9A CN202210689278A CN115103116A CN 115103116 A CN115103116 A CN 115103116A CN 202210689278 A CN202210689278 A CN 202210689278A CN 115103116 A CN115103116 A CN 115103116A
- Authority
- CN
- China
- Prior art keywords
- camera
- interface
- target
- data acquisition
- operating system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Studio Devices (AREA)
Abstract
The present disclosure relates to a camera data acquisition method, apparatus, device, storage medium, and program product, the method comprising: receiving a first trigger operation, wherein the first trigger operation is used for indicating a camera data acquisition instruction; responding to a first trigger operation, calling a uniform calling interface at a script layer, and issuing a camera data acquisition instruction to a native interface of a target operating system, wherein the uniform calling interface is packaged with a plurality of camera data acquisition functions under the operating systems, and the operating systems comprise the target operating system; and receiving response data corresponding to the camera data acquisition instruction returned by the native interface. The application developed based on the uniform calling interface can be operated on different mobile devices of the operating system, so that the software development difficulty can be reduced, and the software development progress can be effectively improved.
Description
Technical Field
The present disclosure relates to the field of terminal technologies, and in particular, to a method and an apparatus for acquiring camera data, an electronic device, a storage medium, and a program product.
Background
With the rapid growth of the mobile application market and the explosive growth of enterprise application needs, more and more developers also want to be able to participate in mobile application development.
However, since different mobile devices support different operating systems, and different operating systems use different development languages, if an application written by a developer is to run on different mobile devices at the same time, the developer must master multiple development languages, which will seriously affect the software development progress and the project online time, and become a big problem for a development team.
Therefore, a method for supporting providing a unified camera data acquisition mode under different operating systems is needed.
Disclosure of Invention
In order to solve the technical problems or at least partially solve the technical problems, the present disclosure provides a camera data acquisition method, an apparatus, an electronic device, a storage medium, and a program product.
In a first aspect of the embodiments of the present disclosure, a method for acquiring camera data is provided, which is applied to an electronic device including a target operating system, and the method includes: receiving a first trigger operation, wherein the first trigger operation is used for indicating a camera data acquisition instruction; responding to a first trigger operation, calling a uniform calling interface at a script layer, and issuing a camera data acquisition instruction to a native interface of a target operating system, wherein the uniform calling interface is packaged with a plurality of camera data acquisition functions under the operating systems, and the operating systems comprise the target operating system; and receiving response data corresponding to the camera data acquisition instruction returned by the native interface.
Optionally, the unified call interface is generated by: encapsulating a native interface of each operating system and an acquisition function of corresponding camera data into a system layer API; encapsulating the system layer APIs of the plurality of operating systems into a cross-platform camera module; and binding the cross-platform camera module to the script layer to generate the unified calling interface.
Optionally, the unified call interface is generated by: binding native interfaces of the plurality of operating systems to the scripting layer; at the script layer, encapsulating the native interface of each operating system and the acquisition function of the corresponding camera data into a script layer API; and encapsulating the script layer API of the plurality of operating systems into the unified calling interface.
Optionally, the issuing the camera data acquisition instruction to the native interface of the target operating system by calling the unified call interface at the script layer in response to the first trigger operation includes: responding to a first trigger operation, and determining that the operating system of the electronic equipment is the target operating system through the unified calling interface; and issuing the camera data acquisition instruction to the native interface of the target operating system by calling a target function encapsulated in the unified calling interface at the script layer, wherein the target function is an acquisition function of the camera data corresponding to the camera data acquisition instruction under the target operating system.
Optionally, after the step of responding to the first trigger operation and invoking the unified call interface at the script layer and issuing the camera data acquisition instruction to the native interface of the target operating system, the method further includes: and under the condition that the response data is not received within a preset time length, displaying first prompt information, wherein the first prompt information is used for prompting to re-trigger the camera data acquisition instruction.
Optionally, the camera data acquisition instruction is for indicating any one of: the method comprises the steps of obtaining a camera list available for the electronic equipment, wherein the camera list comprises at least one camera mark, and each camera mark is used for indicating one camera; acquiring camera parameters of each camera available for the electronic equipment, wherein the camera parameters comprise any one of the following items: the camera identification, the camera image format and the camera connection state; controlling a target camera to perform a target operation, the target operation comprising any one of: and switching to the target camera, opening the target camera, closing the target camera, shooting images and stopping shooting the images.
Optionally, the camera data acquisition instruction is used to instruct a control target camera to execute a target operation, where the target operation includes turning on the target camera; before the unified calling interface is called at the script layer and the camera data acquisition instruction is issued to the native interface of the target operating system, the method further comprises the following steps: under the condition that the target operating system is a preset system, determining whether the current application has the camera authority or not by calling the unified calling interface at a script layer; the step of issuing the camera data acquisition instruction to the native interface of the target operating system by calling the unified calling interface at the script layer includes: and under the condition that the current application has the camera authority, issuing an instruction for starting the target camera to the native interface of the target operating system by calling the unified calling interface at the script layer.
Optionally, in a case that the target operating system is a preset system, after determining whether the current application has the camera right by calling the unified call interface at the script layer, the method further includes: under the condition that the current application does not have the camera authority, displaying second prompt information, wherein the second prompt information is used for prompting whether the camera authority of the current application is started or not; under the condition that the trigger operation of not starting the camera authority of the current application is received, displaying third prompt information, wherein the third prompt information is used for indicating that the current application is forbidden to start the target camera; the step of issuing an instruction for starting the target camera to the native interface of the target operating system by calling the unified calling interface at the script layer under the condition that the current application has the camera permission includes: and under the condition of receiving the trigger operation of starting the camera authority of the current application, issuing an instruction for starting the target camera to the native interface of the target operating system by calling the unified calling interface at the script layer.
In a second aspect of the embodiments of the present disclosure, there is provided a camera data acquiring apparatus, including: the system comprises a receiving module and a sending module; the receiving module is used for receiving a first trigger operation, and the first trigger operation is used for indicating a camera data acquisition instruction; the issuing module is used for responding to the first trigger operation received by the receiving module, issuing the camera data acquisition instruction to a native interface of a target operating system by calling a uniform calling interface in a script layer, wherein the uniform calling interface is packaged with the camera data acquisition function under a plurality of operating systems, and the operating systems comprise the target operating system; the receiving module is further configured to receive response data corresponding to the camera data acquisition instruction returned by the native interface.
Optionally, the unified call interface is generated by: encapsulating a native interface of each operating system and an acquisition function of corresponding camera data into a system layer API; encapsulating the system layer APIs of the plurality of operating systems into a cross-platform camera module; and binding the cross-platform camera module to the script layer to generate the unified calling interface.
Optionally, the unified call interface is generated by: binding native interfaces of the plurality of operating systems to the scripting layer; at the script layer, encapsulating the native interface of each operating system and the acquisition function of the corresponding camera data into a script layer API; and encapsulating the script layer API of the plurality of operating systems into the unified calling interface.
Optionally, the issuing module is specifically configured to determine, in response to the first trigger operation, that the operating system of the electronic device is the target operating system through the unified call interface; and issuing the camera data acquisition instruction to the native interface of the target operating system by calling a target function encapsulated in the unified calling interface at the script layer, wherein the target function is an acquisition function of the camera data corresponding to the camera data acquisition instruction under the target operating system.
Optionally, the apparatus further comprises: a display module; the display module is used for displaying first prompt information under the condition that the response data is not received within a preset time length after the camera data acquisition instruction is issued to a native interface of a target operating system by calling the unified calling interface in the script layer in response to the first trigger operation, wherein the first prompt information is used for prompting to re-trigger the camera data acquisition instruction.
Optionally, the camera data acquisition instruction is for indicating any one of: the method comprises the steps of obtaining a camera list available for the electronic equipment, wherein the camera list comprises at least one camera mark, and each camera mark is used for indicating one camera; acquiring camera parameters of each camera available for the electronic equipment, wherein the camera parameters comprise any one of the following items: the camera identification, the camera image format and the camera connection state; controlling a target camera to execute a target operation, the target operation including any one of: and switching to the target camera, opening the target camera, closing the target camera, shooting images and stopping shooting the images.
Optionally, the camera data acquisition instruction is used to instruct a control target camera to execute a target operation, where the target operation includes turning on the target camera; the device also includes: a determination module; the determining module is used for determining whether the current application has the camera permission or not by calling the unified calling interface at the script layer under the condition that the target operating system is a preset system before the unified calling interface is called at the script layer and the camera data acquisition instruction is issued to the native interface of the target operating system; the issuing module is specifically configured to issue an instruction for starting the target camera to the native interface of the target operating system by calling the unified calling interface at the script layer under the condition that the current application has the camera permission.
Optionally, the display module is further configured to, when the target operating system is a preset system, determine whether the current application has a camera right by calling the unified call interface in a script layer, and display second prompt information when the current application does not have the camera right, where the second prompt information is used to prompt whether to start the camera right of the current application; under the condition that the trigger operation of not starting the current application camera authority is received, displaying third prompt information, wherein the third prompt information is used for indicating that the current application is forbidden to start the target camera; the issuing module is specifically configured to issue an instruction for opening the target camera to the native interface of the target operating system by calling the unified call interface at the script layer under the condition that a trigger operation for opening the currently applied camera permission is received.
In a third aspect of the embodiments of the present disclosure, an electronic device is provided, where the electronic device includes a processor, a memory, and a computer program stored on the memory and executable on the processor, and the computer program, when executed by the processor, implements the camera data acquiring method according to the first aspect.
In a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the camera data acquisition method according to the first aspect.
In a fifth aspect of the embodiments of the present disclosure, a computer program product is provided, where the computer program product includes a computer program, and when the computer program product runs on a processor, the processor executes the computer program to implement the camera data acquisition method according to the first aspect.
In a sixth aspect of the disclosed embodiments, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute program instructions to implement the camera data acquisition method according to the first aspect.
Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages: in the embodiment of the disclosure, a first trigger operation for indicating a camera data acquisition instruction is received; responding to the first trigger operation, calling a unified calling interface at a script layer, issuing the camera data acquisition instruction to a native interface of a target operating system, and then receiving response data corresponding to the camera data acquisition instruction returned by the native interface. The unified calling interface is packaged with the camera data acquisition function under the multiple operating systems, so that the application can issue the camera data acquisition instruction to the native interface of the corresponding operating system by calling the unified calling interface under different operating systems, and further acquire the response data corresponding to the camera data acquisition instruction, so that the application developed based on the unified calling interface can run on different mobile devices of the operating systems, developers do not need to rewrite corresponding program codes for acquiring the camera data aiming at the different mobile devices of the operating systems, the software development difficulty can be reduced, and the software development progress is effectively improved.
Drawings
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 disclosure.
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present disclosure, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a schematic flowchart of a camera data acquisition method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a unified call interface according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a call logic for an operating system according to an embodiment of the present disclosure;
fig. 4 is a block diagram of a camera data acquisition device according to an embodiment of the present disclosure;
fig. 5 is a block diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order that the above objects, features and advantages of the present disclosure may be more clearly understood, aspects of the present disclosure will be further described below. It should be noted that the embodiments and features of the embodiments of the present disclosure may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced in other ways than those described herein; it is to be understood that the embodiments disclosed in the specification are only a few embodiments of the present disclosure, and not all embodiments.
The terms first, second and the like in the description and in the claims of the present disclosure are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the disclosure may be practiced other than those illustrated or described herein, and that the objects identified as "first," "second," etc. are generally a class of objects and do not limit the number of objects, e.g., a first object may be one or more. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.
The electronic device in the embodiments of the present disclosure may be a mobile electronic device, and may also be a non-mobile electronic device. The mobile electronic device may be a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook or a Personal Digital Assistant (PDA), etc.; the non-mobile electronic device may be a Personal Computer (PC), a Television (TV), a teller machine, a self-service machine, or the like; the disclosed embodiments are not particularly limited.
An execution main body of the camera data acquisition method provided by the embodiment of the present disclosure may be the electronic device (including a mobile electronic device and a non-mobile electronic device), or may also be a functional module and/or a functional entity capable of implementing the camera data acquisition method in the electronic device, which may be specifically determined according to actual use requirements, and the embodiment of the present disclosure is not limited.
The electronic device in the embodiments of the present disclosure includes a target operating system, and the target operating system includes any one of: an Android (Android) operating system, a Windows operating system, an iOS operating system, an MAC operating system, and a Linux operating system, and the target operating system may also be another operating system, which is not limited in the embodiments of the present disclosure.
The following describes in detail a camera data acquisition method provided by the embodiments of the present disclosure with reference to the accompanying drawings through specific embodiments and application scenarios thereof.
As shown in fig. 1, an embodiment of the present disclosure provides a camera data acquisition method, which may include steps 101 to 103 described below.
101. A first trigger operation is received.
The first trigger operation is used for indicating a camera data acquisition instruction.
It is understood that the current application receives a user-triggered camera data acquisition instruction.
102. And responding to the first trigger operation, and issuing the camera data acquisition instruction to a native interface of the target operating system by calling the unified calling interface at the script layer.
The unified calling interface is packaged with a function for acquiring data of the camera under a plurality of operating systems, and the operating systems comprise the target operating system.
The script layer is an interface layer convenient for users to use, and mainly provides a visual programming interface for the users, and the script layer is programmed by using a script language.
A scripting language, also known as a build-out language, or dynamic language, is a programming language used to control software applications, and scripts are usually stored in text (ascii) and are only interpreted or compiled when called.
In the embodiment of the present disclosure, the script layer may be a JS layer, a VBScript layer, a Perl layer, a PHP layer, a Python layer, a Ruby layer, an installshield layer, or an ActionScript layer, and the like, which may be determined specifically according to an actual situation and is not limited herein. Correspondingly, the scripting language may be JS, VBScript, Perl, PHP, Python, Ruby, installshield, ActionScript, or the like, and may be determined specifically according to an actual situation, which is not limited herein.
The JS is called full JavaScript, and is a lightweight, interpreted or just-in-time compiling programming language with function priority.
Optionally, the script layer includes any one of: JS layer, Python layer. The JS and the Python are currently more forward and widely applied application program scripting languages, so the scripting layer comprises a JS layer or a Python layer, the obtained unified calling interface can be applied to application development of most frames, the software development difficulty is reduced, and the software development progress is effectively improved.
Wherein the plurality of operating systems may include at least two of: the operating system includes an Android (Android) operating system, a Windows operating system, an iOS operating system, a MAC operating system, and a Linux operating system, and the plurality of operating systems may further include other operating systems, which may be determined specifically according to an actual situation, and is not limited herein.
Among them, the native interface is also called a system interface.
The unified calling interface encapsulates the acquisition function of the camera data of different operating systems, so that the application program installed on the electronic equipment of different operating systems can issue a camera data acquisition instruction to the native interface of the electronic equipment by invoking the camera data acquisition function in the corresponding operating system encapsulated under the unified calling interface, and the application program can call the cameras under different operating systems to realize the function of acquiring the camera data.
In the embodiment of the disclosure, the unified call interface encapsulates the native interface of each operating system and the code of the corresponding acquiring function of the camera data, so that the unified call interface is called to invoke the native interface of the corresponding operating system under different operating systems, thereby implementing the acquiring function of the camera data.
103. And receiving response data corresponding to the camera data acquisition instruction returned by the native interface.
It can be understood that after receiving the camera data acquisition instruction, the native interface acquires corresponding response data according to the camera data acquisition instruction, and then returns the response data to the application layer, so that the application layer displays the response data.
In the embodiment of the disclosure, since the unified calling interface encapsulates the function of acquiring the camera data under multiple operating systems, the application can issue the camera data acquisition instruction to the native interface of the corresponding operating system by calling the unified calling interface under different operating systems, and further acquire the response data corresponding to the camera data acquisition instruction, so that the application developed based on the unified calling interface can run on different mobile devices of the operating systems, and developers do not need to rewrite corresponding program codes for acquiring the camera data for different mobile devices of the operating systems, thereby reducing the difficulty of software development and effectively improving the development progress of software.
Optionally, the unified call interface is generated by:
s11, encapsulating the native Interface of each operating system and the corresponding camera data acquisition function into a system layer Application Programming Interface (API).
In this embodiment of the disclosure, the system layer API may also be referred to as a platform layer API, and the system layer API may be a C layer API, a C + + layer API, a Java layer API, a C # layer API, or an objective-C layer API, and the like, which may be determined specifically according to an actual situation, and is not limited herein.
Optionally, the system layer API comprises any one of: c + + layer API, object-C layer API.
It can be understood that C + + and objective-C are application platform layer programming languages which are currently in the front of comparison and widely applied, so that the system layer API includes a C + + layer API or objective-C layer API, and the obtained unified calling interface can be applied to application development of most platforms, so that the software development difficulty can be effectively reduced, and the software development progress can be effectively improved.
Where C + + is a static type, compiled, general purpose, case sensitive, irregular programming language that supports procedural, object-oriented, and generic programming.
And S12, encapsulating the system layer APIs of the operating systems into a cross-platform camera module.
And S13, binding the cross-platform camera module to the script layer to generate the unified calling interface.
It can be understood that, in the embodiment of the present disclosure, a code of an obtaining function of camera data calling a native interface and the corresponding native interface are encapsulated to obtain a system layer API, then the system layer APIs of a plurality of operating systems are encapsulated into a cross-platform camera module in the system layer through a bottom-layer platform-by-platform encapsulation technology, and then the cross-platform camera module is bound to a script layer from the system layer through a binding technology, so as to generate a unified calling interface. Therefore, in the application development process, the unified calling interface can be directly called under different operating systems to realize the function of acquiring the calling camera data, and the code of the corresponding function of acquiring the camera data is not required to be written under different operating systems based on the development language supported by the operating systems.
Illustratively, if the script layer is a js layer, the binding technique is a JSbinding technique.
In the embodiment of the present disclosure, the unified call interfaces generated in S11 to S13 are friendly to developers, and in the application development process, the unified call interface is called only when the application needs to use the camera, so that it is not necessary to know how the unified call interface specifically implements the function of acquiring the camera data, and it is not necessary to rewrite codes required for implementing the function of acquiring the camera data, and in the process of calling the unified call interfaces generated in S11 to S13, frequent cross-language calling is not required, so that the call time is saved, and the call efficiency is improved.
Exemplarily, taking the script layer as a JS layer and the system layer API as a C + + layer API, as shown in fig. 2, the unified calling interface includes a JS layer camera module, an interface binding module from the C + + layer to the JS layer, and a cross-platform camera module on the C + + layer, where the C + + layer API of each operating system is encapsulated in the cross-platform camera module, and the C + + layer API of each operating system is connected to a native interface of the corresponding operating system.
Exemplarily, referring to fig. 2, as shown in fig. 3, a schematic diagram of a possible calling logic for an operating system in the embodiment of the present disclosure specifically includes: the application layer calls a camera data acquisition function, the JS layer interface receives a camera data acquisition instruction and issues the camera data acquisition instruction to the operating system layer interface, the operating system layer interface issues the camera data acquisition instruction to the native interface provided by the operating system through the API interface provided by the operating system, the native interface provided by the operating system issues the camera data acquisition instruction to the camera, and the camera acquires the camera data and returns the camera data to the application layer through the camera data callback interface.
Optionally, the unified invocation interface is generated by the following steps:
s21, binding the native interfaces of the operating systems to the script layer.
And S22, encapsulating the native interface of each operating system and the acquisition function of the corresponding camera data into a script layer API in the script layer.
S23, packaging the script layer API of the operating systems into the uniform calling interface.
In the embodiment of the present disclosure, the unified call interfaces generated in S21 to S23 are friendly to developers, and in the application development process, the unified call interface is called only when the application needs to use the camera, so that how to specifically implement the function of acquiring the camera data by the unified call interface is not required to be known, and a code required for implementing the function of acquiring the camera data is not required to be rewritten.
Alternatively, the step 102 may be specifically realized by the following steps 102a and 102 b.
102a, in response to the first trigger operation, determining that the operating system of the electronic device is the target operating system through the unified call interface.
102b, issuing the camera data acquisition instruction to the native interface of the target operating system by calling the target function encapsulated in the unified calling interface at the script layer.
The target function is an acquisition function of the camera data corresponding to the camera data acquisition instruction under the target operating system.
When the method is applied to calling the acquisition function of the camera data through the uniform calling interface, the current operating system of the electronic equipment is determined as the target operating system through the uniform calling interface, and then the acquisition function of the corresponding camera data under the target operating system packaged by the uniform calling interface is called to acquire the camera data.
In the embodiment of the disclosure, the operating system of the electronic device can be determined through the unified calling interface, and then the acquisition function of the camera data under the operating system can be called through the unified calling interface, that is, the function of determining the operating system of the electronic device is also encapsulated into the unified calling interface, so that if the unified calling interface provided by the embodiment of the disclosure is used in the cross-platform application development process, the software development difficulty can be further reduced, and the development progress of software can be effectively improved.
Optionally, the operation of determining that the operating system of the electronic device is the target operating system may also be determined by other methods, which is not limited herein.
Optionally, after the step 102, the method for acquiring camera data provided by the embodiment of the present disclosure may further include the following step 104.
104. And displaying the first prompt message under the condition that the response data is not received within the preset time length.
The first prompt information is used for prompting to re-trigger the camera data acquisition instruction.
The preset time length may be determined according to an actual situation, and is not limited herein.
It can be understood that if the response data is not received within the preset time, a problem may occur in the process of issuing a camera data acquisition instruction or acquiring or uploading the response data, so that the user is prompted to re-trigger the camera data acquisition instruction, and thus the problem can be solved, and the response data can be acquired as soon as possible.
Optionally, the camera data acquisition instruction is for indicating any one of: the method comprises the steps of obtaining a camera list available for the electronic equipment, wherein the camera list comprises at least one camera mark, and each camera mark is used for indicating one camera; acquiring camera parameters of each camera available for the electronic equipment, wherein the camera parameters comprise any one of the following items: the camera identification, the camera image format and the camera connection state; controlling a target camera to execute a target operation, the target operation including any one of: and switching to the target camera, opening the target camera, closing the target camera, shooting images and stopping shooting the images.
The camera data acquisition instruction may also be used to instruct other camera data acquisition functions, which is not limited herein.
In the embodiment of the disclosure, the acquisition function of various camera data is encapsulated for each operating system, so that the acquisition of cross-platform camera capability can be realized through unified calling of interfaces, the calling is convenient, and the complexity of camera related function development on node.
The unified calling interface in the embodiment of the disclosure can be applied to the application development of a node.JS + act-based framework.
JS is a JavaScript operation based on Chrome V8 (V8 for short, which is an open source JavaScript engine) engine.
Optionally, the camera data acquisition instruction is used to instruct a control target camera to execute a target operation, where the target operation includes turning on the target camera; before the step 102, the method for acquiring data of a camera provided by the embodiment of the present disclosure may further include the following step 105, and the step 102 may be specifically implemented by the following step 102 a.
105. And under the condition that the target operating system is a preset system, determining whether the current application has the camera authority or not by calling the unified calling interface at the script layer.
102a, under the condition that the current application has the camera authority, issuing an instruction for starting the target camera to the native interface of the target operating system by calling the unified calling interface at the script layer.
The method and the device have the advantages that whether the current application has the camera permission or not can be acquired through the unified calling interface, then when the current application has the camera permission, the camera data acquisition instruction is directly issued through the unified calling interface, when the current application does not have the camera permission, whether the user starts the camera permission or not for the current application is prompted, and therefore the method and the device can achieve the purpose of achieving the undifferentiated calling on a script layer, the acquisition of the camera permission and the acquisition of the camera data. The function of acquiring the camera permission is encapsulated into the unified calling interface, so that the software development difficulty can be further reduced and the development progress of software can be effectively improved if the unified calling interface provided by the embodiment of the disclosure is used in the cross-platform application development process.
Optionally, after the step 105, the method for acquiring camera data provided by the embodiment of the present disclosure may further include the following step 106 and step 107, where the step 102a may be specifically implemented by the following step 102a 1.
106. And displaying second prompt information under the condition that the current application does not have the camera authority.
And the second prompt information is used for prompting whether the camera authority of the current application is started or not.
107. And displaying third prompt information under the condition of receiving a trigger operation of not starting the camera authority of the current application.
And the third prompt message is used for indicating that the current application is forbidden to start the target camera.
102a1, under the condition that a trigger operation for opening the currently applied camera permission is received, calling the unified calling interface at the script layer, and issuing an instruction for opening the target camera to the native interface of the target operating system.
It can be understood that when a user selects to use one camera, the operating system which needs to set the camera authority can inquire whether the equipment is authorized by the current application, if the current application is not authorized, an authorization prompt box of the system is popped up, and if the user selects authorization, data transmission is started for the user; if the User selects to reject, the User stays in an unauthorized state, and simultaneously prompts the User on a User Interface (UI) and gives a link for skipping to open the camera authority, so that the User can conveniently set the authority. Aiming at an operating system without setting the camera authority, when a user selects a camera, data transmission is directly started.
In the embodiment of the disclosure, under the condition that the current application does not have the camera permission, whether the user opens the camera permission of the current application is prompted, under the condition that the triggering operation of not opening the camera permission of the current application is received, the user is prompted to have no permission, the current application is prohibited from opening the target camera, and under the condition that the triggering operation of opening the camera permission of the current application is received, the unified calling interface is called on the script layer, and an instruction for opening the target camera is issued to the native interface of the target operating system, so that the man-machine interaction performance can be improved and the user experience is improved by setting the prompt information.
Illustratively, the unified call interface is generated according to the above S11 to S13, taking the script layer as the JS layer and the system layer API as the C + + layer API, for example, all operations related to the Camera are initiated from the JS layer, and are called into the Camera-like interface (API interface) of the C + + layer packaged by us through the JSbinding interface, and the implementation of the interface is classified into CameraWin, CameraMac, CameraAndroid, and the like according to different operating systems. For example, interfaces encapsulated in a C + + layer mainly include:
a creating function (constraint) of the Camera Camera instance, a Camera data callback function and a Camera permission callback function, wherein the two callbacks are recorded when the instance is created; the Camera creation can call different Camera system level APIs according to different operating systems to ensure that the Camera resource creation of the system level is finished; the camera permission detection interface (checkcamera authority) may query an access permission of a current application to a camera on the device; an available camera list obtaining function (availableCameraList) can obtain the identification of the currently available camera (permission detection is required to be ensured to pass); a switch camera function (switchCamera) function, which may be used to switch different cameras; there are also some common control functions that facilitate the control of the data flow, such as pause, resume and stop.
When the cmake program is executed, the operating system currently running by the electronic device can be acquired, a variable (e.g., PLATFORM _ OS) is set to indicate different operating systems, the variable values are different and represent different operating systems, and the acquisition function of the camera data packaged under different operating systems is invoked.
The interfaces of the Cmara class of the C + + layer can be mapped to the JS layer through the JSbinding technology, and the JS layer only needs to call the corresponding interfaces to complete the corresponding interaction effect, for example, as follows:
firstly, a camera instance C1 is created from the JS layer and a corresponding camera data callback function f1 displayed by an image is transmitted, the data acquired by the camera equipment can be called by f1, and a user can take the corresponding data through f 1; after the camera C1 is created, the authority state needs to be checked, if authorized, it indicates that the camera data can be directly used, and otherwise, the developer/user needs to take corresponding processing; acquiring a usable camera list through a bound availableCameraList interface, then selecting a device to be used to open through a switchCamera interface, and waiting for the data of the camera to be returned through f 1; after the data is returned through f1, these operations may be paused and resumed; the camera can be switched, the list is also acquired through the availableparameralst interface, then the used equipment is switched, and the stop interface can be called to close the camera without using the camera.
In the embodiment of the disclosure, focusing on the use of a camera module in a JS + C + + scene can support a PC terminal and a mobile terminal (windows, mac, linux, android and ios), and a combining layer is added between the C + + and JS layers in the whole process, and the combining layer can be only a transparent transmission layer; therefore, the calling link is shortened, the data analysis is reduced, and the efficiency is improved; the data of the camera is transmitted in a callback mode, and a user can flexibly select a cross-thread mode to process or an asynchronous mode to process and the like.
The camera data callback interface, namely the camera data callback function, refers to a function provided by a developer to the framework. This function serves as an input to the framework to tell the framework what processing the user wants to do with the data provided by the camera. For example, the user may provide a function to perform +1 processing for each pixel value of the image data of the camera. The camera data callback interface is customizable by the user.
Fig. 4 is a block diagram of a camera data acquisition apparatus according to an embodiment of the present disclosure, and as shown in fig. 4, the camera data acquisition apparatus includes: a receiving module 401 and a sending module 402; the receiving module 401 is configured to receive a first trigger operation, where the first trigger operation is used to instruct a camera to acquire a data acquisition instruction; the issuing module 402 is configured to issue the camera data acquisition instruction to a native interface of a target operating system by calling a unified call interface in a script layer in response to a first trigger operation received by the receiving module 401, where the unified call interface encapsulates an acquisition function of camera data under multiple operating systems, and the multiple operating systems include the target operating system; the receiving module 401 is further configured to receive response data corresponding to the camera data obtaining instruction returned by the native interface.
Optionally, the unified call interface is generated by: encapsulating a native interface of each operating system and an acquisition function of corresponding camera data into a system layer API; encapsulating the system layer APIs of the plurality of operating systems into a cross-platform camera module; and binding the cross-platform camera module to the script layer to generate the unified calling interface.
Optionally, the unified call interface is generated by: binding native interfaces of the plurality of operating systems to the scripting layer; on the script layer, encapsulating the native interface of each operating system and the acquisition function of the corresponding camera data into a script layer API; and encapsulating the script layer API of the plurality of operating systems into the unified calling interface.
Optionally, the issuing module 402 is specifically configured to determine, in response to a first trigger operation, that the operating system of the electronic device is the target operating system through the unified call interface; and issuing the camera data acquisition instruction to the native interface of the target operating system by calling a target function encapsulated in the unified calling interface at the script layer, wherein the target function is an acquisition function of the camera data corresponding to the camera data acquisition instruction under the target operating system.
Optionally, the apparatus further comprises: a display module; the display module is used for displaying first prompt information under the condition that the response data is not received within a preset time length after the camera data acquisition instruction is issued to a native interface of a target operating system by calling the unified calling interface in the script layer in response to the first trigger operation, wherein the first prompt information is used for prompting to re-trigger the camera data acquisition instruction.
Optionally, the camera data acquisition instruction is for indicating any one of: acquiring a camera list available for the electronic equipment, wherein the camera list comprises at least one camera identifier, and each camera identifier is used for indicating one camera; acquiring camera parameters of each camera available for the electronic equipment, wherein the camera parameters comprise any one of the following items: the camera identification, the camera image format and the camera connection state; controlling a target camera to execute a target operation, the target operation including any one of: and switching to the target camera, starting the target camera, closing the target camera, shooting images and stopping shooting the images.
Optionally, the camera data acquisition instruction is used to instruct a control target camera to execute a target operation, where the target operation includes turning on the target camera; the device also includes: a determining module; the determining module is used for determining whether the current application has the camera permission or not by calling the unified calling interface at the script layer under the condition that the target operating system is a preset system before the unified calling interface is called at the script layer and the camera data acquisition instruction is issued to the native interface of the target operating system; the issuing module 402 is specifically configured to issue an instruction to open the target camera to the native interface of the target operating system by calling the unified call interface at the script layer under the condition that the current application has the camera permission.
Optionally, the display module is further configured to, when the target operating system is a preset system, determine whether the current application has a camera right by calling the unified call interface in a script layer, and display second prompt information when the current application does not have the camera right, where the second prompt information is used to prompt whether to start the camera right of the current application; under the condition that the trigger operation of not starting the current application camera authority is received, displaying third prompt information, wherein the third prompt information is used for indicating that the current application is forbidden to start the target camera; the issuing module 402 is specifically configured to issue an instruction to open the target camera to the native interface of the target operating system by calling the unified call interface at the script layer, when a trigger operation to open the currently applied camera permission is received.
In the embodiment of the present disclosure, each module may implement the camera data obtaining method provided in the above method embodiment, and may achieve the same technical effect, and for avoiding repetition, details are not repeated here.
Fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure, which is used for exemplarily describing an electronic device implementing any camera data acquisition method in the embodiment of the present disclosure, and should not be construed as a specific limitation to the embodiment of the present disclosure.
As shown in fig. 5, electronic device 500 may include a processor (e.g., central processing unit, graphics processor, etc.) 501 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)502 or a program loaded from a storage device 508 into a Random Access Memory (RAM) 503. In the RAM 503, various programs and data necessary for the operation of the electronic apparatus 500 are also stored. The processor 501, the ROM 502, and the RAM 503 are connected to each other through a bus 504. An input/output (I/O) interface 505 is also connected to bus 504.
Generally, the following devices may be connected to the I/O interface 505: input devices 506 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 507 including, for example, a Liquid Crystal Display (LCD), speakers, vibrators, and the like; storage devices 508 including, for example, magnetic tape, hard disk, etc.; and a communication device 509. The communication means 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. While the electronic device 500 is illustrated with various means, it is not required that all illustrated means be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 509, or installed from the storage means 508, or installed from the ROM 502. When executed by the processor 501, the computer program may perform the functions defined in any of the camera data acquisition methods provided by the embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a first trigger operation, wherein the first trigger operation is used for indicating a camera data acquisition instruction; responding to a first trigger operation, calling a unified calling interface at a script layer, and issuing a camera data acquisition instruction to a native interface of a target operating system, wherein the unified calling interface is packaged with a camera data acquisition function under a plurality of operating systems, and the operating systems comprise the target operating system; and receiving response data corresponding to the camera data acquisition instruction returned by the native interface.
In embodiments of the present disclosure, computer program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Wherein the name of an element does not in some cases constitute a limitation on the element itself.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a computer-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a computer-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and the technical features disclosed in the present disclosure (but not limited to) having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (12)
1. A camera data acquisition method is applied to an electronic device comprising a target operating system, and comprises the following steps:
receiving a first trigger operation, wherein the first trigger operation is used for indicating a camera data acquisition instruction;
responding to the first trigger operation, calling a uniform calling interface at a script layer, and issuing a camera data acquisition instruction to a native interface of a target operating system, wherein the uniform calling interface is packaged with a camera data acquisition function under a plurality of operating systems, and the operating systems comprise the target operating system;
and receiving response data corresponding to the camera data acquisition instruction returned by the native interface.
2. The method of claim 1, wherein the unified invocation interface is generated by:
encapsulating a native interface of each operating system and an acquisition function of corresponding camera data into a system layer Application Program Interface (API);
encapsulating the system layer APIs of the plurality of operating systems into a cross-platform camera module;
binding the cross-platform camera module to the script layer to generate the unified call interface.
3. The method of claim 1, wherein the unified invocation interface is generated by:
binding native interfaces of the plurality of operating systems to the scripting layer;
at the script layer, encapsulating the native interface of each operating system and the acquisition function of the corresponding camera data into a script layer API;
and encapsulating the script layer APIs of the operating systems into the unified calling interface.
4. The method according to claim 1, wherein said issuing the camera data acquisition instruction to a native interface of a target operating system by calling a unified call interface at a script layer in response to the first trigger operation comprises:
responding to the first trigger operation, and determining that the operating system of the electronic equipment is the target operating system through the unified calling interface;
and issuing the camera data acquisition instruction to the native interface of the target operating system by calling a target function encapsulated in the unified calling interface at the script layer, wherein the target function is an acquisition function of the camera data corresponding to the camera data acquisition instruction under the target operating system.
5. The method of claim 1, wherein after issuing the camera data acquisition instruction to a native interface of a target operating system by calling a unified call interface at a script layer in response to the first trigger operation, the method further comprises:
and under the condition that the response data is not received within a preset time length, displaying first prompt information, wherein the first prompt information is used for prompting to re-trigger the camera data acquisition instruction.
6. The method of any of claims 1 to 5, wherein the camera data acquisition instructions are to indicate any of:
acquiring a camera list available for the electronic equipment, wherein the camera list comprises at least one camera identifier, and each camera identifier is used for indicating one camera;
acquiring camera parameters of each camera available for the electronic equipment, wherein the camera parameters comprise any one of the following items: the camera identification, the camera image format and the camera connection state;
controlling a target camera to execute a target operation, the target operation including any one of: and switching to the target camera, starting the target camera, closing the target camera, shooting images and stopping shooting the images.
7. The method of claim 6, wherein the camera data acquisition instructions are used to instruct a control target camera to perform a target operation, the target operation comprising turning on the target camera;
before the unified call interface is called at the script layer and the camera data acquisition instruction is issued to the native interface of the target operating system, the method further comprises the following steps:
under the condition that the target operating system is a preset system, determining whether the current application has the camera authority or not by calling the unified calling interface at a script layer;
the step of issuing the camera data acquisition instruction to a native interface of a target operating system by calling a uniform calling interface at a script layer comprises the following steps:
and under the condition that the current application has the camera authority, issuing an instruction for starting the target camera to the native interface of the target operating system by calling the unified calling interface at the script layer.
8. The method of claim 7, wherein after determining whether the current application has the camera right by calling the unified call interface at a script layer if the target operating system is a preset system, the method further comprises:
under the condition that the current application does not have the camera authority, displaying second prompt information, wherein the second prompt information is used for prompting whether the camera authority of the current application is started or not;
under the condition that a trigger operation of not starting the current application camera authority is received, displaying third prompt information, wherein the third prompt information is used for indicating that the current application is forbidden to start the target camera;
the issuing, by the script layer, the instruction to start the target camera to the native interface of the target operating system by calling the unified calling interface under the condition that the current application has the camera permission includes:
and under the condition of receiving a trigger operation for starting the current applied camera permission, issuing an instruction for starting the target camera to the native interface of the target operating system by calling the unified calling interface at the script layer.
9. A camera data acquisition apparatus, the apparatus including a target operating system, comprising: the system comprises a receiving module and a sending module;
the receiving module is used for receiving a first trigger operation, and the first trigger operation is used for indicating a camera data acquisition instruction;
the issuing module is configured to issue the camera data acquisition instruction to a native interface of a target operating system by calling a unified calling interface in a script layer in response to the first trigger operation received by the receiving module, where the unified calling interface encapsulates an acquisition function of camera data under multiple operating systems, and the multiple operating systems include the target operating system;
the receiving module is further configured to receive response data corresponding to the camera data acquisition instruction returned by the native interface.
10. An electronic device, comprising: a memory for storing a computer program and a processor; the processor is configured to execute the camera data acquisition method of any one of claims 1 to 8 when invoking the computer program.
11. A computer-readable storage medium, characterized in that a computer program is stored thereon, which when executed by a processor implements the camera data acquisition method according to any one of claims 1 to 8.
12. A computer program product, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, realizes the camera data acquisition method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210689278.9A CN115103116A (en) | 2022-06-16 | 2022-06-16 | Camera data acquisition method, device, equipment, storage medium and program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210689278.9A CN115103116A (en) | 2022-06-16 | 2022-06-16 | Camera data acquisition method, device, equipment, storage medium and program product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115103116A true CN115103116A (en) | 2022-09-23 |
Family
ID=83290310
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210689278.9A Pending CN115103116A (en) | 2022-06-16 | 2022-06-16 | Camera data acquisition method, device, equipment, storage medium and program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115103116A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461575A (en) * | 2014-12-26 | 2015-03-25 | 北京华电万通科技有限公司 | Device and method for JavaScript native interface calling conducted by crossing mobile operating system platform |
| CN110908712A (en) * | 2019-12-04 | 2020-03-24 | 北京中启智源数字信息技术有限责任公司 | Data processing method and equipment for cross-platform mobile terminal |
-
2022
- 2022-06-16 CN CN202210689278.9A patent/CN115103116A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461575A (en) * | 2014-12-26 | 2015-03-25 | 北京华电万通科技有限公司 | Device and method for JavaScript native interface calling conducted by crossing mobile operating system platform |
| CN110908712A (en) * | 2019-12-04 | 2020-03-24 | 北京中启智源数字信息技术有限责任公司 | Data processing method and equipment for cross-platform mobile terminal |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110874217B (en) | Interface display method and device for quick application and storage medium | |
| CN111338623B (en) | Method, device, medium and electronic equipment for developing user interface | |
| CN110069919B (en) | Information acquisition method and device | |
| CN113835992B (en) | Memory leakage processing method and device, electronic equipment and computer storage medium | |
| CN110007936B (en) | Data processing method and device | |
| CN110990105A (en) | Interface display method and device, electronic equipment and storage medium | |
| CN114595065A (en) | Data acquisition method and device, storage medium and electronic equipment | |
| CN111324376B (en) | Function configuration method, device, electronic equipment and computer readable medium | |
| CN111309304B (en) | Method, device, medium and electronic equipment for generating IDL file | |
| CN111078325B (en) | Application program running method and device, electronic equipment and storage medium | |
| CN110851211A (en) | Method, apparatus, electronic device, and medium for displaying application information | |
| CN112416303B (en) | Software development kit hot repair method and device and electronic equipment | |
| CN109840109B (en) | Method and apparatus for generating software development toolkit | |
| CN110069185B (en) | Method and apparatus for co-running hosted applications | |
| CN115103116A (en) | Camera data acquisition method, device, equipment, storage medium and program product | |
| CN111124523A (en) | Method and apparatus for initializing applications | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN113391860B (en) | Service request processing method and device, electronic equipment and computer storage medium | |
| CN111104183B (en) | Application program running method and device, electronic equipment and storage medium | |
| CN111309323A (en) | Parameter initialization method and device and electronic equipment | |
| CN111240801A (en) | Method, device, medium and electronic equipment for generating heap memory snapshot file | |
| CN112306469A (en) | Barrier-free component construction method, device, equipment and storage medium | |
| CN111324386A (en) | Method and device for starting personal application program, electronic equipment and storage medium | |
| CN110704767B (en) | Page opening method and device, electronic equipment and storage medium | |
| CN116346924A (en) | Network request processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |