Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Application of Recorded Actions on Similar Objects in a User Interface

IP.com Disclosure Number: IPCOM000213449D
Publication Date: 2011-Dec-14
Document File: 3 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database


Disclosed is a method to record a set of actions that the user performs on an object and at a later time apply the recorded actions on a similar object.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 41% of the total text.

Page 01 of 3

Application of Recorded Actions on Similar Objects in a User Interface

Record and playback functions of a macro recorder are limited to working within a single application or rudimentary in capturing user gestures. Advanced functions are only able to play back predefined (i.e., in the program) sequences of steps. Methods are needed that can associate complex recorded steps to an object of a specific type and apply the steps to other objects of the same type.

Macro recording support within an application is limited to that application's functions. Stand-alone macros are not effective in handling complex steps associated with an object of a particular type.

Disclosed is a method to record a series of actions performed by a user on a particular object to accomplish a change on the object so that it can be played on similar objects later, to achieve the same changes on them, without having the user manually repeat the actions on all the objects.

The proposed invention has advantages over several known recording mechanisms. Its working is not limited to a single application as in case of built-in macros; rather, it is able to record and make any changes on any file type maintained in any system. This automates the process of making the same set of changes on similar objects, reducing manual effort and errors.

Details for the various inventive components follow.

Recording Component

Records user activities. This may involve following processes:

• User requests to initiate recording. The application can be started as a standalone application either through keyboard (via short-cut key) or by a mouse-click on the installed application icon. It could also be possible that a standalone application launches the recording application to use it as a built-in feature.

• Object identification. After the application is started, it performs few steps to complete the object identification. This is actually associating the object type, properties, and state to the recording so that it can be later determined if a second object is of the same type and state. The application gathers information such as the file extension (i.e., file type), various operating system level properties of the file, and the properties specific to the owner application (only if the file is maintained by any particular application. For example, the file may be maintained by an Integrated Development Environment (IDE) that maintains information/states of the file (e.g., if the file is locked /checked out for editing in any repository). This might involve the object identification component to interact with the parent application of the object.

• Recording. The completion of the Object identification may fire the recording to record the user activities. This may include a few steps, as follows:

- Capture of user interaction. The application may use the known methods


Page 02 of 3

to capture user interaction. It may generate instructions in the background in response to ea...