CN110457621B - Page display method, device and medium for hybrid application - Google Patents
Page display method, device and medium for hybrid application Download PDFInfo
- Publication number
- CN110457621B CN110457621B CN201910755677.9A CN201910755677A CN110457621B CN 110457621 B CN110457621 B CN 110457621B CN 201910755677 A CN201910755677 A CN 201910755677A CN 110457621 B CN110457621 B CN 110457621B
- Authority
- CN
- China
- Prior art keywords
- interface
- application
- displayed
- application interface
- native
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 144
- 230000008569 process Effects 0.000 claims abstract description 91
- 238000009877 rendering Methods 0.000 claims abstract description 64
- 230000006870 function Effects 0.000 claims abstract description 63
- 230000004044 response Effects 0.000 claims abstract description 21
- 238000004590 computer program Methods 0.000 claims description 14
- 238000004891 communication Methods 0.000 claims description 13
- 230000001960 triggered effect Effects 0.000 claims description 7
- 230000000763 evoking effect Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 16
- 238000012545 processing Methods 0.000 description 7
- 238000011161 development Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 238000003745 diagnosis Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000005236 sound signal Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 201000010099 disease Diseases 0.000 description 1
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 description 1
- 238000012905 input function Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000007500 overflow downdraw method Methods 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000010897 surface acoustic wave method Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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; CALCULATING OR 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
The application discloses a page display method of a hybrid application, which comprises the following steps: when the main control process of the hybrid application is started, rendering a native window and residing the native window in a memory; acquiring a configuration file when an application interface is to be displayed in the process of running a process; determining the type of the application interface corresponding to the application interface to be displayed according to the service function type and the configuration file to which the application interface to be displayed belongs; when the application interface to be displayed is a native interface, loading a native window and rendering the application interface to be displayed in the native window; when the application interface to be displayed is a webpage interface, loading a native window, rendering the loaded interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loaded interface, and embedding the application interface to be displayed in the native window. The characteristics of Web application are reserved, more service types can be supported, and application compatibility and response performance are improved. The application also discloses a corresponding device, equipment and medium.
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 rapidly develop applications to market to reach the market, many application projects currently mainly use Web page programming language for application development, and the applications developed in this way are simply called Web applications.
The method for upgrading the application display content of the Web application only needs to update the Web page at the server side, so that users have no perception, the Web application has the advantage of being convenient to develop and update, meanwhile, the problems of low application interface loading speed, long waiting time of the users, poor experience and the like exist, more importantly, the type of the Web application supporting service is limited, the Web application cannot realize the service of pushing and resident background and the like aiming at some messages, and in addition, the black box characteristic of the Web application causes difficulty in good linkage communication with other systems.
Based on the above, it is urgently needed to provide a solution that can not only preserve the characteristics of Web applications but also support more service types, so that the application has higher compatibility and response performance, and thus, the requirements of high quality experience in many aspects of users are met.
Disclosure of Invention
The embodiment of the application provides a page display method of a hybrid application, which can keep the characteristics of Web application, can support more service types and improves application compatibility and response performance. The embodiment of the application also provides a corresponding device, equipment, a storage medium and a computer program product.
The first aspect of the application provides a page display method of a hybrid application, which comprises the following steps:
when the main control process of the hybrid application is started, rendering a native window and residing the native window in a memory;
when an application Interface (UI) is about to be displayed in the process of running the process, acquiring a configuration file, wherein the configuration file is configured with the 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 in the native window;
when the application interface to be displayed is a webpage interface, loading the native window, rendering the loaded interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loaded 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 device, the device comprising:
the first control module is used for rendering the native window and residing the native window in the memory when the main control process of the hybrid application is started;
the acquisition module is used for acquiring a configuration file when the application interface needs to be displayed in the process of running the process, wherein the configuration file is configured with the corresponding relation between each service function type and the application interface type;
the interface type determining module is used for determining the type of the application interface 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 in 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 the 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 webpage 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 method for displaying a page of a hybrid application according to the first aspect described above according to the computer program.
A fourth aspect of the present application provides a computer-readable storage medium storing a computer program for executing the page display method of the hybrid application described in the first aspect.
A fifth aspect of the application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of page display of a hybrid application as described in the first aspect above.
From the above technical solutions, the embodiment of the present application has the following advantages:
the embodiment of the application provides a page display method of a hybrid application, which is characterized in that a native UI is fused on the basis of a webpage UI, a UI layer is dynamically switched through a configuration file, a control layer uniformly processes response, hybrid programming of the two UIs is realized, the hybrid application is obtained, when a main control process of the hybrid application is started, a native window is rendered and is resident in a memory, the configuration file configured with a corresponding relation between a service function type and a UI type is acquired when the 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, the UI to be displayed is rendered in the native window, if the UI type is the webpage UI, the native window is loaded, the UI to be displayed is rendered in the native window, the browser kernel is used, then the loading interface is hidden, and the UI to be displayed is embedded in the native window. The method can effectively combine the flexibility of the webpage UI and the high-performance low-consumption characteristic of the original UI, and can simultaneously keep the high-performance of the main functions on the premise of rapidly supporting the dynamic UI, ensure the stable operation on the low-configuration machine and promote the user experience. In addition, decoupling of the UI layer and the control layer can enable application stability to be increased and application usability to be enhanced.
Drawings
Fig. 1 is a scene structure diagram of a page display method of a hybrid application in an embodiment of the present application;
FIG. 2 is a flowchart of a method for displaying a page of 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 chart of a hybrid application loading UI in an embodiment of the application;
FIG. 5 is a flow chart of a hybrid application closing UI in an embodiment of the application;
fig. 6A is an application scenario schematic diagram of a method for displaying a page of a hybrid application in an embodiment of the present application;
FIG. 6B is a schematic diagram showing the effect of the hybrid application displaying the login UI according to the embodiment of the application;
FIG. 6C is a schematic diagram illustrating an effect of the hybrid application display image viewing UI according to an embodiment of the application;
FIG. 7 is a schematic diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 9 is a schematic diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 10 is a schematic diagram of a hybrid application page display device according to an embodiment of the present application;
FIG. 11 is a schematic diagram of a structure of a display device for a hybrid application page according to an embodiment of the present application;
Fig. 12 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
In order to make the present application better understood by those skilled in the art, the following description will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented, for example, 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.
In order to facilitate understanding of the technical scheme of the application, the technical terms related to the technical scheme are first described.
An application is also called an application program and refers to a computer program that performs some specific task or tasks. When it is operating in user mode, it can interact with the user through a visual user interface UI. Applications may be classified into native (active) applications and web applications according to the type of UI used in the development process.
Native applications are applications developed using a platform-specific development language and using Native UIs provided by the platform. The web application specifically refers to an application developed by using a web UI and adopting a web page program Language such as a hypertext markup Language (HTML), a JavaScript (JavaScript), a cascading style (Cascading Style Sheet, CSS) and the like, the terminal device can access the application through a browser, and the application can support cross-platform.
The application provides a page display method for forming a mixed application by fusing a native UI on the basis of a web UI, which is different from a common client embedded with an active dynamic web page, aiming at the problems of low loading speed, limited service type support and difficult linkage communication with other systems of web applications developed for occupying the market.
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 or a notebook computer, or may be a portable mobile terminal such as a tablet computer or a mobile phone, or may be a vehicle-mounted terminal or an augmented Reality (Augmented Reality, AR)/Virtual Reality (VR) terminal, which is not limited in this embodiment.
The page display method of the hybrid application provided by the 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 program, or may be a functional module, a plug-in, or an applet integrated with other application programs.
In practical application, the method for displaying the page of the hybrid application provided by the application can be applied to an application environment as shown in fig. 1, but is not limited to the application environment.
As shown in fig. 1, a hybrid application is carried on a terminal 100, where the hybrid application includes a main control process, when the main control process is started, a native window is rendered and is resident in a memory, when an application interface is about to be displayed in the process of running the process, a configuration file is obtained, according to a 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 is determined, 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; when the application interface to be displayed is a webpage interface, loading the native window, rendering the loaded interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loaded interface, and embedding the application interface to be displayed in the native window.
In order to make the technical scheme of the application clearer and easier to understand, the page display method of the hybrid application provided by the embodiment of the application is 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:
and S201, when the main control process of the hybrid application is started, rendering a native window and residing the native window in the memory.
The hybrid application refers to an application that merges a web page UI and a native UI, and specifically to the present embodiment, the hybrid application may be an application that merges a native UI on the basis of a web page UI. It can be appreciated that the above fusion method can be used to develop hybrid applications in the fields of medical, educational, social, entertainment, etc.
Taking the medical field as an example, a hybrid image application can be formed by fusing a native UI on the basis of the original webpage UI of the image application, and a doctor can view patient image data by running the hybrid image application on a workstation of the doctor and perform disease diagnosis based on the image data.
The hybrid application includes a control layer and a UI layer. The control layer comprises a main control module which is mainly responsible for some preloaded business logic, such as background communication, 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 primary UI module is initialized in advance and occupies the main loop, the progress is ensured not to exit, and then UI control and rendering work are dynamically performed after the user behavior is responded in the main loop.
When the method is applied practically, a user can start a main control process by triggering a main control module of the hybrid application, so that control of the native UI and the webpage UI is realized. Specifically, the user may initiate the master control process in a plurality of ways, for example, using the hybrid application as an influencing application in the medical field, and the terminal may initiate the master control process of the hybrid application in response to the image archiving and communication system invoking operation for the hybrid application.
In some possible implementations, the terminal may display a shortcut icon of the hybrid application, and the user may trigger a start operation by clicking the shortcut icon or controlling the shortcut icon through a voice command, and the terminal starts an active process of the hybrid application in response to the start operation triggered by the shortcut icon for the hybrid application. Of course, the terminal may also provide a shortcut key of 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 the main loop, i.e. whether rendering of the UI occurs or not, 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, no matter what type of UI is used, the terminal may pre-render the native window when the main control process starts, and reside it in the memory, so that the native window can be directly invoked from the memory later.
S202, acquiring a configuration file when an application interface is about to be displayed in the process of running the process.
And the configuration file is configured with the corresponding relation between each service function type and the application interface type. The business function type is used for identifying a business function corresponding to the application interface, for example, in medical image application, the business function type can identify the UI as a login UI, an image viewing UI, a diagnosis conclusion generating UI or a help center UI, and the like. The application interface type is mainly used for identifying the application interface as a native interface or a web page interface (i.e., a native UI or a web page UI).
In consideration of that the web page UI is easier to update than the original UI, the interface types corresponding to the service function types can be configured according to the service function update period corresponding to the service function types. Specifically, the interface type corresponding to the service function type with the service function update period being greater than the preset period may be configured as a native interface, and the interface type corresponding to the service function type with the service function update period not greater than the preset period may be configured as a web page interface. As one example, the help center UI may be configured as a native UI and the shadow viewing UI may be configured as a web page UI.
In the process of running the main control process, if the UI is about to be displayed, the terminal can obtain the configuration file corresponding to the hybrid application from the application server in advance. Of course, in some cases, the terminal may first determine whether the configuration file corresponding to the hybrid application is stored in the cache, if so, the terminal may directly obtain the configuration file from the cache, so that the efficiency of obtaining the configuration file may be improved, and further the response efficiency may be improved, if not, the terminal may obtain the configuration file from the application server.
S203, determining the type of the application interface 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. When the application interface to be displayed is a native interface, executing S204; and when the application interface to be displayed is a web page interface, executing S205.
Specifically, the terminal matches the service function type of the UI to be displayed with the configuration file, and if the service function type is hit in the configuration file, the application interface type corresponding to the hit service function type in the configuration file is determined as the application interface type corresponding to the UI to be displayed.
Considering different characteristics of the native UI and the web page UI, the embodiment of the application provides different rendering policies for the native UI and the web page UI, respectively, wherein the rendering policies of the native UI may be referred to as S204, and the rendering policies of the web page UI may be referred to as S205.
S204, loading the native window and rendering the application interface to be displayed in 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 needs no repeated loading, so that loading logic of the native UI can be set to be loaded as required, and the native UI is resident in the memory after rendering is completed. Further, considering that the destruction cost after the window is created is high, when a user triggers a closing operation for the native UI, the terminal can respond to the closing operation to hide the native window without performing a releasing operation, when the native window is evoked, the native window is re-displayed, and when the application is exited, the native window is released. Practical tests prove that the resources occupied by the hidden native window are only tens of times of that of the UI of the webpage, and the method can realize quick response through less resources.
Aiming at a webpage UI, when loading the native window, the terminal renders a loading interface, namely a loading UI, in the native window, then loads the UI to be displayed through a browser kernel, and after the UI to be displayed is loaded, 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 configured to load on demand, with the loading process being somewhat complex relative to the original UI loading process. Since it is described that the kernel requires more than 500 milliseconds to block the main thread time and occupies a relatively high memory, the native kernel is not typically preloaded, but rather the kernel is loaded asynchronously when the first web page UI is rendered. Once loading is completed, the kernel resides in memory, avoiding the repeated consumption of resources to block the main process.
Based on the above, the terminal can also judge whether the UI to be displayed is the first web page UI to be displayed of the hybrid application before loading the UI, if yes, the browser kernel is loaded asynchronously and is resident in the memory, if no, the browser kernel in the memory is directly evoked, then the loading of the native window and the rendering of the loading UI on the native window are executed, the UI to be displayed is loaded through the browser kernel, and the loading UI is hidden and the application interface to be displayed is embedded in the native window. 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 directly called later, so that the loading time is saved, and the response efficiency is improved.
Further, when the user triggers the closing operation for the webpage UI, the terminal can respond to the closing operation, count the number of webpage rendering processes in the system, hide the webpage UI when the number of webpage rendering processes is one, and store the rendering process corresponding to the webpage UI in the memory, and unload the webpage UI and close the rendering process corresponding to the webpage UI when the number of webpage rendering processes is greater than one, so that the hybrid application can maintain the quick response performance.
As can be seen from the foregoing, the embodiment of the present application provides a method for displaying a page of a hybrid application, which merges a native UI on the basis of a web UI, dynamically switches a UI layer when running under configuration, uniformly processes a response by a control layer, and implements hybrid programming of two UIs, thereby obtaining the hybrid application. The method can effectively combine the flexibility of the webpage UI and the high-performance low-consumption characteristic of the original UI, and can simultaneously keep the high-performance of the main functions on the premise of rapidly supporting the dynamic UI, ensure the stable operation on the low-configuration machine and promote the user experience. In addition, decoupling of the UI layer and the control layer can enable application stability to be increased and application usability to be enhanced.
For ease of understanding, the following description is exemplary of a specific implementation of the page display method for a hybrid application in a browser.
Referring to the flow chart of the hybrid application shown in fig. 3, the hybrid application includes a main control module, a native UI module and a web page UI module, wherein the native UI module includes a native UI and corresponding controller and model, the web page UI module includes a web page UI and corresponding controller and model, and the main control module can perform UI control. Specifically, when the hybrid application runs, a native window is firstly rendered, the native window is resident in a memory, then when the UI to be displayed is a webpage UI, a child window is rendered in the native window to serve as a browser UI (namely the webpage UI), a browser rendering process is called, and a child window controller is handed to the rendering process for processing. After the internal rendering is completed, js in the rendering process can be communicated with the main process c++ through a native bridge, so that interaction at some native level 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 accompanying drawings.
Referring to the flow chart of UI loading in the hybrid application shown in fig. 4, when a user triggers a UI loading operation by clicking a control or the like, the terminal responds to the user operation to load the UI, firstly, the terminal can determine whether the UI to be displayed is a native UI based on the configuration file, if yes, the native UI is directly rendered, the user can execute the corresponding user operation through the native UI, if no, the native loading UI is loaded first, then whether the browser kernel is loaded is judged to be completed, if no, the browser kernel is loaded first, if yes, the webpage UI is directly rendered based on the browser kernel, after the webpage UI is rendered, the loadingUI is hidden, the webpage control is loaded into the window to complete the display of the webpage UI, and the unified control module responds to the user operation.
Referring to the flow chart of UI closing in the application shown in fig. 5, when the user operates to close the web page window, since the main loop of the web page kernel runs in a separate thread, the idle state of the kernel cannot be dynamically maintained, and more than one control must be maintained in operation, otherwise, the kernel thread exits the loop and needs to repeatedly call up consumed resources, so when the web page window is closed, the number of currently existing web page rendering processes can be checked first, if the number of web page rendering processes is equal to one, the window is hidden, and the window is resident in memory, if the number of 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 also provides a detailed description of the page display method of the mixed application in combination with related application scenes in the medical field.
Referring to fig. 6A, an application scenario of a method for displaying a page of a hybrid application is shown, where the application scenario includes a terminal 610, an application server 620 and an image scanner 630, where the terminal 610 may be a workstation, and an image archiving and communication system is installed on the workstation, and the system may call up the hybrid 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 diagnosis based on the image information by the terminal 610.
Specifically, the doctor starts the main control process of the hybrid application by clicking on the shortcut icon of the hybrid application displayed by the terminal 610, the terminal 610 renders the native window and residents it in the memory, and in the process of running the main control process, the login UI is first displayed, for this purpose, the terminal 610 first determines whether the local cache stores the configuration file corresponding to the hybrid application, if not, the configuration file is obtained from the application server 620, and determines the 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 login UI effect schematic shown in fig. 6B, the login UI is provided with a user name input control, a password input control, and a login control, and the doctor inputs the user name and the password through the user name input control and the password input control, and then performs the login operation by triggering the login control. In response to the above login operation, the terminal 610 transmits a login request message to the application server, where the login request message carries a user name and a password, and the application server 620 compares the user name and the password in the login request message with the user name and the password stored in the application server, and if they are consistent, the login is successful.
Upon successful login, the terminal 610 will next display a login success UI and a hybrid application home UI, which in this example is the web page UI, the terminal 610 determines the login success UI as the native UI based on the configuration file. The terminal 610 directly renders the login success UI at the rendering window and jumps to the hybrid application homepage UI after 3 seconds, renders the loadingUI at the native window first when the application homepage UI is displayed, then loads the hybrid application homepage UI through the browser kernel, hides the loadingUI after the loading is completed, and embeds the hybrid application homepage UI at the native window.
In the hybrid application home UI, a doctor may trigger an image viewing operation through a menu control, and in response to the viewing operation, the terminal 610 jumps to display an image viewing UI, which is a web page UI, so that a loadingUI is rendered in a native window at the terminal 610, the image viewing UI is loaded through a browser kernel, the loadingUI is hidden after the loading is completed, the image viewing UI is displayed, and specifically, see fig. 6C, at this time, the doctor may select a patient name or other conditions, and the terminal 610 may obtain image data corresponding to the patient name from the application server 620 by sending an image viewing request message to the application server 620, and display the image data.
When the user triggers the 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 the corresponding rendering process.
The above is a specific implementation manner of the method for displaying a page of a hybrid application provided by the embodiment of the present application, based on which the embodiment of the present application further provides a corresponding device, and the device is described in terms of functional modularization.
Referring to the schematic structural diagram of the hybrid application page display device shown in fig. 7, the device 700 includes:
the first control module 710 is configured to render the native window and reside the native window in the memory when the master control process of the hybrid application is started;
the obtaining module 720 is configured to obtain a configuration file when the application interface needs to be displayed in the process of running the process, where a corresponding relationship between each service function type and the application interface type is configured in the configuration file;
the interface type determining module 730 is configured to determine an application interface type corresponding to an application interface to be displayed according to a service function type to which the application interface to be displayed belongs and the configuration file, where the application interface type is used to identify that the application interface is a native interface or a web page interface;
The first display module 740 is configured to load the native window and render the application interface to be displayed in the native window when the application interface to be displayed is a native interface;
and the second display module 750 is configured to load the native window and render a load interface in the native window and load the application interface to be displayed through a browser kernel when the application interface to be displayed is a web page interface, hide the load 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 on the basis of the structure shown in fig. 7, the second display module 750 includes:
the first display sub-module 751 is configured to asynchronously load a browser kernel and reside the browser kernel in a memory when the application interface to be displayed is a first web page interface to be displayed of the hybrid application, load the native window and render a load interface on the native window, load the application interface to be displayed through the browser kernel, hide the load interface and embed the application interface to be displayed in the native window;
The second display sub-module 752 is configured to call the browser kernel in the memory, load the native window and render the loaded interface in the native window when the application interface to be displayed is not the first web page interface to be displayed of the hybrid application, load the application interface to be displayed through the browser kernel, hide the loaded 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 device according to an embodiment of the present application, and on the basis of the structure shown in fig. 7, the device 700 further includes:
the first closing operation response module 761 is configured to respond to a closing operation triggered by a target application interface displayed for the hybrid application, and when the target application interface is a native interface, hide the native window;
and the second closing operation response module 762 is configured to, when the target application interface is a web page interface, count the number of intra-system web page rendering processes, when the number of web page rendering processes is one, hide the target application interface and store the rendering process corresponding to the web page interface in a memory, and when the number of web page rendering processes is greater than one, uninstall the target application interface and close the rendering process corresponding to the target application interface.
Optionally, referring to fig. 10, fig. 10 is a schematic structural diagram of a hybrid application page display device according to an embodiment of the present application, and on the basis of the structure shown in fig. 7, the device 700 further includes:
a calling module 771 for starting a master control process of the hybrid application in response to a calling operation of the image archiving and communication system for the hybrid application; or alternatively, the first and second heat exchangers may be,
a starting module 772, configured to start the master process of the hybrid reference in response to a starting operation triggered by the shortcut icon for the hybrid application.
Of course, the device 700 may also include the aforementioned evoked module 771 and the activation module 772 in addition to the configuration shown in fig. 8.
Optionally, referring to fig. 11, fig. 11 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 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;
a first obtaining sub-module 722, configured to obtain, from a local cache, a configuration file corresponding to the hybrid application; the interface types corresponding to the service function types in the configuration file are determined according to the service function update periods corresponding to the service function types, wherein the interface types corresponding to the service function types with the service function update periods larger than the preset periods are primary interfaces, and the interface types corresponding to the service function types with the service function update periods not larger than the preset periods are web interfaces.
Of course, the acquiring module 720 in the apparatus 700 may also include the first acquiring sub-module 721 and the first acquiring sub-module 722 based on the structure shown in fig. 8.
The embodiment of the present application further provides a terminal, as shown in fig. 12, for convenience of explanation, only the relevant parts of the embodiment of the present application are shown, and specific technical details are not disclosed, please refer to the method part of the embodiment of the present application. The terminal can be any terminal equipment including a desktop, a notebook, a tablet computer and the like, taking the desktop as an example:
fig. 12 is a block diagram showing a partial structure of a desktop related to a terminal device provided by an embodiment of the present application. Referring to fig. 12, the desktop includes: radio Frequency (r.f. Frequency) circuit 1210, memory 1220, input unit 1230, display unit 1240, sensor 1250, audio circuit 1260, wireless fidelity (r.f. wireless fidelity, wiFi) module 1270, processor 1280, and power supply 1290. Those skilled in the art will appreciate that the desktop structure shown in fig. 12 is not limiting of a desktop and may include more or fewer components than shown, or may combine certain components, or may be arranged in a different arrangement of components.
The following describes the components of the desktop in detail with reference to fig. 12:
the RF circuit 1210 may be used for receiving and transmitting signals during a message or a call, and in particular, after receiving downlink information of a base station, the signal is processed by the processor 1280; in addition, the data of the design uplink is sent to the base station. Generally, RF circuitry 1210 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (English full name: low Noise Amplifier, english abbreviation: LNA), a duplexer, and the like. In addition, RF circuitry 1210 may also communicate with networks and other devices through wireless communication.
Memory 1220 may be used to store software programs and modules that may be executed by processor 1280 to perform various functional applications and data processing for the desktop by executing the software programs and modules stored in memory 1220. The memory 1220 may mainly include a storage program area that may store an operating system, application programs required for at least one function (such as a sound playing function, an image playing function, etc.), and a storage data area; the storage data area may store data created according to the use of the desktop (such as audio data, phonebook, etc.), and the like. In addition, 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 controls of the desktop. In particular, 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, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 1231 or thereabout using any suitable object or accessory such as a finger, a stylus, etc.), and drive the corresponding connection device according to a predetermined program. Alternatively, the touch panel 1231 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth 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 detection device and converts it into touch point coordinates, which are then sent to the processor 1280, and can receive commands from the processor 1280 and execute them. In addition, the touch panel 1231 may be implemented in various types such as resistive, capacitive, infrared, and 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 (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.
The display unit 1240 may be used to display information input by a user or information provided to the user and various menus of a desktop. The display unit 1240 may include a display panel 1241, and alternatively, the display panel 1241 may be configured in the form of a liquid crystal display (english full name: liquid Crystal Display, acronym: LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch panel 1231 may overlay the display panel 1241, and when the touch panel 1231 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 1280 to determine the type of touch event, and then the processor 1280 provides a corresponding visual output on the display panel 1241 according to the type of touch event. Although in fig. 12, the touch panel 1231 and the display panel 1241 are two separate components to implement the input and input functions of the desktop, in some embodiments, the touch panel 1231 may be integrated with the display panel 1241 to implement the input and output functions of the desktop.
The desktop may also include at least one sensor 1250, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor, which may adjust the brightness of the display panel 1241 according to the brightness of ambient light. Other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured with the desktop are not described in detail herein.
Audio circuitry 1260, speakers 1261, and microphone 1262 may provide an audio interface between the user and the desktop. Audio circuit 1260 may transmit the received electrical signal after audio data conversion to speaker 1261, where the electrical signal is converted to a sound signal by speaker 1261 for output; on the other hand, microphone 1262 converts the collected sound signals into electrical signals, which are received by audio circuit 1260 and converted into audio data, which are processed by audio data output processor 1280 for transmission to, for example, another desktop computer via RF circuit 1210, or which are output to memory 1220 for further processing.
WiFi belongs to a short-distance wireless transmission technology, and a desktop can help a user to send and receive e-mails, browse web pages, access streaming media and the like through a WiFi module 1270, so that wireless broadband Internet access is provided for the user. Although fig. 12 shows a WiFi module 1270, it is understood that it does not belong to the essential constitution of a desktop, and can be omitted entirely as required within a range that does not change the essence of the invention.
Processor 1280 is a control center of the desktop, connects various parts of the entire desktop using various interfaces and lines, and performs various functions and processes data of the desktop by running or executing software programs and/or modules stored in memory 1220, and calling data stored in memory 1220, thereby performing overall monitoring of the desktop. In the alternative, processor 1280 may include one or more processing units; preferably, the processor 1280 may integrate an application processor and a modem processor, wherein the application processor primarily handles operating systems, user interfaces, application programs, etc., and the modem processor primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1280.
The desktop also includes a power supply 1290 (e.g., a battery) that provides power to the various components, preferably in logical communication with the processor 1280 via a power management system, to manage charging, discharging, and power consumption via the power management system.
Although not shown, the desktop may further include a camera, a bluetooth module, etc., which will not be described herein.
In the embodiment of the present application, the processor 1280 included in the terminal device further has the following functions:
when the main control process of the hybrid application is started, rendering a native window and residing the native window in a memory;
when an application interface is about to be displayed in the process of running the process, acquiring a configuration file, wherein the configuration file is configured with the 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 in the native window;
When the application interface to be displayed is a webpage interface, loading the native window, rendering the loaded interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loaded interface, and embedding the application interface to be displayed in the native window.
Optionally, the processor 1280 is further configured to execute steps of any implementation manner of the method for displaying a page of the hybrid application provided by the embodiment of the present application.
The embodiments of the present application also provide a computer readable storage medium storing a computer program for executing any one of the embodiments of the method for displaying a page of a hybrid application.
The embodiments of the present application also provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform any one of the implementations of a method of displaying pages of a hybrid application as described in the foregoing embodiments.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: u disk, mobile hard disk, read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.
It should be understood that in the present application, "at least one (item)" means one or more, and "a plurality" means two or more. "and/or" for describing the association relationship of the association object, the representation may have three relationships, for example, "a and/or B" may represent: only a, only B and both a and B are present, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). 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 for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (12)
1. A method for displaying a page of a hybrid application, the method comprising:
when the main control process of the hybrid application is started, rendering a native window and residing the native window in a memory;
when an application interface is about to be displayed in the process of running the process, acquiring a configuration file, wherein the configuration file is configured with the 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 in the native window;
when the application interface to be displayed is a webpage interface, loading the native window, rendering the loaded interface on the native window, loading the application interface to be displayed through a browser kernel, hiding the loaded 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 displayed is a web page interface, loading the native window and rendering the loaded interface in the native window, loading the application interface to be displayed through a browser kernel, hiding the loaded interface and embedding the application interface to be displayed in the native window, comprises:
when the application interface to be displayed is the first webpage 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 the loaded interface on the native window, loading the application interface to be displayed through the browser kernel, hiding the loaded interface and embedding the application interface to be displayed in the native window;
When the application interface to be displayed is not the first webpage interface to be displayed of the hybrid application, the browser kernel in the memory is evoked, the native window is loaded, the loading interface is rendered on the native window, the application interface to be displayed is loaded through the browser kernel, the loading interface is hidden, and the application interface to be displayed is embedded in the native window.
3. The method according to claim 1 or 2, characterized in that the method further comprises:
responding to a closing operation triggered by a target application interface displayed for the hybrid application, and 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 a system, hiding the target application interface and resident memory of the rendering process corresponding to the webpage interface when the number of 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 webpage rendering processes is greater than one.
4. The method according to claim 1, wherein the method further comprises:
In response to a call-up operation of the image archiving and communication system for the hybrid application, starting a master control process of the hybrid application; or alternatively, the first and second heat exchangers may be,
and starting the master control process of the mixed reference in response to a starting operation triggered by the shortcut icon for the mixed application.
5. The method of claim 1, wherein the 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 types corresponding to the service function types in the configuration file are determined according to the service function update periods corresponding to the service function types, wherein the interface types corresponding to the service function types with the service function update periods larger than the preset periods are primary interfaces, and the interface types corresponding to the service function types with the service function update periods not larger than the preset periods are web interfaces.
6. A hybrid application page display device, the device comprising:
the first control module is used for rendering the native window and residing the native window in the memory when the main control process of the hybrid application is started;
The acquisition module is used for acquiring a configuration file when the application interface needs to be displayed in the process of running the process, wherein the configuration file is configured with the corresponding relation between each service function type and the application interface type;
the interface type determining module is used for determining the type of the application interface 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 in 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 the 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 webpage interface.
7. The device according to claim 6, wherein the second display module is specifically configured to:
When the application interface to be displayed is the first webpage 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 the loaded interface on the native window, loading the application interface to be displayed through the browser kernel, hiding the loaded 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 webpage interface to be displayed of the hybrid application, the browser kernel in the memory is evoked, the native window is loaded, the loading interface is rendered on the native window, the application interface to be displayed is loaded through the browser kernel, the loading interface is hidden, and the application interface to be displayed is embedded in the native window.
8. The apparatus according to claim 6 or 7, characterized in that the apparatus further comprises:
the first closing operation response module is used for responding to a closing operation triggered by a target application interface displayed for 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 page rendering processes in the system when the target application interface is a web page interface, hiding the target application interface and resident memory of the rendering process corresponding to the web page interface when the number of page 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 page rendering processes is greater than one.
9. The apparatus according to claim 6 or 7, characterized in that the apparatus further comprises:
the calling module is used for responding to the calling operation of the image archiving and communication system for the hybrid application and starting the main control process of the hybrid application; or alternatively, the first and second heat exchangers may be,
and the starting module is used for responding to the starting operation triggered by the shortcut icon aiming at the hybrid application and starting the master control process of the hybrid reference.
10. The apparatus according to claim 6 or 7, wherein the acquisition module is specifically configured to:
the method comprises the steps that a first slave application server obtains a configuration file corresponding to the mixed application; or,
acquiring a configuration file corresponding to the hybrid application from a local cache; the interface types corresponding to the service function types in the configuration file are determined according to the service function update periods corresponding to the service function types, wherein the interface types corresponding to the service function types with the service function update periods larger than the preset periods are primary interfaces, and the interface types corresponding to the service function types with the service function update periods not larger than the preset periods are web interfaces.
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 is used for storing a computer program;
the processor for running the computer program to perform the method of page display of a hybrid application of any of claims 1 to 5.
12. A computer-readable storage medium storing a computer program for executing the page display method of the hybrid application of 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 CN110457621A (en) | 2019-11-15 |
| CN110457621B true 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) |
Families Citing this family (6)
| 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 |
| CN113568720A (en) * | 2020-04-29 | 2021-10-29 | 阿里巴巴集团控股有限公司 | Process management, development and configuration method, device, electronic equipment 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 |
| CN113891135B (en) * | 2021-03-08 | 2023-10-27 | 北京字跳网络技术有限公司 | Multimedia data playing method and device, electronic equipment and storage medium |
| CN116775164A (en) * | 2022-03-08 | 2023-09-19 | 腾讯科技（深圳）有限公司 | Sub-application program running method and device, electronic equipment and readable storage medium |
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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110457621A (en) | 2019-11-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110457621B (en) | Page display method, device and medium for hybrid application | |
| KR102182917B1 (en) | Graphic code display method and device | |
| WO2018188289A1 (en) | Information display method, apparatus, and terminal | |
| KR102481065B1 (en) | Application function implementation method and electronic device | |
| US20220300302A1 (en) | Application sharing method and electronic device | |
| US10474507B2 (en) | Terminal application process management method and apparatus | |
| WO2015172704A1 (en) | To-be-shared interface processing method, and terminal | |
| CN106547844B (en) | A kind for the treatment of method and apparatus of user interface | |
| CN107066268B (en) | Display position switching method and device for widget application | |
| WO2018077041A1 (en) | Method and apparatus for running application | |
| CN104915091B (en) | A kind of method and apparatus for the prompt information that Shows Status Bar | |
| CN106254910B (en) | Method and device for recording image | |
| US20140379824A1 (en) | Apparatuses and methods for web page sharing | |
| CN110020293B (en) | Multimedia data display method, device and storage medium | |
| CN108681427B (en) | Access right control method and terminal equipment | |
| CN115454286A (en) | Application data processing method and device and terminal equipment | |
| CN105955739A (en) | Graphical interface processing method, apparatus and system | |
| CN111383175A (en) | Picture acquisition method and electronic equipment | |
| US20240289004A1 (en) | Method of controlling component, apparatus, electronic device, and storage medium | |
| CN106095423B (en) | Method, terminal and server for providing browsing service | |
| CN111399715A (en) | Interface display method and electronic equipment | |
| CN108780400A (en) | Data processing method and electronic equipment | |
| CN106484480A (en) | A kind of determination method of application of attending to anything else, device and terminal | |
| KR101876394B1 (en) | Method and device for playing media data on a terminal | |
| CN111694497B (en) | Page combination method and electronic equipment |
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 |