Combining server-side and client-side user interface elements

• US 8,959,142 B2
• Filed: 08/16/2012
• Issued: 02/17/2015
• Est. Priority Date: 02/29/2012
• Status: Active Grant

• Current Assignee: Zesty.ai, Inc.
• Original Assignee: Microsoft Corporation
• Inventors: D'Aurelio, Ryan James, Leece, Mark John Sawrey, Johnson, Zachariah Glen, Berrett, Douglas Duane, Kollenkark, Sean
• Primary Examiner(s): Hussain, Tauqir
• Application Number:
  US13/587,863
• Publication Number:
  US 20130226994A1
• Time in Patent Office: 915 Days
• Field of Search: 709/203
• US Class Current: 709/203
• CPC Class Codes: G06F 15/16 Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs coordinating program control therefor G06F9/52; in regulating and control system G05B
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions
• CPC Class Codes: G06F 21/00 Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 3/041 Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
• CPC Class Codes: G06F 3/048 Interaction techniques based on graphical user interfaces [GUI]
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/137 Hierarchical processing, e.g. outlines
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5683 Storage of data provided by user terminals, i.e. reverse caching

Abstract

A method and apparatus are disclosed for combining server-supplied user interface elements with client-supplied user interface elements. The server-supplied user interface elements can be received by a client device and inserted into a client-supplied object model, such as a Document Object Model (DOM). The object model can then be used to render a page, such as a webpage. By injecting server-supplied user interface elements into a client object model, the client can intelligently combine UI elements from a server with UI elements from a client. In the situation where there are conflicting or overlapping UI elements, the client device can modify the object model to eliminate such conflicts or overlaps.

Claims

1. A method of combining server-supplied user interface elements with client-supplied user-interface elements, comprising:

receiving user interface elements including style information from a server computer;

inserting the user interface elements and the style information into a client-supplied object model used to render a page;

rendering the page using the object model, wherein the object model includes client-supplied user interface elements and the user interface elements received from the server computer so that both the client-supplied user interface elements and the user interface elements received from the server computer are blended together on the rendered page, with the style information being applied to both the client-supplied user interface elements and the user interface elements received from the server computer;

wherein inserting includes searching on tags in the client-supplied object model and inserting the user interface elements and style information from the server computer between the tags; and

further including checking a network connection and if the network connection is down, using previously received user interface elements including the style information received from the server computer or suppressing the user interface elements from the server computer and expanding use of the client-supplied user interface elements.

2. The method of claim 1, wherein the user interface elements and style information from the server computer are in HTML.

3. The method of claim 1, wherein at least one of the tags is a division tag in the client-supplied object model.

4. The method of claim 1, wherein the object model is a Document Object Model used for HTML and further including the server computer for transmitting the user interface elements.

5. The method of claim 1, further including using a script to manipulate the user interface elements supplied by the server in the client-supplied object model.

6. The method of claim 1, wherein the user interface elements received from the server computer are cached and stored locally on the client device.

7. The method of claim 1, further including comparing the client-supplied user interface elements with the server-supplied user interface elements, and, if there is a match, suppressing at least one of the matching user interface elements.

8. The method of claim 1, further including receiving content from the server computer and inserting the content in the client-supplied object model.

9. The method of claim 8, wherein the content is XML data.

10. A computer-readable nonvolatile storage storing instructions for performing a method of displaying a page on a client device, the method comprising:

receiving server-supplied user interface elements and style information;

inserting the server-supplied user interface elements and the style information into a client-supplied Document Object Model including client-supplied user interface elements, wherein the inserting includes searching on a division tag in the Document Object Model and inserting the server-supplied user interface elements into the division tag;

checking a network connection and using the previously received server-supplied user interface elements and style information if the network connection is down or suppressing the server-supplied user interface elements and style information and using additional client-supplied user interface elements.

applying the style information to both the server-supplied user interface elements and the client-supplied user interface elements; and

displaying the server-supplied user interface elements with the client-supplied user interface elements on a same page using the Document Object Model on the client device with the applied styling information.

11. The computer-readable nonvolatile storage of claim 10, wherein receiving server-supplied user interface elements includes receiving HTML for displaying the server-supplied user interface elements.

12. The computer-readable nonvolatile storage of claim 10, further including executing a script on the client device and manipulating the server-supplied user interface elements in the Document Object Model.

13. An apparatus for displaying a page of content on a client device, comprising:

a controller on the client device;

memory for storing an object model used to display the page of content, wherein the controller is programmed to receive user interface elements and style information from a server computer and to insert, using one or more tags in the object model, the received user interface elements and style information in the object model for display so as to blend the received user interface elements from the server and user interface elements supplied by the client device;

a network connector coupled to the controller, wherein if the network connector has connectivity problems with a network, then the controller is programmed to insert previously received server-supplied user interface elements and style information into the object model;

a display for displaying the page of content using the object model including the user interface elements received from the server computer.

14. The apparatus of claim 13, wherein the object model is a Document Object Model and the user interface elements are in HTML.

15. The apparatus of claim 13, further including a script to manipulate the server-supplied user interface elements.

16. The apparatus of claim 15, wherein the script uses client data to make decisions about how to manipulate the server-supplied user interface elements.