CN106406846B - Display interface creating method and device - Google Patents

Abstract

The application discloses a display interface creating method and device. Wherein, the method comprises the following steps: after entering a display interface, acquiring an interface template file for configuring the display interface; analyzing the interface template file, and acquiring the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface; acquiring a component object of each component according to the component information of each component; and assembling each component object to a corresponding position in the display interface according to the position information of each component to generate a new display interface. The method and the device solve the technical problem that the client is frequently updated due to the change of the display interface because the template for controlling the display interface cannot be updated independently.

Description

Display interface creating method and device

Technical Field

The application relates to the field of mobile terminals, in particular to a display interface creating method and device.

Background

In recent years, with the popularization of intelligent terminals and the internet, the life style of people is gradually changed by the intelligent terminals and the internet. For example: shopping through the network mall, selecting games through the network game center, interacting with friends through a social network, and the like.

With the increase of the usage of the intelligent terminal and the internet, the number of network companies providing various network services is also gradually increased. In order to improve the user experience and the user stickiness, a network company usually develops a corresponding client according to the product content of its own network service product.

For the development of the client, especially when the interface development is performed on an interface with a large number of repeated interfaces and a part of personalized function interfaces, one of the important problems is how to dynamically display each function of the application program in the interface, for example: a merchant display interface, a game area interface, a personal center interface and the like. The interfaces described above are typically used to present the same type of content. However, when the content is displayed through the interface, in order to highlight the characteristics of the displayed content, there is a demand for personalized setting of the content displayed on the interface.

In existing solutions, a limited number of fixed presentation templates are typically provided for selection by the user. When a new display template needs to be added in the client program, the display template needs to be updated by issuing a new client program package, or the display template in the client program needs to be updated in an incremental updating mode by issuing a plug-in update package containing the new display template, and a Web page is embedded in the client program, and the display template is updated by utilizing the Web page.

The method for updating the display template for personalized setting in the display interface in the manner has the following disadvantages:

1. when the display template is updated by releasing a new client-side program package, all the contents of the application program are required to be downloaded for each update, and many users are unwilling to wait because the time required for downloading is long. Meanwhile, in the case of using a mobile network, downloading the application program requires consuming a large amount of traffic resources, which will generate additional costs. Moreover, even if the downloading is completed, the user is required to install the program again, the updating step is too complicated, and the installation interface is not friendly to the user, which affects the use experience of the user.

2. In the method of updating the presentation template in the client program in an incremental updating mode by issuing a plug-in update package containing a new presentation template, the following disadvantages exist: many client programs do not support plug-in development by themselves. Therefore, when the plug-in development aiming at the client program is carried out, what is needed to be solved is how to load the codes in the plug-in update package on the original client program, so that the development cost is greatly increased. Meanwhile, the display template is updated in the above manner, so that many potential safety hazards exist, and the security of the personal information of the user is not protected.

3. Although the method of embedding the Web page in the client program and updating the display template by using the Web page can well solve the problem of updating the display template, the Web page has limited functions, and sometimes the requirement of the display interface on the function realization aspect cannot be met. In addition, the web page is affected by the hardware environment and the local software environment of the client program installation, and the display effect of the web page is not easy to control.

In view of the above problems, no effective solution has been proposed.

Disclosure of Invention

The embodiment of the invention provides a method and a device for creating a display interface, which at least solve the technical problem that a client is frequently updated due to the change of the display interface because a template for controlling the display interface cannot be independently updated.

According to an aspect of an embodiment of the present invention, there is provided a method for creating a display interface, including: after entering a display interface, acquiring an interface template file for configuring the display interface; analyzing the interface template file, and acquiring the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface; acquiring a component object of each component according to the component information of each component; and assembling each component object to a corresponding position in the display interface according to the position information of each component to generate a new display interface.

According to another aspect of the embodiments of the present invention, there is also provided a display interface creating apparatus, including: the first acquisition module is used for acquiring an interface template file for configuring a display interface after entering the display interface; a second obtaining module, configured to parse the interface template file, and obtain component information of each component included in the interface template file, where the component information at least includes: the name of the component, the type of the component and the position information of the component in the display interface; the third acquisition module is used for acquiring the component object of each component according to the component information of each component; and the assembling module is used for assembling each component object to the corresponding position in the display interface according to the position information of each component to generate a new display interface.

In the embodiment of the invention, after entering the display interface, the interface template file for configuring the display interface is acquired; analyzing the interface template file, and acquiring the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface; acquiring a component object of each component according to the component information of each component; assembling each component object to a corresponding position in a display interface according to the position information of each component, and generating a new display interface, wherein the first acquisition module is used for acquiring an interface template file for configuring the display interface after entering the display interface; a second obtaining module, configured to parse the interface template file, and obtain component information of each component included in the interface template file, where the component information at least includes: the name of the component, the type of the component and the position information of the component in the display interface; the third acquisition module is used for acquiring the component object of each component according to the component information of each component; the assembling module is used for assembling each component object to a corresponding position in the display interface according to the position information of each component to generate a new display interface, and the purpose of conveniently carrying out self-defining setting on the display interface is achieved, so that the technical effect that the new display interface can be generated only by updating the interface template file is achieved, and the technical problem that the client is frequently updated due to the change of the display interface because the template used for controlling the display interface cannot be independently updated is solved.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a block diagram of a hardware structure of a computer terminal of a method for creating a display interface according to an embodiment of the present application;

FIG. 2 is a flowchart of a method for creating a display interface according to a first embodiment of the present application;

FIG. 3 is an interface schematic diagram of a client-side primary interface according to an embodiment of the application;

FIG. 4 is a first game community interface schematic of a client primary interface according to an embodiment of the present application;

FIG. 5 is a second game community interface schematic of a client primary interface according to an embodiment of the present application;

FIG. 6 is a flowchart illustrating steps in a method for creating an alternative display interface according to a first embodiment of the present application;

FIG. 7 is a schematic diagram of a server configuration template interface according to an embodiment of the present application;

FIG. 8 is a flowchart illustrating steps in a method for creating an alternative display interface according to a first embodiment of the present application; and

fig. 9 is a block diagram of a device for creating a display interface according to a first embodiment of the present application; and

fig. 10 is a block diagram of a computer terminal according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The terms referred to in this application are to be construed as follows:

homogeneous interface: the core contents of the plurality of display interfaces are similar, but each display interface has independent personalized requirements, and the personalized requirements may be different in the module placement position or different in the content displayed inside the module.

Example 1

In accordance with an embodiment of the present application, there is provided a method embodiment of a method for creating a display interface, it should be noted that the steps illustrated in the flowchart of the drawings may be performed in a computer system such as a set of computer executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.

The method provided by the first embodiment of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking an example of the application running on a computer terminal, fig. 1 is a hardware structure block diagram of a computer terminal of a method for creating a display interface according to an embodiment of the present application. As shown in fig. 1, the computer terminal 10 may include one or more (only one shown) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.

The memory 104 may be configured to store software programs and modules of application software, such as program instructions/modules corresponding to the method for creating a display interface in the embodiment of the present application, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implements the method for creating a display interface described above. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the computer terminal 10 via 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 transmission device 106 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device 106 can be a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.

Fig. 2 is a flowchart of a method for creating a display interface according to a first embodiment of the present application, where in the foregoing operating environment, the present application provides the method for creating a display interface shown in fig. 2, where the method includes:

step S102, after entering the display interface, acquiring an interface template file for configuring the display interface.

Specifically, the client acquires an interface template file for configuring the display interface from a predetermined location through step S102. The interface template file acquired by the client can be changed according to different interface display contents, namely, the interface template file corresponding to the interface display contents can be acquired at the client according to the interface display contents. The interface template file may be cached in the cache of the client, may be stored in a local designated location, and may of course be stored in a server corresponding to the client.

Step S104, analyzing the interface template file, and acquiring the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface.

Specifically, in step S104, the client performs parsing processing on the obtained interface template file, and obtains the component name, the component type, and the location information in the display interface of each component included in the interface template file through parsing.

When the client is developed, the component name and/or the component type can be set for each component object in the client, and when the interface template file is edited, the operations of adding the component to the interface, deleting the component and the like can be realized only by editing the component name and/or the component type corresponding to the component object. The component object is a set of function functions in the client for implementing certain functions.

And step S106, acquiring the component object of each component according to the component information of each component.

And S108, assembling each component object to a corresponding position in the display interface according to the position information of each component, and generating a new display interface.

Specifically, in step S108, according to the position information corresponding to the component name included in the interface template file, the component object obtained according to the component name is assembled into the display interface, so that the display interface corresponding to the interface template file can be generated.

In practical applications, the detailed description is given by using a client installed in a mobile intelligent terminal. The client is a platform for providing exclusive game communities for game players according to games, and meanwhile, communication platforms can be provided for the game players in the game communities. As shown in fig. 3, the display interface at this time is a main interface of the game community, and the main interface includes community lists of a plurality of game communities. And when the user clicks the game icon corresponding to the game community in the community list, the client enters a display page of the game community. The display page of the game community can include functions related to the game, such as game downloading, game gift bag getting, personal game information checking, game strategy checking, game topic checking, game video checking, game forum checking and the like. In the display pages of different game communities, the similarity of the game community interfaces is high because the included functions are largely the same and slightly different. However, in order to reflect the difference between games, as shown in fig. 4 and fig. 5, the display page needs to be customized, so that the display page has differences, for example: the number of components of the types of page information columns, navigation columns, advertising columns, information columns, video columns, topic columns and the like in the display interface, the arrangement sequence among the components and the like are changed.

In the development process, if the interface is not set individually by using the interface template file, a set of interface needs to be developed for each game community independently, so that a large number of repeated codes appear, the size of the file installed on the client side is increased, and the interface of a game area is not convenient to adjust.

Therefore, the game communities with different display interfaces can be generated by individually setting the interface template files corresponding to the game communities and configuring different interface template files for different games in the background according to the methods described in steps S102 to S108. Therefore, the game community interfaces corresponding to different games can be customized, and the difference among the game communities can be generated. Meanwhile, the content of the special area can be flexibly configured according to the operation strategy of the user.

Specifically, in the development process, component objects corresponding to component types are generated according to components of types such as a page information bar, a navigation bar, an advertisement bar, an information bar, a video bar and a topic bar in a display interface. For example, taking the display interface shown in fig. 3 as an example, when a user clicks a "enter a special area" button of a "magic dragon and warrior", the user enters a certain game community, at this time, the game client obtains an interface template file corresponding to the game community according to the identifier of the game community, obtains component objects according to component information obtained by analyzing the interface template, and fills each component object to a corresponding position in the display interface according to the position information. And finally, rendering each component object by the client to generate a new display interface corresponding to the interface template file.

Through the method of analyzing the acquired interface template file in the steps from S102 to S108 and generating a new display interface according to the component information obtained through analysis, the technical effect that a new display interface can be generated only by updating the interface template file is achieved. Therefore, the purpose of conveniently carrying out user-defined setting on the display interface is achieved. Therefore, the technical problem that the client is frequently updated due to the change of the display interface because the template for controlling the display interface cannot be independently updated in the prior art is solved.

As an alternative embodiment, the step S102 of obtaining an interface template file for configuring a display interface includes:

and step S21, inquiring whether an interface template file for configuring a display interface is cached from the local cache.

And step S23, if the interface template file is cached in the local cache, reading the interface template file cached in the local cache.

And step S25, if the interface template file is not cached in the local cache, acquiring a pre-configured interface template file by accessing the first server.

Through steps S21 to S25, when the interface template file for configuring the display interface is acquired, first, whether the interface template file for configuring the display interface is cached in the local cache is queried. The interface template file cached in the local cache may be an interface template file downloaded from the server to the local cache when the client is operated last time, or an interface template file directly stored in the local cache when the client is installed. Typically, there will be several different interface template files corresponding to the display interface at the client. At this time, when inquiring whether the interface template file for configuring the display interface is cached from the local cache, it is also necessary to inquire whether the interface template file corresponding to the current display interface is cached. And when the interface template file corresponding to the current display interface is cached in the local cache, directly reading the interface template file from the local cache. When the interface template file is not cached in the local cache, the interface template file corresponding to the current display interface is acquired by accessing the first server.

In practical applications, the implementation method for obtaining the pre-configured interface template file by accessing the first server includes many methods. The client may send acquisition information for acquiring the interface template file to the first server, and after receiving the acquisition information, the first server pushes the corresponding interface template file to the client. The interface template file for the current display interface can be directly downloaded by accessing the storage address for storing the interface template file in the first server through the client. Of course, the interface template file may also be obtained by other methods, which are not described herein.

As an alternative embodiment, as shown in fig. 6, after reading the interface template file cached in the local cache in step S23, the method further includes:

step S241, reading the first version information of the cached interface template file.

In step S243, second version information of the interface template file stored in the first server is obtained.

Step S245, comparing the first version information and the second version information of the interface template file.

In step S247, in the case that the first version information and the second version information are the same, a new display interface is generated using the interface template file already cached in the local cache.

Step S249, when the first version information is different from the second version information and the first version information is the latest version information, obtain the interface template file of the latest version from the first server.

Specifically, the interface template file may further include version information for recording a version of the interface template file. After the interface template file cached in the local cache is read, through the steps S241 to S249, the first version information of the interface template file cached in the local cache is compared with the second version information of the interface template file corresponding to the first version information stored in the first server, so as to determine whether the interface template file read from the local cache is the interface template file of the latest version. Therefore, the version of the interface template file is always the latest.

As an alternative embodiment, before the step S25 obtaining the pre-configured interface template file by accessing the first server, the method further includes:

step S41, selecting at least one component from the template component list stored in the first server, wherein the template component list is displayed in the template configuration interface of the first server.

Step S43, triggering a drag event of the selected at least one component, dragging the selected at least one component to a predetermined area, and recording position information of the at least one component in the predetermined area.

And step S45, generating an interface template file according to the selected at least one component and the position information of the at least one component in the preset area.

Step S47, storing the interface template file and the identification information associated with the interface template file in the first server, where after receiving the access request of the front-end client in the first server, the first server returns the acquired corresponding interface template file to the front-end client according to the identification information carried in the access request.

Specifically, before the interface template file is acquired, the interface template file needs to be edited. The function module for editing the interface template file may be disposed in the first server, and the template component list holding various components may be disposed in the first server. As shown in fig. 7, in a template configuration interface disposed in a first server, at least one component in a template component list is dragged to an interface preview position in the template configuration interface in a dragging manner as needed, and a position coordinate where the component is placed in the template configuration interface is recorded. And generating a new interface template file according to the component type and/or the component name dragged to the template configuration interface and the position coordinate, and storing the new interface template file in the first server after setting the association relationship between the interface template file and the display interface. Of course, the function module for editing the interface template file and the template configuration interface for editing the interface template file may also be disposed in the client or other servers. After the interface template file is edited by the client or other servers, the interface template file is uploaded to the first server, which is not described herein.

As an alternative embodiment, the step S106 obtains the component object of each component according to the component information of each component, and includes:

in step S61, the component name and the component type of any one of the components are identified.

Step S63, obtaining the component metadata of the corresponding component according to the component name and the component type.

In step S65, a component object corresponding to the component is created according to the component metadata of the component.

Wherein the source code of the component metadata corresponding thereto is acquired in the memory for storing the component metadata according to the component name and the component type through steps S61 to S65. And packaging the acquired source code, and creating to obtain a component object corresponding to the component name and the component type. Through the steps, the component metadata is obtained and encapsulated according to the component name and the component type, and the flexibility of generating the display interface through the interface template file is further improved.

As an optional embodiment, the already displayed components in the display interface at least include components included in a new display interface, where step S108 assembles each component object to a corresponding position in the display interface according to the position information of each component, and generates the new display interface, including:

in step S81, the component name and the original location information of each component that have been displayed in the display interface are read locally.

Step S83, matching the component name of each component contained in the interface template file with the component name of each component already displayed in the display interface.

And step S85, extracting the components with the same component names as the components already displayed in the display interface from the interface template file, and generating at least one updated component.

And step S87, moving the component with the same component name as the updated component in the display interface to the corresponding position according to the position information of the updated component.

In step S89, after the components in the interface template file except the updated component are mounted at the predetermined position of the display interface, a new display interface is generated.

Specifically, as shown in fig. 8, the component name and the original location information of the component already displayed in the current display interface are obtained through steps S81 to S89, and are respectively matched with the component name and the location information included in the interface template file, so as to determine whether the component already displayed in the current display interface is consistent with the new display interface generated according to the interface template file. Firstly, matching the component name of the displayed component in the current display interface with the component name contained in the interface template file, extracting the component with the same name as the component name in the displayed interface in the current display interface in the interface template file, and generating an updated component containing the component name and the original component position information. And comparing the component name of the updated component with the original component position information and the position information corresponding to the component name in the interface template file. And when the original assembly position information is different from the position information contained in the interface template file, generating a new display interface according to the position information contained in the interface template file.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

Example 2

According to an embodiment of the present application, there is also provided a display interface creating apparatus for implementing the display interface creating method, as shown in fig. 9, the apparatus includes: a first acquisition module 32, a second acquisition module 34, a third acquisition module 36, and an assembly module 38.

The first obtaining module 32 is configured to obtain an interface template file for configuring a display interface after entering the display interface; a second obtaining module 34, configured to parse the interface template file, and obtain component information of each component included in the interface template file, where the component information at least includes: the name of the component, the type of the component and the position information of the component in the display interface; a third obtaining module 36, configured to obtain a component object of each component according to the component information of each component; and the assembling module 38 is configured to assemble each component object to a corresponding position in the display interface according to the position information of each component, so as to generate a new display interface.

By the first acquisition module 32, the second acquisition module 34, the third acquisition module 36 and the assembly module 38 described above. The method for analyzing the acquired interface template file and generating the new display interface according to the component information obtained by analyzing achieves the technical effect that the new display interface can be generated only by updating the interface template file. Therefore, the purpose of conveniently carrying out user-defined setting on the display interface is achieved. Therefore, the technical problem that the client is frequently updated due to the change of the display interface because the template for controlling the display interface cannot be independently updated in the prior art is solved.

As an alternative embodiment, the first obtaining module 32 includes: a first sub-query module 321, a first sub-read module 323, and a first sub-acquisition module 325.

The first sub-query module 321 is configured to query whether an interface template file for configuring a display interface is cached from a local cache; the first sub-reading module 323 is configured to, if the interface template file is cached in the local cache, read the cached interface template file in the local cache; the first sub-obtaining module 325 is configured to, if the interface template file is not cached in the local cache, obtain a pre-configured interface template file by accessing the first server.

When the interface template file for configuring the display interface is obtained by the first sub-query module 321, the first sub-reading module 323, and the first sub-obtaining module 325, it is first queried in the local cache whether to cache the interface template file for configuring the display interface. The interface template file cached in the local cache may be an interface template file downloaded from the server to the local cache when the client is operated last time, or an interface template file directly stored in the local cache when the client is installed. Typically, there will be several different interface template files corresponding to the display interface at the client. At this time, when inquiring whether the interface template file for configuring the display interface is cached from the local cache, it is also necessary to inquire whether the interface template file corresponding to the current display interface is cached. And when the interface template file corresponding to the current display interface is cached in the local cache, directly reading the interface template file from the local cache. When the interface template file is not cached in the local cache, the interface template file corresponding to the current display interface is acquired by accessing the first server.

As an optional embodiment, the apparatus may further include: a reading module 241, a fourth obtaining module 243, a comparing module 245 and a fifth obtaining module 249.

The reading module 241 is configured to read first version information of the cached interface template file; a fourth obtaining module 243, configured to obtain second version information of the interface template file stored in the first server; a comparing module 245, configured to compare the first version information and the second version information of the interface template file; a first generating module 247, configured to generate a new display interface by using the interface template file cached in the local cache if the first version information and the second version information are the same; a fifth obtaining module 249, configured to obtain the interface template file of the latest version from the first server when the first version information is different from the second version information and the first version information is the latest version information.

Specifically, the interface template file may further include version information for recording a version of the interface template file. After the interface template file cached in the local cache is read, the first version information of the interface template file cached in the local cache is compared with the second version information of the interface template file corresponding to the first version information stored in the first server through the reading module 241, the fourth obtaining module 243, the comparing module 245 and the fifth obtaining module 249, so that whether the interface template file read from the local cache is the interface template file of the latest version or not is judged. Therefore, the version of the interface template file is always the latest.

As an optional embodiment, the apparatus may further include: a selecting module 41, a processing module 43, a second generating module 45 and a storing module 47.

The selecting module 41 is configured to select at least one component from a template component list stored in the first server, where the template component list is displayed in a template configuration interface of the first server; the processing module 43 is configured to trigger a drag event of the selected at least one component, drag the selected at least one component to a predetermined area, and record position information of the at least one component in the predetermined area; the second generating module 45 is configured to generate an interface template file according to the selected at least one component and the position information of the at least one component in the predetermined area; and the storage module 47 is configured to store the interface template file and the identification information associated with the interface template file in the first server, where after receiving an access request of the front-end client in the first server, the storage module returns the acquired corresponding interface template file to the front-end client according to the identification information carried in the access request.

Specifically, before the interface template file is acquired, the interface template file needs to be edited. The function module for editing the interface template file may be disposed in the first server, and the template component list holding various components may be disposed in the first server. As shown in fig. 7, in a template configuration interface disposed in a first server, at least one component in a template component list is dragged to an interface preview position in the template configuration interface in a dragging manner as needed, and a position coordinate where the component is placed in the template configuration interface is recorded. And generating a new interface template file according to the component type and/or the component name dragged to the template configuration interface and the position coordinate, and storing the new interface template file in the first server after setting the association relationship between the interface template file and the display interface. Of course, the function module for editing the interface template file and the template configuration interface for editing the interface template file may also be disposed in the client or other servers. After the interface template file is edited by the client or other servers, the interface template file is uploaded to the first server, which is not described herein.

As an alternative embodiment, the third obtaining module 36 includes: a sub-identification module 361, a second sub-acquisition module 363, and a sub-creation module 365.

The sub-identification module 361 is used for identifying the component name and the component type of any one component; a second sub-obtaining module 363, configured to obtain component metadata of a corresponding component according to a component name and a component type; the sub-creation module 365 is configured to create a component object corresponding to a component according to the component metadata of the component.

The sub-identification module 361, the second sub-obtaining module 363, and the sub-creation module 365 obtain the source code of the component metadata corresponding to the component name and the component type from the storage for storing the component metadata. And packaging the acquired source code, and creating to obtain a component object corresponding to the component name and the component type. Through the steps, the component metadata is obtained and encapsulated according to the component name and the component type, and the flexibility of generating the display interface through the interface template file is further improved.

As an alternative embodiment, the components already displayed in the display interface at least include components included in the new display interface, wherein the assembly module 38 includes: a second sub reading module 381, a sub matching module 383, a first sub generating module 385, a sub moving module 387, and a second sub generating module 389.

The second sub-reading module 381 is configured to locally read the component name and the original location information of each component that has been displayed in the display interface; a sub-matching module 383, configured to match the component name of each component included in the interface template file with the component name of each component already displayed in the display interface; a first sub-generation module 385, configured to extract, from the interface template file, a component having the same component name as a component already displayed in the display interface, and generate at least one updated component; the sub-moving module 387 is configured to move, according to the location information of the updated component, a component having the same component name as the updated component in the display interface to a corresponding location; a second sub-generation module 389, configured to generate a new display interface after assembling components in the interface template file, except for the updated component, at the predetermined position of the display interface.

Specifically, as shown in fig. 8, the second sub-reading module 381, the sub-matching module 383, the first sub-generating module 385, the sub-moving module 387, and the second sub-generating module 389 are used to obtain the component name and the original location information of the component that has been displayed in the current display interface, and respectively match the component name and the original location information with the component name and the location information that are included in the interface template file, so as to determine whether the component that has been displayed in the current display interface is consistent with the new display interface that is generated according to the interface template file. Firstly, matching the component name of the displayed component in the current display interface with the component name contained in the interface template file, extracting the component with the same name as the component name in the displayed interface in the current display interface in the interface template file, and generating an updated component containing the component name and the original component position information. And comparing the component name of the updated component with the original component position information and the position information corresponding to the component name in the interface template file. And when the original assembly position information is different from the position information contained in the interface template file, generating a new display interface according to the position information contained in the interface template file.

Example 3

According to the embodiment of the application, a computer terminal for implementing the method for creating the display interface is also provided, and the computer terminal can be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal may also be replaced with a terminal device such as a mobile terminal.

In this embodiment, the computer terminal may execute the program code of the following steps in the method for creating a display interface: after entering a display interface, acquiring an interface template file for configuring the display interface; analyzing the interface template file, and acquiring the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface; acquiring a component object of each component according to the component information of each component; and assembling each component object to a corresponding position in the display interface according to the position information of each component to generate a new display interface.

Optionally, fig. 10 is a block diagram of a computer terminal according to an embodiment of the present application. As shown in fig. 10, the computer terminal a may include: one or more processors 51 (only one of which is shown), a memory 53, and a transmission device 55.

The memory 53 may be used to store software programs and modules, such as program instructions/modules corresponding to the device and creation of the display interface in the embodiment of the present invention, and the processor 51 executes various functional applications and data processing by running the software programs and modules stored in the memory 53, that is, implements the above-mentioned method for creating the display interface. The memory 53 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 53 may further include memory located remotely from the processor 51, which may be connected to terminal a via 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 transmission means 55 is used for receiving or transmitting data via a network. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 55 includes a network adapter (NIC) that can be connected to a router via a network cable and other network devices to communicate with the internet or a local area network. In one example, the transmission device 55 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

Specifically, the memory 53 is used for storing preset action conditions, information of preset authorized users, and application programs.

The processor 51 may call the information and applications stored in the memory 53 through the transmission device to perform the following steps: after entering a display interface, acquiring an interface template file for configuring the display interface; analyzing the interface template file, and acquiring the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface; acquiring a component object of each component according to the component information of each component; and assembling each component object to a corresponding position in the display interface according to the position information of each component to generate a new display interface.

Optionally, the processor 51 may further execute program codes of the following steps: inquiring whether an interface template file for configuring a display interface is cached from a local cache; if the interface template file is cached in the local cache, reading the cached interface template file in the local cache; and if the interface template file is not cached in the local cache, acquiring a pre-configured interface template file by accessing the first server.

Optionally, the processor 51 may further execute program codes of the following steps: reading first version information of the cached interface template file; acquiring second version information of an interface template file stored in a first server; comparing the first version information and the second version information of the interface template file; under the condition that the first version information is the same as the second version information, generating a new display interface by using an interface template file cached in a local cache; and acquiring the interface template file of the latest version from the first server under the condition that the first version information is different from the second version information and the first version information is the latest version information.

Optionally, the processor 51 may further execute program codes of the following steps: selecting at least one component from a template component list stored by a first server, wherein the template component list is displayed in a template configuration interface of the first server; triggering a dragging event of the selected at least one component, dragging the selected at least one component to a preset area, and recording position information of the at least one component in the preset area; generating an interface template file according to the selected at least one component and the position information of the at least one component in the preset area; and storing the interface template file and the identification information associated with the interface template file in a first server, wherein after receiving an access request of the front-end client in the first server, the first server returns the acquired corresponding interface template file to the front-end client according to the identification information carried in the access request.

Optionally, the processor 51 may further execute program codes of the following steps: identifying the component name and the component type of any one component; acquiring component metadata of a corresponding component according to the component name and the component type; and creating a component object corresponding to the component according to the component metadata of the component.

Optionally, the processor 51 may further execute program codes of the following steps: assembling each component object to a corresponding position in the display interface according to the position information of each component, wherein the step of generating a new display interface comprises the following steps: reading the component name and the original position information of each component which is displayed in the display interface locally; matching the component name of each component contained in the interface template file with the component name of each component already displayed in the display interface; extracting components with the same component names as the components already displayed in the display interface from the interface template file, and generating at least one updating component; according to the position information of the updated assembly, moving the assembly with the same assembly name as the updated assembly in the display interface to a corresponding position; and generating a new display interface after assembling the components except the updated component in the interface template file at the preset position of the display interface.

Optionally, the specific examples in this embodiment may refer to the examples described in embodiment 1 and embodiment 2, and this embodiment is not described herein again.

Example 4

Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the storage medium may be configured to store a program code executed by the method for creating a display interface provided in the first embodiment.

Optionally, in this embodiment, the storage medium may be located in at least one of a plurality of network devices in a computer network.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:

s1, after entering the display interface, acquiring an interface template file for configuring the display interface;

s2, analyzing the interface template file, and obtaining the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface;

s3, acquiring the component object of each component according to the component information of each component;

and S4, assembling each component object to the corresponding position in the display interface according to the position information of each component, and generating a new display interface.

Optionally, the storage medium is further arranged to store program code for performing the steps of: inquiring whether an interface template file for configuring a display interface is cached from a local cache; if the interface template file is cached in the local cache, reading the cached interface template file in the local cache; and if the interface template file is not cached in the local cache, acquiring a pre-configured interface template file by accessing the first server.

Optionally, the storage medium is further configured to store first version information of the interface template file cached for program code reading for performing the following steps; acquiring second version information of an interface template file stored in a first server; comparing the first version information and the second version information of the interface template file; under the condition that the first version information is the same as the second version information, generating a new display interface by using an interface template file cached in a local cache; and acquiring the interface template file of the latest version from the first server under the condition that the first version information is different from the second version information and the first version information is the latest version information.

Optionally, the storage medium is further arranged to store program code for performing the steps of: selecting at least one component from a template component list stored by a first server, wherein the template component list is displayed in a template configuration interface of the first server; triggering a dragging event of the selected at least one component, dragging the selected at least one component to a preset area, and recording position information of the at least one component in the preset area; generating an interface template file according to the selected at least one component and the position information of the at least one component in the preset area; and storing the interface template file and the identification information associated with the interface template file in a first server, wherein after receiving an access request of the front-end client in the first server, the first server returns the acquired corresponding interface template file to the front-end client according to the identification information carried in the access request.

Optionally, the storage medium is further arranged to store program code for performing the steps of: identifying the component name and the component type of any one component; acquiring component metadata of a corresponding component according to the component name and the component type; and creating a component object corresponding to the component according to the component metadata of the component.

Optionally, the storage medium is further arranged to store program code for performing the steps of:

s1, account data are cached to a local cache, wherein the account data comprise at least any one or more of the following data: and the third party account, the inquired unified account corresponding to the third party account and the generation time of the unified account are obtained.

Optionally, the storage medium is further arranged to store program code for performing the steps of: assembling each component object to a corresponding position in the display interface according to the position information of each component, wherein the step of generating a new display interface comprises the following steps: reading the component name and the original position information of each component which is displayed in the display interface locally; matching the component name of each component contained in the interface template file with the component name of each component already displayed in the display interface; extracting components with the same component names as the components already displayed in the display interface from the interface template file, and generating at least one updating component; according to the position information of the updated assembly, moving the assembly with the same assembly name as the updated assembly in the display interface to a corresponding position; and generating a new display interface after assembling the components except the updated component in the interface template file at the preset position of the display interface.

Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

Optionally, the specific examples in this embodiment may refer to the examples described in embodiment 1 and embodiment 2, and this embodiment is not described herein again.

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including instructions for causing one or more computer devices (which may be personal computers, servers, network devices, or the like) to execute all or part of the steps of the method described in the embodiments of the present application.

In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.

Claims (11)

1. A method for creating a display interface, comprising:

after entering a display interface, acquiring an interface template file for configuring the display interface;

analyzing the interface template file, and acquiring the component information of each component contained in the interface template file, wherein the component information at least comprises: the name of the component, the type of the component and the position information of the component in the display interface;

acquiring the component object of each component according to the component information of each component;

assembling each component object to a corresponding position in the display interface according to the position information of each component to generate a new display interface;

the acquiring of the interface template file for configuring the display interface includes:

inquiring whether the interface template file for configuring the display interface is cached from a local cache;

if the interface template file is cached in the local cache, reading the interface template file cached in the local cache;

reading first version information of the cached interface template file;

acquiring second version information of the interface template file stored in a first server;

comparing the first version information and the second version information of the interface template file;

under the condition that the first version information and the second version information are the same, generating the new display interface by using the interface template file cached in a local cache;

acquiring the interface template file of the latest version from the first server under the condition that the first version information is different from the second version information and the first version information is the latest version information;

acquiring second version information of the interface template file stored in the first server, including:

sending acquisition information for acquiring the interface template file to the first server, and receiving the pushed interface template file after the first server receives the acquisition information; or

And accessing a storage address used for storing the interface template file in the first server, and directly downloading the interface template file for the current display interface.

2. The method of claim 1, wherein after querying from a local cache whether the interface template file for configuring the display interface is cached, the method further comprises:

and if the interface template file is not cached in the local cache, acquiring the pre-configured interface template file by accessing a first server.

3. The method of claim 2, wherein prior to obtaining the pre-configured interface template file by accessing the first server, the method further comprises:

selecting at least one component from a template component list stored by the first server, wherein the template component list is displayed in a template configuration interface of the first server;

triggering a dragging event of the selected at least one component, dragging the selected at least one component to a preset area, and recording position information of the at least one component in the preset area;

generating the interface template file according to the selected at least one component and the position information of the at least one component in the preset area;

storing the interface template file and identification information associated with the interface template file in the first server, wherein,

and after receiving an access request of a front-end client in the first server, returning the acquired corresponding interface template file to the front-end client according to identification information carried in the access request.

4. The method according to claim 1, wherein obtaining the component object of each component according to the component information of each component comprises:

identifying the component name and the component type of any one component;

acquiring component metadata of a corresponding component according to the component name and the component type;

and creating the component object of the corresponding component according to the component metadata of the component.

5. The method according to any one of claims 1 to 3, wherein the components already displayed in the display interface include at least components included in the new display interface, wherein,

assembling each component object to a corresponding position in the display interface according to the position information of each component, wherein the step of generating a new display interface comprises the following steps:

locally reading the component name and the original position information of each component which is already displayed in the display interface;

matching the component name of each component contained in the interface template file with the component name of each component already displayed in the display interface;

extracting components with the same component names as the components already displayed in the display interface from the interface template file, and generating at least one updating component;

according to the position information of the updating component, moving a component with the same component name as the updating component in the display interface to a corresponding position;

generating the new display interface after assembling the components in the interface template file except the updated component at the preset position of the display interface.

6. An apparatus for creating a display interface, comprising:

the device comprises a first acquisition module, a second acquisition module and a display module, wherein the first acquisition module is used for acquiring an interface template file for configuring a display interface after entering the display interface;

a second obtaining module, configured to parse the interface template file, and obtain component information of each component included in the interface template file, where the component information at least includes: the name of the component, the type of the component and the position information of the component in the display interface;

a third obtaining module, configured to obtain a component object of each component according to the component information of each component;

the assembly module is used for assembling each component object to a corresponding position in the display interface according to the position information of each component to generate a new display interface;

wherein the first obtaining module comprises:

the first sub-query module is used for querying whether the interface template file for configuring the display interface is cached from a local cache;

the first sub-reading module is used for reading the interface template file cached in the local cache if the interface template file is cached in the local cache;

the reading module is used for reading the cached first version information of the interface template file;

the fourth obtaining module is used for obtaining second version information of the interface template file stored in the first server;

the comparison module is used for comparing the first version information and the second version information of the interface template file;

a first generation module, configured to generate the new display interface by using the interface template file cached in a local cache under the condition that the first version information is the same as the second version information;

a fifth obtaining module, configured to obtain, from the first server, an interface template file of a latest version when the first version information is different from the second version information and the first version information is latest version information;

wherein the fourth obtaining module is further configured to

Sending acquisition information for acquiring the interface template file to the first server, and receiving the pushed interface template file after the first server receives the acquisition information; or

And accessing a storage address used for storing the interface template file in the first server, and directly downloading the interface template file for the current display interface.

7. The apparatus of claim 6, wherein the first obtaining module further comprises:

the first sub-obtaining module is configured to, after querying whether the interface template file for configuring the display interface is cached from a local cache, obtain a pre-configured interface template file by accessing a first server if the interface template file is not cached in the local cache.

8. The apparatus of claim 7, further comprising:

the selection module is used for selecting at least one component from a template component list stored in the first server, wherein the template component list is displayed in a template configuration interface of the first server;

the processing module is used for triggering a dragging event of the selected at least one component, dragging the selected at least one component to a preset area, and recording position information of the at least one component in the preset area;

the second generation module is used for generating the interface template file according to the selected at least one component and the position information of the at least one component in the preset area;

a storage module, configured to store the interface template file and identification information associated with the interface template file in the first server, where,

and after receiving an access request of a front-end client in the first server, returning the acquired corresponding interface template file to the front-end client according to identification information carried in the access request.

9. The apparatus of claim 6, wherein the third obtaining module comprises:

the sub-identification module is used for identifying the component name and the component type of any one component;

the second sub-acquisition module is used for acquiring component metadata of a corresponding component according to the component name and the component type;

and the sub-creation module is used for creating the component object of the corresponding component according to the component metadata of the component.

10. The apparatus according to any one of claims 6 to 8, wherein the components already displayed in the display interface at least include components included in the new display interface, wherein the assembling module comprises:

the second sub-reading module is used for locally reading the component name and the original position information of each component which is displayed in the display interface;

the sub-matching module is used for matching the component name of each component contained in the interface template file with the component name of each component already displayed in the display interface;

the first sub-generation module is used for extracting components with the same component names as the components already displayed in the display interface from the interface template file and generating at least one updating component;

the sub-moving module is used for moving the component with the same component name as the updated component in the display interface to a corresponding position according to the position information of the updated component;

and the second sub-generation module is used for generating the new display interface after the components except the updated component in the interface template file are assembled at the preset position of the display interface.

11. A storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 5 when executed.

Images