Integrating native user interface components on a mobile device
First Claim
1. A method, comprising:
- presenting, by a mobile device, at least a portion of a window for a remote resource on a graphical user interface of the mobile device, wherein the remote resource is hosted by a remote computing device;
transmitting a click event from the mobile device to the remote computing device;
receiving, by the mobile device from the remote computing device, information associated with the window for the remote resource, wherein the information received from the remote computing device comprises an initialization packet that is responsive to the click event, and wherein the initialization packet contains Z-order information that may be used to identify a date picker native to the mobile device;
in response to receipt of the information from the remote computing device, comparing, by the mobile device, the Z-order information contained in the initialization packet to window data of a graphical user interface of the mobile device to determine that the date picker native to the mobile device should be activated, wherein the window data describes one or more properties of the window for the remote resource on the graphical user interface of the mobile device; and
displaying, on the mobile device, the date picker native to the mobile device;
receiving, from the remote computing device, a termination packet;
processing the termination packet to identify the date picker native to the mobile device; and
causing the date picker native to the mobile device to be not displayed on the mobile device.
7 Assignments
0 Petitions
Accused Products
Abstract
By enabling mobile devices, such as smart phones and tablets, to leverage native user interface components, the methods and systems described herein provide users a more seamless experience, wherein the user can potentially be oblivious to the fact that the application is not executing locally on the mobile device. In some embodiments, a user interface is provided which the user uses to trigger the display of a native user interface component. In some embodiments, the systems and methods described herein auto-adjust the pan and zoom settings on the mobile device to ensure that remote windows are presented in a manner that makes it easier for the user to interact with the device. The systems and methods described herein permit the user to switch to the new window in focus or a visual cue may be displayed to indicate that a window has been created somewhere on the remote desktop.
38 Citations
13 Claims
-
1. A method, comprising:
-
presenting, by a mobile device, at least a portion of a window for a remote resource on a graphical user interface of the mobile device, wherein the remote resource is hosted by a remote computing device; transmitting a click event from the mobile device to the remote computing device; receiving, by the mobile device from the remote computing device, information associated with the window for the remote resource, wherein the information received from the remote computing device comprises an initialization packet that is responsive to the click event, and wherein the initialization packet contains Z-order information that may be used to identify a date picker native to the mobile device; in response to receipt of the information from the remote computing device, comparing, by the mobile device, the Z-order information contained in the initialization packet to window data of a graphical user interface of the mobile device to determine that the date picker native to the mobile device should be activated, wherein the window data describes one or more properties of the window for the remote resource on the graphical user interface of the mobile device; and displaying, on the mobile device, the date picker native to the mobile device; receiving, from the remote computing device, a termination packet; processing the termination packet to identify the date picker native to the mobile device; and causing the date picker native to the mobile device to be not displayed on the mobile device. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A mobile computing device, comprising:
-
one or more processors; and memory storing executable instructions that, when executed by the one or more processors, cause the mobile computing device to; present at least a portion of a window for a remote resource on a graphical user interface of the mobile computing device, wherein the remote resource is hosted by a remote computing device; transmit a click event to the remote computing device; receive, from the remote computing device, information associated with the window for the remote resource, wherein the information received from the remote computing device comprises an initialization packet that is responsive to the click event, and wherein the initialization packet contains Z-order information that may be used to identify a date picker native to the mobile computing device; in response to receipt of the information from the remote computing device, compare the Z-order information contained in the initialization packet to window data of a graphical user interface of the mobile computing device to determine that the date picker native to the mobile computing device should be activated, wherein the window data describes one or more properties of the window for the remote resource on the graphical user interface of the mobile computing device; display the date picker native to the mobile computing device; receive, from the remote computing device, a termination packet; process the termination packet to identify the date picker native to the mobile computing device; and cause the date picker native to the mobile computing device to be not displayed on the mobile computing device. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. One or more non-transitory computer-readable media storing executable instructions that, when executed, cause a mobile computer device to:
-
present at least a portion of a window for a remote resource on a graphical user interface of the mobile computing device, wherein the remote resource is hosted by a remote computing device; transmit a click event to the remote computing device; receive, from the remote computing device, information associated with the window for the remote resource, wherein the information received from the remote computing device comprises an initialization packet that is responsive to the click event, and wherein the initialization packet contains Z-order information that may be used to identify a date picker native to the mobile computing device; in response to receipt of the information from the remote computing device, compare the Z-order information contained in the initialization packet to window data of a graphical user interface of the mobile computing device to determine that the date picker native to the mobile computing device should be activated, wherein the window data describes one or more properties of the window for the remote resource on the graphical user interface of the mobile computing device; display the date picker native to the mobile computing device; receive, from the remote computing device, a termination packet; process the termination packet to identify the date picker native to the mobile computing device; and cause the date picker native to the mobile computing device to be not displayed on the mobile computing device.
-
Specification