This page is likely outdated. Visit the new documentation for updated content.

Status Owner Importance Complexity MD Version
Pending Normal High

Objectives

Reasons for the Redesign

Problems with the Existing Editor

Potential for Increased Userbase

Architectural Plans

WebKit’s Advantages over Gecko

High-Level Design

In order to implement a designer/source split view, the HTML/ASP.NET editor needs to handle three editing modes simultaneously: the HTML editing surface, the text editor, and the control host (editable via the property grid). Each of these has some sort of internal representations of the document (a DOM), and it is not feasible for them all to operate on the same DOM.

The following architecture is proposed: 700px

Edits to the document will be encapsulated in Action objects, which will be sent to the Editing Manager. This is responsible for broadcasting the changes to the DOMs. The editing manager also tracks selection using the mechanism, and the application of styles to the selected elements.

The ASP.NET host runs in a separate AppDomain or process so that third-party controls can be unloaded. The overall design should not exclusively support ASP.NET; it should be flexible enough to allow other control hosts and templating systems. The WebKit editor will treat these as unmodifiable blobs of HTML.

Features Required in WebKit