CN114265661B

CN114265661B - Page display method, device, equipment and storage medium for mobile client

Info

Publication number: CN114265661B
Application number: CN202210200810.6A
Authority: CN
Inventors: 李兴涛; 李炜豪
Original assignee: Suzhou Dajiaying Information Technology Co Ltd
Current assignee: Suzhou Dajiaying Information Technology Co Ltd
Priority date: 2022-03-03
Filing date: 2022-03-03
Publication date: 2022-06-21
Anticipated expiration: 2042-03-03
Also published as: CN114265661A

Abstract

The invention discloses a page display method, a device, equipment and a storage medium of a mobile client, wherein the method comprises the following steps: acquiring a user login role and first page rendering data from a server; responding to a viewing request of a current login user for a target page in a target client, and acquiring second page rendering data according to the first page rendering data; then acquiring control layout data matched with the target page from a preset resource pool according to page level data acquired by analyzing the second page rendering data; and rendering and displaying the target page according to the control layout data and a preset total data source. According to the technical scheme, the user login role and the page rendering data are obtained from the server, page display with more complex page levels can be achieved, the display real-time performance of the client page can be improved while the client page is displayed in a differentiated mode, and the update display efficiency of the client page can be improved.

Description

Page display method, device and equipment of mobile client and storage medium

Technical Field

The embodiment of the invention relates to a mobile application development technology, in particular to a page display method, a page display device, page display equipment and a storage medium of a mobile client.

Background

With the continuous development of mobile application technology, in the display page of the mobile client, aiming at different page contents displayed by different users, the method has important significance for improving the page display effect of the mobile client and improving the use experience of the mobile client of the users.

At present, in an existing page display method of a mobile client, corresponding permission information is generally configured for different users manually, and when the mobile client detects that a user requests to view a certain page, the mobile client displays a client page corresponding to a page display effect and page display content to the user according to the permission information corresponding to the user. However, in the prior art, when the number of users of the mobile client is large, it is difficult to implement effective permission configuration for a large number of users, and thus it is impossible to implement differentiated display of a relatively complex client page. In addition, when the page display content and the page display effect of at least one page need to be updated, the page of the client cannot be updated and displayed in real time on the premise of not reinstalling a new version client, so that the real-time performance of page update display is poor.

Disclosure of Invention

The invention provides a page display method, a page display device and a storage medium of a mobile client, which can realize the page display with more complex page levels when a current login user requests to check a target page of the client, can improve the display real-time performance of the page of the client while displaying the page of the client in a differentiation mode, and can improve the update display efficiency of the page of the client.

In a first aspect, an embodiment of the present invention provides a page display method for a mobile client, including:

when the target client side is detected to meet the preset login state detection condition currently, a page display request is sent to a server, and a user login role matched with the current login user and first page rendering data corresponding to the user login role fed back by the server are received;

responding to a viewing request of a current login user for a target page in a target client, and acquiring second page rendering data corresponding to the target page according to first page rendering data corresponding to the user login role;

analyzing second page rendering data corresponding to the target page to acquire page level data corresponding to the target page; the page level data comprises at least one control group and a function control corresponding to each control group;

acquiring control layout data matched with the target page from a preset resource pool according to page level data corresponding to the target page;

and rendering and displaying the target page according to the control layout data matched with the target page and a preset total data source.

In a second aspect, an embodiment of the present invention further provides a page display apparatus for a mobile client, including:

the first page rendering data acquisition module is used for sending a page display request to the server when detecting that the target client currently meets the preset login state detection condition, and receiving a user login role matched with the current login user and first page rendering data corresponding to the user login role, which are fed back by the server;

the second page rendering data acquisition module is used for responding to a viewing request of a current login user for a target page in a target client, and acquiring second page rendering data corresponding to the target page according to the first page rendering data corresponding to the user login role;

the page level data acquisition module is used for analyzing second page rendering data corresponding to the target page and acquiring page level data corresponding to the target page; the page level data comprises at least one control group and a function control corresponding to each control group;

the control layout data acquisition module is used for acquiring control layout data matched with the target page from a preset resource pool according to the page level data corresponding to the target page;

and the page rendering display module is used for rendering and displaying the target page according to the control layout data matched with the target page and a preset total data source.

In a third aspect, an embodiment of the present invention further provides a client device, where the client device includes:

one or more processors;

storage means for storing one or more programs;

when the one or more programs are executed by the one or more processors, the one or more processors implement the page display method of the mobile client according to any embodiment of the present invention.

In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the page display method of the mobile client provided in any embodiment of the present invention.

According to the technical scheme provided by the embodiment of the invention, when the target client side is detected to meet the preset login state detection condition currently, the login role of the user and the first page rendering data are obtained from the server; responding to a viewing request of a current login user for a target page in a target client, and acquiring second page rendering data corresponding to the target page according to the first page rendering data; then acquiring control layout data matched with the target page from a preset resource pool according to page level data acquired by analyzing the second page rendering data; and rendering and displaying the target page according to the control layout data and a preset total data source. When a current login user requests to view a target page of a client, acquiring a user login role and page rendering data from a server, and analyzing the acquired page rendering data to obtain page level data, so that more complex page display of page levels can be realized; the page display is carried out based on the page rendering data which is acquired from the server and corresponds to the latest user login role, the display real-time performance of the client page can be improved while the client page is displayed in a differentiated mode, and the updating display efficiency of the client page can be improved.

Drawings

Fig. 1 is a flowchart of a page display method of a mobile client according to a first embodiment of the present invention;

fig. 2A is a flowchart of a page display method of a mobile client according to a second embodiment of the present invention;

fig. 2B is a schematic diagram of a control layout corresponding to a function control in the second embodiment of the present invention;

fig. 2C is a schematic diagram of a client page according to a second embodiment of the present invention;

fig. 3 is a flowchart of a page display method of a mobile client according to a third embodiment of the present invention;

fig. 4 is a flowchart of a page display method of a mobile client according to a fourth embodiment of the present invention;

FIG. 5 is a block diagram of a page displaying apparatus of a mobile client according to a fifth embodiment of the present invention;

fig. 6 is a block diagram of a client device according to a sixth embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Example one

Fig. 1 is a flowchart of a page displaying method of a mobile client according to an embodiment of the present invention, where this embodiment is applicable to a situation where different users display respective corresponding client pages to the different users when it is detected that the different users log in the client, and the method may be executed by a page displaying apparatus of a mobile client according to a fifth embodiment of the present invention and integrated on a client device, where the client device may typically be a mobile terminal. The method specifically comprises the following steps:

s110, when the target client side is detected to meet the preset login state detection condition currently, a page display request is sent to the server, and a user login role matched with the current login user and first page rendering data corresponding to the user login role fed back by the server are received.

The target client may be an Application (APP) client of a mobile terminal (e.g., a mobile phone, a tablet computer, etc.); in this embodiment, the APP may support an android operating system or an IOS operating system, which is not specifically limited in this embodiment.

In this embodiment, the preset login state detection condition may be a preset condition for determining whether the latest user login role and page rendering data need to be requested from the server; for example, the preset login state detection condition may be that the target client starts to run in the foreground and is in a logged-in state, and when detecting that the detection condition is met, the target client may send a page display request to the server to request to acquire a user login role matched with the current login user and first page rendering data corresponding to the user login role. The server may be a remote device communicating with the target client.

The user login role can be associated with the user right corresponding to the target client; the user right corresponding to the target client may include a user right corresponding to a function page in the target client, a user right corresponding to a control grouping in the function page, and a user right corresponding to a function control in the control grouping. When the user login role is associated with the user authority corresponding to the function page in the target client, the target client provides different function pages for different users of the target client; for example, for user A, page 1 and page 2 are provided; for user B, page 1 and page 3 are provided.

When the user login role is associated with the user authority corresponding to the control grouping in the function page, the target client provides the function page comprising different control groupings for different users clicking to view the same function page; for example, both user a and user B view page 1, and for user a, page 1 includes control group 1 and control group 2; and for user B, page 1 includes control grouping 1 and control grouping 3. In addition, when the user login role is associated with the function controls in the control group, aiming at different users, the same control group of the same function page of the target client comprises different function controls; for example, for user a, control grouping 1 of page 1 includes functionality control a and functionality control B; and for user B, the control grouping 1 of page 1 includes functionality control B and functionality control C.

In this embodiment, the server may configure, by giving a user login role corresponding to the user of the target client, a user right corresponding to each function page, control group, and function control for the user. The functional control refers to a program entity for implementing a specific function, and for example, the functional control may include a payroll billing control, a replacement billing control, a flexible employment control, and the like. Correspondingly, the user authority can comprise a behavior authority and a state authority; taking the user right corresponding to the function control as an example, the behavior right corresponding to the function control may include whether the control can be clicked, whether the control can jump to other pages after being clicked, and the like; the state permission corresponding to the function control may include whether the control is visible or not.

In this embodiment, a corresponding user right is configured for a user of a target client by giving a user login role, so that when different users correspond to the same user right, only one user login role corresponding to the same user right needs to be configured. At the moment, the same user login role is given to each user, so that the corresponding same user authority can be configured for each user, manual and repeated configuration of the same user authority can be avoided, and the configuration efficiency of the user authority can be greatly improved; in addition, in the interaction process of the user and the target client, when the user permission needs to be updated, only the latest user login role of the current user needs to be given, and the real-time performance of user permission updating can be improved.

The first page rendering data may include rendering data corresponding to each functional page in the target client; typically, the first page rendering data may be in a Json format. It should be noted that the page rendering data is independent of the page layout, and only includes page level data such as the function pages included in the target client, the control groups included in each function page, and the function controls included in each control group. In addition, the page rendering data may further include configuration information corresponding to each function control, for example, whether the control may be clicked, a page type and a routing path of a jump page after the control is clicked, and the like.

In this embodiment, while configuring a user login role matched with the user using the target client, the server may also configure corresponding page rendering data for the user login role. Therefore, after detecting the page display request of the target client, the server can search the user login role matched with the current login user and the first page rendering data corresponding to the user login role, and feed the data back to the target client.

The advantage of above-mentioned setting lies in, through obtaining the first page rendering data that corresponds with the newest user login role from the server, and then based on this first page rendering data carries out the rendering display of client page, can promote the real-time of page show when the differentiation shows client page.

S120, responding to a viewing request of a current login user to a target page in a target client, and acquiring second page rendering data corresponding to the target page according to first page rendering data corresponding to the user login role.

In this embodiment, when detecting that the current login user clicks a selection target page (or clicks an access entry corresponding to the target page), the target client may update the history page rendering data locally cached by the target client by using the acquired first page rendering data, and may filter, from the updated history page rendering data, second page rendering data corresponding to the target page.

In an optional implementation manner of this embodiment, obtaining, according to the first page rendering data corresponding to the user login role, second page rendering data corresponding to a target page may include: updating the locally cached historical page rendering data according to the changed page rendering data and the corresponding change type identifier; and screening the updated historical page rendering data to obtain second page rendering data corresponding to the target page.

The first page rendering data may include changed page rendering data and a corresponding change type identifier. In this embodiment, the first page rendering data fed back by the server may only include a user login role matched with the current login user, changed page rendering data in the page rendering data having a corresponding user right in the target client, and a change type identifier corresponding to each part of the changed page rendering data, and does not need to include all page rendering data having a corresponding user right in the user login role. Therefore, the target client can realize the targeted change operation of the function page, the control group and the function control by rendering the data through the first page. The change type may include addition, deletion, replacement, and the like, and the corresponding change type identifier may be in the form of numbers, letters, and the like.

In a specific embodiment, when a new function control in a page needs to be added, the changed page rendering data needs to include a complete hierarchy corresponding to the function control, for example, a page identifier, a control grouping identifier, and a function control identifier corresponding to the function control; and the change type identifier should be the change type identifier corresponding to the "new addition". And determining the corresponding functional page and control grouping of the functional control in the target client through the page identification and the control grouping identification.

When the historical page rendering data is updated according to the changed page rendering data and the corresponding change type identifier, the function page corresponding to the function control can be determined according to the page identifier corresponding to the function control. Then, if the function page corresponding to the function control is not the existing page, a function page needs to be added; if the function page corresponding to the function control is the existing page, it needs to further determine whether a control group corresponding to the function control exists. If the control group corresponding to the functional control is determined not to be the existing control group, a new control group is needed to be added, and then the functional control is added to the new control group. If the control group corresponding to the function control is determined to be the existing control group, a new function control can be directly added in the control group.

In addition, when the page data needs to be deleted, the changed page rendering data only needs to include the page identifier corresponding to the functional page to be deleted, the control grouping identifier corresponding to the control grouping to be deleted, or the control identifier corresponding to the functional control to be deleted. When the page data needs to be replaced, the changed page rendering data needs to include a complete page level corresponding to the data part to be replaced; for example, if the replacement object is a control group, the page identifier and the control group identifier of the function page corresponding to the control group to be replaced and the control group identifier corresponding to the replaced control group need to be included; for another example, if the replacement object is a function control, the replacement object needs to include a control grouping identifier of a control grouping corresponding to the function control to be replaced and a page identifier of the function page.

The advantages of the above arrangement are: the server need only return the changed portion of the page rendering data, rather than the entire page rendering data. Therefore, unnecessary data transmission amount can be greatly reduced in the process of acquiring the page rendering data corresponding to the latest user login role.

Optionally, the first page rendering data fed back by the server may further include all page rendering data of a user right of a user login role matched with the current login user. At this time, after receiving the first page rendering data fed back by the server, the target client may directly replace the locally cached historical page rendering data with the first page rendering data, so as to complete updating of the historical page rendering data. Through the arrangement, the updating logic of the historical page rendering data can be simplified, and the data processing pressure of the target client can be reduced.

It should be noted that, in some special scenarios, for example, when a current login user logs in a target client for the first time, historical page rendering data may not exist in a local cache of the target client. At this time, the target client may acquire preset standard page rendering data as historical page rendering data. The preset standard page rendering data may include page rendering data with general authority of different users.

S130, analyzing second page rendering data corresponding to the target page, and acquiring page level data corresponding to the target page.

The page level data may include at least one control group, and a function control corresponding to each control group. In the present embodiment, the page hierarchy data is used to define the page hierarchy structure of the function page, for example, the number of control groups and types of the control groups included in the function page, and the number of function controls and types of the function controls included in each control group.

In this embodiment, after the target client acquires the second page rendering data corresponding to the target page, the target client may perform data parsing on the second page rendering data to acquire control groups included in the target page and function controls included in each control group.

The advantages of the above arrangement are: the page rendering data fed back by the server is analyzed to obtain the page level data, so that when the display content or the display effect of the page of the client needs to be updated, the latest page level data can be analyzed and obtained only by obtaining the latest page rendering data from the server without reinstalling the new version client, and the real-time update of the page display of the client can be realized. Meanwhile, by setting the control groups included by the pages and the functional controls included by the control groups, more complex page display of page levels can be realized, and thus the page display diversity of the target client can be improved. In addition, when the target client has more users, the corresponding client pages can be displayed for different users, and the differentiated display capability of the client pages can be improved.

And S140, acquiring control layout data matched with the target page from a preset resource pool according to the page level data corresponding to the target page.

The preset resource pool can comprise all function pages contained in the target client, all control groups corresponding to the function pages and configuration data of all function controls corresponding to the control groups; for example, the configuration data of the function page may include page frame layout data corresponding to the function page; the configuration data of the control group may include group frame layout data corresponding to the control group; the configuration data of the functional control may include a page identifier, a control group identifier, a control name, and the like corresponding to the functional control.

In a specific example, taking an android operating system as an example, the preset resource pool may be implemented based on an ArrayList type container, in which a plurality of myview type functionality controls may be defined. It should be noted that the ArrayList may configure a unique corresponding control identifier for each stored function control, so as to serve as an identity identifier of each function control in the ArrayList.

The control layout data matched with the target page may include configuration data of each control group in the target page (for example, the width and height of a display area corresponding to the control group, the display position of a function control included in the control group, and the like) and configuration data of each function control (for example, the width and height of a display area corresponding to the function control, and the like). In this embodiment, after the page level data corresponding to the target page is obtained, the matched configuration data may be searched in the preset resource pool according to the control grouping identifiers and the function control identifiers in the page level data, so as to obtain the control layout data matched with the target page.

S150, rendering and displaying the target page according to the control layout data matched with the target page and a preset total data source.

The preset total data source may include sub data sources adapted to all the function controls of the target client; the sub data sources may be a collection of multiple types of data content (e.g., pictures, text, etc.).

In this embodiment, after the control layout data matched with the target page is obtained, the grouping layout corresponding to each control grouping in the target page may be determined according to the control layout data, for example, the size of the grouping region, the functional controls included in the grouping, the display positions of the functional controls in the grouping region, and the like; and a control layout corresponding to each of the functionality controls, for example, a size of the control area, sub-controls (e.g., a picture sub-control and a text sub-control) included in the functionality controls, relative positions of the sub-controls in the control area, and the like. And then, the sub data source adapted to each function control can be determined, and the adaptation relationship between each sub control included in the function control and each data content in the adapted sub data source is established.

When the target page is rendered and displayed, the page frame can be rendered and displayed firstly, then the grouping frames of the control groups can be rendered and displayed in the page frame, and finally the functional controls can be rendered and displayed in the grouping frames, so that the rendering and display of the target page can be completed finally.

It should be noted that, for the target client, not all the function pages need to be dynamically generated based on the user login role matched by the user and the page rendering data corresponding to the user login role. In this embodiment, a part of pages of the target client can be made to support dynamic generation, and the other part of pages are fixed pages (the pages seen by all users are the same). The part of the client pages supporting dynamic generation can be preset, so that when the part of the client pages are displayed, dynamic display can be performed according to the corresponding control layout data.

According to the technical scheme provided by the embodiment of the invention, when the target client side is detected to meet the preset login state detection condition currently, the login role of the user and the first page rendering data are obtained from the server; responding to a viewing request of a current login user for a target page in a target client, and acquiring second page rendering data corresponding to the target page according to the first page rendering data; then acquiring control layout data matched with the target page from a preset resource pool according to page level data acquired by analyzing the second page rendering data; and rendering and displaying the target page according to the control layout data and a preset total data source. When a current login user requests to view a target page of a client, acquiring a user login role and page rendering data from a server, and analyzing the acquired page rendering data to obtain page level data, so that more complex page display of page levels can be realized; the page is displayed based on the page rendering data corresponding to the latest user login role and acquired from the server, so that the display real-time performance of the client page can be improved while the client page is displayed in a differentiated mode, and the updating display efficiency of the client page can be improved.

In an optional implementation manner of this embodiment, the detecting that the target client currently satisfies the preset login state detection condition may include: when detecting that a target client starts to run in a foreground currently, judging whether the target client is in a logged-on state or not; if yes, determining that the target client side meets a preset login state detection condition when detecting that the foreground running state of the target client side is not waken from the background to the foreground.

The "foreground" and "background" are relative to the operating system of the mobile terminal. Taking an android operating system as an example, when a client is determined to be in a running state, if the client has a corresponding user visible view component, has a running foreground service or has another client associated with the client, the client can be determined to run in the "foreground" of the android operating system; correspondingly, if the conditions are not met, the client can be determined to run in the background of the android operating system.

In this embodiment, when it is detected that the target client is currently started, it may be determined that the target client currently starts to operate in the foreground; or when the view component corresponding to a certain page of the target client is detected to be created, the target client can be determined to be currently started to run in the foreground. Further, when it is determined that the target client starts to run in the foreground, whether the target client is currently in a logged-on state is determined.

It should be noted that if the target client wakes up from the background to the foreground, it indicates that the target client has been started before a short time and is not currently logged out; at this time, because the interval time is short, the user login role corresponding to the current login user is not changed. If the target client requests the server for the user login role again, repeated requests for the same user login role in a short time are caused, the effectiveness of obtaining the user login role is reduced, the request times of the corresponding interface of the server are increased, and the data processing pressure of the server is increased.

In view of the above problem, in this embodiment, after determining that the target client is in the logged-on state, it is further determined whether the target client is woken up from the background to the foreground, that is, whether the target client has been started before and has not logged out. If the current foreground running state of the target client is determined not to be awakened from the background to the foreground, a page display request can be sent to the server. After receiving the page display request, the server may search a pre-established correspondence between a user identifier and a user login role according to a user identifier (e.g., a user name or a user account) of a current login user, obtain a user login role matched with the current login user, and send first page rendering data corresponding to the user login role to the target client. And if the current foreground running state of the target client is determined to be awakened from the background to the foreground, the locally cached user login role and historical page rendering data can be continuously used.

The advantages of the above arrangement are: by judging the current foreground operating state of the target client, whether the matched user login role and first page rendering data are requested to the background server or not is determined, repeated requests for the same user login role and page rendering data can be avoided, the effectiveness of obtaining the user login role and the page rendering data can be improved, in addition, frequent and unnecessary requests for the user login role to the server can be avoided, the number of requests for a corresponding interface of the server can be reduced, and the data processing pressure of the server is reduced.

Wherein, it is not awaken from the background to the foreground to detect the foreground running state, and may include: detecting whether a view component corresponding to a main page of the target client exists in a view component manager of the target client; if not, determining that the foreground running state is not waken from the background to the foreground.

The view components are software entities for realizing the display of the client pages and correspond to the client pages one to one; correspondingly, the view component manager is a functional module for recording and managing the view components. In this embodiment, a view component manager having a history view component recording function may be locally provided to store view components corresponding to pages displayed by a target client within a certain time. It is noted that when the target client is completely closed, killed by the background of the operating system, or restarted by the terminal on which the target client is installed, the view component manager corresponding to the target client will be completely emptied.

It should be noted that, after the user opens the client, the user defaults to enter the main page of the client, that is, the default main page is the 1 st page displayed after the client is opened. Therefore, if the target client is previously opened and is not completely closed, the user must open the main page of the target client, and thus a view component for displaying the main page of the target client must exist in the view component manager; therefore, whether the target client is awakened from the background to the foreground can be judged by searching the view component corresponding to the main page in the view component manager of the target client.

In a specific example, when the target client corresponds to an android operating system, the corresponding view component may be an Activity component; the Activity component is an inherent component of the android system and is used for providing an interactive interface between a program and a user; specifically, the Activity component can realize the whole process of creating, displaying and ending the interactive interface through a series of preconfigured controls. Specifically, in an Activity component manager of a target client, whether an Activity component corresponding to a main page of the target client exists or not is detected; if the target client is determined to exist, the target client can be determined to be woken up from the background to the foreground.

It should be noted that, at present, the login states of many APPs are cached locally, even if the APPs are completely turned off or the mobile phone is restarted, if the APPs are restarted within the validity period, the APPs are still in the logged-in state, and do not need to be logged in again, for example, after the WeChat is turned off, the APP does not need to be logged in again when being turned on again. However, the validity period of the APP setting may be 1 week or more, and during this time, the backend server may update the matching user login role. Therefore, if only the login state of the target client is detected, the latest user login role matched with the current login user may not be obtained in time, and thus, the real-time performance of page display is poor while the page of the client is displayed in a differentiated manner.

In this embodiment, after the target client is detected to be in the logged-in state, whether to request the background server to acquire the current user login role is determined according to whether the view component corresponding to the home page exists in the view component manager, so that the latest user login role can be acquired in time, frequent and unnecessary requests for the user login role caused by the situation that the target client wakes up from the background to the foreground can be avoided, the number of requests for the corresponding interface of the background server can be reduced, and the data processing pressure of the background server is reduced.

In another optional implementation manner of this embodiment, after determining whether the target client is in a logged-in state, the method may further include: if not, displaying a login page of the target client to the current access user, and acquiring user login information input by the current access user in the login page; generating a user login authentication request according to the user login information, and sending the user login authentication request to a server; and when login verification passing information corresponding to the current access user fed back by the server is detected, determining that the target client currently meets a preset login state detection condition.

In one scenario, after a target client is opened, the target client is in an unregistered state; at this time, the target client may provide the login page to the current accessing user in the form of a human-computer interaction interface. The current access user can input user login information such as a user account, a user password and the like in the login page and click a login button. When the target client detects that the login button is clicked, a user login authentication request can be generated according to user login information input by a user, and the user login authentication request is sent to the server so as to request the server to verify the user login information. When detecting a user login authentication request sent by a target client, a server verifies user login information in the user login authentication request; if the user identity verification is successfully passed, login verification passing information can be fed back to the target client. When receiving login verification passing information fed back by the server, the target client can determine that the preset login state detection condition is currently met.

Example two

Fig. 2A is a flowchart of a page display method of a mobile client according to a second embodiment of the present invention, which is a further refinement of the foregoing technical solution, and the technical solution in this embodiment may be combined with one or more of the foregoing embodiments. Specifically, referring to fig. 2A, the method specifically includes the following steps:

s210, when the target client side is detected to meet the preset login state detection condition currently, a page display request is sent to the server, and a user login role matched with the current login user and first page rendering data corresponding to the user login role fed back by the server are received.

S220, responding to a viewing request of a current login user to a target page in a target client, and acquiring second page rendering data corresponding to the target page according to first page rendering data corresponding to the user login role.

S230, analyzing the second page rendering data corresponding to the target page, and acquiring page level data corresponding to the target page.

The page level data comprises at least one control group and a function control corresponding to each control group.

S240, acquiring control layout data matched with the target page from a preset resource pool according to the page level data corresponding to the target page.

And S250, establishing a target adapter matched with the target page according to the control layout data matched with the target page and a preset total data source.

The target adapter may include an adaptation relationship between a control layout corresponding to each functional control in the target page and the sub data source matched with each functional control.

And S260, rendering and displaying the target page according to the target adapter matched with the target page.

In this embodiment, after the target adapter matched with the target page is established, the functional controls of the target page may be traversed based on each pair of adaptation relations in the target adapter, so that the functional controls supporting the current user login role are rendered and displayed in the corresponding grouping frame, and the rendering and display of the target page is realized.

In an optional implementation manner of this embodiment, establishing, according to the control layout data matched with the target page and a preset total data source, a target adapter matched with the target page may include: acquiring control layout corresponding to each functional control in the target page according to the control layout data matched with the target page; determining subdata sources matched with the functional controls in the target page in preset total data sources according to the control identifications corresponding to the functional controls in the target page; and if the historical adapter matched with the target page does not exist, respectively establishing an adaptation relation between the control layout corresponding to each functional control and the sub-data source matched with each functional control through a preset adapter component to obtain the target adapter matched with the target page. The sub-data sources may include picture data and text data corresponding to each function control in the target page.

The control layout corresponding to the function control may include each sub-control corresponding to the function control, a display position of each sub-control, and a display state (e.g., visible or invisible) corresponding to each sub-control. Taking the functional control shown in fig. 2B as an example, the sub-controls included therein are two picture sub-controls (a control icon sub-control and a red dot sub-control at the upper right corner) and two text sub-controls (a control name sub-control and an unread message number sub-control); the control icon sub-control is located in the middle, the red dot sub-control is located on the upper right of the control icon sub-control, the control name sub-control is located below the control icon sub-control, and the unread message number sub-control is located in the red dot sub-control on the upper right corner. In this embodiment, the form of the layout of the control corresponding to the function control is not particularly limited.

It should be noted that, the control layout corresponding to the function control is defined by the configuration data of the function control, and when the control layout corresponding to one function control needs to be adjusted, only the configuration data of the function control needs to be modified correspondingly. Therefore, after the control layout data matched with the target page is obtained, the control layout corresponding to each functional control in the target page can be determined according to the configuration data corresponding to each functional control in the control layout data. It is worth noting that each function control in the current target page supports the user login role matched with the current login user.

In this embodiment, each sub-data source of the preset total data source has a mapping relationship with the control identifier corresponding to the function control, so that the sub-data source matched with each function control can be searched in the preset total data source according to the control identifier corresponding to each function control in the target page.

The function control can comprise a picture sub control and a text sub control, and the corresponding sub data source matched with the function control can comprise picture data corresponding to the picture sub control and text data corresponding to the text sub control. The historical adapter can be an adapter which is established when the current login user accesses the target page before.

In this embodiment, after obtaining the sub data sources matched with the function controls in the target page, it may be first determined whether there is a history adapter matched with the target page, and if it is determined that there is no history adapter matched with the target page, it indicates that the current login user accesses the target page for the first time; at this time, the adapter component for configuring the adapter relationship between the control layout and the sub data source can be preset to establish the adapter relationship between the control layout corresponding to each functional control and the sub data source matched with each functional control, so as to establish the target adapter matched with the target page.

It should be noted that the control layout corresponding to one function control may include a plurality of sub-controls (e.g., a picture sub-control, a text sub-control, etc.), and in this embodiment, the order corresponding to each sub-control may be predefined; correspondingly, in the sub-data sources matched with the function controls, the data contents matched with the sub-controls are also stored according to a predefined sequence. Therefore, after the adaptation relationship between the control layout corresponding to one function control and the sub data source matched with the function control is determined, the adaptation relationship between each sub control in the control layout and the data content is also naturally determined. Optionally, a mapping relationship between each data content and a child control identifier corresponding to the child control may also be preconfigured in each child data source; and subsequently, searching data content matched with each sub-control in the sub-data source according to the sub-control identification corresponding to each sub-control.

In a specific example, still taking the android operating system as an example, the adaptive relationship between the control layout corresponding to the functional control and the sub data source matched with the functional control may be set by using a workbench interface of the Adapter component. Specifically, taking the functional control shown in fig. 2B as an example, the adaptation relationship between the picture sub-control and the picture data in the sub-data source matched with the picture sub-control can be determined through the WorkbenchAdapter interface, and the adaptation relationship between the text sub-control and the text data in the sub-data source matched with the text sub-control can be determined. In addition, other control attributes can be set through a WorkbenchAdapter interface, for example, the control display area parameters, whether the control can be clicked, whether the control is displayed, and the like; for example, the number of unread messages corresponding to the functional control may be obtained, and if the number of unread messages is 0, the red dot sub-control in the upper right corner of the functional control may be set to be invisible; if the number of the unread messages is not 0, the red dot sub-control at the upper right corner of the functional control can be set to be visible, and the corresponding unread message number sub-control is displayed in the red dot sub-control, wherein the content corresponding to the unread message number sub-control is the unread message number value.

In this embodiment, a user of the target client may execute a "long press and pull" operation on the target page to trigger a pull-down refresh function, so as to obtain the number of unread messages corresponding to each function control in the target client. Furthermore, the unread message number corresponding to each function control can be displayed through the unread message number sub-control at the upper right corner of the function control.

In another optional implementation manner of this embodiment, after determining, in a preset total data source, a child data source that matches each of the function controls in the target page, the method may further include: and if the historical adapter matched with the target page exists, updating the adaptation relation in the historical adapter matched with the target page according to the control layout corresponding to each functional control in the target page and the subdata source matched with each functional control to obtain the target adapter matched with the target page.

If the historical adapter matched with the target page is determined to exist, the target page is loaded by the target client before, and when page refreshing operation or data source change is detected, the original adaptation relation in the historical adapter can be updated by adopting control layout corresponding to each functional control in the current target page and the sub-data source matched with each functional control, so that the target adapter matched with the target page is obtained.

According to the technical scheme provided by the embodiment of the invention, when the target client side is detected to currently meet the preset login state detection condition, the login role of the user and the first page rendering data are obtained from the server; responding to a viewing request of a current login user for a target page in a target client, and acquiring second page rendering data corresponding to the target page according to the first page rendering data; then acquiring control layout data matched with the target page from a preset resource pool according to page level data acquired by analyzing the second page rendering data; finally, according to the control layout data matched with the target page and a preset total data source, a target adapter matched with the target page is established, and then the target page is rendered and displayed according to the target adapter matched with the target page; the target adapter matched with the target page is established to render and display each function control, so that the display efficiency of the client page can be improved, and the display real-time performance of the client page can be improved while the client page is displayed in a differentiated mode.

In another optional implementation manner of this embodiment, before rendering and displaying the target page according to the target adapter matched with the target page, the method may further include: and acquiring grouping frame layout data corresponding to each control group in the target page according to the control layout data matched with the target page.

The group frame layout data may be definition data of a group frame corresponding to the control group, for example, the width and height of a display area corresponding to the control group, the display position of the functional control in the display area corresponding to the control group, and the like. In this embodiment, an association relationship between the control group identifier corresponding to each control group and the group frame layout data may be preconfigured. It should be noted that, the packet frame layout data corresponding to different control groups may be the same or different, and this embodiment is not limited in this respect.

In this embodiment, before rendering and displaying each function control in the target page according to the target adapter matched with the target page, the grouping frame layout data corresponding to each control group may be obtained from the control layout data matched with the target page, and based on the grouping frame layout data corresponding to each control group, the grouping frame corresponding to each control group may be rendered and displayed first. The group frame may include a group header (for displaying the control group identifier or name) and a group body (for displaying the control group content, for example, the function control included in the group, etc.), among others.

Correspondingly, rendering and displaying the target page according to the target adapter matched with the target page may include: rendering and displaying the grouping frames corresponding to the control groups in the target page according to the grouping frame layout data corresponding to the control groups in the target page; acquiring the adaptation relation between the control layout corresponding to each functional control in the target adapter and the sub-data source matched with each functional control; and rendering and displaying each functional control at the display position of each group frame in the target page by adopting a preset page layout component corresponding to the target page according to the adaptation relation.

The preset page layout component may be a preset system component for rendering and displaying the function control, for example, the preset page layout component may be a recycle view component of an android operating system. The RecycleView component supports rendering display of multiple types of page layouts, for example, a linear layout (supporting horizontal and vertical effects), a grid layout (supporting horizontal and vertical effects) and a distributed layout (supporting waterfall flow effects) can be realized, and by using the RecycleView component, more flexible and more efficient page rendering display can be realized.

Specifically, after the group frame layout data corresponding to each control group is obtained, the group frames corresponding to each control group may be rendered and displayed according to the group frame layout data, and the recycle view component may be bound to the target adapter on the basis of the group frames, so as to render and display each function control at the corresponding position of each group frame according to the adaptation relationship between the control layout corresponding to each function control in the target adapter and the sub data source matched with each function control.

In this embodiment, the rendering display may be performed on the grouping frame corresponding to one control grouping, then the rendering display is performed on each functional control included in the control grouping, and the above process is repeated until the rendering display of all the control groupings is completed. Or rendering and displaying the grouping frames corresponding to all the control groups, and then rendering and displaying the functional controls included in the control groups one by one in each grouping frame until the rendering and displaying of all the functional controls are completed.

In a specific example, the page display effect that can be achieved by the technical solution of the present embodiment can be as shown in fig. 2C. The workbench page comprises two control groups, namely an enterprise authorization service and an operation report; for the enterprise authorization service, the enterprise authorization service comprises six functional controls which are paid bills, generation and replacement, flexible employment, My Y bills, president audit and boss authorization respectively; for the operation report, the operation report comprises three functional components, namely a business report, an on-duty report and a snail billboard. The control layout corresponding to each function control is divided into a picture sub-control (displaying an icon corresponding to the function control) and a text sub-control (displaying a control name corresponding to the function control). It is worth noting that for different users, the number and types of the control groups and the function controls displayed in the function page are different, and differential display of the client page can be achieved.

EXAMPLE III

Fig. 3 is a flowchart of a page display method of a mobile client according to a third embodiment of the present invention, which is a further refinement of the foregoing technical solution, and the technical solution in this embodiment may be combined with one or more of the foregoing embodiments. Specifically, referring to fig. 3, the method specifically includes the following steps:

s310, when the target client side is detected to meet the preset login state detection condition currently, a page display request is sent to the server, and a user login role matched with the current login user and first page rendering data corresponding to the user login role fed back by the server are received.

S320, responding to a viewing request of a current login user to a target page in a target client, and acquiring second page rendering data corresponding to the target page according to first page rendering data corresponding to the user login role.

S330, analyzing the second page rendering data corresponding to the target page, and acquiring page level data corresponding to the target page.

S340, acquiring control layout data matched with the target page from a preset resource pool according to the page level data corresponding to the target page.

And S350, establishing a target adapter matched with the target page according to the control layout data matched with the target page and a preset total data source.

And S360, rendering and displaying the target page according to the target adapter matched with the target page.

S370, responding to a click request of a current login user for a target function control in a target page, and acquiring a control identification corresponding to the target function control when a user login role matched with the current login user is determined to have a page jump right corresponding to the target function control.

In this embodiment, for each function control in the target page, a corresponding jump page may be configured, so that when a click selection request of the current login user for the function control is detected, the jump page corresponding to the function control may be displayed to the current login user.

It should be noted that, after detecting a click request of a current login user to a target function control, it needs to first determine whether a user login role matched with the current login user has a page jump permission of the target function control. In this embodiment, the user right corresponding to the target function control may be obtained from the second page rendering data corresponding to the target page, so that whether the page jump right corresponding to the target function control exists or not may be determined according to the user right corresponding to the target function control. When the user login role matched with the current login user is determined to have the page jump authority corresponding to the target function control, the control identification corresponding to the target function control can be obtained.

And S380, acquiring a jump page type corresponding to the target function control from second page rendering data corresponding to the target page according to the control identification corresponding to the target function control.

The jump page type may include a local page, an external web page, and a general page. The jump page of the local page type is a page pre-configured by the target client, has a fixed page frame, and when rendering and displaying are needed, only data (for example, control names corresponding to the functional controls, grouping names of control groups, and the like) need to be filled into corresponding positions in the corresponding page frame. And for the jump page of the external webpage type, the jump page can be accessed through a browser built in the target client according to the corresponding routing path. The jump pages of the general page type, such as a login page, an abnormal alarm page, and the like, can realize page jump by calling the corresponding general function modules.

In this embodiment, it may be configured, in the page rendering data, whether each function control can jump to another page when clicked, and when the function control can jump to another page when clicked, configure a jump page type corresponding to the jump page, a jump page identifier corresponding to the jump page, and a routing path corresponding to the jump page. The skip page type may further include a message prompt box, a dialog box, and the like.

And S390, when the jump page type corresponding to the target function control is detected to be a local page, acquiring a control name corresponding to the function control and a grouping name of control grouping.

S3100, acquiring a target jump page identifier corresponding to the target function control, and frame layout data and page content data corresponding to the target jump page identifier according to the control identifier corresponding to the target function control.

Frame layout data corresponding to the target jump page identifier is definition data of a page frame of the target jump page; the page content data corresponding to the target jump page identifier refers to specific page information contained in the target jump page.

In this embodiment, when the jump page type corresponding to the target function control is a local page, the jump pages of the local page type corresponding to each function control have the same page frame; therefore, for a plurality of function controls in the target page, the function controls can be configured to multiplex the same jump page. When the jump page is rendered and displayed, the page content data corresponding to the functional control can be obtained by identifying the page jump from which functional control the current login user jumps, and the page content data is filled to the corresponding position of the jump page.

Specifically, when the type of the jump page corresponding to the target function control is a local page, a target jump page identifier corresponding to the target function control may be obtained from second page rendering data first; and then, frame layout data and page content data corresponding to the target jump page identifier can be obtained from a local cache of the target client.

S3110, rendering and displaying the page frame corresponding to the target jump page according to the frame layout data corresponding to the target jump page identifier.

And S3120, rendering and displaying the control name corresponding to the target function control, the grouping name of the control grouping corresponding to the target function control and the page content data corresponding to the target jump page identification at each display position of the page frame corresponding to the target jump page.

In this embodiment, when rendering and displaying a target jump page of a local page type, a page frame corresponding to the target jump page may be rendered and displayed according to frame layout data corresponding to a target jump page identifier; then, the control name, the grouping name of the corresponding control grouping and the page content data can be filled in each corresponding position of the page frame.

In a specific example, the page frame corresponding to the target jump page may include a main title, a sub-title and page content; the main title may include a control grouping name of a control grouping corresponding to the target function control, the subtitle may include a control name corresponding to the target function control, and the page content may include page content data corresponding to the target jump page identifier. Therefore, the contents of the parts can be filled to the corresponding positions in the page frame corresponding to the target jump page, so that the rendering display of the target jump page is completed.

In an optional implementation manner of this embodiment, after obtaining, according to the control identifier corresponding to the target functionality control, a skip page type corresponding to the target functionality control from the second page rendering data corresponding to the target page, the method may further include: when the type of the jump page corresponding to the target function control is detected to be an external webpage, acquiring a standard routing path corresponding to the target function control from second page rendering data corresponding to the target page according to a control identification corresponding to the target function control;

according to the control identification corresponding to the target function control, a specific routing path corresponding to the target function control is obtained in a local cache of a target client; acquiring a target routing path corresponding to the target function control according to a standard routing path and a specific routing path corresponding to the target function control; and performing page skipping according to a target routing path corresponding to the target function control through a preset webpage access module.

The standard routing path can be the same general part in the routing path corresponding to the jump page of the external webpage type; correspondingly, the specific routing path may be a difference portion corresponding to each function control in the routing path corresponding to the jump page of the external web page type. For example, when the routing path is a Uniform Resource Locator (URL) of the jumping page, the standard routing path may be a host address and a port number in the URL, and the specific routing path may be a file path and a request parameter in the URL; by splicing the standard routing path and the specific routing path, a complete routing path of a jump page of an external webpage type corresponding to the target function control, namely a target routing path, can be obtained.

In this embodiment, for the jump pages of the external web page types corresponding to different function controls, the jump pages may correspond to the same standard routing path and different specific routing paths corresponding to each of the standard routing paths; therefore, by combining the same standard routing path and different specific routing paths corresponding to each functional control, the routing paths of different jump pages corresponding to each functional control can be obtained.

It is worth noting that the server configures and manages the standard routing path corresponding to the jump page of the external webpage type; and the corresponding specific routing path is configured and managed by the target client. Therefore, when the jump page corresponding to the functional control needs to be modified, only the modification of the specific routing path is needed to be carried out on the target client, and the modification of the standard routing path is not needed. Through the arrangement, repeated modification of the complete routing path corresponding to the jump page by the server can be avoided, the configuration efficiency of the jump page corresponding to the functional control can be improved, the data processing pressure of the server can be reduced, the client side can be easy to maintain, and therefore the maintenance cost of the client side can be reduced.

Optionally, obtaining, according to the control identifier corresponding to the target function control, a standard routing path corresponding to the target function control from second page rendering data corresponding to the target page may include: according to the control identification corresponding to the target function control, obtaining a routing path field corresponding to the target function control from second page rendering data corresponding to the target page; and splitting a routing path field corresponding to the target function control by adopting preset characters, and acquiring a standard routing path corresponding to the target function control.

The preset character may be an _ "character. In the present embodiment, in the page rendering data, the standard routing path is stored in the form of "a _ B"; therefore, after the routing path field corresponding to the target function control is acquired from the page rendering data, the routing path field needs to be split and converted by using an _ "character to acquire the standard routing path in the form of" a/B ".

The preset web page access module may be a browser built in the target client. In this embodiment, after the target routing path corresponding to the target function control is obtained, a browser built in the target client may perform page skipping according to the target routing path, that is, display the web content corresponding to the target routing path.

In another optional implementation manner of this embodiment, after obtaining, according to the control identifier corresponding to the target functionality control, a jump page type corresponding to the target functionality control from the second page rendering data corresponding to the target page, the method may further include: when the type of the jump page corresponding to the target function control is detected to be a general page, acquiring a general function module identification corresponding to the target function control and a routing path corresponding to the general function module identification according to a control identification corresponding to the target function control; and accessing the general function module corresponding to the general function module identification according to the routing path corresponding to the general function module identification so as to carry out page jump.

The general function module is a pre-written program entity for realizing specific functions; for example, the general function module may be a login module, an alarm module, and the like.

In this embodiment, when it is determined that the type of the jump page corresponding to the target function control is a general page, a general function module identifier corresponding to the target function control may be obtained from second page rendering data corresponding to the target page according to a control identifier corresponding to the target function control; then, according to the universal function module identifier, a routing path corresponding to the universal function module identifier may be obtained in a local cache of the target client. And then accessing the general function module corresponding to the general function module identification according to the routing path to perform page jump.

According to the technical scheme provided by the embodiment of the invention, after the target page is rendered and displayed, the click request of the current login user on the target function control in the target page is responded, and when the user login role matched with the current login user is determined to have the page jump authority corresponding to the target function control, the jump page type corresponding to the target function control is obtained; when the type of the jump page is detected to be a local page, acquiring a control name corresponding to the functional control, a grouping name of the control grouping, a target jump page identifier corresponding to the target functional control, and frame layout data and page content data corresponding to the target jump page identifier; rendering and displaying a page frame corresponding to the target jump page according to the frame layout data corresponding to the target jump page identifier; and rendering and displaying the control name corresponding to the target function control, the grouping name of the control grouping corresponding to the target function control and the page content data corresponding to the target jump page identification at each display position of the page frame corresponding to the target jump page. When a current login user clicks and checks a target function control, the client jumps to a target jump page corresponding to the target function control, the display effect of a client page is enriched, the jump page is multiplexed by setting different function controls, the configuration and adjustment efficiency of the jump page corresponding to the function controls can be improved, the client is easy to maintain, and the display real-time performance of the jump page corresponding to the function controls can be improved.

Example four

Fig. 4 is a flowchart of a page display method of a mobile client according to a fourth embodiment of the present invention, which is a further refinement of the foregoing technical solution, and the technical solution in this embodiment may be combined with one or more of the foregoing embodiments. Specifically, referring to fig. 4, the method specifically includes the following steps:

s410, when the target client side is detected to meet the preset login state detection condition currently, a page display request is sent to the server, and a user login role matched with the current login user and first page rendering data corresponding to the user login role fed back by the server are received.

S420, responding to a viewing request of a current login user to a target page in a target client, and acquiring second page rendering data corresponding to the target page according to first page rendering data corresponding to the user login role.

S430, analyzing the second page rendering data corresponding to the target page, and acquiring page level data corresponding to the target page.

S440, acquiring control layout data matched with the target page from a preset resource pool according to the page level data corresponding to the target page.

S450, establishing a target adapter matched with the target page according to the control layout data matched with the target page and a preset total data source.

And S460, rendering and displaying the target page according to the target adapter matched with the target page.

S470, when detecting a user login role update message sent by the server, sending an update user login role acquisition request to the server through the background processing module of the target client, and receiving an update user login role matched with the current login user and fed back by the server, and third page rendering data corresponding to the update user login role.

The background processing module of the target client can be a functional module configured in the target client and used for processing background tasks, the tasks processed by the background processing module all run in the background of the terminal operating system, and the user of the client does not feel the background processing module.

In one scenario, a target client runs in the foreground of an operating system, and a server updates a user login role; at this time, because the preset login state detection condition is not met, the target client does not actively send a page display request to the server to acquire the updated user login role and the updated page rendering data, so that the client page cannot be updated and displayed based on the updated page rendering data, and the latest user login role is asynchronous with the currently displayed client page.

In this case, the server may first determine whether a user login role update message needs to be sent to the target client; specifically, if the server detects that the user login role matched with the current login user of the target client is updated, the server may send a user login role update message to the target client. And when receiving the user login role updating message, the target client sends an updating user login role acquiring request to the server through the background processing module so as to acquire an updating user login role matched with the current login user and fed back by the server and third page rendering data corresponding to the updating user login role.

Optionally, the determining whether the user login role update message needs to be sent to the target client includes: when detecting that a user login role corresponding to a certain user is updated, acquiring a user identifier corresponding to the detected user; judging whether a login certificate corresponding to the detected user exists or not according to the user identification corresponding to the detected user; and if so, sending a user login role updating message to the client corresponding to the detected user when detecting that the login credential corresponding to the detected user is in the validity period.

It should be noted that, after receiving a login request sent by a user through a client, if it is determined that the user passes authentication, the server issues a login credential (e.g., token) to the client. The client stores the received login credentials, and then the client carries the login credentials issued by the server when sending request data to the server. Accordingly, the server may determine whether to send a user login role update message to the current login user by detecting whether a login credential corresponding to the current login user exists.

It should be noted that the login credential issued by the server has a validity period, and when detecting that the login credential is expired or is about to expire, the client may send a login credential update request to the server to obtain an updated login credential. Therefore, the server may send the user login role update message to the target client only when determining that the login credential corresponding to the current login user is still within the validity period while detecting that the login credential corresponding to the current login user exists.

In another scenario, the target client is in a non-login state, and the server updates the user login role; and then, when the user logs in the target client again, the target client actively sends a page display request to the server so as to obtain the updated user login role and the corresponding page rendering data fed back by the server.

In this embodiment, through the above setting, the target client can actively or passively acquire the latest user login role and the corresponding page rendering data in various operating states (for example, a foreground operating state, an unregistered state, and the like) at the first time, so that the synchronization between the latest user login role and the currently displayed client page can be ensured, and the real-time performance of the update display of the client page can be improved while the client page is differentially displayed.

Optionally, after the target client acquires the updated user login role sent by the server and the third page rendering data corresponding to the updated user login role, the updated user login role may be compared with the locally cached historical user login role to determine whether the user login role is changed; if the user login role is determined to be changed, the updated user login role can be adopted to replace the locally cached historical user login role; if it is determined that the user login role has not been changed, the updated user login role and the third page rendering data may be discarded.

And S480, acquiring fourth page rendering data corresponding to the target page according to the third page rendering data corresponding to the user login role through a background processing module of the target client.

And S490, analyzing fourth page rendering data corresponding to the target page through a background processing module of the target client, and acquiring updated page level data corresponding to the target page.

S4100, acquiring, by a background processing module of the target client, update control layout data matched with the target page from a preset resource pool according to the update page level data corresponding to the target page.

In this embodiment, after receiving the third page rendering data corresponding to the updated user login role, the target client may update, through the background processing module, the locally cached historical page rendering data based on the third page rendering data in the background of the terminal operating system, and may screen the updated historical page rendering data to obtain the fourth page rendering data corresponding to the target page. Further, the fourth page rendering data may be analyzed to obtain updated page level data corresponding to the target page; and according to the updated page level data, the updated control layout data matched with the target page is screened from a preset resource pool.

S4110, updating the target adapter matched with the target page according to the updating control layout data matched with the target page and a preset total data source through a background processing module of the target client.

In this embodiment, after the updated control layout data matched with the target page is obtained, the updated control layout corresponding to each functional control in the target page and the sub data source matched with each functional control can be obtained through the background processing module according to the updated control layout data; then, the original adaptation relation in the target adapter can be updated by adopting the updated control layout corresponding to each functional control and the sub-data source matched with each functional control, so as to obtain the updated target adapter.

S4120, rendering and displaying the target page again according to the updated target adapter matched with the target page.

Specifically, after the updated target adapter is obtained, the target client may render and display each function control in the target page according to the adaptation relationship in the updated target adapter, so as to implement the rendering and display of the target page again. In a specific example, after the updated target adapter is obtained, the current login user may be prompted to refresh the page (e.g., pop-up prompt), or the page may be forcibly refreshed; and further performing rendering display on the target page again based on the updated target adapter. It is noted that the target page is not operable in rendering and displaying the target page again.

The advantages of the above arrangement are: the user has no perception in the processes of user login role updating and page rendering data updating, the user client use experience can be improved, and the interruption of the user client operation is avoided. In addition, when the function control of the client needs to be updated, only the updated user login role and the updated page rendering data need to be obtained, and operations such as reinstallation of the client are not needed, so that the functions of the client can be updated in real time, the page of the client can be updated and displayed in real time, and the user experience of the client of a user can be further improved.

According to the technical scheme provided by the embodiment of the invention, after the target page is rendered and displayed, when the user login role updating message sent by the server is detected, the background processing module of the target client sends an updating user login role obtaining request to the server, and receives the updating user login role matched with the current login user and the third page rendering data corresponding to the updating user login role fed back by the server; based on the third page rendering data, obtaining updated control layout data matched with the target page; then, updating a target adapter matched with the target page through a background processing module of the target client according to the updated control layout data matched with the target page and a preset total data source; and rendering and displaying the target page again according to the updated target adapter matched with the target page. The user login role and the page rendering data are updated through the background processing module based on the target client, so that the user can realize no perception in the updating process of the client page, the client use experience of the user can be improved, and the interruption of the client operation of the user is avoided; the updating display efficiency of the client page can be improved by acquiring the page rendering data corresponding to the login role of the updating user from the server to update and display the client page.

EXAMPLE five

Fig. 5 is a block diagram of a structure of a page display apparatus of a mobile client according to a fifth embodiment of the present invention, where the apparatus specifically includes: a first page rendering data acquisition module 510, a second page rendering data acquisition module 520, a page hierarchy data acquisition module 530, a control layout data acquisition module 540, and a page rendering display module 550; wherein;

a first page rendering data obtaining module 510, configured to send a page display request to a server when it is detected that a target client currently meets a preset login state detection condition, and receive a user login role matched with a current login user and first page rendering data corresponding to the user login role, which are fed back by the server;

a second page rendering data obtaining module 520, configured to, in response to a request for viewing a target page in a target client from a currently logged-in user, obtain, according to first page rendering data corresponding to the user login role, second page rendering data corresponding to the target page;

a page level data obtaining module 530, configured to analyze the second page rendering data corresponding to the target page, and obtain page level data corresponding to the target page; the page level data comprises at least one control group and function controls corresponding to the control groups;

a control layout data obtaining module 540, configured to obtain, according to the page level data corresponding to the target page, control layout data matched with the target page from a preset resource pool;

and a page rendering and displaying module 550, configured to render and display the target page according to the control layout data matched with the target page and a preset total data source.

Optionally, on the basis of the above technical solution, the first page rendering data includes changed page rendering data and a corresponding change type identifier;

a second page rendering data obtaining module 520, comprising:

the data updating unit is used for updating the locally cached historical page rendering data according to the changed page rendering data and the corresponding change type identification;

and the data screening unit is used for screening the updated historical page rendering data to obtain second page rendering data corresponding to the target page.

Optionally, on the basis of the foregoing technical solution, the first page rendering data obtaining module 510 includes:

the login judging unit is used for judging whether the target client is in a logged-in state or not when detecting that the target client starts to run in the foreground currently;

and the running state detection unit is used for determining that the target client side meets the preset login state detection condition when detecting that the foreground running state of the target client side is not waken from the background to the foreground if the target client side is in the running state.

the login information acquisition unit is used for displaying a login page of a target client to a current access user and acquiring user login information input by the current access user in the login page if the current access user does not access the target client;

a login authentication request sending unit, configured to generate a user login authentication request according to the user login information, and send the user login authentication request to a server;

and the login verification passing information detection unit is used for determining that the target client currently meets the preset login state detection condition when login verification passing information corresponding to the current access user fed back by the server is detected.

Optionally, on the basis of the above technical solution, the operation state detecting unit includes:

a view component detection subunit, configured to detect, in a view component manager of the target client, whether a view component corresponding to a main page of the target client exists;

and the running state determining subunit is used for determining that the foreground running state is not waken from the background to the foreground if the foreground running state is not waken from the background to the foreground.

Optionally, on the basis of the foregoing technical solution, the page rendering and displaying module 550 includes:

the target adapter establishing unit is used for establishing a target adapter matched with the target page according to the control layout data matched with the target page and a preset total data source, and the target adapter comprises an adaptive relation between the control layout corresponding to each functional control in the target page and a subdata source matched with each functional control;

and the page rendering display unit is used for rendering and displaying the target page according to the target adapter matched with the target page.

Optionally, on the basis of the above technical solution, the target adapter establishing unit includes:

the control layout obtaining subunit is used for obtaining the control layout corresponding to each functional control in the target page according to the control layout data matched with the target page;

a matching sub-data source determining subunit, configured to determine, according to the control identifier corresponding to each functional control in the target page, a sub-data source matching each functional control in the target page in a preset total data source;

the adaptive relationship establishing subunit is used for respectively establishing an adaptive relationship between the control layout corresponding to each functional control and the sub data source matched with each functional control through a preset adapter component if the historical adapter matched with the target page does not exist, so as to obtain the target adapter matched with the target page;

the sub data source comprises picture data and text data corresponding to each function control in the target page.

the group frame layout data acquisition unit is used for acquiring group frame layout data corresponding to each control group in the target page according to the control layout data matched with the target page;

a page rendering display unit comprising:

a group frame rendering subunit, configured to render and display the group frame corresponding to each control group in the target page according to the group frame layout data corresponding to each control group in the target page;

the adaptive relationship acquiring subunit is used for acquiring adaptive relationships between control layouts corresponding to the functional controls in the target adapter and the sub data sources matched with the functional controls;

and the functional control rendering subunit is used for rendering and displaying each functional control at the display position of each group frame in the target page by adopting a preset page layout component corresponding to the target page according to the adaptation relation.

Optionally, on the basis of the above technical solution, the page display apparatus of the mobile client further includes:

the control identification acquisition module is used for responding to a click request of a current login user for a target function control in a target page, and acquiring a control identification corresponding to the target function control when a user login role matched with the current login user is determined to have a page jump right corresponding to the target function control;

a skip page type obtaining module, configured to obtain, according to a control identifier corresponding to the target function control, a skip page type corresponding to the target function control from second page rendering data corresponding to the target page;

the group name acquisition module is used for acquiring the control name corresponding to the functional control and the group name of the control group when detecting that the skip page type corresponding to the target functional control is a local page;

the page content data acquisition module is used for acquiring a target jump page identifier corresponding to the target function control, and frame layout data and page content data corresponding to the target jump page identifier according to the control identifier corresponding to the target function control;

the page frame rendering module is used for rendering and displaying the page frame corresponding to the target jump page according to the frame layout data corresponding to the target jump page identifier;

and the data rendering module is used for rendering and displaying the control name corresponding to the target function control, the grouping name of the control grouping corresponding to the target function control and the page content data corresponding to the target jump page identification at each display position of the page frame corresponding to the target jump page.

Optionally, on the basis of the above technical solution, the page display device of the mobile client further includes:

the standard routing path acquisition module is used for acquiring a standard routing path corresponding to the target function control from second page rendering data corresponding to the target page according to a control identification corresponding to the target function control when the skip page type corresponding to the target function control is detected to be an external webpage;

a specific routing path obtaining module, configured to obtain, according to the control identifier corresponding to the target function control, a specific routing path corresponding to the target function control in a local cache of a target client;

the target routing path acquisition module is used for acquiring a target routing path corresponding to the target function control according to a standard routing path and a specific routing path corresponding to the target function control;

and the first page jump module is used for performing page jump according to a target routing path corresponding to the target function control through a preset webpage access module.

a general function module identifier obtaining module, configured to, when it is detected that the type of the jump page corresponding to the target function control is a general page, obtain, according to the control identifier corresponding to the target function control, a general function module identifier corresponding to the target function control and a routing path corresponding to the general function module identifier;

and the second page skipping module is used for accessing the general function module corresponding to the general function module identifier according to the routing path corresponding to the general function module identifier so as to skip pages.

the update user login role acquisition module is used for sending an update user login role acquisition request to the server through a background processing module of the target client when a user login role update message sent by the server is detected, and receiving an update user login role matched with a current login user and third page rendering data corresponding to the update user login role, which are fed back by the server;

a fourth page rendering data obtaining module, configured to obtain, by the background processing module of the target client, fourth page rendering data corresponding to the target page according to the third page rendering data corresponding to the user login role;

the updated page level data acquisition module is used for analyzing fourth page rendering data corresponding to the target page through a background processing module of the target client to acquire updated page level data corresponding to the target page;

the updating control layout data acquisition module is used for acquiring updating control layout data matched with the target page from a preset resource pool according to the updating page level data corresponding to the target page through the background processing module of the target client;

the target adapter updating module is used for updating the target adapter matched with the target page according to the updating control layout data matched with the target page and a preset total data source through the background processing module of the target client;

and the page re-rendering module is used for re-rendering and displaying the target page according to the updated target adapter matched with the target page.

The device can execute the page display method of the mobile client provided by the embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the methods provided in the foregoing embodiments of the present invention.

EXAMPLE six

Fig. 6 is a schematic structural diagram of a client device according to a sixth embodiment of the present invention, as shown in fig. 6, the client device includes a processor 610, a memory 620, an input device 630, and an output device 640; the number of processors 610 in the client device may be one or more, and one processor 610 is taken as an example in fig. 6; the processor 610, memory 620, input device 630, and output device 640 in the client device may be connected by a bus or other means, such as by a bus in fig. 6. The memory 620 is used as a computer readable storage medium for storing software programs, computer executable programs, and modules, such as program instructions/modules corresponding to a page display method of a mobile client in any embodiment of the present invention (for example, the first page rendering data obtaining module 510, the second page rendering data obtaining module 520, the page level data obtaining module 530, the control layout data obtaining module 540, and the page rendering display module 550 in a page display device of a mobile client). The processor 610 executes various functional applications and data processing of the client device by executing software programs, instructions and modules stored in the memory 620, so as to implement the page display method of the mobile client. That is, the program when executed by the processor implements:

analyzing second page rendering data corresponding to the target page to acquire page level data corresponding to the target page; the page level data comprises at least one control group and function controls corresponding to the control groups;

The memory 620 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 620 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 non-volatile solid state storage device. In some examples, memory 620 may further include memory located remotely from processor 610, which may be connected to client devices over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The input device 630 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the client device, and may include a keyboard and a mouse, etc. The output device 640 may include a display device such as a display screen.

EXAMPLE seven

Seventh embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the method according to any embodiment of the present invention. Of course, the computer-readable storage medium provided in the embodiments of the present invention may perform related operations in the page displaying method of the mobile client provided in any embodiment of the present invention. That is, the program when executed by the processor implements:

From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.

It should be noted that, in the embodiment of the page display apparatus of the mobile client, each unit and each module included in the page display apparatus are only divided according to functional logic, but are not limited to the above division as long as the corresponding function can be implemented; in addition, the specific names of the functional units are only for the convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.

It is to be noted that the foregoing description is only exemplary of the invention and that the principles of the technology may be employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A page display method of a mobile client is characterized by comprising the following steps:

rendering and displaying the target page according to the control layout data matched with the target page and a preset total data source;

the method for rendering and displaying the target page according to the control layout data matched with the target page and a preset total data source comprises the following steps:

according to the control layout data matched with the target page and a preset total data source, a target adapter matched with the target page is established, wherein the target adapter comprises an adaptive relation between the control layout corresponding to each functional control in the target page and a subdata source matched with each functional control;

and rendering and displaying the target page according to the target adapter matched with the target page.

2. The method of claim 1, wherein the first page rendering data comprises altered page rendering data and a corresponding alteration type identifier; acquiring second page rendering data corresponding to the target page according to the first page rendering data corresponding to the user login role, wherein the second page rendering data comprises:

updating the locally cached historical page rendering data according to the changed page rendering data and the corresponding change type identifier;

and screening the updated historical page rendering data to obtain second page rendering data corresponding to the target page.

3. The method of claim 1, wherein detecting that the target client currently satisfies a predetermined login state detection condition comprises:

when detecting that a target client starts to run in a foreground currently, judging whether the target client is in a logged-on state or not;

if yes, determining that the target client side meets a preset login state detection condition when detecting that the foreground running state of the target client side is not waken from the background to the foreground.

4. The method of claim 3, after determining whether the target client is in a logged-on state, further comprising:

if not, displaying a login page of the target client to the current access user, and acquiring user login information input by the current access user in the login page;

generating a user login authentication request according to the user login information, and sending the user login authentication request to a server;

and when login verification passing information which is fed back by the server and corresponds to the current access user is detected, determining that the target client currently meets the preset login state detection condition.

5. The method of claim 4, wherein detecting that the foreground operating state is not waking from background to foreground comprises:

detecting whether a view component corresponding to a main page of the target client exists in a view component manager of the target client;

if not, determining that the foreground running state is not waken from the background to the foreground.

6. The method of claim 1, wherein establishing a target adapter matching the target page according to the control layout data matching the target page and a preset total data source comprises:

acquiring control layout corresponding to each functional control in the target page according to the control layout data matched with the target page;

determining subdata sources matched with the functional controls in the target page in preset total data sources according to the control identifications corresponding to the functional controls in the target page;

if the historical adapter matched with the target page does not exist, respectively establishing an adaptation relation between the control layout corresponding to each functional control and the sub-data source matched with each functional control through a preset adapter component to obtain the target adapter matched with the target page;

7. The method of claim 1, further comprising, prior to rendering the target page for display according to a target adapter that matches the target page:

acquiring grouping frame layout data corresponding to each control group in the target page according to the control layout data matched with the target page;

rendering and displaying the target page according to the target adapter matched with the target page, wherein the rendering and displaying comprises the following steps:

rendering and displaying the grouping frames corresponding to the control groups in the target page according to the grouping frame layout data corresponding to the control groups in the target page;

acquiring the adaptation relation between the control layout corresponding to each functional control in the target adapter and the sub-data source matched with each functional control;

and rendering and displaying each functional control at the display position of each group frame in the target page by adopting a preset page layout component corresponding to the target page according to the adaptation relation.

8. The method of claim 1, after rendering and displaying the target page according to the target adapter matched with the target page, further comprising:

responding to a click request of a current login user on a target function control in a target page, and acquiring a control identification corresponding to the target function control when a user login role matched with the current login user is determined to have a page jump right corresponding to the target function control;

acquiring a skip page type corresponding to the target function control from second page rendering data corresponding to the target page according to the control identification corresponding to the target function control;

when the jumping page type corresponding to the target function control is detected to be a local page, acquiring a control name corresponding to the function control and a grouping name of control grouping;

acquiring a target jump page identifier corresponding to the target function control, and frame layout data and page content data corresponding to the target jump page identifier according to the control identifier corresponding to the target function control;

rendering and displaying a page frame corresponding to the target jump page according to the frame layout data corresponding to the target jump page identifier;

and rendering and displaying the control name corresponding to the target function control, the grouping name of the control grouping corresponding to the target function control and the page content data corresponding to the target jump page identification at each display position of a page frame corresponding to the target jump page.

9. The method of claim 8, after obtaining the jumped page type corresponding to the target functionality control from the second page rendering data corresponding to the target page according to the control identification corresponding to the target functionality control, further comprising:

when the type of the jump page corresponding to the target function control is detected to be an external webpage, acquiring a standard routing path corresponding to the target function control from second page rendering data corresponding to the target page according to a control identification corresponding to the target function control;

according to the control identification corresponding to the target function control, acquiring a specific routing path corresponding to the target function control in a local cache of a target client;

acquiring a target routing path corresponding to the target function control according to a standard routing path and a specific routing path corresponding to the target function control;

and performing page skipping according to a target routing path corresponding to the target function control through a preset webpage access module.

10. The method according to claim 8, further comprising, after obtaining the jump page type corresponding to the target functionality control from the second page rendering data corresponding to the target page according to the control identification corresponding to the target functionality control:

when the type of the jump page corresponding to the target function control is detected to be a general page, acquiring a general function module identification corresponding to the target function control and a routing path corresponding to the general function module identification according to a control identification corresponding to the target function control;

and accessing the general function module corresponding to the general function module identification according to the routing path corresponding to the general function module identification so as to carry out page jump.

11. The method of claim 6, after rendering and displaying the target page according to the target adapter matched with the target page, further comprising:

when a user login role updating message sent by a server is detected, sending an updating user login role obtaining request to the server through a background processing module of the target client, and receiving an updating user login role matched with a current login user and fed back by the server and third page rendering data corresponding to the updating user login role;

acquiring fourth page rendering data corresponding to a target page according to the third page rendering data corresponding to the user login role through a background processing module of the target client;

analyzing fourth page rendering data corresponding to the target page through a background processing module of the target client, and acquiring updated page level data corresponding to the target page;

acquiring, by a background processing module of the target client, update control layout data matched with the target page from a preset resource pool according to update page level data corresponding to the target page;

updating a target adapter matched with the target page according to the updated control layout data matched with the target page and a preset total data source through a background processing module of the target client;

and rendering and displaying the target page again according to the updated target adapter matched with the target page.

12. A page display device of a mobile client is characterized by comprising:

the page rendering display module is used for rendering and displaying the target page according to the control layout data matched with the target page and a preset total data source;

wherein, the page rendering display module comprises:

13. A client device, the client device comprising:

one or more processors;

storage means for storing one or more programs;

when executed by the one or more processors, cause the one or more processors to implement a page presentation method for a mobile client according to any one of claims 1-11.

14. A computer storage medium on which a computer program is stored, which program, when being executed by a processor, carries out a page presentation method for a mobile client according to any one of claims 1 to 11.