Abstract: The present invention extends to methods, systems, and computer program products for synchronizing data between different editor views. Embodiments of the present invention can be used to incrementally parse a portion of a document using a mark-up language (e.g., HTML) snippet. The parsed snippet is then merged back into the main document. Accordingly, code changes in a text view can be integrated into a design view's main document structure (e.g., parse tree) such that the preservation information for the parsed snippet is merged with the preservation information for the rest of the document. Fully reparsing the document is not required and incremental reparsing can be done in automated fashion. Thus, a document can be automatically re-outputted with full preservation of what the document would have looked like in code view without fully reparsing the document.

Abstract: The present invention extends to methods, systems, and computer program products for synchronizing undo/redo operations between different document views. A unified undo stack uniformly stores undo operations and information for multiple views of a document. When a change in first view is detected, the first view submits an undo unit for storage in a global undo unit in the unified undo stack. A second view is notified of the detected change in the first view. In response, the second view submits an undo unit for storage in the global undo unit. Accordingly, undo information for both views is stored together at the unified undo stack. When an undo command is receive from either view, appropriate undo units for each view are applied to each view respectively.

Abstract: Table elements, such as HTML elements, are automatically formatted relative to a change in visual appearance of a displayed decorative panel. The decorative panel comprises a plurality of separate but visually related regions defined by the table elements, and organized in predefined logical relationships to each other. A visual change causes an automatic revision to one or more attributes of the table elements that define the regions affected by the visual change. The visual change and automatic formatting are preferably accomplished with a Web page design tool, which identifies the decorative panel from comments associated with the table elements but do not affect rendering by a conventional browser. Visual properties of the decorative panel are mapped to the attributes, so that when the visual appearance is changed, a corresponding attribute is automatically revised. The resulting revised table elements are validated against predetermined inference rules that define valid patterns of regions.

Abstract: The present invention extends to methods, systems, and computer program products for synchronizing undo/redo operations between different document views. A unified undo stack uniformly stores undo operations and information for multiple views of a document. When a change in first view is detected, the first view submits an undo unit for storage in a global undo unit in the unified undo stack. A second view is notified of the detected change in the first view. In response, the second view submits an undo unit for storage in the global undo unit. Accordingly, undo information for both views is stored together at the unified undo stack. When an undo command is receive from either view, appropriate undo units for each view are applied to each view respectively.

Abstract: The present invention extends to methods, systems, and computer program products for synchronizing data between different editor views. Embodiments of the present invention can be used to incrementally parse a portion of a document using a mark-up language (e.g., HTML) snippet. The parsed snippet is then merged back into the main document. Accordingly, code changes in a text view can be integrated into a design view's main document structure (e.g., parse tree) such that the preservation information for the parsed snippet is merged with the preservation information for the rest of the document. Fully reparsing the document is not required and incremental reparsing can be done in automated fashion. Thus, a document can be automatically re-outputted with full preservation of what the document would have looked like in code view without fully reparsing the document.