COMBINING SERVER-SIDE AND CLIENT-SIDE USER INTERFACE ELEMENTS
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.
Latest Microsoft Patents:
This application is a continuation of U.S. patent application Ser. No. 13/587,863, filed Aug. 16, 2012, which claims priority from U.S. Provisional Application No. 61/605,119, filed Feb. 29, 2012, which applications are incorporated herein by reference in their entirety.
BACKGROUNDThe Document Object Model (DOM) is an application programming interface (API) for HTML and XML documents. It defines the logical structure of documents and ways for documents to be accessed and manipulated. One objective for DOM is to provide a standard programming interface that can be used in a wide variety of environments and applications. Generally, DOM provides a hierarchical tree structure having a plurality of nodes in parent/child relationships. Using this structure, script programs can examine and dynamically change a web page.
Other languages can be associated with object models different than DOM. However, whatever model is used, it is desirable to allow programmers to build documents, navigate their structure, and add, modify, or delete elements and content.
Even with well-defined object models, authoring pages that can be used across different platforms can be challenging. For example, different pages often need to be created based on whether the page is to be displayed on a server or a client, despite an overlap in content between the pages. In one simple example, a server-side page can display headers and footers that are not displayed on a client page. In such a situation, two different pages need to be created even if the content is the same.
SUMMARYThis Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
A method and apparatus are disclosed for combining server-supplied user interface elements with client-supplied user interface (UI) 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. Thus, the client's access to user information stored on the client device can be used to modify server-supplied UI elements. Additionally, by being able to dynamically modify the object model, a page can be created for different platforms and then modified in the object model.
The foregoing and other objects, features, and advantages of the invention will become more apparent from the following detailed description, which proceeds with reference to the accompanying figures.
It will be understood by those skilled in the art that building an object model on the client device using server-supplied UI elements and client-supplied UI elements is fundamentally different than simply rendering a page that pulls in images or text from a server computer, as such images or text are not copied to the object model and cannot be manipulated by a client script.
With reference to
A computing environment may have additional features. For example, the computing environment 600 includes storage 640, one or more input devices 650, one or more output devices 660, and one or more communication connections 670. An interconnection mechanism (not shown) such as a bus, controller, or network interconnects the components of the computing environment 600. Typically, operating system software (not shown) provides an operating environment for other software executing in the computing environment 600, and coordinates activities of the components of the computing environment 600.
The tangible storage 640 may be removable or non-removable, and includes magnetic disks, magnetic tapes or cassettes, CD-ROMs, DVDs, or any other medium which can be used to store information in a non-transitory way and which can be accessed within the computing environment 600. The storage 640 can store instructions for the software 680 implementing one or more innovations disclosed herein for combining client-supplied and server-supplied UI elements.
The input device(s) 650 may be a touch input device such as a keyboard, mouse, pen, or trackball, a voice input device, a scanning device, or another device that provides input to the computing environment 600. The output device(s) 660 may be a display, printer, speaker, CD-writer, or another device that provides output from the computing environment 600.
The communication connection(s) 670 enable communication over a communication medium to another computing entity. The communication medium conveys information such as computer-executable instructions, audio or video input or output, or other data in a modulated data signal. A modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired or wireless techniques implemented with an electrical, optical, RF, or other carrier.
The techniques and tools can be described in the general context of computer-readable media. Computer-readable media are any available tangible media that can be accessed within a computing environment. By way of example, and not limitation, with the computing environment 600, computer-readable media include memory 620, storage 640, and combinations of any of the above.
The techniques and tools can be described in the general context of computer-executable instructions, such as those included in program modules, being executed in a computing environment on a target real or virtual processor. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Computer-executable instructions for program modules may be executed within a local or distributed computing environment.
The terms “system” and “device” are used interchangeably herein. Unless the context clearly indicates otherwise, neither term implies any limitation on a type of computing system or computing device. In general, a computing system or computing device can be local or distributed, and can include any combination of special-purpose hardware and/or general-purpose hardware with software implementing the functionality described herein.
For the sake of presentation, the detailed description uses terms like “determine” and “select” to describe computer operations in a computing environment. These terms are high-level abstractions for operations performed by a computer, and should not be confused with acts performed by a human being. The actual computer operations corresponding to these terms vary depending on implementation.
Although the operations of some of the disclosed methods are described in a particular, sequential order for convenient presentation, it should be understood that this manner of description encompasses rearrangement, unless a particular ordering is required by specific language set forth below. For example, operations described sequentially may in some cases be rearranged or performed concurrently. Moreover, for the sake of simplicity, the attached figures may not show the various ways in which the disclosed methods can be used in conjunction with other methods.
Any of the disclosed methods can be implemented as computer-executable instructions stored on one or more computer-readable storage media (e.g., non-transitory computer-readable media, such as one or more optical media discs, volatile memory components (such as DRAM or SRAM), or nonvolatile memory components (such as hard drives)) and executed on a computer (e.g., any commercially available computer, including smart phones or other mobile devices that include computing hardware). Any of the computer-executable instructions for implementing the disclosed techniques as well as any data created and used during implementation of the disclosed embodiments can be stored on one or more computer-readable media (e.g., non-transitory computer-readable media). The computer-executable instructions can be part of, for example, a dedicated software application or a software application that is accessed or downloaded via a web browser or other software application (such as a remote computing application). Such software can be executed, for example, on a single local computer (e.g., any suitable commercially available computer) or in a network environment (e.g., via the Internet, a wide-area network, a local-area network, a client-server network (such as a cloud computing network), or other such network) using one or more network computers.
For clarity, only certain selected aspects of the software-based implementations are described. Other details that are well known in the art are omitted. For example, it should be understood that the disclosed technology is not limited to any specific computer language or program. For instance, the disclosed technology can be implemented by software written in C++, Java, Perl, JavaScript, Adobe Flash, or any other suitable programming language. Likewise, the disclosed technology is not limited to any particular computer or type of hardware. Certain details of suitable computers and hardware are well known and need not be set forth in detail in this disclosure.
The disclosed framework allows the client to blend UI elements delivered from the Internet with UI already on the client. This allows for sensitive business logic to be executed on the server, where it is more secure and updatable. These UI elements can then be seamlessly blended with client elements. For example, HTML, CSS and Javascript can be delivered securely from the Internet and injected into Client's DOM. This method allows code delivered from the server to blend with UI elements generated on the client. This is valuable because the client has access to user information that the server does not have.
In view of the many possible embodiments to which the principles of the disclosed invention may be applied, it should be recognized that the illustrated embodiments are only preferred examples of the invention and should not be taken as limiting the scope of the invention. Rather, the scope of the invention is defined by the following claims. We therefore claim as our invention all that comes within the scope of these claims.
Claims
1-20. (canceled)
21. A user device capable of combining server-supplied user interface elements with client-supplied user-interface elements, comprising:
- a processor;
- a display;
- an input device; and
- memory storing instructions that when executed by the processor cause the user device to: receive server-supplied user interface elements and style information from a server computer; insert the server-supplied user interface elements into a client-supplied object model, wherein the object model also includes client-supplied user interface elements; and render, for viewing by a user of the device on the display, a page using the object model so that both one or more of the client-supplied user interface elements and one or more of the server-supplied user interface elements appear together on the rendered page, wherein the rendering further comprises: comparing at least one client-supplied user interface element with at least one server-supplied user interface element and, if there is a match, suppressing at least one client-supplied user interface element or at least one user interface element received from the server computer; applying the style information to both the one or more of the client-supplied user interface elements and the one or more of the server-supplied user interface elements.
22. The user device of claim 21, wherein the server-supplied user interface elements and style information are in HTML.
23. The user device of claim 21, wherein the inserting includes searching on a division tag in the client-supplied object model and inserting the user interface elements and style information from the server computer into the division tag.
24. The user device of claim 21, wherein the object model is a Document Object Model used for HTML and further including the server computer for transmitting the user interface elements.
25. The user device of claim 21, wherein the user interface elements received from the server computer are cached and stored locally on the client device.
26. The user device of claim 21, wherein the instructions, when executed by the processor, further cause the user device to receive server-supplied content from the server computer and insert the server-supplied content in the client-supplied object model.
27. The user device of claim 26, wherein the server-supplied content is XML data.
28. The user device of claim 1, wherein the user device is a mobile device and the input device is a touch screen.
29. A method for allowing a server computer to control aspects of the look and feel of a user interface on a mobile user device comprising:
- receiving server-supplied user interface elements and style information from a server computer;
- searching on a division tag in a client-supplied object model used to render a page on a display on the mobile user device, wherein the client-supplied object model contains client-supplied user interface elements;
- inserting the server-supplied user interface elements into a client-supplied object model used to render a page on the display, wherein the inserting comprises inserting at least one of the server-supplied user interface elements into the division tag, based on the results of the searching; and
- rendering, for viewing by a user of the mobile user device, the page using the object model so that both one or more of the client-supplied user interface elements and one or more of the server-supplied user interface elements appear on the rendered page, wherein the rendering further comprises applying the style information to both the one or more of the client-supplied user interface elements and the one or more of the server-supplied user interface elements.
30. The method of claim 29, wherein the rendering further comprises comparing at least one client-supplied user interface element with at least one server-supplied user interface element and, if there is a match, suppressing at least one client-supplied user interface element or at least one user interface element received from the server computer.
31. The method of claim 29, wherein the server-supplied user interface elements and style information are in HTML.
32. The method of claim 29, wherein the object model is a Document Object Model used for HTML and further including the server computer for transmitting the user interface elements.
33. The method of claim 29, wherein the user interface elements received from the server computer are cached and stored locally on the mobile user device.
34. The method of claim 29, further comprising receiving server-supplied content from the server computer and inserting the server-supplied content in the client-supplied object model.
35. The method of claim 34, wherein the server-supplied content is XML data.
36. The method of claim 34, wherein the rendering further comprises rendering the server-supplied content.
37. A method for applying server-supplied style information to a combination of server-supplied user interface elements and client-supplied user-interface elements, comprising:
- in response to user interaction with an input device on a client device, receiving the server-supplied user interface elements and style information from a server computer;
- adding the server-supplied user interface elements to a client-supplied object model that contains client-supplied user interface elements, wherein the object model is used to render a page on a display of the client device;
- for viewing by the user, rendering the page using the client-supplied object model, wherein the rendering comprises: comparing at least one client-supplied user interface element with at least one server-supplied user interface element and, if there is a match, suppressing at least one client-supplied user interface element or at least one user interface element received from the server computer; applying the style information to both one or more of the client-supplied user interface elements and one or more of the server-supplied user interface elements; and displaying together on the rendered page the one or more of the client-supplied user interface elements and the one or more of the server-supplied user interface elements.
38. The method of claim 37, wherein the rendering further comprises expanding the area on the display for the client-supplied user interface elements.
39. The method of claim 37, wherein adding includes searching on a division tag in the client-supplied object model and adding the user interface elements and style information from the server computer into the division tag.
40. The method of claim 37, further comprising caching the server-supplied user interface elements at the client device.
Type: Application
Filed: Feb 27, 2017
Publication Date: Jun 15, 2017
Applicant: Microsoft Technology Licensing, LLC (Redmond, WA)
Inventors: Ryan James D'Aurelio (Seattle, WA), Mark John Sawrey Leece (Bellevue, WA), Zachariah Glen Johnson (Woodinville, WA), Douglas Duane Berrett (Seattle, WA), Sean Kollenkark (Seattle, WA)
Application Number: 15/443,158