Browse Prior Art Database

Record/Playback Model

IP.com Disclosure Number: IPCOM000106416D
Original Publication Date: 1993-Nov-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 2 page(s) / 66K

Publishing Venue

IBM

Related People

Conner, MH: AUTHOR [+2]

Abstract

Record/Playback of interactive operations is a requirement in application frameworks. A record/playback mechanism is used to create a recording of a group of consecutive operations. Such a recording can be playbacked again if the user needs to perform the same sequence of operations. This type of functionality simplifies the repetitive tasks that a user has to perform in interactive applications. The following describes a record/playback mechanism implemented by using System Object Model(SOM). The algorithm disclosed here is used internally in two application frameworks.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Record/Playback Model

      Record/Playback of interactive operations is a requirement in
application frameworks.  A record/playback mechanism is used to
create a recording of a group of consecutive operations.  Such a
recording can be playbacked again if the user needs to perform the
same sequence of operations.  This type of functionality simplifies
the repetitive tasks that a user has to perform in interactive
applications.  The following describes a record/playback mechanism
implemented by using System Object Model(SOM).  The algorithm
disclosed here is used internally in two application frameworks.

      An application framework establishes policies used by the
applications.  The applications can cooperate with each other if they
all behave  according to the rules set by the application framework.
The following describes a model that shows how a record/playback
mechanism is implemented by dividing application responsibilities
between the application object and application framework
implementation.

      Record/Playback Object Programming Model - An application
object writer designs recording logic when he/she implements the
class methods.  For each method invocation, a decision is made
whether to implement a recording.  For operations that require
recording logic,  the first line of the method body records
information about the current operation.

Example:

  In a text editor the user does the following operations:

     -- set search "key" and replacement key "newkey"

     -- search "key"

     -- replace "key" with "newkey"

     -- add a new line after this line.

     -- add a new word "newword" on current position.

  The operations that achieve this logic could be the following:

     -- SetSearchKey("key") (1)

     -- SetReplaceKey("newkey") (2)

     -- FindNextSearchPos (3)

     -- Replace (4)

     -- AddNewLine (5)

    -- AddNewWord("newword") (6)

  Each of the above operations will have a "RecordCommand" call
  as the first line in the method body.

  Each "RecordCommand" call reco...