Abstract: A computer-implemented process for replacing old files having old names on a permanent storage medium with new files in volatile memory. Some of these files may be opaque files, which are old files that have become new files without undergoing any changes, other than possibly name changes. The primary steps of this replacement can comprise first saving the non-opaque new files onto the permanent storage medium and assigning them temporary filenames. An opaque recovery file listing the old name and a temporary name for each opaque file is created. A primary recovery file listing the temporary name and a final name for each new file is created. After the names of the opaque files are changed to their temporary names, the names of the non-opaque old files are changed from their old names to backup names. Then, the names of the new files are changed from their temporary names to their final names. The recovery files and the old files can be deleted.

Abstract: A computer-implemented process for replacing old files having old names on a permanent storage medium with new files in volatile memory. Some of these files may be opaque files, which are old files that have become new files without undergoing any changes, other than possibly name changes. The primary steps of this replacement can include first saving the non-opaque new files onto the permanent storage medium and assigning them temporary filenames. An opaque recovery file listing the old name and a temporary name for each opaque file is created. A primary recovery file listing the temporary name and a final name for each new file is created. After the names of the opaque files are changed to their temporary names, the names of the non-opaque old files are changed from their old names to backup names. Then, the names of the new files are changed from their temporary names to their final names. The recovery files and the old files can be deleted.

Abstract: A computer-implemented process for simulating, in an HTML-formatted primary file, certain user-expected characteristics of an electronic document containing an embedded file. In response to initiating a save operation for a primary file to be saved as an HTML document, a file embedded within the primary file is detected. In turn, a support file is created for storage, in a separate storage location and physically removed from the primary file, to logically represent the embedded file. In addition, a current file list, which is associated with the primary file, is created and saved to the storage mechanism, typically the hard disk drive for the computer. When the HTML-formatted primary file is opened in a work session, the editor can open a link to each support file identified by the file list. In response to conducting a save operation for a primary file, an inquiry can be conducted to determine if a prior file list is associated with the primary document.

Abstract: An Envelope provides the integration of the functionality of an electronic mail (email) application program and the functionality of a document editor. Users can more easily generate and edit sophisticated documents for email transmission by invoking an Envelope that provides the user with the functions of an email client. A user that is editing a document in a document editor, such as a word processor or spreadsheet application can invoke the Envelope within the user interface of the document editor. The Envelope has its own user interface that is fully functional within the confines of the document editor's user interface to provide the user with the functionality of the email client application program. With the Envelope invoked, the user is enabled to execute many of the email client's functions while still editing the document within the document editor's user interface.