Patent classifications
G06F2209/545
Method and electronic device for sending and receiving data
A method and an electronic device for sending and receiving data are provided. The method of the electronic device for sending and receiving data includes detecting a communication event of other electronic device, if detecting the communication event, sending information of an application running on the electronic device, to the other electronic device, receiving information of an application running on the other electronic device, from the other electronic device, determining an application execution screen by comparing the application information of the electronic device with the application information received from the other electronic device, and displaying the determined application execution screen.
GRAPHICS RENDERING METHOD AND APPARATUS
This application provides a graphics rendering method and apparatus. A service starts an application and obtains a rendering instruction sent by the application; and sends the rendering instruction to an electronic device. The electronic device performs graphics rendering according to the rendering instruction, to display an image related to the application. According to the technical solutions provided in this application, the electronic device, instead of the server, can perform graphics rendering according to the rendering instruction, thereby improving picture quality and user experience.
Computing system with contextual interaction mechanism and method of operation thereof
A method of operation of a computing system includes: determining a context for performing a user-initiated action; determining an operational order based on the context for performing the user-initiated action; and generating an application order based on the operational order for implementing an execution file and a further executable file according to the application order to perform the user-initiated action through displaying on a device.
Method and system for focus management in a software application
A method for focus management in a software application, wherein at least a subset of Node objects of said software application forms a hierarchy of Node objects and wherein each Node object of said hierarchy of Node objects of said software application comprises: a first routine that when returning true denotes that the Node object is a focused one; and a second routine that when returning true denotes that the Node object is a focused, or at least one of its descendants is a focused; a routine for handling an incoming event; the method comprising the steps of: providing, for each Node object of said hierarchy of Node objects a third routine, that when returning true denotes that the Node object and all descendants of the Node object, excluding these Node objects for which the third routine returns true, forms a single monofocus area having a single focus root.
Application state client-side cache for a state-based client-server application
A client updates a display of a user interface associated with a state-based client-server application in accordance with a client-side cache. The server supplies data for a new state and additional data for one or more subsequent states that possibly follow the new state if appropriate one or more operations are performed. When a client request is generated that indicates an operation that causes the application to transition to the new state, the client updates the display in accordance with the data that corresponds to the new state from the client-side cache, if available from the client-side cache. The new state data is available since the server has previously supplied the new state data.
Proxy gesture recognizer
An electronic device displays one or more views. A first view includes a plurality of gesture recognizers. The plurality of gesture recognizers in the first view includes one or more proxy gesture recognizers and one or more non-proxy gesture recognizers. Each gesture recognizer indicates one of a plurality of predefined states. A first proxy gesture recognizer in the first view indicates a state that corresponds to a state of a respective non-proxy gesture recognizer that is not in the first view. The device delivers a respective sub-event to the respective non-proxy gesture recognizer that is not in the first view and at least a subset of the one or more non-proxy gesture recognizers in the first view. The device processes the respective sub-event in accordance with states of the first proxy gesture recognizer and at least the subset of the one or more non-proxy gesture recognizers in the first view.
USER INTERFACE PROCESSING METHOD AND DEVICE
Disclosed are a user interface processing method and device. The method is applied to a user terminal which is configured to execute a game client, the game client comprises a first thread and a second thread, and the second thread is pre-packaged in a browser kernel of the game client, and the method includes: obtaining, by the first thread, a user interface rendering event which is to be processed: obtaining by the second thread, a to-be-rendered object corresponding to the user interface rendering event; rendering, by the second thread, the to-be-rendered object, and sending a rendering result to the first thread through a first interface, wherein the first interface is an interface provided by the second thread for storing the rendering result and presenting by the first thread, the rendering result.
Reverse seamless integration between local and remote computing environments
Methods and systems for transparent user interface integration between remote applications and their local counterparts are described, providing a seamless, unified user experience, and allowing integration of a start menu, dock, taskbar, desktop shortcuts, windows, window and application switching, system tray elements, client-to-host and host-to-client file type association, URL redirection, browser cookie redirection, token redirection, status message interception and redirection, and other elements. These methods and systems further enhance theme-integration between a client and remote desktop or virtual machine by remoting all UI elements to a recipient for generation, including text controls, buttons, progress bars, radio buttons, list boxes, or other elements; presenting them with the receiver's product and OS-specific UI; and returning status back to the sender. This may achieve a more unified and transparent UI integration. Furthermore, international text may be correctly received in cross-language environments, or translated into the language of the presenting environment.
Proxy gesture recognizer
An electronic device displays one or more views. A first view includes a plurality of gesture recognizers. The plurality of gesture recognizers in the first view includes one or more proxy gesture recognizers and one or more non-proxy gesture recognizers. Each gesture recognizer indicates one of a plurality of predefined states. A first proxy gesture recognizer in the first view indicates a state that corresponds to a state of a respective non-proxy gesture recognizer that is not in the first view. The device delivers a respective sub-event to the respective non-proxy gesture recognizer that is not in the first view and at least a subset of the one or more non-proxy gesture recognizers in the first view. The device processes the respective sub-event in accordance with states of the first proxy gesture recognizer and at least the subset of the one or more non-proxy gesture recognizers in the first view.
Data shipper agent management and configuration systems and methods
Data shipper agent management and configuration systems and methods are disclosed herein. In some embodiments, an example method includes enrolling data shipper agents which are installed on edge nodes, receiving selections of one or more tags for the data shipper agents, each of the one or more tags representing one or more services assigned to the data shipper agents, configurations of the services being modifiable through the one or more GUIs using a configuration application programming interface (API), providing the one or more GUIs, receiving configurations for at least one of the modules of one of the data shipper agents through one of the one or more GUIs, and automatically reconfiguring the configurations to other ones of the data shipper agents automatically.