Browse Prior Art Database

Method for regeneration using saved undoes

IP.com Disclosure Number: IPCOM000201866D
Publication Date: 2010-Nov-29
Document File: 2 page(s) / 93K

Publishing Venue

The IP.com Prior Art Database

Abstract

When automating the creation of a software entity, for example a document, it is frequently the case that further changes must be made after its creation and is often desirable to reapply these changes en masse.

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

Page 01 of 2

Method for regeneration using saved undoes

Disclosed is a process for reapplying changes made to an original creation to any generated entity enabling reapplication of the changes based on extrapolating intent from the individual changes. By employing the disclosed process referred to as undo stack regeneration , the undo/redo information used to make changes is saved. The undo/redo information could be saved in the same file and be reformatted. The undo/redo information could also be saved in the same application or other suitable place as shown in Figure 1.

(This page contains 00 pictures or other non-text object)

Figure 1

The saved undo/redo information is used for reapplying the changes. The information is used to apply the changes in the same order, only apply changes when the part of the entity changed is

p

 resent, or group changes by using temporal proximity (for example, when a set of changes such as adding a header and footer happen at the same time, are likely related). There are several reasons why this focus on the intent of the changes would be desired. Only applying relevant changes enables the changes to be dynamically applied to a large number of documents. Applying changes in the same order could emphasize more important changes first. Applying related changes together would ensure the intent behind a group of changes was preserved.

1


Page 02 of 2

(This page contains 00 pictures or other non-text object)

Figure 2

Consider, for example, the case of regenerating an extensible forms definition language (XFDL) form from an XML schema...