CN110457621A - A kind of page display method, device and the medium of mixing application - Google Patents
A kind of page display method, device and the medium of mixing application Download PDFInfo
- Publication number
- CN110457621A CN110457621A CN201910755677.9A CN201910755677A CN110457621A CN 110457621 A CN110457621 A CN 110457621A CN 201910755677 A CN201910755677 A CN 201910755677A CN 110457621 A CN110457621 A CN 110457621A
- Authority
- CN
- China
- Prior art keywords
- interface
- application
- displayed
- loading
- application interface
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- User Interface Of Digital Computer (AREA)
Abstract
This application discloses a kind of page display methods of mixing application, comprising: when the host process starting of mixing application, renders primary window and is resided in memory；When will show application interface during operation process, configuration file is obtained；According to business function type and configuration file belonging to application interface to be presented, the corresponding application interface type of application interface to be presented is determined；When application interface to be presented is primary interface, loads primary window and render application interface to be presented in primary window；When application interface to be presented is web interface, loads primary window and render load interface in primary window, application interface to be presented is loaded by browser kernel, load interface is hidden and is embedded in application interface to be presented in primary window.The characteristics of so retaining Web application, and can support to improve application compatibility and response performance compared with multi-service type.Disclosed herein as well is corresponding device, equipment and media.
Description
Technical Field
The present application relates to the field of application development technologies, and in particular, to a method, an apparatus, a device, and a computer storage medium for displaying a page of a hybrid application.
Background
In order to quickly develop applications to be put on the market to overcome the market, at present, many application projects mainly adopt a Web page programming language for application development, and applications developed in this way are referred to as Web applications.
The application display content upgrading method of the Web application only needs to update a Web page at a server side, no perception of a user can be achieved, the Web application has the advantage of being convenient for development and updating, meanwhile, the problems of low application interface loading speed, long user waiting time, poor experience and the like exist, more importantly, the Web application support service type is very limited, the Web application cannot be realized aiming at services such as message pushing, resident background and the like, and in addition, the black box characteristic of the Web application causes that the Web application is difficult to be well linked and communicated with other systems.
Based on this, it is urgently needed to provide a solution that can both retain the characteristics of the Web application and support more service types, so that the compatibility and the response performance of the application are higher, and the requirements of users on high-quality experience are met.
Disclosure of Invention
The embodiment of the application provides a page display method for hybrid application, which can keep the characteristics of Web application, support more service types and improve application compatibility and response performance. The embodiment of the application also provides a corresponding device, equipment, a storage medium and a computer program product.
A first aspect of the present application provides a page display method for a hybrid application, where the method includes:
when the master control process of the hybrid application is started, rendering a native window and residing in a memory;
when an application Interface (UI) is to be displayed in the process of running the process, acquiring a configuration file, wherein the configuration file is configured with corresponding relations between various service function types and the application Interface types;
determining an application interface type corresponding to the application interface to be displayed according to the service function type of the application interface to be displayed and the configuration file, wherein the application interface type is used for identifying the application interface as a native interface or a webpage interface;
when the application interface to be displayed is a native interface, loading the native window and rendering the application interface to be displayed on the native window;
and when the application interface to be displayed is a web page interface, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window.
A second aspect of the present application provides a hybrid application page display apparatus, the apparatus comprising:
the first control module is used for rendering a native window and residing the native window in the memory when the master control process of the hybrid application is started;
the acquisition module is used for acquiring a configuration file when an application interface needs to be displayed in the process of running the process, wherein the configuration file is configured with a corresponding relation between each service function type and each application interface type;
the interface type determining module is used for determining an application interface type corresponding to the application interface to be displayed according to the service function type of the application interface to be displayed and the configuration file, wherein the application interface type is used for identifying the application interface as a native interface or a webpage interface;
the first display module is used for loading the native window and rendering the application interface to be displayed on the native window when the application interface to be displayed is the native interface;
and the second display module is used for loading the native window, rendering a loading interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window when the application interface to be displayed is a web page interface.
A third aspect of the present application provides a terminal device, comprising a display, a processor, and a memory:
the memory is used for storing a computer program;
the processor is configured to execute the steps of the page display method of the hybrid application according to the first aspect.
A fourth aspect of the present application provides a computer-readable storage medium for storing a computer program for executing the page display method of the hybrid application according to the first aspect.
A fifth aspect of the present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of page display for a hybrid application of the first aspect described above.
According to the technical scheme, the embodiment of the application has the following advantages:
the embodiment of the application provides a page display method of a hybrid application, which fuses a native UI on the basis of a webpage UI, dynamically switches a UI layer through a configuration file, and controls a layer to uniformly process response to realize the hybrid programming of two UIs so as to obtain the hybrid application, when a main control process of the hybrid application is started, a native window is rendered and resides in a memory, the configuration file configured with the corresponding relation between a service function type and a UI type is obtained when an application interface is to be displayed in the process of running the process, the UI type corresponding to the UI to be displayed is determined based on the configuration file, if the UI type is the native UI, the native window is loaded and the UI to be displayed is rendered in the native window, if the UI type is the webpage UI, the native window is loaded and the loading interface is rendered in the native window, the UI to be displayed is loaded by using a browser kernel, and then hiding the loading interface, and embedding the UI to be displayed in the native window. The method can effectively combine the flexibility of the webpage UI and the high-performance low-consumption characteristic of the native UI, and simultaneously keep the high performance of the main functions on the premise of rapidly supporting the dynamic UI, and can ensure the stable operation on a low-configuration machine, thereby improving the user experience. In addition, the decoupling of the UI layer and the control layer can increase the stability of the application and enhance the usability of the application.
Drawings
Fig. 1 is a scene architecture diagram of a page display method for a hybrid application in an embodiment of the present application;
FIG. 2 is a flowchart of a page display method for a hybrid application according to an embodiment of the present application;
FIG. 3 is a flow chart illustrating the operation of a hybrid application in an embodiment of the present application;
FIG. 4 is a flow diagram of a hybrid application load UI in an embodiment of the present application;
FIG. 5 is a flowchart of a hybrid application close UI in an embodiment of the present application;
fig. 6A is an application scene schematic diagram of a page display method of a hybrid application in the embodiment of the present application;
FIG. 6B is a diagram illustrating an effect of displaying a login UI by a hybrid application in an embodiment of the present application;
fig. 6C is a schematic diagram illustrating an effect of displaying an image viewing UI by a hybrid application in the embodiment of the present application;
FIG. 7 is a schematic structural diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 8 is a schematic structural diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 9 is a schematic structural diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 10 is a schematic structural diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 11 is a schematic structural diagram of a hybrid application page display device according to an embodiment of the present application;
fig. 12 is a schematic structural diagram of a terminal in an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
To facilitate understanding of the technical solutions of the present application, the technical terms related thereto will be described first.
An application, also referred to as an application program, refers to a computer program designed to perform a certain task or tasks. When it is operating in user mode, it can interact with the user through a visual user interface UI. Applications can be classified into native (native) applications and web applications according to the type of UI used in the development process.
Native applications are applications developed using Native UIs provided by a platform in a platform-specific development language. The web application is specifically an application developed by using a web UI and adopting web programming languages such as a uniform standard hypertext markup language (HTML), a JavaScript (JavaScript), a Cascading Style Sheet (CSS), and the like, and the terminal device can access the application through a browser, and the application can support cross-platform.
Aiming at the problems that a web application developed for occupying the market is low in loading speed, limited in supporting service types and difficult to perform linkage communication with other systems, the application provides a page display method for forming a hybrid application by fusing a native UI on the basis of a web UI, and the method is different from a common client embedded activity dynamic web page.
It can be understood that the page display method of the hybrid application provided by the application can be applied to a processing device with a display function. The processing device may specifically be a terminal, where the terminal may be a desktop terminal device such as a desktop computer and a notebook computer, or a portable mobile terminal such as a tablet computer and a mobile phone, or a vehicle-mounted terminal, an Augmented Reality (AR)/Virtual Reality (VR) terminal, which is not limited in this embodiment.
The page display method of the hybrid application can be stored in the terminal in the form of a computer program, and the terminal realizes the page display method of the hybrid application by running the computer program. The computer program may be a stand-alone computer program, or may be a functional module, a plug-in or an applet integrated with other applications.
In practical applications, the page display method of the hybrid application provided by the present application can be applied to, but is not limited to, the application environment shown in fig. 1.
As shown in fig. 1, a terminal 100 is loaded with a hybrid application, where the hybrid application includes a main control process, when the main control process is started, a native window is rendered and resides in a memory, when an application interface is to be displayed in a process of running the process, a configuration file is obtained, an application interface type corresponding to the application interface to be displayed is determined according to a service function type to which the application interface to be displayed belongs and the configuration file, and when the application interface to be displayed is a native interface, the native window is loaded and the application interface to be displayed is rendered in the native window; and when the application interface to be displayed is a web page interface, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window.
In order to make the technical solution of the present application clearer and easier to understand, a page display method for a hybrid application provided in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.
Referring to a flowchart of a page display method of a hybrid application shown in fig. 2, the method is applied to a terminal, and includes:
s201, when the master control process of the hybrid application is started, rendering a native window and residing the native window in a memory.
The hybrid application refers to an application in which a web UI and a native UI are merged, and specifically, in this embodiment, the hybrid application may be an application in which a native UI is merged on the basis of a web UI. It is understood that the fusion method can be used for developing mixed application in the fields of medical treatment, education, social interaction, entertainment and the like.
Taking the medical field as an example, a mixed image application can be formed by fusing the native UI on the basis of the original web UI of the image application, and a doctor checks the image data of a patient by running the mixed image application on his workstation and diagnoses a disease based on the image data.
The hybrid application includes a control layer and a UI layer. The control layer comprises a main control module, and the main control module is mainly responsible for some pre-loaded service logics, such as communication with a background, log initialization, pull configuration and the like; the UI layer includes a native UI module and a web page UI module. After the main control module is started, the native UI module is initialized in advance and occupies the main cycle, so that the progress is not quitted, and then UI control and rendering work are dynamically performed after user behaviors are responded in the main cycle.
In actual application, a user can start a main control process by triggering the main control module of the hybrid application, so that control over the native UI and the webpage UI is realized. Specifically, the user may start the master process in various ways, and taking the hybrid application as an influencing application in the medical field as an example, the terminal may start the master process of the hybrid application in response to a call-up operation of the image archiving and communication system for the hybrid application.
In some possible implementation manners, the terminal may display a shortcut icon of the hybrid application, the user may trigger a start operation by clicking the shortcut icon or controlling the shortcut icon through a voice instruction, and the terminal starts an active process of the hybrid application in response to the start operation triggered by the shortcut icon of the hybrid application. Of course, the terminal may also provide a shortcut key for the hybrid application, and the user may start the master control process of the hybrid application by triggering the shortcut key.
Considering that the native UI needs to occupy a main loop, that is, regardless of whether rendering occurs to the UI, the native UI core needs to be initialized and run for a long time, and the web UI is actually a complex control embedded in a window based on a very simple native UI, therefore, regardless of which type of UI is used, the terminal can pre-render the native window and reside it in the memory when the main control process is started, so that the native window can be directly called from the memory in the subsequent process.
S202, when the application interface is to be displayed in the process of running the process, the configuration file is obtained.
And the configuration file is configured with the corresponding relation between each service function type and each application interface type. The service function type is used to identify a service function corresponding to the application interface, for example, in medical imaging application, the service function type may identify the UI as a login UI, an image viewing UI, a diagnosis conclusion generation UI or a help center UI, and the like. The application interface type is mainly used to identify the application interface as a native interface or a web interface (i.e., a native UI or a web UI).
Considering that the web page UI is easier to update than the native UI, the configuration can be performed according to the service function update period corresponding to each service function type when configuring the interface type corresponding to each service function type. Specifically, the interface type corresponding to the service function type whose service function update period is longer than the preset period may be configured as a native interface, and the interface type corresponding to the service function type whose service function update period is not longer than the preset period may be configured as a web interface. As one example, the help center UI may be configured as a native UI and the shadow view UI may be configured as a web page UI.
In the process of running the main control process, if the UI is to be displayed, the terminal may obtain a configuration file corresponding to the hybrid application from the application server in advance. Certainly, in some cases, the terminal may first determine whether the configuration file corresponding to the hybrid application is stored in the cache, and if so, the terminal may directly obtain the configuration file from the cache, so that efficiency of obtaining the configuration file may be improved, and further response efficiency may be improved, and if not, the terminal may obtain the configuration file from the application server.
S203, determining the application interface type corresponding to the application interface to be displayed according to the service function type of the application interface to be displayed and the configuration file. Executing S204 when the application interface to be displayed is a native interface; and executing S205 when the application interface to be displayed is a web page interface.
Specifically, the terminal matches the service function type to which the UI to be displayed belongs with the configuration file, and if the service function type is hit in the configuration file, determines the application interface type corresponding to the service function type that is hit in the configuration file as the application interface type corresponding to the UI to be displayed.
In consideration of different characteristics of the native UI and the web UI, the embodiment of the present application provides different rendering strategies for the native UI and the web UI, respectively, where the rendering strategy for the native UI may be referred to as S204, and the rendering strategy for the web UI may be referred to as S205.
S204, loading the native window and rendering the application interface to be displayed on the native window.
S205, loading the native window, rendering a loading interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window.
Specifically, the native UI generally belongs to fixed content, and does not need to be repeatedly loaded, so that the loading logic thereof can be set to be loaded as required, and the native UI resides in the memory after the rendering is completed. Further, considering that the destruction cost after the window is created is high, when the user triggers the closing operation for the native UI, the terminal may hide the native window in response to the closing operation without performing a release operation, when the native window is called, the native window is redisplayed, and when the application exits, the native window is released. Practical tests prove that resources occupied by the hidden native window are only one tenth of those of a webpage UI, and the method can realize quick response through less resource occupation.
And for the webpage UI, when the terminal loads the native window, a loading interface, namely a loading UI, is rendered on the native window, then the UI to be displayed is loaded through a browser kernel, and after the loading of the UI to be displayed is completed, the loading interface is hidden and the UI to be displayed is embedded in the native window.
The loading logic of the web page UI may be set to load on demand, with a loading process that is slightly more complex than the original UI loading process. Because the recording kernel needs more than 500 milliseconds to block the main thread time and needs to occupy higher memory, the native kernel is not generally preloaded, but kernel loading is performed asynchronously when the first webpage UI is rendered. Once loading is completed, the kernel resides in the memory, and the main process is prevented from being blocked by repeatedly consuming resources.
Based on this, the terminal can also judge whether the UI to be displayed is the first webpage UI to be displayed in the hybrid application before loading the UI, if so, the browser kernel is asynchronously loaded and resident in the memory, if not, the browser kernel in the memory is directly called, then the steps of loading the native window and rendering the loading UI on the native window, loading the UI to be displayed through the browser kernel, hiding the loading UI and embedding the application interface to be displayed in the native window are executed. Therefore, the browser kernel can be loaded as required, and the browser kernel is resident in the memory in the application running process so as to be called up directly later, thereby saving the loading time and improving the response efficiency.
Further, when a user triggers a closing operation for the web page UI, the terminal may count the number of web page rendering processes in the system in response to the closing operation, hide the web page UI when the number of the web page rendering processes is one, and reside the rendering process corresponding to the web page UI in the memory, and unload the web page UI and close the rendering process corresponding to the web page UI when the number of the web page rendering processes is greater than one, so that the hybrid application can be guaranteed to maintain a fast response performance.
From the above, the embodiment of the present application provides a page display method for a hybrid application, which fuses a native UI on the basis of a web UI, dynamically switches UI layers during configuration and issuing run-time, and controls the layers to uniformly process responses to implement hybrid programming of two UIs, thereby obtaining a hybrid application, wherein when a main control process of the hybrid application is started, a native window is rendered and resides in a memory, a configuration file configured with a correspondence between a service function type and a UI type is obtained when an application interface is to be displayed during a run process, a UI type corresponding to the UI to be displayed is determined based on the configuration file, if the UI type is a native UI, the native window is loaded and the UI to be displayed is rendered in the native window, if the UI type is a web UI, the native window is loaded and the loading interface is rendered in the native window, the UI to be displayed is loaded by using a kernel of a browser, and then hiding the loading interface, and embedding the UI to be displayed in the native window. The method can effectively combine the flexibility of the webpage UI and the high-performance low-consumption characteristic of the native UI, and simultaneously keep the high performance of the main functions on the premise of rapidly supporting the dynamic UI, and can ensure the stable operation on a low-configuration machine, thereby improving the user experience. In addition, the decoupling of the UI layer and the control layer can increase the stability of the application and enhance the usability of the application.
For ease of understanding, the following description is made with reference to a specific implementation of the page display method of the hybrid application in a browser.
Referring to the operation flow diagram of the hybrid application shown in fig. 3, the hybrid application includes a main control module, a native UI module, and a web UI module, where the native UI module includes a native UI, a corresponding controller, and a model module, the web UI module includes a web UI, a corresponding controller, and a model module, and the main control module may perform UI control. Specifically, when the hybrid application runs, a native window is first rendered, the native window resides in a memory, then when the UI to be displayed is a web UI, a sub-window is rendered in the native window as a browser UI (i.e., a web UI), a browser rendering process is invoked, and a sub-window controller is handed to the rendering process for processing. After internal rendering is completed, communication between js in the rendering process and the main process c + + can be realized through the native bridge, and therefore interaction at some native levels is responded.
Next, a UI loading process and a UI closing process of the hybrid application will be described in detail with reference to the drawings.
Referring to a flow diagram of UI loading in a hybrid application shown in fig. 4, when a user triggers UI loading operation by clicking a control or the like, a terminal loads a UI in response to the user operation, and first the terminal may determine whether a UI to be displayed is a native UI based on a configuration file, if so, directly render the native UI, and a user may perform a corresponding user operation through the native UI, and if not, first load the native UI, and then judge whether a browser kernel is loaded completely, if not, first load the browser kernel, if so, directly render a web UI based on the browser kernel, and after rendering of the web UI, hide the loadingUI, load a web control into a window, complete displaying of the web UI, and respond to the user operation by the web and a native unified control module.
Referring to the flow diagram of UI closing in the composite application shown in fig. 5, when a user operates to close a web page window, since a main loop of a web page kernel is run in a single thread, the idle state of the kernel cannot be dynamically maintained, and more than one control must be kept in running, otherwise the kernel thread exits the loop and the consumed resources need to be repeatedly invoked, when the web page window is closed, the number of currently existing web page rendering processes can be checked first, if the number of the web page rendering processes is equal to one, the window is hidden and resides in a memory, and if the number of the web page rendering processes is greater than one, the web page control is destroyed, the rendering processes are stopped, and a single page is dynamically unloaded.
In order to make the technical scheme of the application clearer and easier to understand, the application further combines with relevant application scenes in the medical field to describe in detail the page display method of the hybrid application.
Referring to an application scene schematic diagram of a page display method of a hybrid application shown in fig. 6A, the application scene includes a terminal 610, an application server 620 and an image scanner 630, where the terminal 610 may specifically be a workstation, an image archiving and communication system is installed on the workstation, the system may invoke the hybrid application of the image application, and the hybrid application may interact with the application server 620 to obtain image information obtained by scanning a body part of a patient by the image scanner 630, so that a doctor may view the image information and perform a diagnosis based on the image information by the terminal 610.
Specifically, a doctor starts a main control process of the hybrid application by clicking a shortcut icon of the hybrid application displayed by the terminal 610, the terminal 610 renders a native window and resides in a memory, a login UI is first displayed in the process of running the main control process, for this reason, the terminal 610 first determines whether a configuration file corresponding to the hybrid application is stored in a local cache, and if not, acquires the configuration file from the application server 620, determines a UI type corresponding to the UI to be displayed based on the configuration file, in this example, the login UI is a native UI, the terminal 610 directly loads the native window, and directly renders the login UI in the native window.
Referring to the effect diagram of the login UI shown in fig. 6B, the login UI is provided with a username input control, a password input control and a login control, and the doctor inputs a username and a password through the username input control and the password input control and then executes a login operation by triggering the login control. The terminal 610 responds to the login operation, sends a login request message to the application server, the login request message carries a user name and a password, the application server 620 compares the user name and the password in the login request message with the stored user name and password, and if the user name and the password are consistent, the login is successful.
Upon successful login, the terminal 610 will next display a login successful UI and a home UI of the hybrid application, in this example, the terminal 610 determines that the login successful UI is a native UI and the hybrid application home UI is a web UI based on the profile. The terminal 610 directly renders the login success UI in the rendering window, jumps to the hybrid application home page UI after 3 seconds, renders the loadingUI in the native window when displaying the application home page UI, loads the hybrid application home page UI through the browser kernel, hides the loadingUI after the loading is completed, and embeds the hybrid application home page UI in the native window.
In the mixed application homepage UI, a doctor may trigger an image viewing operation through a menu control, and the terminal 610 skips to display the image viewing UI, which is a web page UI, in response to the viewing operation, so that the terminal 610 renders the loadingUI in a native window, loads the image viewing UI through a browser kernel, hides the loadingUI after the loading is completed, and displays the image viewing UI, which may specifically refer to fig. 6C, at this time, the doctor may select a patient name or other conditions, and the terminal 610 sends an image viewing request message to the application server 620 to obtain image data corresponding to the patient name from the application server 620, and displays the image data.
When the user triggers a closing operation for the image viewing UI, since the UI is a web page UI, the terminal 610 counts the number of web page rendering processes in the system, in this example, the number of web page rendering processes is greater than one, and the terminal 610 unloads the image viewing UI and closes its corresponding rendering process.
Based on the above specific implementation manner of the page display method for hybrid application provided in the embodiment of the present application, the embodiment of the present application further provides a corresponding device, and then the device is introduced from the perspective of function modularization.
Referring to fig. 7, a schematic structural diagram of a hybrid application page display device is shown, where the device 700 includes:
the first control module 710 is configured to render a native window and reside in a memory when a master control process of the hybrid application is started;
an obtaining module 720, configured to obtain a configuration file when an application interface needs to be displayed in a process of running the process, where the configuration file is configured with a corresponding relationship between each service function type and an application interface type;
the interface type determining module 730 is configured to determine, according to the service function type to which the application interface to be displayed belongs and the configuration file, an application interface type corresponding to the application interface to be displayed, where the application interface type is used to identify that the application interface is a native interface or a web interface;
a first display module 740, configured to, when the application interface to be displayed is a native interface, load the native window and render the application interface to be displayed in the native window;
and a second display module 750, configured to, when the application interface to be displayed is a web page interface, load the native window, render a loading interface in the native window, load the application interface to be displayed through a browser kernel, hide the loading interface, and embed the application interface to be displayed in the native window.
Optionally, referring to fig. 8, fig. 8 is a schematic structural diagram of a hybrid application page display device according to an embodiment of the present application, and based on the structure shown in fig. 7, the second display module 750 includes:
the first display submodule 751 is configured to, when the application interface to be displayed is a first web page interface to be displayed in the hybrid application, asynchronously load a browser kernel and reside in a memory, load the native window and render a loading interface on the native window, load the application interface to be displayed through the browser kernel, hide the loading interface, and embed the application interface to be displayed in the native window;
the second display submodule 752 is configured to, when the application interface to be displayed is not the first web page interface to be displayed in the hybrid application, call the browser kernel in the memory, load the native window and render a loading interface on the native window, load the application interface to be displayed through the browser kernel, hide the loading interface, and embed the application interface to be displayed in the native window.
Optionally, referring to fig. 9, fig. 9 is a schematic structural diagram of a hybrid application page display apparatus provided in an embodiment of the present application, and on the basis of the structure shown in fig. 7, the apparatus 700 further includes:
a first closing operation response module 761, configured to, in response to a closing operation triggered by a target application interface displayed for the hybrid application, hide the native window when the target application interface is a native interface;
a second closing operation response module 762, configured to count the number of web page rendering processes in the system when the target application interface is a web page interface, hide the target application interface and resident a rendering process corresponding to the web page interface in a memory when the number of the web page rendering processes is one, and unload the target application interface and close the rendering process corresponding to the target application interface when the number of the web page rendering processes is greater than one.
Optionally, referring to fig. 10, fig. 10 is a schematic structural diagram of a hybrid application page display apparatus provided in an embodiment of the present application, and on the basis of the structure shown in fig. 7, the apparatus 700 further includes:
a call-up module 771, configured to, in response to a call-up operation of the video archiving and communication system for the hybrid application, start a master control process of the hybrid application; or,
a start module 772, configured to start the master process of the hybrid reference in response to a start operation triggered by the shortcut icon for the hybrid application.
Of course, the apparatus 700 may also include the above-mentioned call-out module 771 and the start module 772 on the basis of the structure shown in fig. 8.
Optionally, referring to fig. 11, fig. 11 is a schematic structural diagram of a hybrid application page display apparatus provided in an embodiment of the present application, and on the basis of the structure shown in fig. 7, the obtaining module 720 includes:
a first obtaining sub-module 721, configured to obtain a configuration file corresponding to the hybrid application from an application server;
the first obtaining submodule 722 is configured to obtain a configuration file corresponding to the hybrid application from a local cache; the interface type corresponding to each service function type in the configuration file is determined according to a service function updating period corresponding to each service function type, wherein the interface type corresponding to the service function type with the service function updating period being greater than the preset period is a native interface, and the interface type corresponding to the service function type with the service function updating period not greater than the preset period is a web interface.
Of course, the obtaining module 720 in the apparatus 700 may also include the first obtaining sub-module 721 and the first obtaining sub-module 722 on the basis of the structure shown in fig. 8.
As shown in fig. 12, for convenience of description, only the portions related to the embodiments of the present application are shown, and details of the specific technology are not disclosed, please refer to the method portion of the embodiments of the present application. The terminal can be any terminal equipment including a desktop computer, a notebook computer, a tablet computer and the like, and the terminal is taken as the desktop computer as an example:
fig. 12 is a block diagram illustrating a partial structure of a desktop related to a terminal device provided in an embodiment of the present application. Referring to fig. 12, the desktop includes: radio Frequency (RF) circuit 1210, memory 1220, input unit 1230, display unit 1240, sensor 1250, audio circuit 1260, wireless fidelity (WiFi) module 1270, processor 1280, and power supply 1290. Those skilled in the art will appreciate that the desktop configuration shown in FIG. 12 is not meant to be a limitation of a desktop and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.
The following describes each component of the desktop computer in detail with reference to fig. 12:
the RF circuit 1210 is configured to receive and transmit signals during information transmission and reception or during a call, and in particular, receive downlink information of a base station and then process the received downlink information to the processor 1280; in addition, the data for designing uplink is transmitted to the base station. In general, RF circuit 1210 includes, but is not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a low noise Amplifier (Lownoise Amplifier; LNA), a duplexer, and the like. In addition, the RF circuit 1210 may also communicate with networks and other devices via wireless communication.
The memory 1220 may be used to store software programs and modules, and the processor 1280 performs various functional applications and data processing of the desktop computer by operating the software programs and modules stored in the memory 1220. The memory 1220 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the desktop computer, and the like. Further, the memory 1220 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The input unit 1230 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the desktop computer. Specifically, the input unit 1230 may include a touch panel 1231 and other input devices 1232. The touch panel 1231, also referred to as a touch screen, can collect touch operations of a user (e.g., operations of the user on or near the touch panel 1231 using any suitable object or accessory such as a finger, a stylus, etc.) thereon or nearby, and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 1231 may include two portions, a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, and sends the touch point coordinates to the processor 1280, and can receive and execute commands sent by the processor 1280. In addition, the touch panel 1231 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 1230 may include other input devices 1232 in addition to the touch panel 1231. In particular, other input devices 1232 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 1240 may be used to display information input by or provided to the user and various menus of the desktop computer. The Display unit 1240 may include a Display panel 1241, and optionally, the Display panel 1241 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, touch panel 1231 can overlay display panel 1241, and when touch panel 1231 detects a touch operation thereon or nearby, the touch panel 1231 can transmit the touch operation to processor 1280 to determine the type of the touch event, and then processor 1280 can provide a corresponding visual output on display panel 1241 according to the type of the touch event. Although in fig. 12, the touch panel 1231 and the display panel 1241 are implemented as two separate components to implement the input and output functions of the desktop computer, in some embodiments, the touch panel 1231 and the display panel 1241 may be integrated to implement the input and output functions of the desktop computer.
The desktop may also include at least one sensor 1250, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor, and the ambient light sensor may adjust the brightness of the display panel 1241 according to the brightness of ambient light. As for the desktop, other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor may be further configured, which are not described herein.
Audio circuitry 1260, speaker 1261, microphone 1262 may provide an audio interface between the user and the desktop. The audio circuit 1260 can transmit the received electrical signal converted from the audio data to the speaker 1261, and the audio signal is converted into a sound signal by the speaker 1261 and output; on the other hand, the microphone 1262 converts the collected sound signals into electrical signals, which are received by the audio circuit 1260 and converted into audio data, which are processed by the audio data output processor 1280, and then passed through the RF circuit 1210 to be transmitted to, for example, another desktop computer, or output to the memory 1220 for further processing.
WiFi belongs to short-range wireless transmission technology, and the desktop can help the user send and receive e-mail, browse web pages, access streaming media, etc. through the WiFi module 1270, which provides the user with wireless broadband internet access. Although fig. 12 shows the WiFi module 1270, it is understood that it does not belong to the essential constitution of the desktop, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The processor 1280 is a control center of the desktop computer, connects various parts of the entire desktop computer using various interfaces and lines, performs various functions of the desktop computer and processes data by running or executing software programs and/or modules stored in the memory 1220 and calling data stored in the memory 1220, thereby monitoring the entire desktop computer. Optionally, processor 1280 may include one or more processing units; preferably, the processor 1280 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It is to be appreciated that the modem processor described above may not be integrated into the processor 1280.
The desktop computer also includes a power supply 1290 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 1280 via a power management system configured to manage charging, discharging, and power consumption.
Although not shown, the desktop may further include a camera, a bluetooth module, etc., which will not be described herein.
In this embodiment, the processor 1280 included in the terminal device further has the following functions:
when the master control process of the hybrid application is started, rendering a native window and residing in a memory;
when the application interface is to be displayed in the process of running the process, acquiring a configuration file, wherein the configuration file is configured with a corresponding relation between each service function type and the application interface type;
determining an application interface type corresponding to the application interface to be displayed according to the service function type of the application interface to be displayed and the configuration file, wherein the application interface type is used for identifying the application interface as a native interface or a webpage interface;
when the application interface to be displayed is a native interface, loading the native window and rendering the application interface to be displayed on the native window;
and when the application interface to be displayed is a web page interface, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window.
Optionally, the processor 1280 is further configured to execute the steps of any implementation manner of the page display method for the hybrid application provided in the embodiment of the present application.
The embodiment of the present application further provides a computer-readable storage medium for storing a computer program, where the computer program is configured to execute any one implementation manner of the page display method for a hybrid application described in the foregoing embodiments.
The present application further provides a computer program product including instructions, which when run on a computer, causes the computer to execute any one implementation of the page display method for a hybrid application described in the foregoing embodiments.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more. "and/or" for describing an association relationship of associated objects, indicating that there may be three relationships, e.g., "a and/or B" may indicate: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (12)
1. A page display method for a hybrid application, the method comprising:
when the master control process of the hybrid application is started, rendering a native window and residing in a memory;
when the application interface is to be displayed in the process of running the process, acquiring a configuration file, wherein the configuration file is configured with a corresponding relation between each service function type and the application interface type;
determining an application interface type corresponding to the application interface to be displayed according to the service function type of the application interface to be displayed and the configuration file, wherein the application interface type is used for identifying the application interface as a native interface or a webpage interface;
when the application interface to be displayed is a native interface, loading the native window and rendering the application interface to be displayed on the native window;
and when the application interface to be displayed is a web page interface, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window.
2. The method according to claim 1, wherein when the application interface to be presented is a web page interface, loading the native window and rendering a loading interface in the native window, loading the application interface to be presented through a browser kernel, hiding the loading interface and embedding the application interface to be presented in the native window, comprises:
when the application interface to be displayed is the first web page interface to be displayed of the hybrid application, asynchronously loading a browser kernel and residing the browser kernel in a memory, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through the browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window;
when the application interface to be displayed is not the first web page interface to be displayed in the hybrid application, calling the browser kernel in the memory, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through the browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
in response to a closing operation triggered by a target application interface displayed for the hybrid application, hiding the native window when the target application interface is a native interface;
when the target application interface is a webpage interface, counting the number of webpage rendering processes in the system, hiding the target application interface and residing the rendering process corresponding to the webpage interface in an internal memory when the number of the webpage rendering processes is one, and unloading the target application interface and closing the rendering process corresponding to the target application interface when the number of the webpage rendering processes is more than one.
4. The method of claim 1, further comprising:
responding to the image archiving and communication system to call up the hybrid application, and starting a master control process of the hybrid application; or,
and responding to a starting operation triggered by the shortcut icon aiming at the hybrid application, and starting the master control process of the hybrid reference.
5. The method of claim 1, wherein obtaining the configuration file comprises:
acquiring a configuration file corresponding to the hybrid application from an application server; or,
acquiring a configuration file corresponding to the hybrid application from a local cache; the interface type corresponding to each service function type in the configuration file is determined according to a service function updating period corresponding to each service function type, wherein the interface type corresponding to the service function type with the service function updating period being greater than the preset period is a native interface, and the interface type corresponding to the service function type with the service function updating period not greater than the preset period is a web interface.
6. A hybrid application page display apparatus, the apparatus comprising:
the first control module is used for rendering a native window and residing the native window in the memory when the master control process of the hybrid application is started;
the acquisition module is used for acquiring a configuration file when an application interface needs to be displayed in the process of running the process, wherein the configuration file is configured with a corresponding relation between each service function type and each application interface type;
the interface type determining module is used for determining an application interface type corresponding to the application interface to be displayed according to the service function type of the application interface to be displayed and the configuration file, wherein the application interface type is used for identifying the application interface as a native interface or a webpage interface;
the first display module is used for loading the native window and rendering the application interface to be displayed on the native window when the application interface to be displayed is the native interface;
and the second display module is used for loading the native window, rendering a loading interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window when the application interface to be displayed is a web page interface.
7. The apparatus of claim 6, wherein the second display module is specifically configured to:
when the application interface to be displayed is the first web page interface to be displayed of the hybrid application, asynchronously loading a browser kernel and residing the browser kernel in a memory, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through the browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window; or,
when the application interface to be displayed is not the first web page interface to be displayed in the hybrid application, calling the browser kernel in the memory, loading the native window and rendering a loading interface on the native window, loading the application interface to be displayed through the browser kernel, hiding the loading interface and embedding the application interface to be displayed in the native window.
8. The apparatus of claim 6 or 7, further comprising:
the first closing operation response module is used for responding to a closing operation triggered by a target application interface displayed aiming at the hybrid application, and hiding the native window when the target application interface is a native interface;
and the second closing operation response module is used for counting the number of webpage rendering processes in the system when the target application interface is a webpage interface, hiding the target application interface and residing the rendering process corresponding to the webpage interface in the memory when the number of the webpage rendering processes is one, and unloading the target application interface and closing the rendering process corresponding to the target application interface when the number of the webpage rendering processes is more than one.
9. The apparatus of claim 6 or 7, further comprising:
the image archiving and communication system is used for responding to the image archiving and communication system and calling the hybrid application, and starting a master control process of the hybrid application; or,
and the starting module is used for responding to a starting operation triggered by the shortcut icon aiming at the mixed application and starting the master control process of the mixed reference.
10. The apparatus according to claim 6 or 7, wherein the obtaining module is specifically configured to:
a first slave application server acquires a configuration file corresponding to the hybrid application; or,
acquiring a configuration file corresponding to the hybrid application from a local cache; the interface type corresponding to each service function type in the configuration file is determined according to a service function updating period corresponding to each service function type, wherein the interface type corresponding to the service function type with the service function updating period being greater than the preset period is a native interface, and the interface type corresponding to the service function type with the service function updating period not greater than the preset period is a web interface.
11. A terminal device, characterized in that the terminal device comprises a display, a memory and a processor; wherein,
the display is used for displaying an application interface;
the memory for storing a computer program;
the processor for executing the computer program to perform the page display method of the hybrid application according to any one of claims 1 to 5.
12. A computer-readable storage medium for storing a computer program for executing the page display method of the hybrid application according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910755677.9A CN110457621B (en) | 2019-08-15 | 2019-08-15 | Page display method, device and medium for hybrid application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910755677.9A CN110457621B (en) | 2019-08-15 | 2019-08-15 | Page display method, device and medium for hybrid application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110457621A true CN110457621A (en) | 2019-11-15 |
| CN110457621B CN110457621B (en) | 2023-09-15 |
Family
ID=68486917
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910755677.9A Active CN110457621B (en) | 2019-08-15 | 2019-08-15 | Page display method, device and medium for hybrid application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110457621B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110837616A (en) * | 2019-09-27 | 2020-02-25 | 云深互联(北京)科技有限公司 | Method, system and storage medium for managing browser kernel |
| CN112153064A (en) * | 2020-09-28 | 2020-12-29 | 上海缓存命中科技有限公司 | Application store and method of use thereof |
| CN113568720A (en) * | 2020-04-29 | 2021-10-29 | 阿里巴巴集团控股有限公司 | Process management, development, configuration method, apparatus, electronic device and storage medium |
| CN113835789A (en) * | 2020-06-08 | 2021-12-24 | 阿里巴巴集团控股有限公司 | Rendering method, rendering device, electronic equipment and computer storage medium |
| CN113891135A (en) * | 2021-03-08 | 2022-01-04 | 北京字跳网络技术有限公司 | A multimedia data playback method, device, electronic device and storage medium |
| CN114116267A (en) * | 2021-09-10 | 2022-03-01 | 武汉武钢绿色城市技术发展有限公司 | Method for APP awakening and non-sensing login to H5 page directly |
| CN115905742A (en) * | 2021-08-27 | 2023-04-04 | 腾讯科技（深圳）有限公司 | A data display method, device, equipment and storage medium |
| WO2023169157A1 (en) * | 2022-03-08 | 2023-09-14 | 腾讯科技（深圳）有限公司 | Sub application running method and apparatus, electronic device, program product, and storage medium |
| CN119045921A (en) * | 2024-07-15 | 2024-11-29 | 广州三七极梦网络技术有限公司 | Webpage application program running method, device, equipment and storage medium |
| CN119149253A (en) * | 2024-11-19 | 2024-12-17 | 北京安宁创新网络科技股份有限公司 | Client application development platform and method based on multi-process framework |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105354013A (en) * | 2014-08-18 | 2016-02-24 | 阿里巴巴集团控股有限公司 | Application interface rendering method and apparatus |
| CN106293645A (en) * | 2015-05-13 | 2017-01-04 | Tcl集团股份有限公司 | A kind of method and system improving Web application interface rendering efficiency |
| CN107992301A (en) * | 2017-11-27 | 2018-05-04 | 腾讯科技（上海）有限公司 | User interface implementation method, client and storage medium |
| CN108427597A (en) * | 2018-03-16 | 2018-08-21 | 崔红保 | Accelerate the method and device of page rendering |
| CN109800374A (en) * | 2018-12-13 | 2019-05-24 | 平安普惠企业管理有限公司 | Temporary page data processing method, device, computer equipment and storage medium |
-
2019
- 2019-08-15 CN CN201910755677.9A patent/CN110457621B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105354013A (en) * | 2014-08-18 | 2016-02-24 | 阿里巴巴集团控股有限公司 | Application interface rendering method and apparatus |
| CN106293645A (en) * | 2015-05-13 | 2017-01-04 | Tcl集团股份有限公司 | A kind of method and system improving Web application interface rendering efficiency |
| CN107992301A (en) * | 2017-11-27 | 2018-05-04 | 腾讯科技（上海）有限公司 | User interface implementation method, client and storage medium |
| CN108427597A (en) * | 2018-03-16 | 2018-08-21 | 崔红保 | Accelerate the method and device of page rendering |
| CN109800374A (en) * | 2018-12-13 | 2019-05-24 | 平安普惠企业管理有限公司 | Temporary page data processing method, device, computer equipment and storage medium |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110837616A (en) * | 2019-09-27 | 2020-02-25 | 云深互联(北京)科技有限公司 | Method, system and storage medium for managing browser kernel |
| CN113568720B (en) * | 2020-04-29 | 2025-04-25 | 阿里巴巴集团控股有限公司 | Process management, development, configuration method, device, electronic device and storage medium |
| CN113568720A (en) * | 2020-04-29 | 2021-10-29 | 阿里巴巴集团控股有限公司 | Process management, development, configuration method, apparatus, electronic device and storage medium |
| CN113835789A (en) * | 2020-06-08 | 2021-12-24 | 阿里巴巴集团控股有限公司 | Rendering method, rendering device, electronic equipment and computer storage medium |
| CN112153064B (en) * | 2020-09-28 | 2022-11-22 | 上海缓存命中科技有限公司 | Application store and use method thereof |
| CN112153064A (en) * | 2020-09-28 | 2020-12-29 | 上海缓存命中科技有限公司 | Application store and method of use thereof |
| CN113891135A (en) * | 2021-03-08 | 2022-01-04 | 北京字跳网络技术有限公司 | A multimedia data playback method, device, electronic device and storage medium |
| CN113891135B (en) * | 2021-03-08 | 2023-10-27 | 北京字跳网络技术有限公司 | Multimedia data playing method and device, electronic equipment and storage medium |
| CN115905742A (en) * | 2021-08-27 | 2023-04-04 | 腾讯科技（深圳）有限公司 | A data display method, device, equipment and storage medium |
| CN114116267A (en) * | 2021-09-10 | 2022-03-01 | 武汉武钢绿色城市技术发展有限公司 | Method for APP awakening and non-sensing login to H5 page directly |
| CN114116267B (en) * | 2021-09-10 | 2025-04-22 | 武汉武钢绿色城市技术发展有限公司 | A method for waking up an APP and directly accessing an H5 page without any sense of login |
| WO2023169157A1 (en) * | 2022-03-08 | 2023-09-14 | 腾讯科技（深圳）有限公司 | Sub application running method and apparatus, electronic device, program product, and storage medium |
| CN119045921A (en) * | 2024-07-15 | 2024-11-29 | 广州三七极梦网络技术有限公司 | Webpage application program running method, device, equipment and storage medium |
| CN119149253A (en) * | 2024-11-19 | 2024-12-17 | 北京安宁创新网络科技股份有限公司 | Client application development platform and method based on multi-process framework |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110457621B (en) | 2023-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110457621B (en) | Page display method, device and medium for hybrid application | |
| CN111061574B (en) | Object sharing method and electronic device | |
| US11681432B2 (en) | Method and terminal for displaying input method virtual keyboard | |
| KR102182917B1 (en) | Graphic code display method and device | |
| US20230195298A1 (en) | Permission setting method and apparatus and electronic device | |
| US12340234B2 (en) | Application sharing method and electronic device | |
| US11455075B2 (en) | Display method when application is exited and terminal | |
| WO2018188289A1 (en) | Information display method, apparatus, and terminal | |
| CN115454286B (en) | Application data processing method and device and terminal equipment | |
| CN106547844B (en) | A kind for the treatment of method and apparatus of user interface | |
| US20190213241A1 (en) | Web page display method and apparatus, mobile terminal, and storage medium | |
| WO2017129031A1 (en) | Information acquisition method and device | |
| CN112257135A (en) | A method, device, storage medium and terminal for model loading based on multithreading | |
| CN107066268B (en) | Display position switching method and device for widget application | |
| WO2018077041A1 (en) | Method and apparatus for running application | |
| CN111026299A (en) | Information sharing method and electronic equipment | |
| JP2010287205A (en) | Electronic device, computer-implemented system, and application program display control method therefor | |
| CN111383175A (en) | Image acquisition method and electronic device | |
| KR20220154825A (en) | How to create notes and electronic devices | |
| CN113190143A (en) | Interface display method and device, electronic equipment and medium | |
| CN108763544A (en) | A display method and terminal | |
| CN114327087A (en) | Input event processing method and device, electronic equipment and storage medium | |
| CN113794795A (en) | Information sharing method, apparatus, electronic device and readable storage medium | |
| JP7319431B2 (en) | Application function implementation method and electronic device | |
| US20240289004A1 (en) | Method of controlling component, apparatus, electronic device, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |