Generic interface

• US 7,199,885 B2
• Filed: 11/15/2004
• Issued: 04/03/2007
• Est. Priority Date: 10/24/2003
• Status: Active Grant

• Current Assignee: ServiceNow Incorporated
• Original Assignee: Microsoft Corporation
• Inventors: Feldman, Kyril, Kolmykov-Zotov, Alexander J., Dodge, Steve, Goldberg, Arin J., Balaz, Rudolph, Biswas, Manoj K., Pichaiah, Shenbagalakshmi, Krantz, Brigette
• Primary Examiner(s): Lamb; Twyler
• Assistant Examiner(s): Ebrahimi; Saeid
• Application Number:
  US10/986,779
• Publication Number:
  US 20050093840A1
• Time in Patent Office: 869 Days
• Field of Search: 358/1.1, 358/1.13, 709/218, 709/203, 719/310, 719/331, 250/458.1, 250/401, 382/186
• US Class Current: 358/1.1
• 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 method for communicating between a component and plug-in objects, said component including a synchronous interface and an asynchronous interface, said method comprising the steps of:

receiving a data packet at said component;

placing said data packet at a location;

notifying a list of plug-in objects to the existence of said data packet;

processing said data packet through said list of plug-in objects using said synchronous interface;

receiving said data packet from said list of plug-in objects;

placing said data packet in an output queue of said component;

notifying a second list of plug-in objects to the existence of said data packet; and

processing said data packet through said second list of plug-in objects through said asynchronous interface.

2. A method for relating plug-in objects to a component comprising the steps of:

forming a first list that may contain a reference to plug-in objects;

attaching said first list to a synchronous interface of said component;

populating said first list with references to at least one plug-in object,

forming a second list that may contain a reference to plug in objects;

attaching said second list to an asynchronous interface of said component; and

populating said second list with references to at least one plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first list, and

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second list attached to said asynchronous interface.

3. A method for relating plug-in objects to a component comprising the steps of:

attaching a first plug-in object to a synchronous interface on said component; and

attaching a second plug-in object to a synchronous interface on said first plug-in object to form a first chain linking said component, said first plug-in object, and said second plug-in object;

attaching a third plug-in object to an asynchronous interface on said component; and

attaching a fourth plug-in object to an asynchronous interface on said third plug-in object to form a second chain linking said component, said third plug-in object, and said fourth plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first chain,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second chain.

4. A system for communicating between a component and plug-in objects, said component having a synchronous interface and an asynchronous interface, said system comprising:

means for receiving a data packet at said component;

means for placing said data packet at a location;

means for notifying a list of plug-in objects to the existence of said data packet;

means for processing said data packet through said list of plug-in objects using said synchronous interface;

means for receiving said data packet from said list of plug-in objects;

means for placing said data packet in an output queue of said component;

means for notifying a second list of plug-in objects to the existence of said data packet; and

means for processing said data packet through said second list of plug-in objects through said asynchronous interface.

5. A system for relating plug-in objects to a component, said component including a synchronous interface and an asynchronous interface, said system comprising:

means for forming a first list that may contain a reference to plug-in objects;

means for attaching said first list to a synchronous interface of said component;

means for populating said first list with references to at least one plug-in object;

means for forming a second list that may contain a reference to plug-in objects;

means for attaching said second list to said asynchronous interface of said component; and

means for populating said second list with references to at least one plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first list, and

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second list attached to said asynchronous interface.

6. A system for relating plug-in objects to a component, said component including a synchronous interface and an asynchronous interface, said system comprising:

means for attaching a first plug-in object to an interface on said component;

means for attaching a second plug-in object to an interface on said first plug-in object to form a first chain linking said component, said first plug-in object, and said second plug-in object;

means for attaching a third plug-in object to said asynchronous interface on said component; and

means for attaching a fourth plug-in object to an asynchronous interface on said third plug-in object to form a chain linking said component, said third plug-in object, and said fourth plug-in object,

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said first chain, and

wherein data may be processed by said plug-in objects according to the order of said plug-in objects in said second chain.