Cross platform and cross operating system macros

• US 6,357,038 B1
• Filed: 04/13/1998
• Issued: 03/12/2002
• Est. Priority Date: 04/13/1998
• Status: Expired due to Term

• Current Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Scouten, Eric A.
• Primary Examiner(s): Powell, Mark R.
• Assistant Examiner(s): NGUYEN BA, HOANG VU A
• Application Number:
  US09/059,167
• Time in Patent Office: 1,429 Days
• Field of Search: 395/703, 395/685, 395/200.36, 395/704, 345/348, 345/335, 345/331, 324/760, 714/738, 717/3, 717/4, 717/1, 703/26, 703/27, 703/28
• US Class Current: 717/122
• CPC Class Codes: G06F 9/45512 Command shells

Abstract

A macro for use by an application program is described. The macro is embedded in a macro file including at least two versions of executable configuration code corresponding to two different operating systems to interface the macro file to an application program. Attached to the macro file is a sequence of actions to apply to an application file produced by the application program. Also attached is application identification information that identifies an original host application corresponding to the macro. The sequence of actions in the macro file can be produced by storing commands, applied to a data file opened in the application program, into a log file and transferring at least one stored command from the log file to the macro file.

Claims

1. A method of producing a macro file for use by an application program comprising:

producing a macro file including at least two versions of configuration code corresponding to two different operating systems to interface the macro file to an application program;

attaching to the macro file a sequence of actions to apply to an application file, said sequence of actions providing the macro file with the sequence of actions produced by use of the application program; and

attaching application identification information to the macro file that identifies an original host application corresponding to the macro file.

3. The method of claim 1 wherein the configuration code for at least two versions is executable configuration code.

4. The method of claim 1 wherein the macro file is stored independent of the application program in an address location outside of an application program address space.

5. The method of claim 1 further comprising:

transferring the macro file on a computer storage medium.

6. The method of claim 5, further comprising:

transferring the macro file to a folder corresponding to a computer desktop folder such that an icon pointing to the macro file can be displayed on the computer desktop.

2. The method of attaching application identification information further comprises inserting a call to the application program that produced the macro file into the executable.

7. A computer program product residing on a computer readable medium for producing a macro for use by an application program comprising instructions for causing a computer to:

produce a macro file including executable configuration code to interface the macro file to an application program;

insert at least two versions of executable configuration code corresponding to two different operating systems;

attach to the macro file a sequence of actions to apply to an application file produced by the application program;

package the sequence of actions into an executable; and

attach application identification information to the macro file that identifies an original host application corresponding to the macro file and to insert a call to the application program into the macro file.

8. A data structure stored on a computer readable medium representing a macro file, said data structure comprising:

a field for a first executable configuration code for invoking an application program in a first environment;

a field for a second executable configuration code for invoking the application program in a second environment;

a field corresponding to an executable call to the application program; and

a script file corresponding to a list of actions that are applied to an application program file.

9. The data structure of claim 8, further comprising:

a pointer to the end of the first executable.

10. The data structure of claim 8, further comprising a level one check value field.