Generating a graphical user interface based on formatted structure data

Patent metadata

Field	Value
Publication number	US-11216610-B2
Application number	US-201816019716-A
Country	US
Kind code	B2
Filing date	Jun 27, 2018
Priority date	Dec 30, 2015
Publication date	Jan 4, 2022
Grant date	Jan 4, 2022

Abstract

Methods, systems, and computer-readable storage media for generation of a unified view of the graphical user interface. Implementations include actions of receiving, from a server, structured data of an interface template that is generated by the server by parsing interface template data associated with the interface template. The interface template is identified based on an interface identifier included in the service data. A virtual view node for the widget is determined based on the structured data. The widget is retrieved based on the location information associated with the virtual view node. A unified view of the graphical user interface is generated by rendering the widget with a plurality of widgets associated with the graphical user interface and is displayed on a display device.

First claim

What is claimed is:

1. A computer-implemented method executed by one or more processors, the method comprising:
receiving, by a client application from a server, JavaScript Object Notation (JSON) data corresponding to an interface template, the interface template being separate from the client application, wherein the JSON data is generated by the server by parsing Hypertext Markup Language of interface template data associated with the interface template, wherein the JSON data is written in a general protocol markup language comprising a syntax tree that is simpler than the syntax tree of the Hypertext Markup Language of the interface template data, wherein the JSON data contains data corresponding to the Hypertext Markup Language of the interface template data comprising a plurality of tags each describing a respective widget, wherein each widget is a visual component included in a graphical user interface containing a plurality of widgets corresponding to the interface template;
identifying, by the client application, the interface template based on a first interface identifier included in the received data, wherein each interface template has a unique interface identifier to distinguish between different interface templates;
in response to identifying the interface template, determining, by the client application, a document object model node for each widget based on the JSON data, wherein each document object model node stores information related to each respective tag, and wherein each document object model node comprises location information of each respective widget in the interface template described by a respective tag;
parsing, by the client application, the JSON data into a tree structure of virtual view nodes for storing information for a plurality of document object model nodes of the interface template, each virtual view node storing a respective document object model node and at least one virtual view node comprising response event information associated with the client application;
retrieving, by a client application from the server, service data during a service data exchange procedure, wherein the service data contains a second interface identifier, wherein the service data contains service data for binding with a first virtual view node of the plurality of virtual view nodes;
searching, by the client application, for an interface template that corresponds to the second interface identifier;
in response to locating the searched for interface template, identifying the located interface template as the searched for interface template without initiating a server request;
in response to failing to locate the searched for interface template:
requesting, by the client application, a structured data of an updated interface template that corresponds to the second interface identifier from the server;
receiving, by the client application, the structured data of the updated interface template corresponding to the second interface identifier and instructing the first virtual view node to update its stored document object model node information based on the received structured data;
identifying the updated interface template as the searched for interface template;
after identifying the searched for interface template, binding, by the client application, the service data to the first virtual view node by using an entry function;

determining, by the client application, location information of a widget based on the information stored in the first virtual view node;
retrieving, by the client application, the widget based on the location information;
generating, by the client application, a unified view of the graphical user interface comprising rendering the widget with the plurality of widgets associated with the graphical user interface; and
displaying, by the client application, the unified view of the graphical user interface on a display device.

2. The method of claim 1 , wherein information stored in the first virtual view node comprises information related to a tag and a type of a corresponding application.

3. The method of claim 1 , wherein updating the information stored in the first virtual view node comprises redrawing the unified view of the graphical user interface.

4. The method of claim 3 , wherein receiving the service data comprises invoking attributes and methods in native code.

5. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a client application from a server, JavaScript Object Notation (JSON) data corresponding to an interface template, the interface template being separate from the client application, wherein the JSON data is generated by the server by parsing Hypertext Markup Language of interface template data associated with the interface template, wherein the JSON data is written in a general protocol markup language comprising a syntax tree that is simpler than the syntax tree of the Hypertext Markup Language of the interface template data, and wherein the JSON data contains data corresponding to the Hypertext Markup Language of the interface template data comprising a plurality of tags each describing a respective widget, wherein each widget is a visual component included in a graphical user interface containing a plurality of widgets corresponding to the interface template;
identifying the interface template based on a first interface identifier included in the received data, wherein each interface template has a unique interface identifier to distinguish between different interface templates;
in response to identifying the interface template, determining a document object model node for each widget based on the JSON data, wherein each document object model node stores information related to each respective tag, and wherein each document object model node comprises location information of each respective widget in the interface template described by a respective tag;
parsing the JSON data into a tree structure of virtual view nodes for storing information for a plurality of document object model nodes of the interface template, each virtual view node storing a respective document object model node and at least one virtual view node comprising response event information associated with the client application;
retrieving, by a client application from the server, service data during a service data exchange procedure, wherein the service data contains a second interface identifier, wherein the service data contains service data for binding with a first virtual view node of the plurality of virtual view nodes;
searching, by the client application, for an interface template that corresponds to the second interface identifier;
in response to locating the searched for interface template, identifying the located interface template as the searched for interface template without initiating a server request;
in response to failing to locate the searched for interface template:
requesting a structured data of an updated interface template that corresponds to the second interface identifier from the server;
receiving the structured data of the updated interface template corresponding to the second interface identifier and instructing the first virtual view node to update its stored document object model node information based on the received structured data;
identifying the updated interface template as the searched for interface template
after identifying the searched for interface template, binding, by the client application, the service data to the first virtual view node by using an entry function;

determining location information of a widget based on the information stored in the first virtual view node;
retrieving the widget based on the location information;

Assignees

• Advanced New Technologies Co Ltd

Inventors

• He Sanyuan
• Rao Junxue
• Wang Fei
• Weng yuedong
• Zhu Deliang
• Sun Xi
• Wen Xuelong
• Xu Wenting
• Chen Rui
• Xi Jiangbo
• Deng Xufeng

Classifications

• G06F9/451

  Execution arrangements for user interfaces · CPC title

• H04L67/60

  Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) · CPC title

• G06F40/205

  Parsing · CPC title

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• G06F8/38 Primary

  for implementing user interfaces · CPC title