WO2019127904A1 - 应用程序运行方法、装置、计算机设备和存储介质 - Google Patents
应用程序运行方法、装置、计算机设备和存储介质 Download PDFInfo
- Publication number
- WO2019127904A1 WO2019127904A1 PCT/CN2018/078319 CN2018078319W WO2019127904A1 WO 2019127904 A1 WO2019127904 A1 WO 2019127904A1 CN 2018078319 W CN2018078319 W CN 2018078319W WO 2019127904 A1 WO2019127904 A1 WO 2019127904A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- built
- kernel
- page
- server
- background image
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Definitions
- the present application relates to the field of computer technology, and in particular, to an application running method, apparatus, computer device, and storage medium.
- An application running method comprising:
- the target interface is obtained by rendering the built-in browser kernel according to the page program.
- An application running device comprising:
- a page acquisition request sending module configured to send a page acquisition request to the built-in server kernel of the application by using a built-in browser kernel of the application, where the page acquisition request carries a page identifier;
- a page program sending module configured to acquire a page program corresponding to the page identifier by using the built-in server kernel, and send the page program to the built-in browser kernel;
- a rendering module configured to render a target interface according to the page program by using the built-in browser kernel.
- a computer device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, the processor executing the computer program to implement the following steps:
- the target interface is obtained by rendering the built-in browser kernel according to the page program.
- a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the following steps:
- the target interface is obtained by rendering the built-in browser kernel according to the page program.
- the above application running method, device, computer device and storage medium do not need to develop different applications for different SDKs, just embed the built-in browser kernel and built-in server kernel into the application, and because of the built-in browser
- the kernel has powerful rendering capabilities, so it can still display the graphical interface of the application, reducing the development of the SDK while maintaining the original functionality.
- FIG. 1 is an application scenario diagram of an application running method in an embodiment
- FIG. 2 is a schematic flow chart of an application running method in an embodiment
- FIG. 3 is a schematic diagram of a login interface of an application in an embodiment
- FIG. 5 is a structural block diagram of an application running device in an embodiment
- Figure 6 is a diagram showing the internal structure of a computer device in an embodiment.
- the application running method provided by the present application can be applied to the application environment as shown in FIG. 1.
- the terminal includes a built-in browser kernel and a built-in server kernel, and the application page display is implemented by the built-in browser kernel and the built-in server kernel, for example, the terminal sends a page to the application's built-in server kernel through the application's built-in browser kernel.
- Obtaining a request the page obtaining request carries a page identifier; the terminal obtains a page program corresponding to the page identifier through the built-in server kernel, and sends the page program to the built-in browser kernel; the terminal renders the target interface according to the page program through the built-in browser kernel .
- the terminal can be, but is not limited to, various personal computers, notebook computers, smart phones, tablets, and portable wearable devices.
- an application running method is provided, which is applied to the terminal in FIG. 1 as an example, and includes the following steps:
- S202 Send a page acquisition request to the built-in server kernel of the application through the built-in browser kernel of the application, where the page acquisition request carries a page identifier.
- the built-in browser kernel and the built-in server kernel are embedded in the terminal's graphical interface application, so that the built-in browser kernel can be used as a graphical interface module to replace the sdk of various operating systems in the traditional development mode, and the built-in server
- the kernel acts as a model and data controller for the non-interface portion of the application.
- the built-in browser kernel directly interacts with the built-in server kernel using the browser's scripting language, which uses the standard http protocol.
- the built-in server kernel not only focuses on its interaction with the built-in browser kernel, but also includes data models, ie page programs.
- the built-in browser kernel in this embodiment may use the google company's browser kernel chromium kernel as an embedded graphical interface sdk provider, and use the GNU organization's microhttpd open source http server library as a built-in server kernel.
- the terminal When the terminal detects that the application is started, or the display interface of the application needs to be changed, the terminal sends a page acquisition request to the built-in server kernel of the application through the built-in browser kernel of the application, where the page acquisition request carries the page identifier,
- the page identifier may be an identifier that uniquely identifies the corresponding page program, such as a specific ID, etc., and is not specifically limited herein.
- S204 Obtain a page program corresponding to the page identifier through the built-in server kernel, and send the page program to the built-in browser kernel.
- the built-in server kernel receives the page acquisition request, the corresponding page program is obtained according to the page identifier carried by the page acquisition request, where the page programs may be pre-stored in the terminal, for example, they may be packaged in The application installation package is installed in the terminal along with the application installation package.
- the terminal queries the page program through the built-in server kernel, the page program is sent to the built-in browser kernel, so that the built-in browser kernel can be The page program is rendered.
- the target interface is obtained by rendering according to the page program through the built-in browser kernel.
- the built-in browser kernel receives the page program
- the page program is executed, so that the corresponding page can be rendered to obtain a target interface, and the application image interface is displayed.
- the above application running method, device, computer device and storage medium do not need to develop different applications for different SDKs, just embed the built-in browser kernel and built-in server kernel into the application, and because of the built-in browser
- the kernel has powerful rendering capabilities, so it can still display the graphical interface of the application, reducing the development of the SDK while maintaining the original functionality.
- the built-in browser kernel and built-in server kernel are embedded in the application of the front-end terminal.
- the built-in browser kernel communicates with the built-in server kernel through the standard http protocol, and the built-in browser kernel and built-in server kernel are combined and placed in the application.
- the built-in browser kernel provides interaction, the built-in server kernel provides data status, communicates via the standard http protocol, ensuring that the graphical interface of the application can be displayed, reducing the development of the SDK while maintaining the original functionality.
- the application running method further includes a pre-processing step, including receiving an input page program and a background image corresponding to the page program; installing the page program and the background image to the application installation In the directory.
- FIG. 3 is a schematic diagram of a login interface of an application in an embodiment, where the login interface includes a background image, a logo, an input box, and a login button.
- the background image, logo, and input box on the login interface and The login button and the like are all drawn using the sdk rendering of the windows platform, but in this embodiment, the developer first writes the page program login.html of the page, and if the background image exists on the page, the page program login of the page .html is packaged together with the background image images/logo.png and stored in the application's installation package. During the application installation, the page program login.html is installed with the background image images/logo.png. Go to the application's installation directory.
- a unique ID may be assigned to the page program of the application, and the background image corresponding to the page program is associated with the page program for storage, thereby installing The associated installation will also be done accordingly.
- the built-in browser kernel and the built-in server kernel are embedded in the application, and the related page program and the background image are written and stored in the built-in server kernel, thereby using the application.
- the built-in browser kernel can directly interact with the built-in server kernel to obtain the page program in the built-in server kernel. It does not need to develop different applications for different SDKs, which reduces the development of the SDK while maintaining the original The function.
- the step S206 that is, the step of rendering the target interface according to the page program by using the built-in browser kernel may include: rendering by the built-in browser kernel according to the page program; when the background image needs to be acquired during the rendering process, Sending a background image acquisition request to the built-in server kernel through the built-in browser kernel; obtaining a background image corresponding to the background image acquisition request through the built-in server kernel, and sending the background image to the built-in browser kernel; and using the built-in browser kernel according to the background image Continue to render to get the target interface.
- the built-in browser kernel when the built-in browser kernel obtains the page program, the built-in browser kernel is used to render according to the page program.
- the background image acquisition request is sent to the built-in server kernel through the built-in browser kernel.
- the request is also based on the standard http protocol.
- the built-in server kernel obtains the high background image acquisition request, it can be queried according to the ID of the page program.
- the corresponding background image is sent to the built-in browser kernel, so that the built-in browser kernel can continue to render according to the background image to obtain the target interface, that is, the target interface in FIG. 3 .
- the image resource can be continuously requested from the built-in http server through the http protocol.
- the application running method may further include: receiving the input parameter through the rendered target interface; sending the parameter to the built-in server kernel through the built-in browser kernel; verifying the parameter through the built-in server kernel, and Send the verification results to the built-in server kernel; display the verification results to the target interface through the built-in server kernel.
- the login interface has an input box through which parameters input by the user, such as a user name and a password, can be received, and the received parameters are sent to the built-in server through the built-in browser kernel.
- the kernel, the built-in server kernel executes a php script on the parameter to verify the parameters, and returns the verification result to the built-in browser kernel.
- the built-in browser kernel continues the subsequent steps according to the verification result, for example, the verification fails.
- the interface that fails verification is displayed. If the verification is successful, the interface for successful verification is displayed.
- the php script (PHP: acronym for Hypertext Preprocessor, Chinese name: "hypertext preprocessor”) is a general-purpose open source scripting language.
- the grammar absorbs the features of C language, Java and Perl, has a low entry threshold, is easy to learn, and is widely used, mainly for the field of Web development.
- the PHP file suffix is called php.
- sending parameters to the built-in server kernel through the built-in browser kernel may send a parameter asynchronous send request to the built-in server kernel through the built-in browser kernel, and the parameter asynchronous send request carries parameters.
- asynchronous processing of the page acquisition request and the parameter transmission request can improve the processing efficiency of the system.
- the parameter input by the user is received through the rendered target interface, and the parameter is sent to the built-in server kernel, and the built-in server kernel executes the PHP script according to the user parameter to verify the parameter and verify the result. Return to the built-in browser kernel. After receiving the verification result, the built-in browser kernel continues the subsequent steps according to the verification result. For example, if the verification fails, the interface that fails verification is displayed. If the verification is successful, the interface for successful verification is displayed.
- the application running method may further include: looping back the preset port through the built-in server kernel; and when receiving the page obtaining request in the preset port, continuing to obtain the page corresponding to the page identifier through the built-in server kernel. The steps of the program.
- the built-in server kernel can preset a port to receive a page fetch request sent by the built-in browser kernel, so that the built-in server kernel only needs to loop back to the port in real time to determine whether the built-in browser kernel sends a page fetch request to the built-in server kernel, if If there is a page acquisition request on the port, the page program corresponding to the page acquisition request is obtained by the built-in server kernel according to the page identifier. If the page does not have a page acquisition request, the port is continuously looped back and processed accordingly.
- the built-in server core loops back to the preset port.
- the built-in server kernel continues to obtain the page program corresponding to the page acquisition request according to the page identifier, thereby improving efficiency.
- FIG. 4 is a sequence diagram of an application running method in an embodiment.
- the preset port that is, the port of the built-in server loopback is 1234 port, and the page identifier is login.html.
- the application starts loading the built-in server kernel, and the built-in server kernel is on the local loopback port 1234 port.
- the application loads the built-in browser module so that the application's presentation module has the ability to render a web page like a browser.
- the built-in browser kernel sends a page fetch request to port 1234 based on the standard http protocol.
- the built-in server kernel receives the page fetch request of the built-in browser kernel, and obtains the corresponding page program login.html from the local folder and returns it to the built-in browser. Kernel. After the built-in browser kernel receives the page program login.html, it starts rendering the login page.
- the built-in browser kernel can continue to use the standard http protocol to the built-in server.
- the kernel requests a background image.
- the above embodiment has the same convenient development mode as the distributed bs architecture (terminal-server architecture).
- the developer only needs to care about the unified interface design in the html page, and the control logic in the script such as php.
- the rendering of the graphical interface is the responsibility of the built-in browser module, and the development of the back-end logic uses scripts to simplify the maintenance costs.
- the built-in browser module and the built-in server module interact within the program through the http protocol.
- the user of the graphical interface program has no difference in usage habits from the graphics program developed by the ordinary operating system-based sdk.
- FIGS. 2 and 4 are sequentially displayed in accordance with the indication of the arrows, these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in FIGS. 2 and 4 may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be performed at different times, or The order of execution of the stages is also not necessarily sequential, but may be performed alternately or alternately with at least a portion of the sub-steps or stages of other steps or other steps.
- an application running apparatus including: a page acquisition request sending module, a page program sending module, and a rendering module, wherein:
- the page acquisition request sending module 100 is configured to send a page acquisition request to the built-in server kernel of the application through the built-in browser kernel of the application, where the page acquisition request carries the page identifier.
- the page program sending module 200 is configured to obtain a page program corresponding to the page identifier through the built-in server kernel, and send the page program to the built-in browser kernel.
- the rendering module 300 is configured to render a target interface according to a page program by using a built-in browser kernel.
- the apparatus may further include:
- the receiving module is configured to receive the input page program and a background image corresponding to the page program.
- the rendering module can include:
- the first rendering unit is used to render according to the page program through the built-in browser kernel.
- the background image obtaining unit is configured to send a background image obtaining request to the built-in server kernel through the built-in browser kernel when the background image needs to be acquired during the rendering process.
- the background image sending unit is configured to obtain a background image corresponding to the background image obtaining request by using the built-in server kernel, and send the background image to the built-in browser kernel.
- the second rendering unit is configured to continue to render the target interface according to the background image through the built-in browser kernel.
- the apparatus may further include:
- the parameter receiving module is configured to receive the input parameter by using the target interface obtained by the rendering.
- a parameter sending module for sending parameters to the built-in server kernel through the built-in browser kernel.
- a verification module that validates parameters through the built-in server kernel and sends the verification results to the built-in server kernel.
- the parameter sending module can also be configured to send a parameter asynchronous sending request to the built-in server kernel through the built-in browser kernel, and the parameter asynchronous sending request carries the parameter.
- the apparatus may further include: a loopback module for looping back the preset port through the built-in server kernel.
- the page program sending module 200 is further configured to: when receiving the page obtaining request in the preset port, acquire the page program corresponding to the page identifier by using the built-in server kernel.
- the various modules in the above page program running device may be implemented in whole or in part by software, hardware, and combinations thereof.
- the above modules may be embedded in the processor in the computer device or may be stored in the memory in the computer device in a software form, so that the processor can call the corresponding operations of the above modules.
- a computer device which may be a terminal, and its internal structure diagram may be as shown in FIG. 6.
- the computer device includes a processor, memory, network interface, display screen, and input device connected by a system bus.
- the processor of the computer device is used to provide computing and control capabilities.
- the memory of the computer device includes a non-volatile storage medium, an internal memory.
- the non-volatile storage medium stores an operating system and a computer program.
- the internal memory provides an environment for operation of an operating system and computer programs in a non-volatile storage medium.
- the network interface of the computer device is used to communicate with an external terminal via a network connection.
- the computer program is executed by the processor to implement an application running method.
- the display screen of the computer device may be a liquid crystal display or an electronic ink display screen
- the input device of the computer device may be a touch layer covered on the display screen, or may be a button, a trackball or a touchpad provided on the computer device casing. It can also be an external keyboard, trackpad or mouse.
- FIG. 6 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied.
- the specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.
- a computer apparatus comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor performing the following steps: a built-in browsing through the application
- the kernel sends a page fetch request to the built-in server kernel of the application, the page fetch request carries the page identifier; the page program corresponding to the page identifier is obtained through the built-in server kernel, and the page program is sent to the built-in browser kernel; through the built-in browser
- the kernel renders the target interface according to the page program.
- the processor further implements the steps of: receiving an input page program and a background image corresponding to the page program; and installing the page program and the background image into an installation directory of the application.
- the step of executing the computer program by the processor to render the target interface according to the page program by using the built-in browser kernel may include: rendering by the built-in browser kernel according to the page program; When the background image is obtained, the background image acquisition request is sent to the built-in server kernel through the built-in browser kernel; the background image corresponding to the background image acquisition request is obtained through the built-in server kernel, and the background image is sent to the built-in browser kernel; The kernel continues to render the target interface based on the background image.
- the processor executes the computer program to: receive the input parameters through the rendered target interface; send the parameters to the built-in server kernel through the built-in browser kernel; and validate the parameters through the built-in server kernel, The verification results are sent to the built-in server kernel; the verification results are displayed to the target interface through the built-in server kernel.
- the step of sending the parameter to the built-in server kernel through the built-in browser kernel implemented by the processor when executing the computer program may include: sending a parameter asynchronous sending request to the built-in server kernel through the built-in browser kernel, the parameter is asynchronous The sending request carries parameters.
- the processor executes the computer program
- the following steps are further implemented: loopback the preset port through the built-in server kernel; when receiving the page acquisition request in the preset port, proceed to obtain the corresponding page identifier through the built-in server kernel.
- the steps of the page program are further implemented: loopback the preset port through the built-in server kernel; when receiving the page acquisition request in the preset port, proceed to obtain the corresponding page identifier through the built-in server kernel.
- a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements the steps of: transmitting to the application's built-in server kernel through the application's built-in browser kernel
- the page acquisition request carries the page identifier; the page program corresponding to the page identifier is obtained by the built-in server kernel, and the page program is sent to the built-in browser kernel; and the target interface is obtained by the built-in browser kernel according to the page program.
- the computer program when executed by the processor, further implements the steps of: receiving an input page program and a background image corresponding to the page program; installing the page program and the background image into an installation directory of the application.
- the step of the computer program being executed by the processor to render the target interface according to the page program by using the built-in browser kernel may include: rendering by the built-in browser kernel according to the page program; during the rendering process When the background image needs to be obtained, the background image acquisition request is sent to the built-in server kernel through the built-in browser kernel; the background image corresponding to the background image acquisition request is obtained through the built-in server kernel, and the background image is sent to the built-in browser kernel; The browser kernel continues rendering based on the background image to get the target interface.
- the computer program is further executed by the processor to: receive the input parameters through the rendered target interface; send the parameters to the built-in server kernel through the built-in browser kernel; and validate the parameters through the built-in server kernel And send the verification result to the built-in server kernel; display the verification result to the target interface through the built-in server kernel.
- the step of transmitting the parameter to the built-in server kernel through the built-in browser kernel implemented by the processor when the computer program is executed by the processor may include: sending a parameter asynchronous sending request to the built-in server kernel through the built-in browser kernel, the parameter The asynchronous send request carries parameters.
- the following steps are further implemented: loopback the preset port through the built-in server kernel; when receiving the page acquisition request in the preset port, continue to obtain the corresponding page identifier through the built-in server kernel. The steps of the page program.
- Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
- Volatile memory can include random access memory (RAM) or external cache memory.
- RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain.
- SRAM static RAM
- DRAM dynamic RAM
- SDRAM synchronous DRAM
- DDRSDRAM double data rate SDRAM
- ESDRAM enhanced SDRAM
- Synchlink DRAM SLDRAM
- Memory Bus Radbus
- RDRAM Direct RAM
- DRAM Direct Memory Bus Dynamic RAM
- RDRAM Memory Bus Dynamic RAM
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
一种应用程序运行方法、系统、计算机设备和存储介质。该方法包括:通过应用程序的内置浏览器内核向应用程序的内置服务器内核发送页面获取请求,页面获取请求携带有页面标识(S202);通过内置服务器内核获取与页面标识对应的页面程序,并将页面程序发送至内置浏览器内核(S204);通过内置浏览器内核根据页面程序进行渲染得到目标界面(S206)。上述应用程序运行方法、装置、计算机设备和存储介质,不需要针对不同的SDK开发不同的应用程序,仅仅是将内置浏览器内核和内置服务器内核植入应用程序中即可,且由于内置浏览器内核具有强大的渲染能力,因此仍可以显示出应用程序的图形界面,减少了SDK的开发的同时,保持了原有的功能。
Description
本申请申明享有2017年12月30日递交的申请号为201711491035.X、名称为“应用程序运行方法、装置、计算机设备和存储介质”的中国专利申请的优先权,该中国专利申请的整体内容以参考的方式结合在本申请中。
本申请涉及计算机技术领域,特别是涉及一种应用程序运行方法、装置、计算机设备和存储介质。
随着计算机技术的发展,出现了应用程序,其可以安装在不同的操作系统中,且每一种操作系统都为了各自的操作系统平台提供了不同的SDK(Software Development Kit,软件开发工具包)给开发者,供后者使用这些SDK在操作系统平台上构建图形界面的应用程序。
然而,每一个操作系统平台的开发者需要学习了解各自操作系统平台的sdk的说明文档,甚至需要掌握不同的开发语言,了解不同操作系统平台的系统特性。这就导致一个公司一个相同功能应用需要开发多个版本,需要维护不同的版本,同样的应用控制逻辑需要不同的语言实现多个版本。
发明内容
基于此,有必要针对上述技术问题,提供一种能够减少开发版本的应用程序运行方法、装置、计算机设备和存储介质。
一种应用程序运行方法,所述方法包括:
通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;
通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;
通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。
一种应用程序运行装置,所述装置包括:
页面获取请求发送模块,用于通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;
页面程序发送模块,用于通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;
渲染模块,用于通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。
一种计算机设备,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,所述处理器执行所述计算机程序时实现以下步骤:
通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;
通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;
通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。一种计算机可读存储介质,其上存储有计算机程序,所述计算机程序被处理器执行时实现以下步骤:
通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;
通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;
通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。
上述应用程序运行方法、装置、计算机设备和存储介质,不需要针对不同的SDK开发不同的应用程序,仅仅是将内置浏览器内核和内置服务器内核植入应用程序中即可,且由于内置浏览器内核具有强大的渲染能力,因此仍可以显示出应用程序的图形界面,减少了SDK的开发的同时,保持了原有的功能。
图1为一个实施例中应用程序运行方法的应用场景图;
图2为一个实施例中应用程序运行方法的流程示意图;
图3为一实施例中的应用程序的登录界面的示意图;
图4为一实施例中的应用程序运行方法的时序图;
图5为一个实施例中应用程序运行装置的结构框图;
图6为一个实施例中计算机设备的内部结构图。
为了使本申请的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本申请进行进一步详细说明。应当理解,此处描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请提供的应用程序运行方法,可以应用于如图1所示的应用环境中。其中,终端中包括内置浏览器内核和内置服务器内核,通过该内置浏览器内核和内置服务器内核实现应用程序的页面显示,例如终端通过应用程序的内置浏览器内核向应用程序的内置服务器内核发送页面获取请求,页面获取请求携带有页面标识;终端通过内置服务器内核获取与页面标识对应的页面程序,并将页面程序发送至内置浏览器内核;终端通过内置浏览器内核根据页面程序进行渲染得到目标界面。其中,终端可以但不限于是各种个人计算机、笔记本电脑、智能手机、平板电脑和便携式可穿戴设备。
在一个实施例中,如图2所示,提供了一种应用程序运行方法,以该方法应用于图1中的终端为例进行说明,包括以下步骤:
S202:通过应用程序的内置浏览器内核向应用程序的内置服务器内核发送页面获取请求,页面获取请求携带有页面标识。
具体地,在终端的具有图形界面的应用程序中嵌入内置浏览器内核和内置服务器内核,这样内置浏览器内核可以作为图形界面的模块,替换传统开发模式中多样的操作系统的sdk,而内置服务器内核则作为应用程序非界面部分的模型和数据控制者。其中内置浏览器内核直接使用浏览器的脚本语言与内置服务器内核进行直接交互,该交互过程采用的是标准http协议。且关于内置服务器内核不仅仅关注其与内置浏览器内核的交互,还包括数据模型,即页面程序等。
其中,本实施例中的内置浏览器内核可以是使用google公司的浏览器内核chromium内核作为嵌入的图形界面sdk提供者,使用GNU组织的microhttpd开源http服务器库作为内置服务器内核。
当终端检测到应用程序启动时,或者应用程序的显示界面需要改变时,终端通过应用程序的内置浏览器内核向应用程序的内置服务器内核发送页面获取请求,该页面获取请求携带有页面标识,该页面标识可以是唯一确定对应的页面程序的标识,例如特定的ID等,在此不作具体限制。
S204:通过内置服务器内核获取与页面标识对应的页面程序,并将页面程序发送至内置浏览器内核。
具体地,当内置服务器内核接收到该页面获取请求时,则根据页面获取请求携带的页面标识获取到对应的页面程序,其中该些页面程序可以是预先存储在终端中的,例如其可以打包在应用程序安装包中,并随应用程序安装包一起安装在终端中,当终端通过内置服务器内核查询到该页面程序时,则将该页面程序发送至内置浏览器内核,从而内置浏览器内核可以根据页面程序进行渲染。
S206:通过内置浏览器内核根据页面程序进行渲染得到目标界面。
具体地,当内置浏览器内核接收到页面程序时,则执行该页面程序,从而可以将对应的页面进行渲染得到目标界面,实现应用程序图像界面的显示。
上述应用程序运行方法、装置、计算机设备和存储介质,不需要针对不同的SDK开发不同的应用程序,仅仅是将内置浏览器内核和内置服务器内核植入应用程序中即可,且由于内置浏览器内核具有强大的渲染能力,因此仍可以显示出应用程序的图形界面,减少了SDK的开发的同时,保持了原有的功能。在前端的终端的应用程序中内嵌内置浏览器内核和内置服务器内核,内置浏览器内核通过标准http协议与内置服务器内核相通信,将内置浏览器内核和内置服务器内核组合在一起放在应用程序中,内置浏览器内核提供交互,内置服务器内核提供数据状态,通过标准http协议进行通信,确保可以显示出应用程序的图形界面,减少了SDK的开发的同时,保持了原有的功能。
在其中一个实施例中,上述应用程序运行方法还包括一预处理步骤,该预处理步骤包括接收输入的页面程序以及与页面程序对应的背景图片;将页面程序和背景图片安装至应用程序的安装目录中。
具体地,在开发应用程序时,在该应用程序中嵌入内置浏览器内核和内置服务器内核,在此以开发一通信应用程序进行说明,特别以该通信应用程序的登录界面进行说明,参见图3,图3为一实施例中的应用程序的登录界面的示意图,该登录界面上包括背景图片、logo、输入框以及登录按钮等,传统中,该登录界面上的背景图片、logo、输入框以及登录按钮等都是使用windows平台的sdk渲染绘制上去的,但是在该实施例中,开发人员首先编写该页面的页面程序login.html,如果该页面存在背景图片,则将该页面的页面程序login.html和背景图片images/logo.png一起打包在一起存储在应用程序的安装包中,在应用程序安装的过程中,则会将该页面程序 login.html和背景图片images/logo.png一起安装至应用程序的安装目录中。
其中,为了对应用程序的页面程序和背景图片进行分类存储,可以给应用程序的页面程序分配一唯一的ID,并将与该页面程序对应的背景图片与该页面程序进行关联存储,从而在安装的过程中也会相应地进行关联安装。
上述实施例中,在开发应用程序的时候,在应用程序中内嵌内置浏览器内核和内置服务器内核,且将相关的页面程序和背景图片进行编写存储在内置服务器内核中,从而在使用该应用程序时,则内置浏览器内核可以直接向内置服务器内核进行交互,获取内置服务器内核中的页面程序,不需要针对不同的SDK开发不同的应用程序,减少了SDK的开发的同时,保持了原有的功能。
在其中一个实施例中,步骤S206,即通过内置浏览器内核根据页面程序进行渲染得到目标界面的步骤可以包括:通过内置浏览器内核根据页面程序进行渲染;当渲染过程中需要获取背景图片时,则通过内置浏览器内核向内置服务器内核发送背景图片获取请求;通过内置服务器内核获取与背景图片获取请求对应的背景图片,并将背景图片发送至内置浏览器内核;通过内置浏览器内核根据背景图片继续渲染得到目标界面。
具体地,在内置浏览器内核获取到页面程序时,则通过内置浏览器内核根据页面程序进行渲染,当渲染过程中需要获取背景图片时,例如上述实施例中,需要获得登录界面的背景图片时,则通过内置浏览器内核向内置服务器内核发送背景图片获取请求,该请求也是基于标准http协议进行的,当内置服务器内核获取到高背景图片获取请求时,则根据该页面程序的ID可以查询到对应的背景图片,将该背景图片发送至内置浏览器内核,从而内置浏览器内核可以根据该背景图片继续进行渲染得到目标界面,即如图3中的目标界面。
上述实施例中,在渲染过程中如果需要其他资源,例如背景图等图片资 源,可以继续通过http协议向内置的http服务器请求图片资源。
在其中一个实施例中,该应用程序运行方法还可以包括:通过渲染得到的目标界面接收输入的参数;通过内置浏览器内核将参数发送至内置服务器内核;通过内置服务器内核对参数进行验证,并将验证结果发送至内置服务器内核;通过内置服务器内核将验证结果显示至目标界面。
具体地,如图3所示,该登录界面中具有输入框,通过该输入框可以接收到用户输入的参数,例如用户名和密码等,通过内置浏览器内核将该接收到的参数发送至内置服务器内核,内置服务器内核对该参数执行php脚本以对参数进行验证,并将验证结果返回至内置浏览器内核,内置浏览器内核接收该验证结果后,根据验证结果继续后续步骤,例如验证失败,则显示验证失败的界面,验证成功,则显示验证成功的界面。其中php脚本(PHP:Hypertext Preprocessor的缩写,中文名:“超文本预处理器”)是一种通用开源脚本语言。语法吸收了C语言、Java和Perl的特点,入门门槛较低,易于学习,使用广泛,主要适用于Web开发领域。PHP的文件后缀名为php。
在其中一个实施例中,通过内置浏览器内核将参数发送至内置服务器内核可以是通过内置浏览器内核向内置服务器内核发送参数异步发送请求,参数异步发送请求中携带有参数。具体地,将页面获取请求和参数发送请求进行异步处理,可以提高系统的处理效率。
上述实施例中,通过所渲染出的目标界面接收用户输入的参数,并将所述参数发送至内置服务器内核,内置服务器内核根据用户参数执行PHP脚本以对所述参数进行验证,并将验证结果返回至内置浏览器内核,内置浏览器内核接收该验证结果后,根据验证结果继续后续步骤,例如验证失败,则显示验证失败的界面,验证成功,则显示验证成功的界面。
在其中一个实施例中,该应用程序运行方法还可以包括:通过内置服务器内核回环预设端口;当预设端口中接收到页面获取请求时,则继续通过内置服务器内核获取与页面标识对应的页面程序的步骤。
具体地,内置服务器内核可以预设端口来接收内置浏览器内核发送的页面获取请求,从而内置服务器内核只需要实时回环该端口即可以判断内置浏览器内核是否向内置服务器内核发送页面获取请求,如果该端口存在页面获取请求时,则继续通过内置服务器内核根据页面标识获取到与页面获取请求对应的页面程序,如果该端口不存在页面获取请求,则继续回环该端口,并进行相应地处理。
上述实施例中,内置服务器内核在本地回环预设端口,当预设端口中存在页面获取请求,则继续通过内置服务器内核根据页面标识获取到与页面获取请求对应的页面程序,提高效率。
参阅图4,图4为一实施例中的应用程序运行方法的时序图,其中预设的端口,即内置服务器回环的端口为1234端口,页面标识为login.html。
在应用程序启动时,应用程序启动加载内置服务器内核,内置服务器内核在本地回环端口1234端口。应用程序加载内置浏览器模块,使得应用程序的展示模块具备向浏览器一样的渲染网页的能力。内置浏览器内核基于标准http协议向1234端口发送页面获取请求,内置服务器内核接收到该内置浏览器内核的页面获取请求,从本地文件夹获取到对应的页面程序login.html返回给内置的浏览器内核。内置浏览器内核接收到该页面程序login.html后,开始渲染登录页面,如果渲染过程中,需要其他的资源,例如背景图片等图片资源时,内置浏览器内核可以继续通过标准http协议向内置服务器内核请求背景图片。内置浏览器模块渲染登录界面,呈现给用户进行交互,用户填写相应的参数,例如用户名和密码,并点击登录按钮发起登录操作,即内置浏览器内核向内置服务器内核发送一个ajax(Asynchronous JavaScript and XML(异步的JavaScript和XML))异步请求到地址:http://localhost:1234/login.php?user=abc&pass=def。内置服务器内核加载动态脚本解释器php以将内置浏览器内核传过来的参数user=abc&pass=def来执行login.php中的脚本,并把登录后的结果以http 的形式返回给内置浏览器内核。内置浏览器内个接收到ajax的登录处理结果后,执行后续的动作。
上述实施例中具备和分布式bs架构(终端-服务器架构)一样的便捷开发模式,开发者只需要关心html页面里面的统一的界面设计,和php等脚本里面的控制逻辑编写。图形界面的渲染有内置浏览器模块负责,后端逻辑的开发使用脚本也简化了维护的成本。内置的浏览器模块和内置的服务器模块通过http协议在程序内部交互,图形界面程序的用户在使用习惯上和普通的基于操作系统的sdk开发的图形程序没有差异。
应该理解的是,虽然图2和图4的流程图中的各个步骤按照箭头的指示依次显示,但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明,这些步骤的执行并没有严格的顺序限制,这些步骤可以以其它的顺序执行。而且,图2和图4中的至少一部分步骤可以包括多个子步骤或者多个阶段,这些子步骤或者阶段并不必然是在同一时刻执行完成,而是可以在不同的时刻执行,这些子步骤或者阶段的执行顺序也不必然是依次进行,而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
在一个实施例中,如图5所示,提供了一种应用程序运行装置,包括:页面获取请求发送模块、页面程序发送模块和渲染模块,其中:
页面获取请求发送模块100,用于通过应用程序的内置浏览器内核向应用程序的内置服务器内核发送页面获取请求,页面获取请求携带有页面标识。
页面程序发送模块200,用于通过内置服务器内核获取与页面标识对应的页面程序,并将页面程序发送至内置浏览器内核。
渲染模块300,用于通过内置浏览器内核根据页面程序进行渲染得到目标界面。
在其中一个实施例中,装置还可以包括:
接收模块,用于接收输入的页面程序以及与页面程序对应的背景图片。
安装模块,用于将页面程序和背景图片安装至应用程序的安装目录中。
在其中一个实施例中,渲染模块可以包括:
第一渲染单元,用于通过内置浏览器内核根据页面程序进行渲染。
背景图片获取单元,用于当渲染过程中需要获取背景图片时,则通过内置浏览器内核向内置服务器内核发送背景图片获取请求。
背景图片发送单元,用于通过内置服务器内核获取与背景图片获取请求对应的背景图片,并将背景图片发送至内置浏览器内核。
第二渲染单元,用于通过内置浏览器内核根据背景图片继续渲染得到目标界面。
在其中一个实施例中,装置还可以包括:
参数接收模块,用于通过渲染得到的目标界面接收输入的参数。
参数发送模块,用于通过内置浏览器内核将参数发送至内置服务器内核。
验证模块,用于通过内置服务器内核对参数进行验证,并将验证结果发送至内置服务器内核。
显示模块,用于通过内置服务器内核将验证结果显示至目标界面。
在其中一个实施例中,参数发送模块还可以用于通过内置浏览器内核向内置服务器内核发送参数异步发送请求,参数异步发送请求中携带有参数。
在其中一个实施例中,装置还可以包括:回环模块,用于通过内置服务器内核回环预设端口。
页面程序发送模块200还可以用于当预设端口中接收到页面获取请求时,则通过内置服务器内核获取与页面标识对应的页面程序。
关于应用程序运行装置的具体限定可以参见上文中对于应用程序运行方法的限定,在此不再赘述。上述页面程序运行装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独 立于计算机设备中的处理器中,也可以以软件形式存储于计算机设备中的存储器中,以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中,提供了一种计算机设备,该计算机设备可以是终端,其内部结构图可以如图6所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口、显示屏和输入装置。其中,该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统和计算机程序。该内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机程序被处理器执行时以实现一种应用程序运行方法。该计算机设备的显示屏可以是液晶显示屏或者电子墨水显示屏,该计算机设备的输入装置可以是显示屏上覆盖的触摸层,也可以是计算机设备外壳上设置的按键、轨迹球或触控板,还可以是外接的键盘、触控板或鼠标等。
本领域技术人员可以理解,图6中示出的结构,仅仅是与本申请方案相关的部分结构的框图,并不构成对本申请方案所应用于其上的计算机设备的限定,具体的计算机设备可以包括比图中所示更多或更少的部件,或者组合某些部件,或者具有不同的部件布置。
在一个实施例中,提供了一种计算机设备,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,处理器执行计算机程序时实现以下步骤:通过应用程序的内置浏览器内核向应用程序的内置服务器内核发送页面获取请求,页面获取请求携带有页面标识;通过内置服务器内核获取与页面标识对应的页面程序,并将页面程序发送至内置浏览器内核;通过内置浏览器内核根据页面程序进行渲染得到目标界面。
在一个实施例中,处理器执行计算机程序时还实现以下步骤:接收输入的页面程序以及与页面程序对应的背景图片;将页面程序和背景图片安装至应用程序的安装目录中。
在一个实施例中,处理器执行计算机程序时所实现的通过内置浏览器内核根据页面程序进行渲染得到目标界面的步骤,可以包括:通过内置浏览器内核根据页面程序进行渲染;当渲染过程中需要获取背景图片时,则通过内置浏览器内核向内置服务器内核发送背景图片获取请求;通过内置服务器内核获取与背景图片获取请求对应的背景图片,并将背景图片发送至内置浏览器内核;通过内置浏览器内核根据背景图片继续渲染得到目标界面。
在一个实施例中,处理器执行计算机程序时还实现以下步骤:通过渲染得到的目标界面接收输入的参数;通过内置浏览器内核将参数发送至内置服务器内核;通过内置服务器内核对参数进行验证,并将验证结果发送至内置服务器内核;通过内置服务器内核将验证结果显示至目标界面。
在一个实施例中,处理器执行计算机程序时所实现的通过内置浏览器内核将参数发送至内置服务器内核的步骤,可以包括:通过内置浏览器内核向内置服务器内核发送参数异步发送请求,参数异步发送请求中携带有参数。
在一个实施例中,处理器执行计算机程序时还实现以下步骤:通过内置服务器内核回环预设端口;当预设端口中接收到页面获取请求时,则继续通过内置服务器内核获取与页面标识对应的页面程序的步骤。
在一个实施例中,提供了一种计算机可读存储介质,其上存储有计算机程序,计算机程序被处理器执行时实现以下步骤:通过应用程序的内置浏览器内核向应用程序的内置服务器内核发送页面获取请求,页面获取请求携带有页面标识;通过内置服务器内核获取与页面标识对应的页面程序,并将页面程序发送至内置浏览器内核;通过内置浏览器内核根据页面程序进行渲染得到目标界面。
在一个实施例中,计算机程序被处理器执行时还实现以下步骤:接收输入的页面程序以及与页面程序对应的背景图片;将页面程序和背景图片安装至应用程序的安装目录中。
在一个实施例中,计算机程序被处理器执行时所实现的通过内置浏览器 内核根据页面程序进行渲染得到目标界面的步骤,可以包括:通过内置浏览器内核根据页面程序进行渲染;当渲染过程中需要获取背景图片时,则通过内置浏览器内核向内置服务器内核发送背景图片获取请求;通过内置服务器内核获取与背景图片获取请求对应的背景图片,并将背景图片发送至内置浏览器内核;通过内置浏览器内核根据背景图片继续渲染得到目标界面。
在一个实施例中,计算机程序被处理器执行时还实现以下步骤:通过渲染得到的目标界面接收输入的参数;通过内置浏览器内核将参数发送至内置服务器内核;通过内置服务器内核对参数进行验证,并将验证结果发送至内置服务器内核;通过内置服务器内核将验证结果显示至目标界面。
在一个实施例中,计算机程序被处理器执行时所实现的通过内置浏览器内核将参数发送至内置服务器内核的步骤,可以包括:通过内置浏览器内核向内置服务器内核发送参数异步发送请求,参数异步发送请求中携带有参数。
在一个实施例中,计算机程序被处理器执行时还实现以下步骤:通过内置服务器内核回环预设端口;当预设端口中接收到页面获取请求时,则继续通过内置服务器内核获取与页面标识对应的页面程序的步骤。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程,是可以通过计算机程序来指令相关的硬件来完成,所述的计算机程序可存储于一非易失性计算机可读取存储介质中,该计算机程序在执行时,可包括如上述各方法的实施例的流程。其中,本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用,均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限,RAM以多种形式可得,诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM (ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合,为使描述简洁,未对上述实施例中的各个技术特征所有可能的组合都进行描述,然而,只要这些技术特征的组合不存在矛盾,都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式,其描述较为具体和详细,但并不能因此而理解为对发明专利范围的限制。应当指出的是,对于本领域的普通技术人员来说,在不脱离本申请构思的前提下,还可以做出若干变形和改进,这些都属于本申请的保护范围。因此,本申请专利的保护范围应以所附权利要求为准。
Claims (20)
- 一种应用程序运行方法,所述方法包括:通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。
- 根据权利要求1所述的方法,其特征在于,所述方法还包括:接收输入的页面程序以及与所述页面程序对应的背景图片;将所述页面程序和所述背景图片安装至应用程序的安装目录中。
- 根据权利要求2所述的方法,其特征在于,所述通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面的步骤,包括:通过所述内置浏览器内核根据所述页面程序进行渲染;当渲染过程中需要获取背景图片时,则通过所述内置浏览器内核向所述内置服务器内核发送背景图片获取请求;通过所述内置服务器内核获取与所述背景图片获取请求对应的背景图片,并将所述背景图片发送至所述内置浏览器内核;通过所述内置浏览器内核根据所述背景图片继续渲染得到目标界面。
- 根据权利要求1至3任意一项所述的方法,其特征在于,所述方法还包括:通过渲染得到的目标界面接收输入的参数;通过所述内置浏览器内核将所述参数发送至所述内置服务器内核;通过所述内置服务器内核对所述参数进行验证,并将验证结果发送至所述内置服务器内核;通过所述内置服务器内核将所述验证结果显示至所述目标界面。
- 根据权利要求4所述的方法,其特征在于,所述通过所述内置浏览器内核将所述参数发送至所述内置服务器内核的步骤,包括:通过所述内置浏览器内核向所述内置服务器内核发送参数异步发送请求,所述参数异步发送请求中携带有所述参数。
- 根据权利要求4所述的方法,其特征在于,所述方法还包括:通过内置服务器内核回环预设端口;当所述预设端口中接收到页面获取请求时,则继续通过所述内置服务器内核获取与所述页面标识对应的页面程序的步骤。
- 一种应用程序运行装置,其特征在于,所述装置包括:页面获取请求发送模块,用于通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;页面程序发送模块,用于通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;渲染模块,用于通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。
- 根据权利要求7所述的装置,其特征在于,所述装置还包括:接收模块,用于接收输入的页面程序以及与所述页面程序对应的背景图片;安装模块,用于将所述页面程序和所述背景图片安装至应用程序的安装目录中。
- 一种计算机设备,包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序,其特征在于,所述处理器执行所述计算机程序时实现以下步骤:通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。
- 根据权利要求9所述的计算机设备,其特征在于,所述处理器执行所述计算机程序时还实现以下步骤:接收输入的页面程序以及与所述页面程序对应的背景图片;将所述页面程序和所述背景图片安装至应用程序的安装目录中。
- 根据权利要求10所述的计算机设备,其特征在于,所述通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面的步骤,包括:通过所述内置浏览器内核根据所述页面程序进行渲染;当渲染过程中需要获取背景图片时,则通过所述内置浏览器内核向所述内置服务器内核发送背景图片获取请求;通过所述内置服务器内核获取与所述背景图片获取请求对应的背景图片,并将所述背景图片发送至所述内置浏览器内核;通过所述内置浏览器内核根据所述背景图片继续渲染得到目标界面。
- 根据权利要求9-11中任一项所述的计算机设备,其特征在于,所述处理器执行所述计算机程序时还实现以下步骤:通过渲染得到的目标界面接收输入的参数;通过所述内置浏览器内核将所述参数发送至所述内置服务器内核;通过所述内置服务器内核对所述参数进行验证,并将验证结果发送至所述内置服务器内核;通过所述内置服务器内核将所述验证结果显示至所述目标界面。
- 根据权利要求12所述的计算机设备,其特征在于,所述通过所述内置浏览器内核将所述参数发送至所述内置服务器内核的步骤,包括:通过所述内置浏览器内核向所述内置服务器内核发送参数异步发送请求,所述参数异步发送请求中携带有所述参数。
- 根据权利要求12所述的计算机设备,其特征在于,所述处理器执行所述计算机程序时还实现以下步骤:通过内置服务器内核回环预设端口;当所述预设端口中接收到页面获取请求时,则继续通过所述内置服务器内核获取与所述页面标识对应的页面程序的步骤。
- 一种计算机可读存储介质,其上存储有计算机程序,其特征在于,所述计算机程序被处理器执行时实现以下步骤:通过应用程序的内置浏览器内核向所述应用程序的内置服务器内核发送页面获取请求,所述页面获取请求携带有页面标识;通过所述内置服务器内核获取与所述页面标识对应的页面程序,并将所述页面程序发送至所述内置浏览器内核;通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面。
- 根据权利要求9所述的存储介质,其特征在于,所述计算机程序被处理器执行时还实现以下步骤:接收输入的页面程序以及与所述页面程序对应的背景图片;将所述页面程序和所述背景图片安装至应用程序的安装目录中。
- 根据权利要求16所述的存储介质,其特征在于,所述通过所述内置浏览器内核根据所述页面程序进行渲染得到目标界面的步骤,包括:通过所述内置浏览器内核根据所述页面程序进行渲染;当渲染过程中需要获取背景图片时,则通过所述内置浏览器内核向所述内置服务器内核发送背景图片获取请求;通过所述内置服务器内核获取与所述背景图片获取请求对应的背景图片,并将所述背景图片发送至所述内置浏览器内核;通过所述内置浏览器内核根据所述背景图片继续渲染得到目标界面。
- 根据权利要求15-17中任一项所述的存储介质,其特征在于,所述计算机程序被处理器执行时还实现以下步骤:通过渲染得到的目标界面接收输入的参数;通过所述内置浏览器内核将所述参数发送至所述内置服务器内核;通过所述内置服务器内核对所述参数进行验证,并将验证结果发送至所述内置服务器内核;通过所述内置服务器内核将所述验证结果显示至所述目标界面。
- 根据权利要求18所述的存储介质,其特征在于,所述通过所述内置浏览器内核将所述参数发送至所述内置服务器内核的步骤,包括:通过所述内置浏览器内核向所述内置服务器内核发送参数异步发送请求,所述参数异步发送请求中携带有所述参数。
- 根据权利要求18所述的存储介质,其特征在于,所述计算机程序被处理器执行时还实现以下步骤:通过内置服务器内核回环预设端口;当所述预设端口中接收到页面获取请求时,则继续通过所述内置服务器内核获取与所述页面标识对应的页面程序的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711491035.X | 2017-12-30 | ||
CN201711491035.XA CN108108219B (zh) | 2017-12-30 | 2017-12-30 | 应用程序运行方法、装置、计算机设备和存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019127904A1 true WO2019127904A1 (zh) | 2019-07-04 |
Family
ID=62215448
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/078319 WO2019127904A1 (zh) | 2017-12-30 | 2018-03-07 | 应用程序运行方法、装置、计算机设备和存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN108108219B (zh) |
WO (1) | WO2019127904A1 (zh) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108984244A (zh) * | 2018-06-12 | 2018-12-11 | 深圳市网心科技有限公司 | 浏览器页面渲染方法、电子装置及计算机可读存储介质 |
CN109614562B (zh) * | 2018-11-27 | 2024-05-14 | 平安科技(深圳)有限公司 | 邮件显示方法、装置、计算机设备以及存储介质 |
CN110704136B (zh) * | 2019-09-27 | 2023-06-20 | 北京百度网讯科技有限公司 | 小程序组件的渲染方法、客户端、电子设备及存储介质 |
CN111538555A (zh) * | 2020-04-28 | 2020-08-14 | 北京同邦卓益科技有限公司 | 界面处理方法、装置、设备及计算机可读存储介质 |
CN112035193A (zh) * | 2020-07-27 | 2020-12-04 | 成都安易迅科技有限公司 | 应用程序的界面生成方法、装置、存储介质及计算机设备 |
CN113709154B (zh) * | 2021-08-25 | 2023-08-15 | 平安国际智慧城市科技股份有限公司 | 浏览器安全处理方法、装置、计算机设备及存储介质 |
CN114077368B (zh) * | 2022-01-19 | 2022-06-28 | 腾讯科技(深圳)有限公司 | 车载小程序运行方法、装置、计算机设备及存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101930366A (zh) * | 2010-08-27 | 2010-12-29 | 武汉天喻信息产业股份有限公司 | 一种基于浏览器的手机中间件 |
US20150277716A1 (en) * | 2014-03-28 | 2015-10-01 | Wipro Limited | System and method for improved light-weight business process modeling in offline mode using browser resources |
CN106775668A (zh) * | 2016-11-30 | 2017-05-31 | 广东亿迅科技有限公司 | 跨操作系统的移动应用程序开发框架及实现方法 |
CN107341027A (zh) * | 2017-05-18 | 2017-11-10 | 北京金山安全管理系统技术有限公司 | 用户界面的生成方法和生成装置 |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101414257B (zh) * | 2008-11-13 | 2011-09-21 | 成都市华为赛门铁克科技有限公司 | 软件界面实现方法、装置 |
CN101894021A (zh) * | 2010-06-29 | 2010-11-24 | 宇龙计算机通信科技(深圳)有限公司 | 一种嵌入式系统的界面实现方法及系统 |
CN104104707B (zh) * | 2013-04-12 | 2017-02-08 | 腾讯科技(深圳)有限公司 | 网页数据更新方法、终端、缓存服务器及系统 |
CN104516913B (zh) * | 2013-09-30 | 2018-07-20 | 昆明能讯科技有限责任公司 | 基于多种内核技术的网页浏览器 |
CN105553959B (zh) * | 2015-12-11 | 2019-12-10 | Tcl集团股份有限公司 | 动态生成智能设备操作界面的远程控制方法和系统 |
-
2017
- 2017-12-30 CN CN201711491035.XA patent/CN108108219B/zh active Active
-
2018
- 2018-03-07 WO PCT/CN2018/078319 patent/WO2019127904A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101930366A (zh) * | 2010-08-27 | 2010-12-29 | 武汉天喻信息产业股份有限公司 | 一种基于浏览器的手机中间件 |
US20150277716A1 (en) * | 2014-03-28 | 2015-10-01 | Wipro Limited | System and method for improved light-weight business process modeling in offline mode using browser resources |
CN106775668A (zh) * | 2016-11-30 | 2017-05-31 | 广东亿迅科技有限公司 | 跨操作系统的移动应用程序开发框架及实现方法 |
CN107341027A (zh) * | 2017-05-18 | 2017-11-10 | 北京金山安全管理系统技术有限公司 | 用户界面的生成方法和生成装置 |
Also Published As
Publication number | Publication date |
---|---|
CN108108219B (zh) | 2020-10-27 |
CN108108219A (zh) | 2018-06-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2019127904A1 (zh) | 应用程序运行方法、装置、计算机设备和存储介质 | |
US20150378756A1 (en) | Systems and methods for mobile application tracing instrumentation | |
US7689665B2 (en) | Dynamically loading scripts | |
US9104809B2 (en) | Facilitating automated validation of a web application | |
US8150939B1 (en) | Method and system for wrapping and componentizing javascript centric widgets using java components | |
US8640104B2 (en) | Computer method and apparatus for debugging in a dynamic computer language | |
WO2020151333A1 (zh) | 页面加载方法、装置、计算机设备和存储介质 | |
US8539506B2 (en) | Dynamic injection of code into running process | |
US8615750B1 (en) | Optimizing application compiling | |
US9262311B1 (en) | Network page test system and methods | |
US11023558B1 (en) | Executing functions on-demand on a server utilizing web browsers | |
CN110363009B (zh) | 应用程序安全测试方法、装置和计算机可读存储介质 | |
US10423793B2 (en) | Install runtime agent for security test | |
US10789751B2 (en) | Method and apparatus for implementing animation in client application and animation script framework | |
JP2018156294A (ja) | ソフトウェア検証装置およびソフトウェア検証プログラム | |
US20090049423A1 (en) | Javascripttm programming extension | |
CN111930629A (zh) | 页面测试方法、装置、电子设备及存储介质 | |
CN111679828A (zh) | 一种数据处理的方法及装置、电子设备、存储介质 | |
CN116860614A (zh) | 性能测试方法、装置、设备、存储介质和程序产品 | |
CN116795679A (zh) | 一种Web应用测试方法、装置、电子设备及存储介质 | |
CN111338928A (zh) | 基于chrome浏览器测试的方法及装置 | |
US20120174078A1 (en) | Smart cache for a server test environment in an application development tool | |
CN111859403A (zh) | 依赖关系漏洞的确定方法、装置、电子设备及存储介质 | |
Varanasi et al. | Restful spring | |
CN113608745B (zh) | 一种初始化用户权限的方法及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18893667 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 09.11.2020) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18893667 Country of ref document: EP Kind code of ref document: A1 |