CN108829485B - Application interface layout updating method and device, storage medium and computer equipment - Google Patents
Application interface layout updating method and device, storage medium and computer equipment Download PDFInfo
- Publication number
- CN108829485B CN108829485B CN201810661934.8A CN201810661934A CN108829485B CN 108829485 B CN108829485 B CN 108829485B CN 201810661934 A CN201810661934 A CN 201810661934A CN 108829485 B CN108829485 B CN 108829485B
- Authority
- CN
- China
- Prior art keywords
- interface layout
- interface
- application client
- layout file
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to an updating method, a device, a storage medium and computer equipment of application interface layout, wherein the method comprises the following steps: sending an interface data acquisition request to a server; receiving a new layout file, wherein the new layout file is returned to the application client by the server based on an interface data acquisition request; when detecting a layout updating triggering operation and meeting an interface layout updating condition, acquiring a target view created based on the new layout file; and updating the interface layout of the application client based on the target view. The scheme provided by the application eliminates the limitation that the application client needs to be restarted to enable the update to take effect.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for updating an application interface layout, a computer-readable storage medium, and a computer device.
Background
An application Interface refers to a User Interface (UI) of an application client, which is a window where a User interacts with an application program. In the life cycle of an application program, in order to achieve the purposes of enriching interface functions, improving interface attractiveness, improving interface use convenience and the like, the layout of the application interface is often required to be updated.
In a traditional updating mode, a server releases a new version of an application client, and then a user terminal obtains and installs an installation package of the new version of the application client, so that the layout of an application interface is updated. However, the conventional method needs to restart the application client before the update becomes effective, and has certain limitations.
Disclosure of Invention
Therefore, it is necessary to provide an updating method and apparatus for an application interface layout, a computer-readable storage medium, and a computer device, aiming at the technical problem that in the conventional manner, an application client needs to be restarted to enable an update to take effect, which has certain limitations.
An updating method of an application interface layout comprises the following steps:
sending an interface data acquisition request to a server;
receiving a new interface layout file, and returning the new interface layout file to the application client by the server based on the interface data acquisition request;
when detecting that the interface layout updating triggering operation is carried out and the interface layout updating condition is met, acquiring a target view created based on the new version of interface layout file;
and updating the interface layout of the application client based on the target view.
An application interface layout updating apparatus, comprising:
the data acquisition request sending module is used for sending an interface data acquisition request to the server;
the new version interface layout file receiving module is used for receiving a new version interface layout file, and the new version interface layout file is returned to the application client by the server based on the interface data acquisition request;
the target view acquisition module is used for acquiring a target view created based on the new version interface layout file when the interface layout updating triggering operation is detected and the interface layout updating condition is met;
and the interface layout updating module is used for updating the interface layout of the application client based on the target view.
A computer-readable storage medium, storing a computer program which, when executed by a processor, causes the processor to perform the steps of the method of updating an application interface layout.
A computer device comprising a memory and a processor, the memory storing a computer program which, when executed by the processor, causes the processor to perform the steps of the method of updating an application interface layout.
According to the scheme in the embodiment of the application, the interface data acquisition request is sent to the server, and the new version of the interface layout file returned by the server based on the interface data acquisition request is received. And then, when detecting that the interface layout updating triggering operation is performed and the interface layout updating condition is met, acquiring a target view created based on the new version of interface layout file, and updating the interface layout of the application client based on the target view. Therefore, the interface layout of the application client does not need to be updated by installing the application program, and the limitation that the application client is required to be restarted to enable the update to be effective is eliminated.
Drawings
FIG. 1 is a diagram of an application environment for a method for updating an application interface layout, according to an embodiment;
FIG. 2 is a flowchart illustrating a method for updating an application interface layout according to an embodiment;
FIG. 3 is a schematic diagram of an interface of a QQ space in one embodiment;
FIG. 4 is a schematic diagram of an interface of a QQ space in one embodiment;
FIG. 5 is a flowchart illustrating a method for updating an application interface layout according to an embodiment;
FIG. 6 is a block diagram showing an apparatus for updating a layout of an application interface according to another embodiment;
FIG. 7 is a block diagram of a computer device in one embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Furthermore, the terms "comprise," "include," "have," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, article, or apparatus. Furthermore, the term "and/or," as used herein, includes any and all combinations of one or more of the associated listed items.
The method for updating the layout of the application interface provided by the embodiments of the present application can be applied to the application environment shown in fig. 1. The application environment relates to a user terminal 110 and a server 120, the user terminal 110 and the server 120 being connected via a network. The user terminal 110 may have an application client installed thereon, the server 120 is a background server corresponding to the application client, and the server 120 stores a new version of interface layout file (i.e., the latest version of interface layout file) for the application client.
Specifically, the user terminal 110 transmits an interface data acquisition request to the server 120. After receiving the interface data acquisition request, the server 120 issues a new interface layout file to the user terminal 110 where the application client is located. After receiving the new interface layout file, the user terminal 110 obtains a target view created based on the received new interface layout file when detecting an interface layout update trigger operation and meeting an interface layout update condition, and updates the interface layout of the application client based on the target view.
The user terminal 110 may be a desktop terminal or a mobile terminal, and the mobile terminal may include at least one of a mobile phone, a tablet computer, a notebook computer, a personal digital assistant, a wearable device, and the like. The server 120 may be implemented as a stand-alone physical server or as a server cluster of multiple physical servers.
In one embodiment, as shown in FIG. 2, a method for updating an application interface layout is provided. The method is described as applied to the user terminal 110 in fig. 1. The method may include the following steps S202 to S208.
S202, sending an interface data acquisition request to a server.
The server is a background server corresponding to the application client. The application client is a client to be updated in interface layout, and is a native application program running on an operating system of the user terminal. In one embodiment, the application client may be a feed stream based application. A feed stream is a stream of information that is continuously updated and presented to the user's content. Taking the QQ space as an example, each piece of dynamic content (such as say, log, photo, comment, etc.) in the QQ space can be regarded as a feed, and the feed combination represented by the sliding list in the QQ space can be regarded as a feed stream. Feed stream based applications such as QQ applications (e.g., QQ space functionality), WeChat applications (e.g., circle of friends functionality), micro blogging applications, news applications, and so forth.
In this embodiment, the background server of the application client may be used to provide dynamic content that needs to be presented on an application interface (i.e., a user interface of the application client), and may also be used to provide an interface layout file that needs to be used for performing an application interface layout update. Taking the QQ space as an example, the dynamic content may include the above-described speeches, logs, photos, comments, etc., and taking the news application as an example, the dynamic content may be news content.
The interface data acquisition request may be used to instruct the server to return dynamic content to be displayed on the application interface to the user terminal where the application client is located. It can be understood that, in the running process of the application client, the application client may send an interface data acquisition request to the server when detecting a dynamic content refresh operation, so that the server returns corresponding dynamic content. For example, when the QQ client displays the QQ space interface, the interface data acquisition request may be sent to the QQ backend server when detecting a "pull-down refresh operation" or a "load more trigger operation" so that the QQ backend server returns corresponding dynamic content.
And S204, receiving the new interface layout file, and returning the new interface layout file to the application client based on the interface data acquisition request by the server.
The interface layout file is a file for describing the interface layout of the application client. The interface layout relates to the attributes (such as color, size, etc.) of the views on the interface and the relationship attributes (such as the relative positional relationship between the views, etc.) between the views. As for the data format, the interface layout file may be based on JSON (JavaScript Object notification, a lightweight data exchange format), XML (Extensible Markup Language), or the like.
The new interface layout file is the interface layout file needed to be used for updating the application interface layout at this time. In terms of content, the new version of the interface layout file may be the interface layout file corresponding to the latest version of the application interface. The new interface layout file can be stored in the server, and the server issues the new interface layout file to the user terminal based on the interface data acquisition request from the user terminal.
Specifically, after the server receives the interface data acquisition request sent by the user terminal, the new interface layout file is returned to the user terminal when the current interface layout information of the application client is not matched with the new interface layout file stored by the server. The operation of judging whether the current interface layout information of the application client is matched with the new interface layout file stored by the server can be completed by the user terminal where the application client is located or the server.
And the current interface layout information is used for representing the interface layout file currently used by the application client. That is, based on the current interface layout information, the interface layout file currently used by the application client may be distinguished from other interface layout files.
In one embodiment, the current interface layout information may include the interface layout file itself currently in use by the application client. In another embodiment, the current interface layout information may also include a unique identification of the interface layout file currently used by the application client. The unique identification of the interface layout file may also be referred to as a file fingerprint of the interface layout file, which may be used to distinguish between different interface layout files. Taking the example that the interface layout file is based on the JSON format, the essence of the interface layout file is a string, and the unique identifier of the interface layout file can be a 32-bit feature code obtained based on the string.
It can be understood that the current interface layout information of the application client does not match the new version of the interface layout file, indicating that the current interface layout of the application client on the user terminal is not the latest version of the interface layout but an old version of the interface layout. In this case, the application client needs to update the interface layout, and update the current interface layout from the old interface layout to the latest interface layout. Accordingly, the server can send the new version interface layout file to the application client. It is understood that the server sends data to the application client, that is, the server sends data to the user terminal where the application client is located.
In addition, if the current interface layout information of the application client is matched with the new version of interface layout file, the current interface layout of the application client on the user terminal is shown to be the latest version of interface layout. In this case, the application client need not perform an interface layout update, but may continue to use the current interface layout. Correspondingly, the server does not issue a new interface layout file to the user terminal where the application client is located, the application client does not enter the application interface layout updating process, data filling processing can be directly carried out on the dynamic content sent to the application client based on the server, and the filled application interface is presented to the user.
In one embodiment, when the current interface layout information is the unique identifier of the interface layout file currently used by the application client, the unique identifier of the new version of interface layout file may be obtained. Then, the server or the user terminal where the application client is located compares the unique identifier of the new interface layout file with the current interface layout information, and after the unique identifier of the new interface layout file and the current interface layout information are judged to be inconsistent, the server sends the new interface layout file to the user terminal where the application client is located; and after the two are judged to be consistent, the server does not send a new interface layout file to the user terminal where the application client is located.
In another embodiment, when the current interface layout information is the interface layout file itself currently used by the application client, the user terminal where the server or the application client is located may directly compare the current interface layout information with the new version of the interface layout file itself. Similarly, after judging that the two are inconsistent, the server sends a new interface layout file to the user terminal where the application client is located; and after the two are judged to be consistent, the server does not send a new interface layout file to the user terminal where the application client is located. In addition, the unique identifier of the current interface layout information and the unique identifier of the new version interface layout file can be respectively obtained by the user terminal where the server or the application client is located, and then the two unique identifiers are compared.
And S206, when the interface layout updating triggering operation is detected and the interface layout updating condition is met, acquiring the target view created based on the new interface layout file.
And the interface layout updating triggering operation is used for triggering the application client to start the interface layout updating process. The interface layout update trigger operation may be an operation initiated by a user acting on the application interface. For example, the interface layout update triggering operation may specifically be that the user clicks an interface layout update triggering control on the application interface. The interface layout update trigger control may be a control having a "trigger interface layout update" functionality. For another example, the interface layout update triggering operation may be a movement operation specific to a predetermined trajectory of the application interface.
In one embodiment, a dynamic content refresh operation may be used as an interface layout update trigger operation. That is, the dynamic content refresh operation may be used to trigger initiation of an interface layout update procedure. For example, when the QQ client displays the QQ space interface, both the "pull-down refresh operation" and the "load more trigger operation" may be used as the interface layout update trigger operation, and both the "pull-down refresh operation" and the "load more trigger operation" may be used to trigger the start of the QQ space interface layout update process.
In this embodiment, the starting of the interface layout updating process may be the application client starting to execute an operation of determining whether the interface layout updating condition is satisfied. The interface layout update condition may include: the unique identification of the currently available interface layout file recorded by the interface layout manager does not match the interface layout file currently used by the application client. If the application client receives a new interface layout file issued by the server, the new interface layout file is the current available interface layout file, and the interface layout manager records the unique identifier of the new interface layout file.
In this embodiment, if the interface layout update condition is satisfied, the operation of obtaining the target view created based on the new version of the interface layout file and the subsequent operation are continuously executed; and if the interface layout updating condition is not met, ending the updating process of the application interface layout.
Wherein the target view is a view created based on the new version of the interface layout file. The view may be a view control. It should be noted that in the Android (Android) system, view controls can be roughly divided into two types: view and Viewgroup. View is the base class of all UI components on the application interface, and ViewGroup is the container that holds these UI components, i.e., the interface layout manager, which itself is also derived from View.
And S208, updating the interface layout of the application client based on the target view.
In this embodiment, after the application client obtains the target view, the interface layout of the application client may be updated based on the target view. Updating the interface layout of the application client may include updating properties of the views themselves and/or relationship properties between the views. And after the updating of the interface layout is completed, the interface layout displayed by the application client corresponds to the target view.
It should be noted that, in practical applications, after the updating of the interface layout is completed, data filling processing may be performed based on the dynamic content sent by the server to the application client, and then the filled application interface is presented to the user. It will be appreciated that the application interface presented to the user accordingly will present the updated interface layout.
The following description is given with reference to a specific application example. For the QQ space android integrated version, the interface layout of the QQ space is as shown in FIG. 3 before a certain update of the interface layout is performed. The new interface layout file stored in the server is different from the interface layout file currently used in the QQ space (hereinafter referred to as an old interface layout file) in that the background color of the view corresponding to the nickname area of the avatar on the QQ space interface in the old interface layout file is white, whereas the background color of the view corresponding to the nickname area of the avatar on the QQ space interface in the new interface layout file is red. In this case, the user terminal receives a new version of the interface layout file delivered by the server, and when detecting a "pull-down refresh operation" or a "load more trigger operation" and determining that an interface layout update condition is satisfied, obtains a target view created based on the new version of the interface layout file, and updates the interface layout of the application client based on the target view, where the interface layout of the QQ space is as shown in fig. 4 (oblique hatching represents red in fig. 4). In this process, upon updating the interface layout of the application client based on the target view, the update takes effect immediately without restarting the QQ space.
The updating method of the application interface layout sends the interface data acquisition request to the server and receives the new version of the interface layout file returned by the server based on the interface data acquisition request. And then, when detecting that the interface layout updating triggering operation is performed and the interface layout updating condition is met, acquiring a target view created based on the new version of the interface layout file, and updating the interface layout of the application client based on the target view. Therefore, the interface layout of the application client does not need to be updated by installing an application program, the limitation that the application client needs to be restarted to enable the updating to be effective is eliminated, the updated interface layout takes effect immediately after the updating operation of the interface layout is completed, the speed of the updated interface layout application and the speed of problem repair are improved, and the real-time performance of the updated interface layout application is improved; then, the whole interface layout updating process before the updated interface layout is displayed has no perception to the user; in addition, when the application client requests the server for the dynamic content each time, the detection of whether the application client needs to perform interface layout updating is triggered once, so that the timeliness of the interface layout updating can be ensured.
In an embodiment, the method for updating an application interface layout provided in the embodiments of the present application may further include the following steps: receiving target interface layout information returned by a server based on an interface data acquisition request; acquiring current interface layout information of an application client; judging whether the current interface layout information is matched with the target interface layout information; and when the interface layout information is not matched with the target interface layout information, sending an interface layout file acquisition request to the server, wherein the interface layout file acquisition request is used for indicating the server to return a new version of interface layout file corresponding to the target interface layout information to the application client.
In this embodiment, the user terminal where the application client is located may complete the operation of determining whether the current interface layout information of the application client matches the new version of interface layout file stored by the server. Specifically, the interface data acquisition request may be used to request target interface layout information from the server in addition to the dynamic content from the server.
The target interface layout information may be used to characterize a new version of the interface layout file stored by the server. That is, the new version of the interface layout file stored by the server may be distinguished from other interface layout files based on the target interface layout information. Similarly, in one embodiment, the target interface layout information may include a unique identification of the new version of the interface layout file.
In one embodiment, the application client sends an interface data acquisition request to the server, and the server returns target interface layout information to the application client based on the interface data acquisition request. The application client side obtains the current interface layout information of the application client side and judges whether the current interface layout information is matched with the target interface layout information. And if not, indicating that the current interface layout of the application client on the user terminal is not the latest interface layout but the old interface layout. In this case, the application client needs to update the interface layout, and then sends an interface layout file acquisition request to the server, and after receiving the interface layout file acquisition request, the server returns a new version of interface layout file corresponding to the target interface layout information to the application client; and if the current interface layout of the application client on the user terminal is matched with the latest interface layout, the current interface layout of the application client on the user terminal is shown to be the latest interface layout. In this case, the application client may continue to use the current interface layout without updating the interface layout, and accordingly, the application client does not send an interface data acquisition request to the server, and the server does not return an interface layout file corresponding to the target interface layout information to the application client.
In one embodiment, the interface data acquisition request carries current interface layout information of the application client; and the new interface layout file is returned to the application client by the server when the current interface layout information does not match the new interface layout file.
In this embodiment, the server may complete an operation of determining whether the current interface layout information of the application client matches a new version of interface layout file stored by the server. Specifically, the interface data acquisition request is used for requesting the server for the dynamic content, and may also carry current interface layout information of the application client, that is, each time the application client requests the server for the dynamic content, the application client may notify the server of the current interface layout file used by the application client, so that the server may determine whether the application client needs to perform interface layout update.
Specifically, after receiving an interface data acquisition request, the server determines whether current interface layout information carried by the interface data acquisition request matches a new version of interface layout file stored by the server. If the current interface layout of the application client on the user terminal is not the latest interface layout but the old interface layout, the server returns a new interface layout file to the application client; and if the current interface layout of the application client on the user terminal is matched with the latest interface layout, the current interface layout of the application client on the user terminal is shown to be the latest interface layout. In this case, the application client does not need to update the interface layout, but can continue to use the current interface layout, and accordingly, the server does not return the latest version of the interface layout file stored by the server to the application client.
It should be noted that, in the case that the interface data acquisition request carries the current interface layout information of the application client, compared with the scheme that the current interface layout information is the interface layout file itself currently used by the application client, the scheme that the current interface layout information is the unique identifier of the interface layout file currently used by the application client can reduce the data transmission amount between the application client and the server, and improve the transmission efficiency.
In an embodiment, the step of acquiring the target view created based on the new version interface layout file when the interface layout update triggering operation is detected and the interface layout update condition is satisfied in the foregoing, that is, step S206, may include the following steps: when detecting that the interface layout updating triggering operation is performed and the interface layout updating condition is met, analyzing a new interface layout file; and creating a target view based on the information obtained by analyzing the new version interface layout file.
In this embodiment, when the application client detects an interface layout update triggering operation and determines that an interface layout update condition is satisfied, a target view is created immediately based on a new version of an interface layout file. It should be noted that, when applied to the android system, the main thread (i.e., UI thread) may perform an operation of creating a target view based on the new version of the interface layout file.
In an embodiment, when the interface layout update triggering operation is detected and the interface layout update condition is satisfied, before the target view created based on the new version of the interface layout file is acquired, that is, before step S206, the following steps may be further included: analyzing the new interface layout file; and creating and storing the target view based on the information obtained by analyzing the new version interface layout file.
In this embodiment, the application client creates the target view in advance before detecting the interface layout update triggering operation and determining that the interface layout update condition is satisfied. When the target view is needed to be used subsequently, namely the interface layout updating triggering operation is detected and the interface layout updating condition is determined to be met, the interface layout updating triggering operation is not required to be established immediately, but the interface layout updating triggering operation is directly obtained from a local cache. The embodiment can effectively reduce the frame dropping rate and optimize the user experience.
In addition, because the new interface layout file is issued through the network, the problems of operation issuing errors, operator hijacking, network packet loss, data verification errors and the like can occur, and the target view is created in advance and can be used for verifying the availability of the new interface layout file; specifically, the target view is successfully created to indicate that the new version of the interface layout file is available, otherwise, the target view is unsuccessfully created to indicate that the new version of the interface layout file is unavailable. When the new version of the interface layout file is available (namely, after the target view is successfully created), the storage operation is executed, so that large-scale software crash (namely, software crash, which is embodied as flash back) can be effectively avoided.
In one embodiment, storing the target View may specifically be storing the created target View in a singleton object with key-value pairs of < MD5, View [ ] >, the singleton object being globally accessible.
In an embodiment, in the method for updating an application interface layout according to the embodiments of the present application, the step of receiving a new version of an interface layout file described in the foregoing may be implemented by an asynchronous thread; and analyzing the new interface layout file through the asynchronous thread, and creating and storing a target view based on the information obtained by analyzing the new interface layout file.
The asynchronous thread is a thread which can be run in parallel with the main thread, and is different from the main thread.
It should be noted that, when the UI component of the application interface is complex, if the target view is created by the main thread following the system creation timing, the frame rate may be decreased.
Accordingly, in this embodiment, the new interface layout file may be received by the asynchronous thread, and immediately after the new interface layout file is received, the asynchronous thread may parse the new interface layout file, and create and store the target view based on information obtained by parsing the new interface layout file. Therefore, the purpose of avoiding the main thread from being blocked can be achieved, and the software responsiveness can be effectively improved.
In an embodiment, the method for updating an application interface layout according to the embodiments of the present application may further include the following steps: acquiring a unique identifier of a current available interface layout file from an interface layout manager of an application client; and when the unique identifier of the currently available interface layout file is inconsistent with the unique identifier of the currently used interface layout file of the application client, judging that the interface layout updating condition is met.
As described above, the interface layout update condition may include: the unique identification of the currently available interface layout file recorded by the interface layout manager does not match the interface layout file currently used by the application client.
In one embodiment, the application client may obtain the unique identifier of the new version interface layout file after receiving the new version interface layout file sent by the server and confirming that the new version interface layout file is available. And then, recording the obtained unique identifier of the new interface layout file as the unique identifier of the current available interface layout file through the interface layout manager so as to be used for subsequently judging whether the interface layout updating condition is met.
Specifically, after the unique identifier of the new interface layout file is obtained, the unique identifier of the new interface layout file may be used to replace the unique identifier of the currently available interface layout file recorded by the interface layout manager before the unique identifier of the new interface layout file is obtained, so that the unique identifier of the currently available interface layout file recorded by the interface layout manager is updated to the unique identifier of the new interface layout file.
Taking the application to the android system as an example, before judging whether the interface layout updating condition is met, the main thread may first obtain the unique identifier of the currently available interface layout file from the interface layout manager of the application client. Then, the main thread compares the consistency of the unique identifier of the currently available interface layout file with the unique identifier of the currently used interface layout file of the application client; and when the two are not consistent, judging that the interface layout updating condition is met, and when the two are consistent, judging that the interface layout updating condition is not met.
In one embodiment, the step of updating the interface layout of the application client based on the target view, which is described in the foregoing, i.e., step S208, may include the following steps: and replacing the full amount of the current view with the target view, wherein the current view is a view created based on the interface layout file currently used by the application client.
The current view is a view created based on an interface layout file currently used by the application client. That is, for one application interface layout update, the current view is the view for use by the interface display before the update operation is performed, and the target view is the view for use by the interface display after the update operation is completed.
For example, for a certain application interface layout update Up, before performing the update operation, the application client performs an interface display based on the View View 1. After the update operation is performed, the View View1 is replaced with the View View 2. The application client performs an interface display based on the View View2 before performing the next application interface layout update. For the application interface layout update Up, the View View1 is the current View, and the View View2 is the target View.
In this embodiment, the interface layout of the application client is updated in a global refresh manner, that is, the current view is discarded and replaced by the target view. Specifically, replacing the current view full size with the target view may be: and binding the variable defined in the interface layout manager with each sub-view in the target view, and redirecting the variable reference defined in the interface layout manager into each sub-view in the target view after the binding operation. Because the reference variable is unchanged, the change is transparent to subsequent operations such as data setting and the like, the code change amount can be effectively reduced, and the logic risk is avoided.
In one embodiment, the step of updating the interface layout of the application client based on the target view, which is described in the foregoing, i.e., step S208, may include the following steps: comparing the target view with the current view and determining a minimum update set; the current view is a view created based on an interface layout file currently used by the application client; and updating the interface layout of the application client based on the minimum update set.
It should be noted that, in the global refresh mode, resource consumption is large. Accordingly, in the embodiment, the interface layout of the application client can be updated in a local refresh mode, that is, the same part in the current view and the target view does not need to be refreshed, and only the part with the difference between the current view and the target view is refreshed, so that the time consumption for refreshing is reduced.
Specifically, the target view and the current view may be compared by a predetermined difference calculation method, thereby determining the minimum update set. The interface layout of the application client is then updated based on the minimum update set. The predetermined difference calculation method may be set based on actual requirements, for example, a dom diff mode may be selected.
In one embodiment, as shown in FIG. 5, a method for updating an application interface layout is provided. The method is described as applied to the user terminal 110 in fig. 1. The method may include the following steps S502 to S520.
S502, an interface data acquisition request is sent to the server, the interface data acquisition request carries current interface layout information of the application client, and the current interface layout information comprises a unique identifier of an interface layout file currently used by the application client.
S504, receiving the new interface layout file through the asynchronous thread, and returning the new interface layout file to the application client by the server when the current interface layout information is not matched with the new interface layout file.
S506, analyzing the new interface layout file through the asynchronous thread, and creating and storing a target view based on information obtained by analyzing the new interface layout file.
And S508, acquiring the unique identifier of the new interface layout file, and updating the unique identifier of the current available interface layout file recorded by the interface layout manager based on the unique identifier of the new interface layout file.
S510, judging whether an interface layout updating triggering operation is detected; if so, jumping to S512, and if not, not entering an interface layout updating process;
s512, judging whether the unique identifier of the current available interface layout file acquired from the interface layout manager of the application client is consistent with the unique identifier of the current interface layout file used by the application client; if not, jumping to S514, and if so, performing data filling processing directly based on the dynamic content sent to the application client by the server.
And S514, acquiring the target view from the local cache, if the target view is not acquired, jumping to the step S516, and if the target view is acquired, jumping to the step S518.
S516, creating a target view based on the new version interface layout file through the main thread;
s518, replacing the total amount of the current view with a target view, wherein the current view is a view created based on an interface layout file currently used by the application client.
S520, data filling processing is carried out on the basis of the target view and the dynamic content sent to the application client by the server, and a filled application interface is displayed.
It should be noted that specific limitations on each technical feature in this embodiment may be the same as the limitations on the corresponding technical feature in the foregoing, and are not repeated herein.
It should be understood that, under reasonable circumstances, although the steps in the flowcharts referred to in the foregoing embodiments are shown in sequence as indicated by the arrows, the steps are not necessarily executed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in each flowchart may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
In one embodiment, as shown in FIG. 6, an apparatus 600 for updating an application interface is provided. The apparatus may include the following modules 602-608.
A data obtaining request sending module 602, configured to send an interface data obtaining request to the server.
A new version file receiving module 604, configured to receive a new version interface layout file, where the new version interface layout file is returned to the application client by the server based on the interface data obtaining request;
and a target view obtaining module 606, configured to obtain a target view created based on the new version of the interface layout file when the interface layout update trigger operation is detected and the interface layout update condition is met.
An interface layout update module 608 for updating the interface layout of the application client based on the target view.
The above-mentioned updating apparatus 600 for application interface,
and sending an interface data acquisition request to the server, and receiving a new version of interface layout file returned by the server based on the interface data acquisition request. And then, when detecting that the interface layout updating triggering operation is performed and the interface layout updating condition is met, acquiring a target view created based on the new version of the interface layout file, and updating the interface layout of the application client based on the target view. Therefore, the interface layout of the application client does not need to be updated by installing an application program, the limitation that the application client needs to be restarted to enable the updating to be effective is eliminated, the updated interface layout takes effect immediately after the updating operation of the interface layout is completed, the speed of the updated interface layout application and the speed of problem repair are improved, and the real-time performance of the updated interface layout application is improved; then, the whole interface layout updating process before the updated interface layout is displayed has no perception to the user; in addition, when the application client requests the server for the dynamic content each time, the detection of whether the application client needs to perform interface layout updating is triggered once, so that the timeliness of the interface layout updating can be ensured.
In one embodiment, the apparatus 600 for updating an application interface may further include the following modules: the target interface layout information receiving module is used for receiving target interface layout information returned by the server based on the interface data acquisition request; the current interface layout information acquisition module is used for acquiring current interface layout information of the application client; the matching judgment module is used for judging whether the current interface layout information is matched with the target interface layout information; and the layout file acquisition request sending module is used for sending an interface layout file acquisition request to the server when the interface layout file acquisition request is not matched, and the interface layout file acquisition request is used for indicating the server to return a new version of interface layout file corresponding to the target interface layout information to the application client.
In one embodiment, the interface data acquisition request carries current interface layout information of the application client; and returning the new interface layout file to the application client by the server when the current interface layout information is not matched with the new interface layout file.
In one embodiment, the apparatus 600 for updating an application interface may further include the following modules: the interface layout file analysis module is used for analyzing the new interface layout file; and the target view creating and storing module is used for creating and storing the target view based on the information obtained by analyzing the new version interface layout file.
In an embodiment, the new version file receiving module 604 may be specifically configured to implement a step of receiving a new version interface layout file through an asynchronous thread; the interface layout file analysis module can be specifically used for analyzing a new interface layout file through an asynchronous thread; the target view creating and storing module may be specifically configured to create and store the target view based on information obtained by parsing the new version interface layout file.
In one embodiment, the target view acquisition module 606 may include the following elements: the interface layout file analysis unit is used for analyzing the new interface layout file when detecting the interface layout updating triggering operation and meeting the interface layout updating condition; and the target view creating unit is used for creating a target view based on the information obtained by analyzing the new version interface layout file.
In one embodiment, the apparatus 600 for updating an application interface may further include the following modules: the unique identifier acquisition module is used for acquiring a unique identifier of a current available interface layout file from an interface layout manager of the application client; and the satisfaction updating condition judging module is used for judging that the interface layout updating condition is satisfied when the unique identifier of the currently available interface layout file is inconsistent with the unique identifier of the currently used interface layout file of the application client.
In one embodiment, the interface layout update module 608 may be specifically configured to: and replacing the full amount of the current view with the target view, wherein the current view is a view created based on the interface layout file currently used by the application client.
In one embodiment, the interface layout update module 608 may include the following elements:
a minimum update set determination unit for comparing the target view and the current view and determining a minimum update set; the current view is a view created based on an interface layout file currently used by the application client;
and the application interface layout updating unit is used for updating the interface layout of the application client based on the minimum update set.
In one embodiment, the current interface layout information includes a unique identification of the interface layout file currently used by the application client.
It should be noted that, for specific limitations of the above-mentioned updating apparatus 600 for an application interface, reference may be made to the above limitations of the updating method for an application interface layout, and details are not described here again. The modules in the application interface updating apparatus 600 may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the method for providing an update of an application interface layout according to any embodiment of the present application when executing the computer program.
In one embodiment, a computer device is provided, which may be a user terminal, and its internal structure diagram may be as shown in fig. 7. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected by a system bus. Wherein the processor is configured to provide computational and control capabilities. The memory includes a nonvolatile storage medium storing an operating system and a computer program, and an internal memory providing an environment for the operating system and the computer program in the nonvolatile storage medium to run, and the computer program is executed by the processor to implement an update method of an application interface layout. The network interface is used for communicating with an external terminal through a network connection. The display may be a liquid crystal display or an electronic ink display. The input device of the computer equipment can be a touch layer covered on a display screen, a key, a track ball or a touch pad arranged on a shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, the application interface updating apparatus provided in the present application may be implemented in a form of a computer program, and the computer program may be run on a computer device as shown in fig. 7. The memory of the computer device may store various program modules constituting the updating means of the application interface, such as a data acquisition request sending module 602, a new version file receiving module 604, an object view acquiring module 606, and an interface layout updating module 608 shown in fig. 6. The computer program constituted by the respective program modules causes the processor to execute the steps in the update method of the application interface layout of the respective embodiments of the present application described in the present specification. For example, the computer device shown in fig. 7 may execute step S202 through the data acquisition request sending module 602 in the updating apparatus 600 of the application interface shown in fig. 6, execute step S204 through the new version file receiving module 604, execute step S206 through the target view acquiring module 606, execute step S208 through the interface layout updating module 608, and so on.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
Accordingly, in one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, which, when being executed by a processor, implements the steps of any of the embodiments of the present application in providing an update method of an application interface layout.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (22)
1. An updating method of application interface layout is characterized by comprising the following steps:
when the dynamic content refreshing operation is detected, sending an interface data acquisition request to a server; the interface data acquisition request is used for indicating the server to return dynamic contents to be displayed on the application interface to the user terminal where the application client based on the feed stream is located;
receiving a new interface layout file, and returning the new interface layout file to an application client by the server based on the interface data acquisition request;
when detecting that the interface layout updating triggering operation is carried out and the interface layout updating condition is met, acquiring a target view created based on the new version of interface layout file; the interface layout updating condition comprises that the unique identifier of the current available interface layout file recorded by an interface layout manager of the application client is not matched with the currently used interface layout file of the application client, and the current available interface layout file is the latest interface layout file received by the application client;
and updating the interface layout of the application client based on the target view.
2. The method of claim 1, further comprising:
receiving target interface layout information returned by the server based on the interface data acquisition request;
acquiring current interface layout information of the application client;
judging whether the current interface layout information is matched with the target interface layout information;
and when the interface layout information is not matched with the target interface layout information, sending an interface layout file acquisition request to the server, wherein the interface layout file acquisition request is used for indicating the server to return a new version of interface layout file corresponding to the target interface layout information to the application client.
3. The method according to claim 1, wherein the interface data acquisition request carries current interface layout information of the application client;
and returning the new interface layout file to the application client by the server when the current interface layout information is judged not to match the new interface layout file.
4. The method according to claim 1, before acquiring the target view created based on the new version interface layout file when the interface layout update triggering operation is detected and the interface layout update condition is satisfied, further comprising:
analyzing the new interface layout file;
and creating and storing a target view based on the information obtained by analyzing the new version interface layout file.
5. The method of claim 4, wherein:
receiving the new interface layout file through an asynchronous thread;
and analyzing the new interface layout file through the asynchronous thread, and creating and storing a target view based on information obtained by analyzing the new interface layout file.
6. The method according to claim 1, wherein when the interface layout update triggering operation is detected and the interface layout update condition is satisfied, acquiring the target view created based on the new version of the interface layout file comprises:
when detecting that the interface layout updating triggering operation is carried out and the interface layout updating condition is met, analyzing the new interface layout file;
and creating a target view based on the information obtained by analyzing the new version interface layout file.
7. The method of claim 1, further comprising:
acquiring a unique identifier of a current available interface layout file from an interface layout manager of the application client;
and when the unique identifier of the currently available interface layout file is inconsistent with the unique identifier of the currently used interface layout file of the application client, judging that the interface layout updating condition is met.
8. The method of claim 1, wherein the updating the interface layout of the application client based on the target view comprises:
and replacing the total amount of the current view, which is the view created based on the interface layout file currently used by the application client, with the target view.
9. The method of claim 1, wherein updating the interface layout of the application client based on the target view comprises:
comparing the target view with the current view and determining a minimum update set; the current view is a view created based on an interface layout file currently used by the application client;
updating the interface layout of the application client based on the minimum update set.
10. The method of claim 2 or 3, wherein the current interface layout information comprises a unique identification of an interface layout file currently used by the application client.
11. An application interface layout updating apparatus, comprising:
the data acquisition request sending module is used for sending an interface data acquisition request to the server when the dynamic content refreshing operation is detected; the interface data acquisition request is used for indicating the server to return dynamic contents to be displayed on the application interface to the user terminal where the application client based on the feed stream is located;
the new version interface layout file receiving module is used for receiving a new version interface layout file, and the new version interface layout file is returned to the application client by the server based on the interface data acquisition request;
the target view acquisition module is used for acquiring a target view created based on the new version interface layout file when the interface layout updating triggering operation is detected and the interface layout updating condition is met; the interface layout updating condition comprises that the unique identifier of the current available interface layout file recorded by an interface layout manager of the application client is not matched with the currently used interface layout file of the application client, and the current available interface layout file is the latest interface layout file received by the application client;
and the interface layout updating module is used for updating the interface layout of the application client based on the target view.
12. The apparatus of claim 11, further comprising:
the target interface layout information receiving module is used for receiving target interface layout information returned by the server based on the interface data acquisition request;
the current interface layout information acquisition module is used for acquiring the current interface layout information of the application client;
the matching judgment module is used for judging whether the current interface layout information is matched with the target interface layout information;
and the layout file acquisition request sending module is used for sending an interface layout file acquisition request to the server when the interface layout file acquisition request is not matched, and the interface layout file acquisition request is used for indicating the server to return a new version of interface layout file corresponding to the target interface layout information to the application client.
13. The apparatus according to claim 11, wherein the interface data obtaining request carries current interface layout information of the application client; and returning the new interface layout file to the application client by the server when the current interface layout information is judged not to match the new interface layout file.
14. The apparatus of claim 11, further comprising:
the interface layout file analysis module is used for analyzing the new interface layout file;
and the target view creating and storing module is used for creating and storing the target view based on the information obtained by analyzing the new version interface layout file.
15. The apparatus of claim 14,
the new version file receiving module is also used for receiving the new version interface layout file through an asynchronous thread;
the interface layout file analysis module is also used for analyzing the new interface layout file through the asynchronous thread;
and the target view creating and storing module is also used for creating and storing the target view based on the information obtained by analyzing the new version interface layout file.
16. The apparatus of claim 11, wherein the target view acquisition module comprises:
the interface layout file analyzing unit is used for analyzing the new interface layout file when detecting that the interface layout updating triggering operation is detected and the interface layout updating condition is met;
and the target view creating unit is used for creating a target view based on the information obtained by analyzing the new version interface layout file.
17. The apparatus of claim 11, further comprising:
the unique identifier acquisition module is used for acquiring a unique identifier of a current available interface layout file from an interface layout manager of the application client;
and the satisfaction updating condition judging module is used for judging that the interface layout updating condition is satisfied when the unique identifier of the currently available interface layout file is inconsistent with the unique identifier of the currently used interface layout file of the application client.
18. The apparatus of claim 11, wherein the interface layout update module is further configured to replace a full amount of a current view with a target view, wherein the current view is a view created based on an interface layout file currently used by the application client.
19. The apparatus of claim 11, wherein the interface layout update module further comprises:
a minimum update set determining unit, configured to compare the target view with the current view, and determine a minimum update set; the current view is a view created based on an interface layout file currently used by the application client;
and the application interface layout updating unit is used for updating the interface layout of the application client based on the minimum update set.
20. The apparatus of claim 12 or 13, wherein the current interface layout information comprises a unique identification of an interface layout file currently used by the application client.
21. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 10.
22. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor realizes the steps of the method of any one of claims 1 to 10 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810661934.8A CN108829485B (en) | 2018-06-25 | 2018-06-25 | Application interface layout updating method and device, storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810661934.8A CN108829485B (en) | 2018-06-25 | 2018-06-25 | Application interface layout updating method and device, storage medium and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108829485A CN108829485A (en) | 2018-11-16 |
| CN108829485B true CN108829485B (en) | 2021-03-02 |
Family
ID=64138282
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810661934.8A Active CN108829485B (en) | 2018-06-25 | 2018-06-25 | Application interface layout updating method and device, storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108829485B (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109471648A (en) * | 2018-11-08 | 2019-03-15 | 网宿科技股份有限公司 | Screen layout's data processing method, device, electronic equipment and storage medium |
| CN109800039B (en) * | 2018-11-28 | 2020-01-24 | 北京三快在线科技有限公司 | User interface display method and device, electronic equipment and storage medium |
| CN111367518B (en) * | 2018-12-26 | 2024-04-05 | 三六零科技集团有限公司 | Page layout method, page layout device, computing equipment and computer storage medium |
| CN111722890A (en) * | 2019-03-18 | 2020-09-29 | 阿里巴巴集团控股有限公司 | Application interface display method, device, equipment and storage medium |
| CN110109729B (en) * | 2019-05-13 | 2022-09-06 | 百度在线网络技术（北京）有限公司 | Interface layout adjustment method and device, electronic equipment and storage medium |
| CN110147381B (en) * | 2019-05-27 | 2021-07-09 | 智者四海（北京）技术有限公司 | Information processing method, system and recording medium |
| CN111427652B (en) * | 2020-03-31 | 2023-05-19 | 苏宁云计算有限公司 | Display method, device, medium and computer equipment of custom button |
| CN111638897B (en) * | 2020-06-02 | 2023-09-26 | 驭新智行科技(宁波)有限公司 | System updating method, device, terminal equipment and storage medium |
| CN112114913B (en) * | 2020-07-27 | 2022-08-09 | 广东太平洋互联网信息服务有限公司 | Application program interface updating method and device, computer equipment and storage medium |
| CN112527351B (en) * | 2020-12-07 | 2024-06-04 | 深圳创维－Rgb电子有限公司 | Method, system, equipment and storage medium for remotely updating terminal application interface layout |
| CN112882772B (en) * | 2021-03-24 | 2022-04-22 | 腾讯科技（深圳）有限公司 | Configuration method of application interface of mobile terminal, mobile terminal and storage medium |
| CN116074435A (en) * | 2022-12-23 | 2023-05-05 | 深圳前海百递网络有限公司 | Method and device for updating small component, electronic equipment and computer storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105159999A (en) * | 2015-09-08 | 2015-12-16 | 百度在线网络技术（北京）有限公司 | Dynamic page displaying method and dynamic page displaying device |
| CN106502699A (en) * | 2016-11-03 | 2017-03-15 | 腾讯科技（深圳）有限公司 | A kind of five application page processing method, apparatus and system |
| CN106598574A (en) * | 2016-11-25 | 2017-04-26 | 腾讯科技（深圳）有限公司 | Method and device for page rendering |
| CN107168999A (en) * | 2017-03-30 | 2017-09-15 | 咪咕数字传媒有限公司 | A kind of method for updating pages and device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101697123A (en) * | 2009-10-20 | 2010-04-21 | 金蝶软件（中国）有限公司 | Method and device for modifying interface layout in ERP system and ERP system |
| CN102622238A (en) * | 2012-03-15 | 2012-08-01 | 中兴通讯股份有限公司 | Method and device for interface layout of mobile devices |
| US9397844B2 (en) * | 2012-09-11 | 2016-07-19 | Apple Inc. | Automated graphical user-interface layout |
| CN106250158A (en) * | 2016-08-01 | 2016-12-21 | 广州优视网络科技有限公司 | The layout method of a kind of client end interface, device and mobile device |
| CN107066258B (en) * | 2017-03-06 | 2020-10-16 | 武汉斗鱼网络科技有限公司 | Page identification image updating method and system |
-
2018
- 2018-06-25 CN CN201810661934.8A patent/CN108829485B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105159999A (en) * | 2015-09-08 | 2015-12-16 | 百度在线网络技术（北京）有限公司 | Dynamic page displaying method and dynamic page displaying device |
| CN106502699A (en) * | 2016-11-03 | 2017-03-15 | 腾讯科技（深圳）有限公司 | A kind of five application page processing method, apparatus and system |
| CN106598574A (en) * | 2016-11-25 | 2017-04-26 | 腾讯科技（深圳）有限公司 | Method and device for page rendering |
| CN107168999A (en) * | 2017-03-30 | 2017-09-15 | 咪咕数字传媒有限公司 | A kind of method for updating pages and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108829485A (en) | 2018-11-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108829485B (en) | Application interface layout updating method and device, storage medium and computer equipment | |
| CN109672741B (en) | Micro-service monitoring method and device, computer equipment and storage medium | |
| CN108848142B (en) | Message pushing method and device, computer equipment and storage medium | |
| CN108804159B (en) | Javascript module loading method and preprocessing method and device thereof, and computer equipment | |
| CN107135218B (en) | Login state obtaining and sending method, credential configuration method, client and server | |
| CN108829477B (en) | Interface jump method, device, computer equipment and storage medium | |
| CN109814854B (en) | Project framework generation method, device, computer equipment and storage medium | |
| CN110688598B (en) | Service parameter acquisition method and device, computer equipment and storage medium | |
| CN110866198B (en) | Static resource caching method, system, device, computer equipment and storage medium | |
| CN108959384B (en) | Webpage data acquisition method and device, computer equipment and storage medium | |
| CN112114913B (en) | Application program interface updating method and device, computer equipment and storage medium | |
| CN108446172B (en) | Data calling method and device, computer equipment and storage medium | |
| CN108595697B (en) | Webpage integration method, device and system | |
| CN111736811A (en) | Form data verification method, system, server and user terminal | |
| CN110765379A (en) | Method and device for loading resource file, computer equipment and storage medium | |
| CN110888709A (en) | Intelligent operation method and device of monitoring screen, computer equipment and storage medium | |
| CN110659092A (en) | Webpage screenshot method and device, computer equipment and storage medium | |
| US9706006B2 (en) | System and method of context aware adaption of content for a mobile device | |
| CN110780939A (en) | Method and device for loading resource file, computer equipment and storage medium | |
| CN111431767B (en) | Multi-browser resource synchronization method and device, computer equipment and storage medium | |
| CN110020280B (en) | Application page display method and device, storage medium and computer equipment | |
| CN111309991B (en) | Query statement generation method and device and data query method and system | |
| CN110362341B (en) | Business management method, device, equipment and storage medium based on micro-service architecture | |
| CN111026988A (en) | Page loading method, device and system and computer equipment | |
| CN109542962B (en) | Data processing method, data processing device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |