Application programming interface for providing native and non-native display utility
Abstract
Systems are presented including: a first electronic device operative to receive a first input, the first electronic device including: a first data communication unit operative to connect the first electronic device to a second electronic device; and a first processing unit operative to process the first input to generate information representing at least a portion of a first intended display, and operative to establish at least one communication channel between the first and second electronic devices using the first data communication unit operative and to call at least one application programming interface to forward the information representing the at least the portion of the first intended display to the second electronic device for display, and further operative to receive and process a representation of a second input from the second electronic device.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1. A system comprising:
a first electronic device memory with instructions encoded thereon, an operating system framework, and one or more processors that, when executing the instructions, are caused to perform operations comprising:
a first processing unit operative to generategenerating a first intended image to be drawn on a first screen that is a full screen image at the first electronic device native window at a native display for navigation by executing at least one of a plurality of corresponding applications of the first processing unit an application in communication with the operating system framework, wherein native user inputs received from native sources are processed to update the native window;
and operative to generate information representing at least a portion ofgenerating a second intended image to be drawn on a non-native window area on a second screen at a second electronic device from non-native display based on at least a portion of content accessible shown in the first image by at least one of the plurality of corresponding applications the application responding to an event at the first electronic device, wherein the second intended image is distinct from the first intended image and is optimized has a layout on the non-native display based on resolution information of the a non-native window area of the second screen non-native display,
and operative to forward the information representing at least the portion offorwarding the second intended image to the second screen non-native window for display by calling at least one application programming interface (API) by executing at least one of the plural of corresponding applications the application in communication with the operating system framework, wherein the application migrates from the native window of the native display to the non-native window of the non-native display and enables the corresponding non-native inputs to continue the navigation at the non-native display; and
and further operative to receive and processreceiving and processing a representation of a secondnon-native input initiated by a user at the second electronic devicea non-native user input interface in response to the second intended image by executing at least one of the plurality of corresponding applications the application in communication with the operating system framework, and operative to forward information representing at least a portion of forwarding a third intended image to update the second screen non-native window that is generated as a result of processing the second non-native input at the first electronic device by executing at least one of the plurality of corresponding applications, wherein the second device and the second screen could be configured within the first electronic device the application in communication with the operating system framework, wherein non-native user inputs received from non-native sources are different from the native sources.
2. The system of claim 1 , wherein the second intended image is drawn to the non-native window area of the second electronic device non-native display based on “toggle frame” to synchronize draw content of a HyperText Markup Language (HTML) frame from the native window of the first screen native display that has multiple frames, to the non-native window area of the second screen non-native display, wherein the information and images second image drawn on the non-native window area is based on a document content related to-the to the HTML frame of the first screen native display, wherein the second image drawn is optimized has a layout on the non-native display based on the resolution information of the non-native window area of the second screen non-native display, wherein the second intended image drawn using the HTML frame is distinct from the first intended image of the first electronic device native display, wherein the full screen of the first electronic device native display has at least one HTML windows window that contains the HTML frame as one of the multiple frames in the native window.
3. The system of claim 1 , wherein the user input at the second device reception of the non-native input is configured through executing at least one of a callback application programming interface by at least one of the plural of corresponding applications the application.
4. The system of claim 1 , wherein the plurality of corresponding applications of the first processing unit are designed to work together application is configured to do the following intended tasks: to create and show the first and the second intended imagesthat are distinct and synchronized, and to update the first intended image after determine whether a user input is a native user input or a non-native user input before processing the user inputassociated with the second intended image of the window area on the second screen at the second electronic device.
5. The system of claim 1 , wherein the non-native window area of the second screen non-native display is a full screen window of the second electronic device non-native display.
6. The system of claim 1 , wherein a communication channel between the first electronic device native display and the second electronic device non-native display is based on wired or wireless communication network.
7. The system of claim 1 , wherein the first event is an input selected from the group consisting of: a graphical user interface input, a physical user input and a programmatic input related interface such as an operating system (OS) framework.
8. The system of claim 1 , wherein the non-native user input at the second electronic device comprises a navigation command to navigate content generated from the first electronic device application and displayed on the second electronic device non-native display.
9. The system of claim 8 , wherein the two electronic devices native display and the non-native display are used to navigate browser contentselected from any of the group consisting of: browser page content, web content, video content, electronic book content, and document content.
10. The system of claim 1 , wherein the second electronic device non-native display has a graphical user interface that is synchronized with includes content that is based on at least a portion of the content first image displayed on the first screen of the first electronic device native display, and the graphical user interface of the non-native display is used for content navigation while the native display is turned off.
11. The system of claim 1 , wherein the second intended image is displayed as a portion partial screen window of the second screen at the second electronic device non-native display.
12. The system of claim 1 , wherein the at least one application programming interface (API) at the first electronic device associated with interacting with the second electronic device is enabled with a multi-tasking operating systemof the first electronic device selected from the group consisting of: WINDOWS, WINDOWS CE, WINDOWS mobile, APPLE iPhone system, APPLE OS X, Linux, UNIX, and a UNIX derivative OS.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.