Framework for Ordered Handling of Information

• US 20070121125A1
• Filed: 01/24/2007
• Published: 05/31/2007
• Est. Priority Date: 10/24/2003
• Status: Active Grant

• Current Assignee: ServiceNow Incorporated
• Original Assignee: Microsoft Corporation
• Inventors: Balaz, Rudolph, Krantz, Brigette, Feldman, Kyril, Dodge, Steve, Biswas, Manoj, Pichaiah, Shenbagalakshmi, Kolmykov-Zotov, Alexander, Goldberg, Arin
• Granted Patent: US 7,428,736 B2
• Time in Patent Office: Days
• US Class Current: 358/1.100
• CPC Class Codes: G06F 3/038 Control and interface arrangements therefor, e.g. drivers or device-embedded control circuitry
• CPC Class Codes: G06F 3/04883 for inputting data by handwriting, e.g. gesture or text
• CPC Class Codes: G06F 3/1204 resulting in reduced user or operator actions, e.g. presetting, automatic actions, using hardware token storing data
• CPC Class Codes: G06F 3/1206 resulting in increased flexibility in input data format or job format or job type
• CPC Class Codes: G06F 3/1263 based on job priority, e.g. re-arranging the order of jobs, e.g. the printing sequence
• CPC Class Codes: G06F 3/1284 Local printer device
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06V 30/1423 the instrument generating sequences of position coordinates corresponding to handwriting preprocessing or recognising digital ink G06V30/32

Abstract

A system and process for ensuring the smooth flow of electronic ink is described. Dynamic rendering is give priority over other event handlers. Priority may be the use of one or more queues to order when events occur and may be performing dynamic rendering prior to other steps.

Claims

1. A system for processing information comprising:

a storage;

a processor exchanging information with said a storage, said processor hosting a component, said component including;

a synchronous interface to which a first plug-in object is attached, said first plug-in object processing information received by said component synchronously with the receipt of said information by said component, said first plug-in object being a rendering object; and

an asynchronous interface to which a second plug-in object is attached, said second plug-in object processing information received by said component asynchronously with the receipt of said information by said component.

2. The system according to claim 1, where said rendering object is a dynamic rendering object.

3. The system according to claim 2, where said dynamic rendering object includes a temporary storage where information to be rendered is temporarily stored.

4. The system according to claim 3, further comprising:

a storage where information to be rendered is stored, said storage being separate from said dynamic rendering object.

5. The system according to claim 1, wherein said information processed by said second plug-in object is the same information processed by said first plug-in object.

6. The system according to claim 1, wherein said information processed by said second plug-in object is different from the information processed by said first plug-in object, where said first plug-in object modified the information to be later processed by said second plug-in object.

7. The system according to claim 1, said component further including an output queue, said output queue receiving information having been processed by said first plug-in object.

8. The system according to claim 1, said component further including an input queue, said input queue receiving information generated by said first plug-in object to be processed by said first plug-in object.

9. The system according to claim 1, said component further comprising:

a third interface to which a third plug-in object is attached, said third plug-in object processing information having been processed by said first plug-in object.

10. The system according to claim 9, wherein said second plug-in object and said third plug-in object process information asynchronously with regards to information received by said component.

11. The system according to claim 9, wherein at least one of said first plug-in object and said third plug-in object form part of a list attached to said component.

12. The system according to claim 9, wherein at least one of said first plug-in object and said third plug-in object form part of a chain attached to said component.

13. A system for processing information comprising:

a storage;

a processor exchanging information with said a storage, said processor hosting a component, said component including;

a synchronous interface to which a first plug-in object is attached, said first plug-in object processing information received by said component synchronously with the receipt of said information by said component; and

an asynchronous interface to which a second plug-in object is attached, said second plug-in object processing information received by said component asynchronously with the receipt of said information by said component,

wherein one of said first plug-in object and said second plug-in object is a gesture recognizer object.

14. The system according to claim 13, said component further comprising:

a third interface to which a third plug-in object is attached, said third plug-in object processing information having been processed by said first plug-in object.

15. The system according to claim 13, where said gesture recognizer object is said first plug-in object.

16. The system according to claim 13, where said gesture recognizer object is said second plug-in object.

17. The system according to claim 15, where said gesture recognizer object is said first plug-in object, said component further including a dynamic renderer plug-in attached to said synchronous interface.

18. The system according to claim 16, where said gesture recognizer object receives information from said component having been modified by at least one plug-in object attached to said synchronous interface.

19. The system according to claim 13, where said component includes a queue that receives information from at least one plug-in object associated with said synchronous interface and temporarily stores said information for at least one plug-in object associated with said asynchronous interface.

20. The system according to claim 13, where said component includes a queue that receives information from at least one plug-in object associated with said synchronous interface and temporarily stores said information to be later handled by said at least one plug-in object associated with said synchronous interface.