CN114741147A - Method for displaying page on mobile terminal and mobile terminal - Google Patents

Method for displaying page on mobile terminal and mobile terminal Download PDF

Info

Publication number
CN114741147A
CN114741147A CN202210330611.7A CN202210330611A CN114741147A CN 114741147 A CN114741147 A CN 114741147A CN 202210330611 A CN202210330611 A CN 202210330611A CN 114741147 A CN114741147 A CN 114741147A
Authority
CN
China
Prior art keywords
components
data
component
sequence
matching
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
Application number
CN202210330611.7A
Other languages
Chinese (zh)
Other versions
CN114741147B (en
Inventor
闫宇威
纪润
张泽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202210330611.7A priority Critical patent/CN114741147B/en
Publication of CN114741147A publication Critical patent/CN114741147A/en
Application granted granted Critical
Publication of CN114741147B publication Critical patent/CN114741147B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/957Browsing optimisation, e.g. caching or content distillation
    • G06F16/9574Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Human Computer Interaction (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

A method for displaying a page at a mobile terminal, a mobile terminal for displaying a page, an electronic device, and a non-transitory computer-readable storage medium are provided. The method comprises the following steps: acquiring a component set of a page to be displayed on a mobile terminal; arranging the component sets into a first component sequence according to the characteristics of the page to be displayed; splitting the first component sequence, and respectively acquiring and matching data of the split components; merging the plurality of components that have acquired and matched data into a second sequence of components, the components in the second sequence of components having the same order as the first sequence of components; and loading the plurality of components in the order of the second sequence of components.

Description

Method for displaying page on mobile terminal and mobile terminal
Technical Field
The present application relates to the field of computer technology, and in particular, to a method for displaying a page on a mobile terminal, a mobile terminal for displaying a page, an electronic device, and a non-transitory computer-readable storage medium.
Background
At present, along with the popularization of mobile communication and mobile internet, various Applications (APP) that can use on mobile terminal have involved the aspect of people's production and life, and most people all will browse various pages of different APPs and carry out the interaction on mobile terminal every day, and then the rendering and the loading effect of its APP page at the mobile terminal can influence people's daily use greatly and experience.
With the development of the technology, the dynamic scheme is widely used at the mobile terminal, and the high-frequency updated page and the high-frequency updated assembly on the mobile terminal product can be realized in a dynamic building mode. The dynamic establishment is a cross-platform technology which can realize dynamic page update without modifying codes in the field of mobile terminals, and has absolute advantages in the aspects of low code development, online repair, application performance and usability. Under the trend of DevOps, the dynamic scheme can bring the advantages of low code, high availability, cross-platform, high repair and the like, and help developers develop agilely.
However, under the dynamic scheme, the problems of time consumption of component data network requests of each page, dynamic increase and decrease of components and the like can cause page rendering flicker, thereby affecting the use experience of the end user.
Disclosure of Invention
To solve the above-mentioned problems occurring in the prior art, the present application provides a method for displaying a page at a mobile terminal, a mobile terminal for displaying a page, an electronic device, and a non-transitory computer-readable storage medium.
According to an aspect of the present application, there is provided a method for displaying a page in a mobile terminal, including:
acquiring a component set of a page to be displayed on a mobile terminal;
arranging the component sets into a first component sequence according to the characteristics of the page to be displayed;
splitting the first component sequence, and respectively acquiring and matching data of the split components;
merging the plurality of components that have acquired and matched data into a second sequence of components, the components in the second sequence of components having the same order as the first sequence of components; and
loading the plurality of components in the order of the second sequence of components.
According to one embodiment, the plurality of components include a cache-supporting component and a cache-not-supporting component, and the respectively performing data acquisition and matching on the split plurality of components includes:
acquiring data and performing data matching through a network aiming at the components which do not support caching; and
and for the components supporting the cache, completing data acquisition and matching according to the loaded times of the components.
According to one embodiment, for a component that does not support caching, obtaining data through a network and performing data matching comprises:
sending a network request; and
and receiving the data of the components from the server side and performing data matching.
According to one embodiment, for a component supporting cache, completing data acquisition and matching according to the number of times the component has been loaded comprises:
judging whether the component is loaded for the first time;
if the loading is the first time, sending a network request; and
and receiving the data of the components from the server side, performing data matching, and storing the received data to a cache device.
According to one embodiment, for a component supporting caching, completing the data acquisition and matching according to the number of times the component has been loaded further comprises:
and if the data is not loaded for the first time, acquiring the data from the cache device and performing data matching.
According to one embodiment, the first component sequence is split using a load queue, and the plurality of components that have acquired and matched data are merged into a second component sequence using the load queue.
According to one embodiment, loading the plurality of components in the order of the second sequence of components comprises:
and performing combined loading rendering on the components of the page to be displayed by utilizing a rendering tool.
According to one embodiment, the data acquisition and matching of the split components respectively comprises:
creating a plurality of dispatchers, the plurality of dispatchers corresponding respectively to the plurality of components; and
and respectively acquiring and matching data of the components by utilizing the dispatchers.
According to one embodiment, the plurality of components that have acquired and matched data are merged into the second sequence of components using a caching device.
According to another aspect of the present application, there is provided a mobile terminal for displaying a page, including:
the mobile terminal comprises an acquisition unit, a display unit and a display unit, wherein the acquisition unit is used for acquiring a component set of a page to be displayed on the mobile terminal;
the component flow creating unit is used for arranging the component sets into a first component sequence according to the characteristics of the page to be displayed;
the processing unit is used for splitting the first component sequence and respectively acquiring and matching data of the split components;
a merging unit that merges the plurality of components, for which data has been acquired and matched, into a second component sequence, components in the second component sequence having the same order as the first component sequence; and
and the loading unit loads the plurality of components according to the sequence of the second component sequence.
According to another aspect of the present application, there is provided an electronic device including:
a processor; and
a memory storing a computer program which, when executed by the processor, causes the processor to perform the method as described above.
According to another aspect of the present application, there is provided a non-transitory computer readable storage medium having stored thereon computer readable instructions which, when executed by a processor, cause the processor to perform the method as described above.
Therefore, by utilizing the functions of the loading queue and the rendering tool, the page rendering sequence can be ensured to a certain extent through the split processing and the combined loading of the component loading sequence of the page to be displayed, so that the rendering experience of dynamically building the page is optimized on the whole, and the page rendering flicker is avoided.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 shows a flow diagram of a method for displaying a page at a mobile terminal according to one embodiment of the application.
Fig. 2 shows a schematic diagram of a page container and an attachment container for implementing the above-described dynamic building framework.
Fig. 3 schematically shows the process of attaching the container while handling the components.
Fig. 4 shows a flowchart of data acquisition and matching of the split components respectively according to an embodiment of the present application.
Fig. 5 shows a flowchart of data acquisition and matching of the split components, respectively, according to an embodiment of the present application.
FIG. 6 illustrates a flow diagram for data acquisition and data matching over a network for a component that does not support caching according to one embodiment of the present application.
FIG. 7 illustrates a flow diagram for a cache-enabled component to complete data acquisition and matching based on the number of times the component has been loaded, according to an embodiment of the present application.
FIG. 8 is a flow diagram illustrating data retrieval and matching performed by a component supporting caching according to the number of times the component has been loaded according to another embodiment of the present application.
FIG. 9 shows a schematic design of an attachment vessel according to one embodiment of the present application.
FIG. 10 shows a schematic diagram of a mobile terminal for displaying a page according to one embodiment of the present application.
Detailed Description
For better understanding of the technical solutions and advantages of the present application, the following detailed description is made with reference to the accompanying drawings and specific embodiments. The specific embodiments described herein are merely illustrative of the present application and are not intended to be limiting of the present application. In addition, technical features related to each embodiment of the present application described below may be combined and used in other cases than when they conflict with each other, thereby constituting other embodiments within the scope of the present application.
The following description provides many different embodiments or examples for implementing different structures of the application. In order to simplify the disclosure of the present application, specific example components and arrangements are described below. Of course, they are merely examples and are not intended to limit the present application. Moreover, the present application may repeat reference numerals and/or letters in the various examples, such repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.
Except for the steps with definite sequence, the execution sequence of the other steps in the method described below can be changed to form a new technical scheme, and the method also belongs to the protection scope of the application. That is, the sequence shown in the drawings and the sequence described in the specification do not mean that the specific sequence of execution between the steps is fixed, but only schematic.
FIG. 1 shows a flow diagram of a method for displaying a page at a mobile terminal according to one embodiment of the present application. As shown in fig. 1, the method 100 may include steps S110 to S150.
In step S110, a component set of a page to be displayed on the mobile terminal is acquired. Under the dynamic building framework, built pages comprise two parts, namely protocols and data, wherein all parts of components formed by the pages are displayed in the protocols, data sources of all the components are stored in the data, the two parts are issued by a server, and a client (namely a mobile terminal) is responsible for analysis, rendering, data binding and view display. When a user opens a certain APP on the mobile terminal device for interactive operation, the mobile terminal device needs to display a page according to an instruction of the user. In this process, the mobile terminal first needs to acquire the components of the page.
Fig. 2 shows a schematic diagram of a page container and an attachment container for implementing the above-described dynamic building framework. As shown in fig. 2, in the present application, an attachment container is independently designed outside a page container to assist in completing loading and rendering of components, and the attachment container is based on two functions of a load queue and a rendering tool, and can ensure sequential loading, page reservation, temporary caching, and also perform data merging, partial refresh, and combined loading. The description of the operations will be made below in conjunction with fig. 2, but it is understood that the present application is not limited thereto. In step S110, after the page container gets the page protocol, a component set is input to the attachment container.
In step S120, the component sets are arranged into a first component sequence according to the characteristics of the page to be displayed. Referring again to fig. 2, the attachment container may sort the components via a load queue to form a component load stream, which, as described above, may ensure sequential loading of the components.
Fig. 3 schematically shows the process of attaching the container while handling the components. As shown in fig. 3, after the component assembly is received by the attachment container, the component assembly is arranged into a component sequence according to the characteristics of the page to be displayed, that is, the component loading stream. Three components are only schematically shown in fig. 3: component 3/component 2/component 1, but it is understood that the application is not so limited.
In step S130, the first component sequence is split, and data acquisition and matching are performed on the split components respectively. Referring to fig. 2 and 3, the attachment container may split the sequence of components formed in step S120 through a load queue, for example, into component 1, component 2, and component 3 as shown in fig. 3. Subsequently, the data of each component can be acquired and data matching can be performed, respectively, in a manner that will be described in detail below.
In step S140, the plurality of components that have acquired and matched the data are merged into a second sequence of components. As shown in fig. 2 and fig. 3, the attachment container may re-merge the components into a queue structure through the load queue, and ensure that the components in the re-merged component sequence have the same order as the component sequence before splitting (in step S120), i.e., the order of data 3 component 3, data 2 component 2, data 1 component 1 is still shown in fig. 3. According to one embodiment, as shown in FIG. 2, a plurality of components that have acquired and matched data may be merged into a second sequence of components using a caching device to form a sequentially loaded stream.
In step S150, a plurality of components are loaded in the order of the second component sequence. As shown in FIG. 2, the attached container may utilize a rendering tool to perform a combined load rendering of the components of the page to be displayed in the order of the second sequence of components. For example, when a page is refreshed, Modify of data is directly performed for a non-list component, add of newly added data, Reset of modified data, Delete of deleted data is directly performed for a list component.
Therefore, by utilizing the functions of the loading queue and the rendering tool, the page rendering sequence can be ensured to a certain extent through the split processing and the combined loading of the component loading sequence of the page to be displayed, so that the rendering experience of dynamically building the page is optimized on the whole, and the page rendering flicker is avoided. In addition, the attached container is used as a tool container of the break-away service, and the rendering optimization of the page container can be realized in a cross-platform mode, so that an available technical scheme of the break-away service is realized.
Fig. 4 shows a flowchart of data acquisition and matching of the split components, respectively, according to an embodiment of the present application. As shown in fig. 4, the above step S130 may include sub-steps S131 and S132.
In sub-step S131, a plurality of dispatchers is created. The number of dispatchers created may be the same as the number of components in the page to be displayed, so that each dispatcher may correspond to a component.
In sub-step S132, a plurality of dispatchers are utilized to respectively perform data acquisition and matching on the plurality of components. According to one embodiment, multiple dispatchers can be created in sequence under the KMM cross-platform framework, utilizing the characteristics of the Kotlin (a static programming language used for modern multi-platform applications) coroutine, as shown in FIGS. 2 and 3, and can perform data acquisition and matching of each component respectively.
Fig. 5 shows a flowchart of data acquisition and matching of the split components, respectively, according to an embodiment of the present application. As shown in fig. 5, the above step S130 may include sub-steps S135 and S136. It will be appreciated by those skilled in the art that the embodiments shown in fig. 4 and 5 are refinements of the above step S130 from different dimensions.
Furthermore, those skilled in the art will also appreciate that the requirements for the page presentation may differ in different scenarios. For example, for a built page displayed by a common function or information board, the real-time requirement is not very strong, but the experience is smooth, so that each component of the page often supports caching; for a page displayed by real-time information related to a specific category, the real-time requirement is strong, so that each component usually does not support caching.
In sub-step S135, for the component that does not support caching, data is acquired through the network and matching of the data is performed. For example, when a dispatcher is used to perform data acquisition and matching on components, the dispatcher can distinguish different components from each other, i.e., different components can be handled in different ways. And when the dispatcher faces the component which does not support the cache, calling the communication function of the mobile terminal to carry out network request, thereby obtaining data through the network and carrying out data matching.
In sub-step S136, for the component supporting the cache, the data acquisition and matching are completed according to the number of times the component has been loaded. For example, when a dispatcher is utilized to perform data acquisition and matching on a component, when the dispatcher faces a component supporting cache, the data acquisition and matching can be completed according to the loaded times of the component, and the specific operation will be described in detail below.
Thus, the dispatcher can distinguish different components and process in different ways.
FIG. 6 illustrates a flow diagram for data acquisition and data matching over a network for a component that does not support caching according to one embodiment of the present application. As shown in fig. 6, the above sub-step S135 may include sub-steps S135A and S135B.
In sub-step S135A, a network request is sent. After receiving the network request, the server side can send data corresponding to the component to the mobile terminal through equipment such as the mobile base station.
In sub-step S135B, the data of the component is received from the server side and the matching of the data is performed. Therefore, data acquisition and matching of the components which do not support caching can be completed.
FIG. 7 illustrates a flow diagram for a cache-enabled component to complete data acquisition and matching based on the number of times the component has been loaded, according to an embodiment of the present application. As shown in fig. 7, the sub-step S136 may include sub-steps S136A to S136C.
In sub-step S136A, it is determined whether the component is first loaded. In practice, the system records the number of times each component has been loaded, so that it can be determined whether a particular component is loaded for the first time.
In sub-step S136B, if it is the first load, a network request is sent. When a certain component is loaded for the first time, since data is not cached, the data acquisition needs to be completed through network loading.
In sub-step S136C, the data of the component is received from the server side and data matching is performed, and the received data is stored in the cache device. This step is similar to the sub-step S135B, and receives data from the server and matches the data, and in this sub-step, since the component is first loaded, the data obtained through the network at this time needs to be cached for the next loading.
Thus, for a component that supports caching, since it may be first loaded, data needs to be obtained over the network, so that the first loaded component is rendered without flickering to some extent.
FIG. 8 is a flow diagram illustrating data retrieval and matching performed by a component supporting caching according to the number of times the component has been loaded according to another embodiment of the present application. As shown in fig. 8, the sub-step S136 may include the sub-step S136D in addition to the sub-steps S136A to S136C. For the sake of brevity, only the differences between the embodiment shown in fig. 8 and the embodiment of fig. 7 will be described below, and the same parts will not be described again.
In sub-step S136D, if it is not the first load, the data is retrieved from the cache device and matched. Therefore, when the page is refreshed, the data of the component is stored in the cache device, so that the data can be directly acquired from the cache device and matched with the data. Therefore, when the loading is carried out for the second time or even more times, the page-level assembly adding and deleting operation can be effectively avoided, and the problem of rendering flicker is solved from the perspective of non-first loading.
When the page is rendered, the partial refresh capability in the rendering tool (see fig. 2) can be called by comparing the new data with the old data, and only partial components need to be refreshed instead of full-page redrawing can be done.
FIG. 9 shows a schematic design of an attachment vessel according to one embodiment of the present application. As shown in fig. 9, a cross-platform responsive observation mode is implemented in the cross-platform framework KMM, sequential input/output and thread switching of a component loading sequence between an observed person and two ends of the observed person and lifecycle scheduling are completed, and a design of splitting a component loading stream into related components for data loading matching is implemented.
FIG. 10 shows a schematic diagram of a mobile terminal for displaying a page according to one embodiment of the present application. As shown in fig. 10, the mobile terminal 200 may include an acquisition unit 210, a component stream creation unit 220, a processing unit 230, a merging unit 240, and a loading unit 250.
The obtaining unit 210 is configured to obtain a component set of a page to be displayed on a mobile terminal. The component flow creation unit 220 arranges the component sets into a first component sequence according to the characteristics of the page to be displayed. The processing unit 230 splits the first component sequence, and performs data acquisition and matching on the split components respectively. The merging unit 240 merges the plurality of components that have acquired and matched data into a second sequence of components, wherein the components in the second sequence of components have the same order as the first sequence of components. The loading unit 250 loads the plurality of components in the order of the second component sequence.
According to another aspect of the present application, there is also provided an electronic device, which may comprise a processor and a memory, the memory storing a computer program which, when executed by the processor, causes the processor to perform the method as described above.
According to another aspect of the present application, there is also provided a non-transitory computer readable storage medium having stored thereon computer readable instructions which, when executed by a processor, cause the processor to perform the method as described above.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments. The technical features of the embodiments may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The foregoing embodiments have been described in detail to illustrate the principles and implementations of the present application, and the foregoing embodiments are only used to help understand the method and its core idea of the present application. Meanwhile, a person skilled in the art should, according to the idea of the present application, change or modify the embodiments and applications of the present application based on the scope of the present application. In view of the above, the description should not be taken as limiting the application.

Claims (12)

1. A method for displaying a page at a mobile terminal, comprising:
acquiring a component set of a page to be displayed on a mobile terminal;
arranging the component sets into a first component sequence according to the characteristics of the page to be displayed;
splitting the first component sequence, and respectively acquiring and matching data of the split components;
merging the plurality of components that have acquired and matched data into a second sequence of components, the components in the second sequence of components having the same order as the first sequence of components; and
loading the plurality of components in the order of the second sequence of components.
2. The method of claim 1, wherein the plurality of components include cache-enabled components and non-cache-enabled components, and the separately performing data acquisition and matching on the split plurality of components comprises:
aiming at the components which do not support the cache, acquiring data through a network and performing data matching; and
and for the components supporting the cache, finishing the acquisition and the matching of the data according to the loaded times of the components.
3. The method of claim 2, wherein obtaining data over a network and performing matching of data for components that do not support caching comprises:
sending a network request; and
and receiving the data of the components from the server side and carrying out data matching.
4. The method of claim 2, wherein for a component that supports caching, completing the obtaining and matching of data according to the number of times the component has been loaded comprises:
judging whether the component is loaded for the first time;
if the loading is the first time, sending a network request; and
and receiving the data of the components from the server side, performing data matching, and storing the received data to the cache device.
5. The method of claim 4, wherein completing the obtaining and matching of data according to the number of times the component has been loaded for the component that supports the cache further comprises:
and if the data is not loaded for the first time, acquiring the data from the cache device and performing data matching.
6. The method of claim 1, wherein the first sequence of components is split using a load queue and the plurality of components that have acquired and matched data are merged into a second sequence of components using the load queue.
7. The method of claim 1, wherein loading the plurality of components in the order of the second sequence of components comprises:
and performing combined loading rendering on the components of the page to be displayed by using a rendering tool.
8. The method of claim 1, wherein the separately performing data acquisition and matching on the split plurality of components comprises:
creating a plurality of dispatchers, the plurality of dispatchers corresponding respectively to the plurality of components; and
and respectively acquiring and matching data of the components by utilizing the dispatchers.
9. The method of claim 1, wherein the plurality of components that have fetched and matched data are merged into the second sequence of components using a caching device.
10. A mobile terminal for displaying a page, comprising:
the mobile terminal comprises an acquisition unit, a display unit and a display unit, wherein the acquisition unit is used for acquiring a component set of a page to be displayed on the mobile terminal;
the component flow creating unit is used for arranging the component sets into a first component sequence according to the characteristics of the page to be displayed;
the processing unit is used for splitting the first component sequence and respectively acquiring and matching data of the split components;
a merging unit that merges the plurality of components, for which data has been acquired and matched, into a second component sequence, components in the second component sequence having the same order as the first component sequence; and
and the loading unit loads the plurality of components according to the sequence of the second component sequence.
11. An electronic device, comprising:
a processor; and
a memory storing a computer program that, when executed by the processor, causes the processor to perform the method of any one of claims 1-9.
12. A non-transitory computer readable storage medium having stored thereon computer readable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1-9.
CN202210330611.7A 2022-03-30 2022-03-30 Method for displaying page on mobile terminal and mobile terminal Active CN114741147B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210330611.7A CN114741147B (en) 2022-03-30 2022-03-30 Method for displaying page on mobile terminal and mobile terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210330611.7A CN114741147B (en) 2022-03-30 2022-03-30 Method for displaying page on mobile terminal and mobile terminal

Publications (2)

Publication Number Publication Date
CN114741147A true CN114741147A (en) 2022-07-12
CN114741147B CN114741147B (en) 2023-11-14

Family

ID=82279750

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210330611.7A Active CN114741147B (en) 2022-03-30 2022-03-30 Method for displaying page on mobile terminal and mobile terminal

Country Status (1)

Country Link
CN (1) CN114741147B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100318926A1 (en) * 2009-06-15 2010-12-16 Microsoft Corporation User interface for entering account dimension combinations
CN103546505A (en) * 2012-07-12 2014-01-29 百度在线网络技术(北京)有限公司 Method, system and device for displaying page blocks in priority order
CN103888456A (en) * 2014-03-18 2014-06-25 国家电网公司 Webpage client side, server side and data processing device and method
WO2016112791A1 (en) * 2015-01-13 2016-07-21 阿里巴巴集团控股有限公司 Method and device for displaying interface of application program on mobile terminal
CN110046021A (en) * 2019-05-21 2019-07-23 北京字节跳动网络技术有限公司 A kind of page display method, device, system, equipment and storage medium
CN110377361A (en) * 2019-07-15 2019-10-25 北京奇艺世纪科技有限公司 Data load method, device, computer equipment and storage medium
CN112182452A (en) * 2020-09-27 2021-01-05 中国平安财产保险股份有限公司 Page component rendering processing method, device, equipment and computer readable medium
US20210117203A1 (en) * 2019-10-21 2021-04-22 Advanced Micro Devices, Inc. Speculative execution using a page-level tracked load order queue
CN113031946A (en) * 2021-02-24 2021-06-25 北京沃东天骏信息技术有限公司 Method and device for rendering page component
CN113642320A (en) * 2020-04-27 2021-11-12 北京庖丁科技有限公司 Method, device, equipment and medium for extracting document directory structure

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100318926A1 (en) * 2009-06-15 2010-12-16 Microsoft Corporation User interface for entering account dimension combinations
CN103546505A (en) * 2012-07-12 2014-01-29 百度在线网络技术(北京)有限公司 Method, system and device for displaying page blocks in priority order
CN103888456A (en) * 2014-03-18 2014-06-25 国家电网公司 Webpage client side, server side and data processing device and method
WO2016112791A1 (en) * 2015-01-13 2016-07-21 阿里巴巴集团控股有限公司 Method and device for displaying interface of application program on mobile terminal
CN105843594A (en) * 2015-01-13 2016-08-10 阿里巴巴集团控股有限公司 Method and device for displaying application program page of mobile terminal
CN110046021A (en) * 2019-05-21 2019-07-23 北京字节跳动网络技术有限公司 A kind of page display method, device, system, equipment and storage medium
CN110377361A (en) * 2019-07-15 2019-10-25 北京奇艺世纪科技有限公司 Data load method, device, computer equipment and storage medium
US20210117203A1 (en) * 2019-10-21 2021-04-22 Advanced Micro Devices, Inc. Speculative execution using a page-level tracked load order queue
CN113642320A (en) * 2020-04-27 2021-11-12 北京庖丁科技有限公司 Method, device, equipment and medium for extracting document directory structure
CN112182452A (en) * 2020-09-27 2021-01-05 中国平安财产保险股份有限公司 Page component rendering processing method, device, equipment and computer readable medium
CN113031946A (en) * 2021-02-24 2021-06-25 北京沃东天骏信息技术有限公司 Method and device for rendering page component

Also Published As

Publication number Publication date
CN114741147B (en) 2023-11-14

Similar Documents

Publication Publication Date Title
CN110096660B (en) Method and device for loading page pictures and electronic equipment
EP3822828A2 (en) Method, apparatus, device and storage medium for determining page theme and computer program product
CN111581563A (en) Page response method and device, storage medium and electronic equipment
CN109491742B (en) Page table rendering method and device
CN107479868B (en) Interface loading method, device and equipment
CN111125057B (en) Method and device for processing service request and computer system
CN112579928A (en) Page jump method, page jump device, computer equipment and computer readable storage medium
CN111294395A (en) Terminal page transmission method, device, medium and electronic equipment
CN105808307B (en) Page display method and device
CN114385164A (en) Page generation and rendering method and device, electronic equipment and storage medium
CN111881216A (en) Data acquisition method and device based on shared template
CN114780615A (en) Error code management method and device thereof
CN113778581A (en) Page loading method, electronic equipment and storage medium
CN112565870B (en) Content caching and reading method, client and storage medium
CN110134905B (en) Page update display method, device, equipment and storage medium
CN109857503B (en) Page interaction effect self-adaption method and device and electronic equipment
CN110647327A (en) Method and device for dynamic control of user interface based on card
CN114741147B (en) Method for displaying page on mobile terminal and mobile terminal
CN116048609A (en) Configuration file updating method, device, computer equipment and storage medium
CN115438290A (en) Method and system for automatically analyzing static resources of single-page application and preloading
CN113961298A (en) Page switching method, device, equipment and medium
CN115454666A (en) Data synchronization method and device among message queue clusters
CN115186207A (en) Method and device for loading page resources and electronic equipment
CN114968917A (en) Method and device for rapidly importing file data
CN114416212A (en) Mobile terminal application program data resource processing method and device

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