CN112860259B

CN112860259B - Interface processing method, device, electronic equipment and storage medium

Info

Publication number: CN112860259B
Application number: CN202110353511.1A
Authority: CN
Inventors: 王伟; 徐博; 周访
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-03-31
Filing date: 2021-03-31
Publication date: 2024-02-06
Anticipated expiration: 2041-03-31
Also published as: CN112860259A

Abstract

The present disclosure provides an interface processing method applied to the financial field or other fields. The method comprises the steps of obtaining an interface generation request aiming at a target interface; analyzing the interface generation request to obtain M interface components corresponding to the target interface, wherein M is more than or equal to 1; determining a markup language file corresponding to the interface member from a markup language file library aiming at each interface member in the M interface members, wherein the markup language file corresponding to the interface member comprises interface elements for describing the interface member, and the interface elements are obtained by marking the elements for describing the interface member by using the markup language; and analyzing the M markup language files to obtain interface execution sentences for generating the target interface. The disclosure also provides an interface processing device, an electronic device and a computer readable storage medium.

Description

Interface processing method, device, electronic equipment and storage medium

Technical Field

Embodiments of the present disclosure relate to the financial field or other fields, and more particularly, to an interface processing method, an interface processing apparatus, an electronic device, and a computer-readable storage medium.

Background

With the development of internet technology, an interface becomes a main carrier for information display, and meanwhile, challenges are brought to interface development, so that an interface which is easy to use and has good user experience is difficult to develop, and not only is a developer required to have rich knowledge and development experience in application fields and interface fields, but also the interface is required to be realized through multiple iterations of 'design-evaluation-redesign'.

In the process of realizing the disclosed concept, the inventor finds that at least the following problems exist in the related art, and development efficiency and quality of interface development realized by adopting the related art are low.

Disclosure of Invention

In view of this, embodiments of the present disclosure provide an interface processing method, an interface processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

An aspect of an embodiment of the present disclosure provides an interface processing method, including:

acquiring an interface generation request aiming at a target interface;

analyzing the interface generation request to obtain M interface components corresponding to the target interface, wherein M is more than or equal to 1;

determining a markup language file corresponding to each interface member in the M interface members from a markup language file library, wherein the markup language file corresponding to the interface member comprises interface elements for describing the interface member, and the interface elements are obtained by attribute marking the elements for describing the interface member by using markup language; and

And analyzing the M markup language files to obtain interface execution sentences for generating the target interface.

According to an embodiment of the present disclosure, the parsing the M markup language files to obtain an interface execution statement for generating the target interface includes:

analyzing the M markup language files to obtain an object tree, wherein the object tree comprises M nodes, and each node is provided with a corresponding interface component;

traversing each node in the M nodes, and determining interface elements of interface components corresponding to the nodes;

determining attribute information corresponding to interface elements according to the interface elements of the interface components corresponding to the nodes; and

and obtaining interface execution sentences for generating the target interface according to the attribute information of the M interface elements.

According to an embodiment of the present disclosure, the interface processing method further includes:

for each interface component in N interface components, marking the attribute of each element in T elements for describing the interface component by using a marking language to obtain the interface element for describing the interface component, wherein M is more than or equal to 1 and less than or equal to N, and T is more than or equal to 1;

obtaining a markup language file corresponding to the interface component according to the T interface elements; and

And obtaining the markup language file library according to the N markup language files.

According to an embodiment of the present disclosure, the T elements include at least one of an identification element, a context element, a problem to be solved element, a solution element, and a display element, wherein the identification element is an element characterizing a function for identifying the interface member, the context element is an element characterizing a function for understanding the interface member, the problem to be solved element is an element characterizing a problem to be solved with the interface member, the solution element is an element characterizing a solution proposed for the problem to be solved with the interface member, and the display element is an element characterizing a display manner of the interface member.

According to an embodiment of the present disclosure, the display element includes at least one of an identification sub-element, a relationship sub-element, a content sub-element, a style sub-element, a position sub-element, and an interaction sub-element, wherein the identification sub-element is a sub-element characterizing each of P basic interface members constituting the interface member, the relationship sub-element is a sub-element characterizing a relationship between the respective basic interface members constituting the interface member, the content sub-element is a sub-element characterizing a content displayed by each of the P basic interface members, the style sub-element is a sub-element characterizing a style of each of the P basic interface members, the position sub-element is a sub-element characterizing a position of each of the P basic interface members, and the interaction sub-element is a sub-element characterizing an interaction operation corresponding to each of the P basic interface members, and P is equal to or greater than 1.

and executing the interface execution statement to generate the target interface.

According to an embodiment of the present disclosure, the markup language file includes an extensible markup language file.

Another aspect of an embodiment of the present disclosure provides an interface processing apparatus, including:

the acquisition module is used for acquiring an interface generation request aiming at a target interface;

the analysis module is used for analyzing the interface generation request to obtain M interface components corresponding to the target interface, wherein M is more than or equal to 1;

a determining module, configured to determine, for each of the M interface members, a markup language file corresponding to the interface member from a markup language file library, where the markup language file corresponding to the interface member includes an interface element for describing the interface member, where the interface element is obtained by attribute marking an element for describing the interface member using a markup language; and

and the analysis module is used for analyzing the M markup language files to obtain interface execution sentences for generating the target interface.

Another aspect of an embodiment of the present disclosure provides an electronic device, including: one or more processors; and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.

Another aspect of an embodiment of the present disclosure provides a computer-readable storage medium storing computer-executable instructions that, when executed, are configured to implement a method as described above.

Another aspect of the disclosed embodiments provides a computer program product comprising computer executable instructions which, when executed, are to implement a method as described above.

According to the embodiment of the disclosure, the interface elements for describing the interface components included in the markup language file are obtained by attribute marking of the corresponding elements by using the markup language, so that the interface design mode is formalized, and the formalized interface components can be (semi-) automatically converted into the interface execution statement for generating the target interface, so that the workload of developers in the interface development process is reduced, and the development quality and efficiency of the interface development are improved. And because the attribute marking is carried out on the interface component with large granularity, the matching of the interface design and the interface development is realized, and the development efficiency and the quality are further improved, so that the technical problems of low development efficiency and quality of the interface development realized by adopting the related technology are at least partially overcome.

Drawings

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments thereof with reference to the accompanying drawings in which:

fig. 1 schematically illustrates an exemplary system architecture to which an interface processing method may be applied according to an embodiment of the present disclosure.

Fig. 2 schematically illustrates a flow chart of an interface processing method according to an embodiment of the present disclosure.

Fig. 3 schematically illustrates a structural schematic of a target interface according to an embodiment of the present disclosure.

FIG. 4 schematically illustrates a flow chart of target interface construction according to an embodiment of the disclosure.

Fig. 5 schematically illustrates a flowchart of a markup language document processing method according to an embodiment of the present disclosure.

Fig. 6 schematically illustrates a structural diagram of an object tree according to an embodiment of the present disclosure.

Fig. 7 schematically illustrates a schematic structure of a resolver according to an embodiment of the present disclosure.

FIG. 8 schematically illustrates a flowchart of a markup language document library processing method according to an embodiment of the present disclosure.

Fig. 9 schematically illustrates a structural diagram of a markup language file according to an embodiment of the present disclosure.

Fig. 10 schematically illustrates a schematic structure of a markup language file according to another embodiment of the present disclosure.

Fig. 11 schematically illustrates a block diagram of an interface processing apparatus according to an embodiment of the present disclosure.

Fig. 12 schematically shows a block diagram of an electronic device adapted to implement the method described above, according to an embodiment of the disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.

Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the process of realizing the disclosed concept, the inventor finds that the interface development based on texts or pictures in the related technology has a problem of lack of formalization, and design languages in different design modes cannot be used commonly, so that the development efficiency of the interface development is low. Meanwhile, when the interface is developed, a developer is required to manually convert the interface into a corresponding interface execution statement according to a picture or a textified interface, so that the development efficiency is low, errors are easy to occur, and the development quality is influenced. In addition, when designing an interface, a designer adopts a large-granularity interface component to design the interface, however, when developing the interface, a developer adopts a small-granularity basic interface component to realize the interface, so that the interface design is not matched with the interface development, and the development efficiency and quality are further affected.

In order to solve the above-mentioned problems, the embodiments of the present disclosure provide a scheme for performing attribute marking on an interface member by using a markup language, which implements conversion of an un-formatted interface member into a formatted interface member, so that the formatted interface member can be (semi-) automatically converted into an interface execution statement for generating a target interface, which reduces workload of a developer in an interface development process, and improves efficiency and quality of interface development.

The embodiments of the present disclosure provide an interface processing method, apparatus, electronic device, storage medium, and program product, which may be applied to a financial field, or any field other than the financial field, and the embodiments of the present disclosure do not limit the application field. The interface processing method comprises the following steps: acquiring an interface generation request aiming at a target interface; analyzing the interface generation request to obtain M interface components corresponding to the target interface, wherein M is more than or equal to 1; determining a markup language file corresponding to the interface member from a markup language file library aiming at each interface member in the M interface members, wherein the markup language file corresponding to the interface member comprises interface elements for describing the interface member, and the interface elements are obtained by marking the elements for describing the interface member by using the markup language; and analyzing the M markup language files to obtain an interface execution statement for generating the target interface.

Fig. 1 schematically illustrates an exemplary system architecture 100 in which an interface processing method may be applied according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.

As shown in fig. 1, a system architecture 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired and/or wireless communication links, and the like.

The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. Various communication client applications may be installed on the terminal devices 101, 102, 103, such as shopping class applications, web browser applications, search class applications, instant messaging tools, mailbox clients and/or social platform software, to name a few.

The terminal devices 101, 102, 103 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (by way of example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and process the received data such as the user request, and feed back the processing result (e.g., the web page, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that, the interface processing method provided in the embodiments of the present disclosure may be generally executed by the server 105. Accordingly, the interface processing apparatus provided by the embodiments of the present disclosure may be generally disposed in the server 105. The interface processing method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the interface processing apparatus provided by the embodiments of the present disclosure may also be provided in a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Alternatively, the interface processing method provided by the embodiment of the present disclosure may be performed by the terminal device 101, 102, or 103. Accordingly, the interface processing apparatus provided by the embodiments of the present disclosure may be generally provided in the terminal device 101, 102, or 103, or may also be executed by other terminal devices different from the terminal device 101, 102, or 103. Accordingly, the interface processing apparatus provided by the embodiments of the present disclosure may be generally disposed in other terminal devices other than the terminal device 101, 102, or 103.

For example, the interface member corresponding to the target interface may be originally stored in any one of the terminal apparatuses 101, 102, or 103 (for example, but not limited to, the terminal apparatus 101), or stored on an external storage apparatus and may be imported into the terminal apparatus 101. Then, the terminal device 101 may locally perform the interface processing method provided by the embodiment of the present disclosure, or send the interface to be processed to other terminal devices, servers, or server clusters, and perform the interface processing method provided by the embodiment of the present disclosure by other terminal devices, servers, or server clusters that receive the interface to be processed.

It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The interface processing method according to the embodiment of the present disclosure is further described below with reference to fig. 2 to 4.

As shown in fig. 2, the method includes operations S201 to S204.

In operation S201, an interface generation request for a target interface is acquired.

According to embodiments of the present disclosure, a target interface may refer to an interface that needs to be presented on a carrier. The type of target interface may include a web-side interface or a mobile-side interface. The carrier may comprise an electronic device, which may comprise a terminal device, which may comprise a smart phone, a tablet computer, a portable computer, a desktop computer or the like. The interface generation request may include at least one interface component information corresponding to the target interface, the interface component information may be used to determine an interface component corresponding to the interface component information, and each interface component may be used to implement an interface mode corresponding thereto. The interface generation request may be generated according to a trigger operation of the user, which may include clicking or sliding.

For example, the target interface may be a presentation interface of a certain webpage or a login interface of a certain application program on the android phone.

In operation S202, the interface generation request is analyzed to obtain M interface members corresponding to the target interface, wherein M is more than or equal to 1.

According to the embodiment of the disclosure, each interface component information in the interface generation request is analyzed to obtain the interface component corresponding to the interface component information. The interface members may include interface members for implementing various interface modes. The interface modes may include a login mode, a navigation mode, a submit mode, a list mode, or a picture carousel mode, etc. In this embodiment, taking a target interface as an example of a presentation interface of a web page, the presentation interface may include an interface component in login mode (i.e., a login mode interface component), an interface component in navigation mode (i.e., a navigation mode interface component), and an interface component in picture carousel mode (a picture carousel interface component). Therefore, the interface generation request for the display interface includes login mode interface component information, navigation mode interface component information and picture carousel mode interface component information corresponding to the interface components. It should be noted that the above embodiments are only exemplary embodiments, and any target interface including any interface component may be used according to specific implementation requirements.

According to embodiments of the present disclosure, the interface member may comprise at least one basic interface member. The basic interface members may include button basic interface members, basic interface members for defining divided blocks in an interface, basic interface members for displaying pictures, form basic interface members, input box basic interface members, basic interface members for displaying videos, basic interface members for drawing graphics, or the like. In the present embodiment, taking a login mode interface member as an example, the login interface member may include a plurality of input boxes (e.g., a user name input box, a password input box, etc.) basic interface members and selection buttons (e.g., a login button, a cancel button, etc.) basic interface members. It should be noted that the above embodiments are only exemplary embodiments, and any interface member including any basic interface member may be used according to specific implementation requirements.

According to an embodiment of the present disclosure, as shown in fig. 3, a target interface may include a base interface member and an interface member. In this embodiment, the target interface is implemented based on an operating system, wherein the interface component may include a base interface component and the target interface may include an interface component. The above embodiments are merely exemplary embodiments, and other target interface structures may be used according to implementation requirements.

In operation S203, for each of the M interface members, a markup language file corresponding to the interface member is determined from a markup language file library, wherein the markup language file corresponding to the interface member includes interface elements for describing the interface member, the interface elements being obtained by attribute-tagging the elements for describing the interface member with a markup language.

According to an embodiment of the present disclosure, the markup language file may be a file obtained by attribute-tagging the interface member using a markup language. The markup language may include XML (Extensible Markup Language ) or HTML (Hyper Text Markup Language, hyperText markup language). The markup language file may include interface elements for describing the interface members, and the interface elements may be used to describe attribute information of the interface members.

According to embodiments of the present disclosure, converting an un-formatted interface component into a formatted interface component is accomplished by attribute marking the interface component with a markup language such that the interface design schema is formalized, i.e., forms a computer-readable form. And because the attribute marking is performed on the interface components with large granularity (such as a navigation mode interface component, a submission mode interface component, a list mode interface component and the like), the matching of the interface design and the interface development is realized, and the development efficiency and quality are further improved. It should be noted that the above embodiments are only exemplary embodiments, and other markup languages capable of achieving the same technical effects may be used according to specific implementation needs.

In operation S204, the M markup language files are parsed to obtain an interface execution statement for generating the target interface.

According to an embodiment of the present disclosure, as shown in fig. 4, an interface component is determined according to a target interface, a markup language file corresponding to the interface component is determined from a markup language file library according to the interface component, and the markup language file is parsed by a parser to obtain an interface execution statement for generating the target interface.

The method shown in fig. 2 is further described below with reference to fig. 5-10 in conjunction with the exemplary embodiment.

As shown in fig. 5, the method includes operations S501 to S504.

In operation S501, M markup language files are parsed to obtain an object tree, where the object tree includes M nodes, each node having a corresponding interface member.

According to an embodiment of the present disclosure, as shown in fig. 6, each markup language file is parsed by a parser to obtain an object tree corresponding to a target interface. Depending on the specific implementation requirements of the target interface, a plurality of first interface members may be included in the object tree, and a plurality of second interface members may also be included in each first interface member.

According to an embodiment of the present disclosure, parsing the markup language file may be implemented by a parser, for example, as shown in fig. 7. In the present embodiment, the markup language file is taken as an XML file as an example, and in the present embodiment, the parser may include a DOM (Document Object Model ) parser, an object tree generator, and a semantic parser. It should be noted that the above embodiments are only exemplary embodiments, and other resolvers capable of achieving the same technical effects may be used according to specific implementation needs.

According to the embodiment of the disclosure, a presentation interface with a target interface as a web page is taken as an example for explanation, and the presentation interface may include a login mode interface component, a navigation mode interface component, a picture carousel mode interface component, and the like. Further, a search mode interface member may be included in the navigation mode interface member. In this embodiment, the first interface member may be, for example, a login mode interface member, a navigation mode interface member, and a picture carousel mode interface member, and the second interface member may be, for example, a search mode interface member. It should be noted that the above embodiments are merely exemplary embodiments, and any target interface including any interface member may be used according to specific implementation requirements.

In operation S502, each of the M nodes is traversed, and interface elements of interface members corresponding to the nodes are determined.

Traversing each node may be implemented by a depth-first traversal method, according to an embodiment of the present disclosure. In this embodiment, through the depth-first traversal method, first, a complete search is performed for each node along one chain of the object tree until the chain can no longer perform deep search, then, a complete search is performed for the other chain of the object tree, and the above-mentioned process is repeated until the whole object tree is searched. It should be noted that the above embodiments are only exemplary embodiments, and other traversal methods capable of achieving the same technical effects may be used according to implementation needs.

According to an embodiment of the present disclosure, after traversing each node, interface elements of interface members corresponding to the node are determined, which may include a base interface member corresponding to the interface member. In the present embodiment, taking a login mode interface member as an example, the login mode interface member may include a plurality of input boxes (e.g., a user name input box, a password input box, etc.) basic interface members and selection buttons (e.g., a login button, a cancel button, etc.) basic interface members. It should be noted that the above embodiments are only exemplary embodiments, and any interface member including any basic interface member may be used according to specific implementation requirements.

In operation S503, attribute information corresponding to the interface element is determined according to the interface element of the interface member corresponding to the node.

According to an embodiment of the present disclosure, each interface element may have attribute information corresponding thereto, and the attribute information may include attribute information of a size, a position, a style, and the like. In this embodiment, taking a user name input box basic interface member of the login mode interface member as an example, the attribute information of the user name input box basic interface member may include information such as position information of the user name input box basic interface member in the whole login mode interface member, length and width values of the input box, and color style of the input box. It should be noted that the foregoing embodiments are merely exemplary embodiments, and any other basic interface component may be used according to the specific implementation requirements.

In operation S504, an interface execution sentence for generating a target interface is obtained according to attribute information of the M interface elements.

According to embodiments of the present disclosure, the interface execution statement may include an execution statement corresponding to the device or platform. In this embodiment, the interface execution statement may include an HTML statement or a Java statement, or the like.

According to the embodiment of the disclosure, the attribute information of the interface element is analyzed, namely the attribute information can be analyzed into corresponding execution sentences on different platforms or equipment, in the process, the workload of an interface developer can be reduced, the development efficiency and instructions are improved, and the usability of a final target interface is effectively ensured.

As shown in fig. 8, the method includes operations S801 to S803.

In operation S801, for each of the N interface members, attribute marking is performed on each of T elements for describing the interface member by using a markup language to obtain an interface element for describing the interface member, wherein M is greater than or equal to 1 and less than or equal to N, and T is greater than or equal to 1;

according to embodiments of the present disclosure, attribute tags may be hosted for each source using XML, resulting in a tagged element, i.e., an interface element. It should be noted that the above embodiments are only exemplary embodiments, and other markup languages capable of achieving the same technical effects may be used according to specific implementation needs.

In operation S802, a markup language file corresponding to an interface member is obtained according to T interface elements.

According to the embodiment of the disclosure, after marking each interface element of the interface member is completed, a mark-up language file corresponding to the interface member is finally obtained.

In operation S803, a markup language document library is obtained from the N markup language documents.

According to an embodiment of the present disclosure, each markup language file is stored to obtain a markup language file library containing the respective markup language files. In this embodiment, according to actual implementation needs, interface components that are not stored in the markup language file library may be marked at any time, and the markup language file library is updated at the same time, so that the markup language file library meets different use requirements.

According to an embodiment of the present disclosure, the markup language file includes at least one of an identification element, a context element, a problem to be solved element, a solution element, and a display element.

According to an embodiment of the present disclosure, the identification element may be an element characterizing a function for identifying the interface member, the context element may be an element characterizing a function for understanding the interface member, the problem to be solved element may be an element characterizing a problem to be solved with the interface member, the solution element may be an element characterizing a solution proposed for the problem to be solved with the interface member, and the display element may be an element characterizing a display manner of the interface member.

As shown in fig. 9, the markup language file may include an identification element, a context element, a problem to be solved element, a solution element, and a display element.

It should be noted that the above embodiments are only exemplary embodiments, and other markup language files capable of achieving the same technical effects may be used according to specific implementation requirements.

According to embodiments of the present disclosure, the display element may include at least one of an identification sub-element, a relationship sub-element, a content sub-element, a style sub-element, a location sub-element, and an interactivity event sub-element.

Wherein the identification sub-element may be a sub-element characterizing each of the basic interface members used to identify the constituent interface members, the identification sub-element being capable of characterizing the names and types of all of the basic interface members used by one interface member, such as: a simple login interface element is composed of two text entry boxes and two buttons of the basic interface element. The relationship sub-element may be a sub-element that characterizes a relationship between individual basic interface members that make up an interface member, e.g., a parent container in the relationship sub-element that includes the name of the basic interface member and the basic interface member. The content sub-element may be a sub-element that characterizes the content displayed by each of the basic interface members. The style sub-element may be a sub-element that characterizes the style of each of the basic interface members, e.g., size, color, etc., of the current basic interface member. The location sub-element may be a sub-element that characterizes the location of each of the base interface members, e.g., the location sub-element may include the name of the current base interface member and the distance information of the base interface member to the parent container, up, down, left, and right. The interactivity sub-element may be a sub-element that characterizes the interactivity corresponding to each of the basic interface components, i.e., the interactivity sub-element defines the response to user operations (e.g., single-click, double-click, drag-and-drop, etc.) when the target interface is running, and the application logic corresponding to each basic interface component may be written by the developer at his own discretion, depending on the implementation needs.

As shown in fig. 10, the markup language file may include an identification element, a context element, a problem to be solved element, a solution element, and a display element. According to an embodiment of the present disclosure, the markup language file includes at least one of an identification element, a context element, a problem to be solved element, a solution element, and a display element.

According to embodiments of the present disclosure, the recognition element may include a name sub-element, a category sub-element, a keyword sub-element, and an interface component relationship sub-element. In this embodiment, the identification element may include at least one of a name sub-element, a category sub-element, a keyword sub-element, and an interface component relationship sub-element.

Wherein the name sub-element may be a sub-element that characterizes the name of the current interface member. The category sub-element may be a sub-element that characterizes the category of the current interface member. The key sub-element may be a sub-element of a key that characterizes the current interface component, which may be used for the retrieval task of the current interface component. The interface component relationship sub-element may be a sub-element that characterizes a relationship between a current interface component and other interface components.

According to embodiments of the present disclosure, the context elements may include a user population sub-element, a task sub-element, and an environment sub-element. In this embodiment, the context element may include at least one of a user group sub-element, a task sub-element, and an environment sub-element.

The target interfaces of different user groups are presented in different forms because the target interfaces are oriented to different user groups, and the user groups have the differences of social experience, cultural degree, self conditions and the like. The task sub-element may be a sub-element that characterizes the task to be completed by the current interface member, i.e., the function of the target interface member. The environment sub-element may be a sub-element of information characterizing the platform or device to which the current interface member pertains, the socio-cultural environment, related technology, standards, and the like.

According to an embodiment of the present disclosure, the interface processing method further includes: executing the sentence by the execution interface to generate the target interface.

According to the embodiment of the disclosure, the interface execution statement for generating the target interface is obtained by analyzing the attribute information of the interface element. The attribute information of the interface elements is analyzed into corresponding interface execution sentences on different platforms or equipment, and then the corresponding interface execution sentences are executed through the corresponding platforms or equipment, so that the generation of the target interface is realized. In the process, the method can be (semi-) automatically converted into the target interface, so that the workload of developers in the interface development process is reduced, the development quality and efficiency of interface development are further improved, and the usability of the final target interface is effectively ensured.

It should be noted that the above embodiments are only exemplary embodiments, and other target interface generating methods capable of achieving the same technical effects may be used according to specific implementation needs.

Fig. 11 schematically illustrates a structural schematic diagram of an interface processing apparatus 1100 according to an embodiment of the present disclosure.

As shown in fig. 11, the interface processing apparatus 1100 includes an acquisition module 1101, a first parsing module 1102, a determination module 1103, and a second parsing module 1104.

The obtaining module 1101 is configured to obtain an interface generation request for a target interface.

The first parsing module 1102 is configured to parse the interface generation request to obtain M interface components corresponding to the target interface, where M is greater than or equal to 1.

A determining module 1103, configured to determine, for each of the M interface components, a markup language file corresponding to the interface component from a markup language file library, where the markup language file corresponding to the interface component includes an interface element for describing the interface component, and the interface element is obtained by attribute marking the element for describing the interface component with a markup language.

The second parsing module 1104 is configured to parse the M markup language files to obtain an interface execution statement for generating the target interface.

Any number of the modules, sub-modules, units, or at least some of the functionality of any number of the modules, sub-modules, units, may be implemented in one module in accordance with embodiments of the present disclosure. Any one or more of the modules, sub-modules, units according to embodiments of the present disclosure may be implemented as a split into multiple modules. Any one or more of the modules, sub-modules, units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or in hardware or firmware in any other reasonable manner of integrating or packaging the circuits, or in any one of or in any suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.

For example, any of the acquisition module 1101, the first parsing module 1102, the determination module 1103, and the second parsing module 1104 may be combined in one module/unit to be implemented, or any of the modules/units may be split into a plurality of modules/units/sub-units. Alternatively, at least some of the functionality of one or more of the modules/units may be combined with at least some of the functionality of other modules/units and implemented in one module/unit. According to embodiments of the present disclosure, at least one of the acquisition module 1101, the first parsing module 1102, the determination module 1103, and the second parsing module 1104 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable way of integrating or packaging the circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the acquisition module 1101, the first parsing module 1102, the determination module 1103 and the second parsing module 1104 may be at least partially implemented as computer program modules, which when run, may perform the respective functions.

According to the embodiment of the disclosure, the interface elements for describing the interface component included in the markup language file are obtained by attribute marking corresponding elements by using the markup language, and attribute marking is performed on the corresponding elements by using the markup language, so that the problem of lack of formalization in an interface design mode mainly based on texts or pictures in the prior art is at least partially overcome, and further the conversion of an un-formalized interface component into the formalized interface component is realized, so that the formalized interface component can be (semi) automatically converted into a target interface, the workload of developers in the interface development process is reduced, and the efficiency and quality of interface development are improved.

According to an embodiment of the present disclosure, the second parsing module 1104 includes a parsing unit, a traversing unit, a determining unit, and a generating unit.

The parsing unit is used for parsing the M markup language files to obtain an object tree, wherein the object tree comprises M nodes, and each node is provided with a corresponding interface component.

And the traversing unit is used for traversing each node in the M nodes and determining the interface element of the interface component corresponding to the node.

And the determining unit is used for determining attribute information corresponding to the interface element according to the interface element of the interface component corresponding to the node.

And the generating unit is used for obtaining an interface execution statement for generating the target interface according to the attribute information of the M interface elements.

According to the embodiment of the disclosure, the interface processing device further comprises a marking module, a first generating module and a second generating module.

The marking module is used for marking each element in the T elements for describing the interface components by utilizing a marking language according to each interface component in the N interface components to obtain the interface elements for describing the interface components, wherein M is more than or equal to 1 and less than or equal to N, and T is more than or equal to 1.

The first generation module is used for obtaining the markup language file corresponding to the interface component according to the T interface elements.

And the second generation module is used for obtaining a markup language file library according to the N markup language files.

According to an embodiment of the disclosure, the interface processing device further includes an execution module.

And the execution module is used for executing the interface execution statement and generating a target interface.

It should be noted that, in the embodiment of the present disclosure, the interface processing device portion corresponds to the interface processing method portion in the embodiment of the present disclosure, and the description of the interface processing device portion specifically refers to the interface processing method portion, which is not described herein again.

Fig. 12 schematically shows a block diagram of an electronic device adapted to implement the method described above, according to an embodiment of the disclosure. The electronic device shown in fig. 12 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 12, an electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1202 or a program loaded from a storage section 1208 into a Random Access Memory (RAM) 1203. The processor 1201 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 1201 may also include on-board memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.

In the RAM 1203, various programs and data required for the operation of the electronic apparatus 1200 are stored. The processor 1201, the ROM 1202, and the RAM 1203 are connected to each other through a bus 1204. The processor 1201 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1202 and/or RAM 1203. Note that the program may be stored in one or more memories other than the ROM 1202 and the RAM 1203. The processor 1201 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in one or more memories.

According to an embodiment of the disclosure, the electronic device 1200 may also include an input/output (I/O) interface 1205, the input/output (I/O) interface 1205 also being connected to the bus 1204. The electronic device 1200 may also include one or more of the following components connected to the I/O interface 1205: an input section 1206 including a keyboard, a mouse, and the like; an output portion 1207 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 1208 including a hard disk or the like; and a communication section 1209 including a network interface card such as a LAN card, a modem, or the like. The communication section 1209 performs communication processing via a network such as the internet. The drive 1210 is also connected to the I/O interface 1205 as needed. A removable medium 1211 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 1210 so that a computer program read out therefrom is installed into the storage section 1208 as needed.

According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 1209, and/or installed from the removable media 1211. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1201. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

For example, according to embodiments of the present disclosure, the computer-readable storage medium may include the ROM 1202 and/or the RAM 1203 and/or one or more memories other than the ROM 1202 and the RAM 1203 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program comprising program code for performing the methods provided by the embodiments of the present disclosure, the program code for causing an electronic device to implement the interface processing methods provided by the embodiments of the present disclosure when the computer program product is run on the electronic device.

The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1201. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.

In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program can also be transmitted, distributed over a network medium in the form of signals, and downloaded and installed via a communication portion 1209, and/or from a removable medium 1211. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.

Claims

1. An interface processing method, comprising:

acquiring an interface generation request aiming at a target interface;

Analyzing M markup language files to obtain interface execution sentences for generating the target interface;

the parsing the M markup language files to obtain an interface execution statement for generating the target interface includes:

analyzing M markup language files to obtain an object tree, wherein the object tree comprises M nodes, and each node is provided with a corresponding interface component;

2. The method of claim 1, further comprising:

3. The method of claim 2, wherein the T elements include at least one of an identification element, a context element, a to-be-solved problem element, a solution element, and a display element, wherein the identification element is an element that characterizes the interface component for identification, the context element is an element that characterizes the interface component for understanding a function of the interface component, the to-be-solved problem element is an element that characterizes a problem to be solved with the interface component, the solution element is an element that characterizes a solution proposed for the problem to be solved with the interface component, and the display element is an element that characterizes a display manner of the interface component.

4. The method of claim 3, wherein the display element includes at least one of an identification sub-element, a relationship sub-element, a content sub-element, a style sub-element, a location sub-element, and an interactivity sub-element, wherein the identification sub-element is a sub-element that characterizes each of P basic interface members that make up the interface member, the relationship sub-element is a sub-element that characterizes a relationship between the respective basic interface members that make up the interface member, the content sub-element is a sub-element that characterizes content displayed by each of the P basic interface members, the style sub-element is a sub-element that characterizes a style of each of the P basic interface members, the location sub-element is a sub-element that characterizes a location of each of the P basic interface members, and the interactivity sub-element is a sub-element that characterizes an interactivity corresponding to each of the P basic interface members, P is ≡1.

5. The method of claim 1, further comprising:

6. The method of claim 1, wherein the markup language file comprises an extensible markup language file.

7. An interface processing apparatus comprising:

the first analysis module is used for analyzing the interface generation request to obtain M interface components corresponding to the target interface, wherein M is more than or equal to 1;

the second analysis module is used for analyzing the M markup language files to obtain interface execution sentences for generating the target interface;

the second parsing module is further configured to parse M markup language files to obtain an object tree, where the object tree includes M nodes, and each node has a corresponding interface member;

8. An electronic device, comprising:

one or more processors;

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-6.

9. A computer readable storage medium having stored thereon executable instructions which when executed by a processor cause the processor to implement the method of any of claims 1 to 6.