CN112860259A

CN112860259A - Interface processing method, device, electronic equipment, storage medium and program product

Info

Publication number: CN112860259A
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: 2021-05-28
Anticipated expiration: 2041-03-31
Also published as: CN112860259B

Abstract

The 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; for each interface component in the M interface components, determining a markup language file corresponding to the interface component from a markup language file library, wherein the markup language file corresponding to the interface component comprises interface elements for describing the interface component, and the interface elements are obtained by attribute marking of the elements for describing the interface component by using a markup language; and analyzing the M markup language files to obtain interface execution statements for generating the target interface. The disclosure also provides an interface processing device, an electronic device, a computer readable storage medium and a computer program product.

Description

Interface processing method, device, electronic equipment, storage medium and program product

Technical Field

The disclosed embodiments relate to the field of finance or other fields, and more particularly, to an interface processing method, an interface processing apparatus, an electronic device, a computer-readable storage medium, and a computer program product.

Background

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

In the process of implementing the disclosed concept, the inventor finds that at least the following problems exist in the related art, and the development efficiency and quality of interface development implemented by adopting the related art are not high.

Disclosure of Invention

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

One aspect of the embodiments 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;

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

and analyzing the M markup language files to obtain interface execution statements used for generating the target interface.

According to an embodiment of the present disclosure, the parsing M markup language files to obtain interface execution statements 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 of the M nodes, and determining an interface element of the interface member corresponding to the node;

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

and 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 present disclosure, the interface processing method further includes:

for each interface member in N interface members, performing attribute marking on each element in T elements for describing the interface member by using a marking language to obtain the interface elements for describing the interface member, 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 the 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 that characterizes a function for identifying the interface member, the context element is an element that characterizes a function for understanding the interface member, the problem-to-be-solved element is an element that characterizes a problem to be solved with the interface member, the solution element is an element that characterizes a solution proposed for a problem to be solved with the interface member, and the display element is an element that characterizes a display manner of the interface member.

According to the embodiment of the present disclosure, the display element includes at least one of an identification sub-element, a relation sub-element, a content sub-element, a style sub-element, a position sub-element and an interaction event sub-element, wherein the identification sub-element is a sub-element characterizing each of P basic interface members constituting the interface member, the relation sub-element is a sub-element characterizing a relation 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, and the position sub-element is a sub-element characterizing a position of each of the P basic interface members, the interaction event sub-element is a sub-element for representing the interaction operation corresponding to each basic interface component in the P basic interface components, and P is more than or equal to 1.

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

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

Another aspect of the embodiments 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 interface component 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 an element for describing the interface component using a markup language; and

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

Another aspect of an embodiment of the present disclosure provides an electronic device including: one or more processors; 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 embodiments of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.

Another aspect of an embodiment of the present disclosure provides a computer program product comprising computer executable instructions for implementing the method as described above when executed.

According to the embodiment of the disclosure, because the interface elements used for describing the interface component and included in the markup language file are obtained by attribute marking of the corresponding elements by using the markup language, the interface design mode is formalized, and because the formalized interface component can be (semi-) automatically converted into the interface execution statement used for generating the target interface, 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 interface design and interface development is realized, and the development efficiency and quality are further improved, so that the technical problem that the development efficiency and quality of the interface development realized by adopting the related technology are not high is at least partially solved.

Drawings

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

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

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

FIG. 3 schematically shows a structural schematic of a target interface according to an embodiment of the disclosure.

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

FIG. 5 schematically shows a flow chart of a markup language document processing method according to an embodiment of the present disclosure.

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

Fig. 7 schematically shows a structural diagram of a resolver according to an embodiment of the present disclosure.

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

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

Fig. 10 schematically shows a structural diagram of a markup language file according to another embodiment of the present disclosure.

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

Fig. 12 schematically shows a block diagram of an electronic device adapted to implement the above described method according to an embodiment of the present 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 illustrative only 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 disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not 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 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 is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have 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 convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have 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 implementing the disclosed concept, the inventor finds that the interface development mainly based on texts or pictures in the related art has the problem of lack of formalization, and design languages in different design modes cannot be used universally, so that the development efficiency of the interface development is low. Meanwhile, when the interface is developed, a developer needs to manually convert the interface into a corresponding interface execution statement according to the picture or the textual interface, so that not only is the development efficiency low, but also errors are easy to occur, and the development quality is influenced. In addition, during interface design, a designer designs an interface by using a large-particle-size interface component, whereas during interface development, a developer realizes an interface by using a small-particle-size basic interface component, so that the interface design is not matched with the interface development, and further the development efficiency and quality are influenced.

In order to solve the above problem, an embodiment of the present disclosure provides a scheme for performing attribute tagging on an interface component by using a markup language, which realizes that an informal interface component is converted into a formal interface component, so that the formal interface component can be (semi-) automatically converted into an interface execution statement for generating a target interface, thereby reducing the workload of developers in an interface development process and improving the efficiency and quality of interface development.

The embodiment of the disclosure provides an interface processing method, an interface processing device, electronic equipment, a storage medium and a program product. 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; for each interface component in the M interface components, determining a markup language file corresponding to the interface component from a markup language file library, wherein the markup language file corresponding to the interface component comprises interface elements for describing the interface component, and the interface elements are obtained by attribute marking of the elements for describing the interface component by using a markup language; and analyzing the M markup language files to obtain interface execution statements for generating the target interface.

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

As shown in fig. 1, the system architecture 100 according to this embodiment may include

terminal devices

101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, and/or social platform software, etc. (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the

terminal devices

101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, 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 by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the interface processing device provided by the embodiment of the present disclosure may be generally disposed in the server 105. The interface processing method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the interface processing apparatus provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and 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 also be executed by the

terminal device

101, 102, or 103. Accordingly, the interface processing apparatus provided by the embodiment of the present disclosure may be generally disposed in the

terminal device

101, 102, or 103, or may also be executed by another terminal device different from the

terminal device

101, 102, or 103. Accordingly, the interface processing apparatus provided by the embodiment of the present disclosure may be generally disposed in other terminal devices different from the

terminal device

101, 102, or 103.

For example, the interface component corresponding to the target interface may be originally stored in any of the

terminal apparatuses

101, 102, or 103 (e.g., the terminal apparatus 101, but not limited thereto), or stored on an external storage apparatus and may be imported into the terminal apparatus 101. Then, the terminal device 101 may locally execute the interface processing method provided by the embodiment of the present disclosure, or send the interface to be processed to another terminal device, a server, or a server cluster, and execute the interface processing method provided by the embodiment of the present disclosure by another terminal device, a server, or a server cluster that receives 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 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 the target interface may include a web-side interface or a mobile-side interface. The carrier may comprise an electronic device, the electronic device may comprise a terminal device, and the terminal device may comprise a smartphone, a tablet, a laptop or desktop computer, or the like. The interface generation request may include at least one interface component information corresponding to the target interface, and 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 to the interface component. The interface generation request can be generated according to a trigger operation of a user, and the trigger operation can comprise clicking or sliding.

For example, the target interface may be a presentation interface of a web page or a login interface of an application on an android phone.

In operation S202, the interface generation request is parsed to obtain M interface components corresponding to the target interface, where M is greater than or equal to 1.

According to the embodiment of the disclosure, the interface component corresponding to the interface component information is obtained by analyzing each interface component information in the interface generation request. The interface member may include an interface member for implementing various interface modes. The interface mode may include a login mode, a navigation mode, a submit mode, a list mode, or a picture carousel mode, among others. In this embodiment, taking the target interface as the display interface of a certain web page as an example, the display interface may include an interface component in a login mode (i.e., a login mode interface component), an interface component in a navigation mode (i.e., a navigation mode interface component), and an interface component in a 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 component. It should be noted that the above embodiments are only exemplary embodiments, and may be any target interface including any interface component according to specific implementation needs.

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

According to an embodiment of the present disclosure, as shown in fig. 3, the 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 basic interface component and the target interface may include an interface component. It should be noted that the above embodiments are only exemplary embodiments, and other target interface structures may be adopted according to implementation needs.

In operation S203, for each interface member of the M interface members, a markup language file corresponding to the interface member is determined from a markup language file library, where the markup language file corresponding to the interface member includes interface elements for describing the interface member, and the interface elements are obtained by attribute-marking the elements for describing the interface member using a markup language.

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

According to the embodiment of the disclosure, the interface design mode is formalized, namely, the interface design mode is formed into a computer-readable form by using the markup language to perform attribute marking on the interface component, so that the conversion of the unformed interface component into the formalized interface component is realized. And because the attribute marking is carried out on interface components with large granularity (such as navigation mode interface components, submission mode interface components, list mode interface components and the like), the matching of interface design and 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 requirements.

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

According to the embodiment of the 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 with reference to fig. 5-10 in conjunction with specific embodiments.

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

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

According to the embodiment of the disclosure, as shown in fig. 6, each markup language file is parsed by a parser, and an object tree corresponding to a target interface is obtained. According to the specific implementation requirement of the target interface, the object tree may include a plurality of first interface members, and each first interface member may also include a plurality of second interface members.

According to an embodiment of the present disclosure, parsing the markup language file, for example, may be implemented by a parser, as shown in fig. 7. In this embodiment, the markup language file is taken as an XML file for explanation, and in this 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 effect may also be used according to specific implementation needs.

According to the embodiment of the disclosure, a display interface with a target interface as a certain webpage is taken as an example for explanation, and the display 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 component may be included in the navigation mode interface component. In this embodiment, the first interface component may be, for example, a login mode interface component, a navigation mode interface component, and a picture carousel mode interface component, and the second interface component may be, for example, a search mode interface component. It should be noted that the above embodiments are only exemplary embodiments, and may be any target interface including any interface component according to the specific implementation needs.

In operation S502, each of the M nodes is traversed to determine an interface element of the interface member corresponding to the node.

According to an embodiment of the present disclosure, traversing each node may be achieved by a depth-first traversal method. In this embodiment, by using a depth-first traversal method, each node along one chain of the object tree is completely searched until the chain cannot be further searched, and then another chain of the object tree is completely searched, and the above process is repeated until the whole object tree is completely searched. It should be noted that the foregoing embodiments are only exemplary embodiments, and other traversal methods capable of achieving the same technical effect may be used according to implementation needs.

According to an embodiment of the present disclosure, after traversing each node, an interface element of the interface member corresponding to the node is determined, which may include a base interface member corresponding to the interface member. In this embodiment, taking the login mode interface component as an example, the login mode interface component may include a plurality of input boxes (e.g., a user name input box, a password input box, etc.) and a selection button (e.g., a login button, a cancel button, etc.) basic interface component. It should be noted that the above embodiments are only exemplary embodiments, and may be any interface component including any basic interface component 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 such as size, position, style, and the like. In this embodiment, taking the user name input box basic interface component of the login mode interface component as an example, the attribute information of the user name input box basic interface component may include position information of the user name input box basic interface component in the whole login mode interface component, length and width values of the input box, color style of the input box, and other information. It should be noted that the above embodiments are only exemplary embodiments, and may be any other basic interface components according to specific implementation requirements.

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

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

According to the embodiment of the disclosure, the attribute information of the interface element is analyzed, that is, the interface element can be analyzed into corresponding execution statements on different platforms or devices, in the process, the workload of interface developers 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 interface component of the N interface components, attribute labeling is performed on each element of the T elements for describing the interface component by using a markup language to obtain an interface element for describing the interface component, where M is greater than or equal to 1 and is less than or equal to N, and T is greater than or equal to 1;

according to the embodiment of the disclosure, each of the native attributes may be tagged with XML, and a tagged element, that is, an interface element, may be obtained. 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 requirements.

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

According to the embodiment of the disclosure, after each interface element of the interface component is marked, the markup language file corresponding to the interface component is finally obtained.

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

According to the embodiment of the disclosure, each markup language file is stored, and a markup language file library containing each markup language file is obtained. In this embodiment, according to actual implementation requirements, interface components that are not stored in the markup language document library can be marked at any time, and the markup language document library is updated at the same time, so that the markup language document 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 to-be-solved-problem 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 display mode for identifying the interface member, the context element may be an element characterizing a function for understanding the interface member, the problem element to be solved 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 mode of the interface member.

As shown in FIG. 9, the markup language file can include an identification element, a context element, a to-solve problem 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 effect may be used according to specific implementation requirements.

According to an embodiment 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 interaction event sub-element.

The identifier sub-element may be a sub-element that characterizes each of the basic interface members that constitute the interface member, and the identifier sub-element may characterize names and types of all the basic interface members used by one interface member, for example: a simple login interface member is composed of a basic interface member of two text input boxes and two buttons. A relationship sub-element may be a sub-element that characterizes the relationship between the various basic interface members that make up an interface member, e.g., a relationship sub-element that includes the name of a basic interface member and the parent container of the basic interface member. The content sub-elements may be sub-elements that characterize the content displayed by each of the basic interface members. The wind lattice element may be a sub-element that characterizes the style of each of the basic interface members, e.g., information of 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 basic interface members, e.g., the location sub-element may include the name of the current basic interface member and distance information about the basic interface member to the parent container. The interaction event sub-elements may be sub-elements characterizing interaction operations corresponding to each of the basic interface components, that is, the interaction event sub-elements define responses to user operations (e.g., single click, double click, drag and drop, etc.) when the target interface operates, and application program logic corresponding to each of the basic interface components may be written by developers according to specific implementation requirements.

As shown in FIG. 10, the markup language file can include an identification element, a context element, a to-solve problem 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 to-be-solved-problem element, a solution element, and a display element.

According to embodiments of the present disclosure, the identification elements may include a name sub-element, a category sub-element, a keyword sub-element, and an interface member 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 member 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 a category of the current interface member. The keyword sub-elements may be sub-elements of keywords that characterize the current interface member, and may be used for retrieval tasks of the current interface member. The interface member relationship sub-element may be a sub-element that characterizes a relationship between the current interface member and other interface members.

According to embodiments of the present disclosure, context elements may include user group sub-elements, task sub-elements, and environment sub-elements. 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 face different user groups, and the user groups have differences in social experience, cultural degree, self conditions and the like, so that the target interfaces of the different user groups are different in form, and the user groups facing the current interface members are represented by the user group sub-elements, so that the interface development can be more accurate. A 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-elements can be sub-elements that characterize the platform or device to which the current interface component belongs, the socio-cultural environment, the relevant technology, the standard, etc.

According to the embodiment of the disclosure, the interface processing method further includes: and executing the interface execution statement to generate a 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 statements on different platforms or equipment, and then the corresponding interface execution statements are executed through the corresponding platforms or equipment, so that the generation of the target interface is realized. In the process, the target interface can be (semi-) automatically converted, so that the workload of developers in the interface development process is reduced, the development quality and efficiency of the interface development are 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 requirements.

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

Fig. 11 schematically shows a structural 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 obtaining module 1101, a first parsing module 1102, a determining module 1103, and a second parsing module 1104.

An 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 interface component 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 interface elements for describing the interface component, and the interface elements are obtained by attribute-marking the elements for describing the interface component using a markup language.

And the second analysis module 1104 is configured to analyze the M markup language files to obtain an interface execution statement for generating a target interface.

Any number of modules, sub-modules, units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units according to the embodiments of the present disclosure may be implemented at least partially 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 may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of or a suitable combination of software, hardware, and the same. Alternatively, one or more of the modules, sub-modules, units according to embodiments of the disclosure may be implemented at least partly as computer program modules, which, when executed, may perform corresponding functions.

For example, any plurality of the obtaining module 1101, the first parsing module 1102, the determining module 1103 and the second parsing module 1104 may be combined and implemented in one module/unit, or any one of the modules/units may be split into a plurality of modules/units/sub-units. Alternatively, at least part of the functionality of one or more of these modules/units may be combined with at least part of the functionality of other modules/units and implemented in one module/unit. According to an embodiment of the present disclosure, at least one of the obtaining module 1101, the first parsing module 1102, the determining module 1103 and the second parsing module 1104 may be at least partially implemented 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 may be implemented by hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or implemented by any one of three implementations of software, hardware and firmware, or an appropriate combination of any several of them. Alternatively, at least one of the obtaining module 1101, the first parsing module 1102, the determining module 1103 and the second parsing module 1104 may be at least partially implemented as a computer program module, which when executed may perform a corresponding function.

According to the embodiment of the disclosure, the interface elements used for describing the interface component and included in the markup language file are obtained by performing attribute marking on the corresponding elements by using the markup language, and the 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 informal interface component is converted into the formalized interface component, 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 the quality of interface development are improved.

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

And the analysis unit is used for 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.

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 the 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 used 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.

And the marking module is used for carrying out attribute marking on each element in the T elements for describing the interface component by utilizing a marking language aiming at each interface component in the N interface components to obtain the interface elements 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.

And 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 the embodiment of the disclosure, the interface processing device further comprises 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 the interface processing apparatus portion in the embodiment of the present disclosure corresponds to the interface processing method portion in the embodiment of the present disclosure, and the description of the interface processing apparatus 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 above described method according to an embodiment of the present disclosure. The electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 12, an electronic apparatus 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 associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The 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 present disclosure.

In the RAM 1203, various programs and data necessary 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 by 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 the RAM 1203. Note that the programs may also 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 method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 1200 may also include input/output (I/O) interface 1205, according to an embodiment of the disclosure, input/output (I/O) interface 1205 also connected to bus 1204. The system 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 display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 1208 including a hard disk and 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. A driver 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 mounted on the drive 1210 as necessary, so that a computer program read out therefrom is mounted into the storage section 1208 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. 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 containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 1209, and/or installed from the removable medium 1211. The computer program, when executed by the processor 1201, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.

According to an embodiment 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 present 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, a 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 containing program code for performing the method provided by the embodiments of the present disclosure, when the computer program product is run on an electronic device, the program code being configured to cause the electronic device to implement the interface processing method provided by the embodiments of the present disclosure.

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

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

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, 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., through the internet using an internet service provider).

The flowchart 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 various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been 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 separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. An interface processing method, comprising:

acquiring an interface generation request aiming at a target interface;

2. The method of claim 1, wherein said parsing M markup language files for interface execution statements for generating the target interface comprises:

3. The method of claim 1, further comprising:

4. The method of claim 3, wherein 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 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.

5. The method of claim 4, 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 interaction event sub-element, wherein the identification sub-element is a sub-element that characterizes each of the 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, and the location sub-element is a sub-element that characterizes a location of each of the P basic interface members, the interaction event sub-element is a sub-element for representing the interaction operation corresponding to each basic interface component in the P basic interface components, and P is more than or equal to 1.

6. The method of claim 1, further comprising:

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

8. An interface processing device, comprising:

9. 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-7.

10. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to carry out the method of any one of claims 1 to 7.

11. A computer program product comprising a computer program which, when executed by a processor, is adapted to carry out the method of any one of claims 1 to 7.