Method and apparatus for remotely displaying screen files and efficiently handling remote operator input

• US 8,732,588 B2
• Filed: 09/09/2008
• Issued: 05/20/2014
• Est. Priority Date: 09/09/2008
• Status: Active Grant

• Current Assignee: Applied Systems Incorporated
• Original Assignee: Applied Systems Incorporated
• Inventors: Klawitter, Paul T., Gallagher, Robert S.
• Primary Examiner(s): Pesin, Boris
• Assistant Examiner(s): Ell, Matthew
• Application Number:
  US12/207,448
• Publication Number:
  US 20100064230A1
• Time in Patent Office: 2,079 Days
• Field of Search: 715/748
• US Class Current: 715/748
• CPC Class Codes: G06F 9/452 Remote windowing, e.g. X-Window System, desktop virtualisation protocols for virtual reality H04L67/131

Abstract

A system and method for remotely displaying screen files and for trapping a customized set of operator input is disclosed. A server generates and deploys a plurality of screen files to a remote client. The screen files each include a plurality of display control elements and a list of events to be trapped and forwarded to the server. The list of events may be optimized for each particular screen file. The remote client displays the plurality of display control elements and stores the list of events. For any event that occurs which is included in the list of events, such as a submit data event, the remote client sends data indicative of the event to the server. The server interprets the data indicative of the occurrence of the event, processes the event, and, if appropriate, generates and sends a command to update the displayed representation of the screen file.

Claims

1. A method of remotely displaying data, the method comprising:

storing a database of content data;

storing a first screen file, the first screen file including a first display control element and a first set of trappable events including at least a first trappable event customized to the first display control element;

storing a second screen file, the second screen file including a second display control element and a second set of trappable events including at least a second trappable event customized to the second display control element, and the second set of trappable events is different from the first set of trappable events;

deploying the first screen file to a remote device configured to display the first control element and handle at least two events for the first screen file, the at least two events including at least the first trappable event and a third locally handled event;

receiving data indicative of a first trapped event corresponding to the first trappable event;

modifying the database of content data based on the data indicative of the first trapped event;

generating a command in response to the data indicative of the first trapped event, the command being sendable to alter the first display control element based on the first trapped event;

sending the command for execution by the remote device; and

deploying the second screen file to the remote device configured to display the second control element and handle at least two events for the second screen file, the at least two events including at least the second trappable event and a fourth locally handled event.

2. The method of claim 1, wherein the first display control element includes a representation of a feature of an interface of a software application.

3. The method of claim 2, wherein the feature is one selected from the group consisting of a list, a data entry field, a radio button, a check box, and a submit data button.

4. The method of claim 2, wherein the software application is database access software.

5. The method of claim 1, wherein the first trappable event is a selection of the first display control element.

6. The method of claim 1, wherein the modified database content reflects data entered into the first display control element.

7. The method of claim 1, wherein the command is additionally sendable to reveal a previously hidden third display control element.

8. The method of claim 7, wherein revelation of the third display control element causes an activation of an inactive third trappable event.

9. The method of claim 1, wherein the first screen file has a file size of less than twenty kilobytes.

10. The method of claim 1, wherein the first screen file has a file size of less than ten kilobytes.

11. The method of claim 1, wherein the first screen file has a file size of less than two kilobytes.

12. The method of claim 1, wherein the first screen file and the second screen file display different representations of a user interface of application software stored on a server.

13. The method of claim 12, wherein the application software is insurance database access software.

14. The method of claim 1, which is configured to be implemented using a data network.

15. The method of claim 14, wherein the data network is an internet.

16. A screen file deployment apparatus, the screen file deployment apparatus comprising:

at least one processor;

at least one memory device; and

at least one network interface device;

wherein the at least one processor is programmed to operate with the at least one memory device and the at least one network interface device to;

store a database of content data;

store a first screen file, the first screen file including a first display control element and a first set of trappable events including at least a first trappable event customized to the first display control element;

store a second screen file, the second screen file including a second display control element and a second set of trappable events including at least a second trappable event customized to the second display control element, and the second set of trappable events is different from the first set of tappable events;

deploy the first screen file to a remote device configured to display the first control element and handle at least two events for the first screen file, the at least two events including at least the first trappable event and third locally handled event;

receive data indicative of a first trapped event corresponding to the first trappable event;

modify the database of content data based on the data indicative of the first trapped event;

generate a command in response to the data indicative of the first trapped event, the command being sendable to alter the first display control element based on the first trapped event;

send the command for execution by the remote device; and

deploy the second screen file to the remote device configured to display the second control element and handle at least two events for the second screen file, the at least two events including at least the second trappable event and a fourth locally handled event.

17. The screen file deployment apparatus of claim 16, wherein the first display control element includes a representation of a feature of an interface of a software application executable by the processor.

18. The screen file deployment apparatus of claim 17, wherein the feature is one selected from the group consisting of a list, a data entry field, a radio button, a check box, and a submit data button.

19. The screen file deployment apparatus of claim 16, wherein the command is additionally sendable to reveal a previously hidden third display control element.

20. The screen file deployment apparatus of claim 19, wherein revelation of the third display control element causes an activation of an inactive third trappable event.

21. The screen file deployment apparatus of claim 16, wherein the first screen file has a file size on the at least one memory device of less than twenty kilobytes.

22. The screen file deployment apparatus of claim 16, wherein the first screen file has a file size on the at least one memory device of less than two kilobytes.

23. The screen file deployment apparatus of claim 16, wherein the first screen file and the second screen file display different representations of a user interface of application software stored on a server.

24. A non-transitory machine readable memory storing instructions structured to cause an apparatus to:

store a database of content data;

store a first screen file, the first screen file including a first display control element and a first set of trappable events including at least a first trappable event customized to the first display control element;

store a second screen file, the second screen file including a second display control element and a second set of trappable events including at least a second trappable event customized to the second display control element, and the second set of trappable events is different from the first set of trappable events;

deploy the first screen file to a remote device configured to display the first control element and handle at least two events for the first screen file, the at least two events including at least the first trappable event and a third locally handled event;

receive data indicative of a first trapped event corresponding to the first trappable event;

modify the database of content data based on the data indicative of the first trapped event;

generate a command in response to the data indicative of the first trapped event, the command being sendable to alter the first display control element based on the first trapped event;

send the command for execution by the remote device; and

deploy the second screen file to the remote device configured to display the second control element and handle at least two events for the second screen file, the at least two events including at least the second trappable event and a fourth locally handled event.

25. The non-transitory machine readable memory of claim 24, wherein the first display control element includes a representation of a feature of an interface of a software application executable by the processor.

26. The non-transitory machine readable memory of claim 25, wherein the feature is one selected from the group consisting of a list, a data entry field, a radio button, a check box, and a submit data button.

27. The non-transitory machine readable memory of claim 24, wherein the command is additionally sendable to reveal a previously hidden third display control element.

28. The non-transitory machine readable memory of claim 27, wherein revelation of the third display control element causes an activation of an inactive third trappable event.

29. The non-transitory machine readable memory of claim 24, wherein the first screen file has a file size on the at least one memory device of less than twenty kilobytes.

30. The non-transitory machine readable memory of claim 24, wherein the first screen file has a file size on the at least one memory device of less than two kilobytes.

31. The non-transitory machine readable memory of claim 24, wherein the first screen file and the second screen file display different representations of a user interface of application software stored on a server.