C# Class Bloom.Edit.EditingModel

user has selected or de-selected a content language

Return the DOM that represents the content of the current page. Note that this is typically not the top-level thing displayed by the browser; rather, it is embedded in an iframe.

Return the top-level document that should be displayed in the browser for the current page.

For some reason, we need to call this code OnIdle. We couldn't figure out the timing any other way.

Save anything we want to persist from page to page but which is not part of the book from the page's current state. Currently this is just the zoom level.

Although browsers are happy to let you manipulate the DOM, in most cases gecko/xulrunner does not expect that we, the host process, are going to need access to those changes. For example, if we have a control that adds a class to some element based on a user choice, the user will see the choice take effect, but then when they come back to the page later, their choice will be lost. This is because that new class just isn't in the html that gets returned to us, if we do, for example, _browser.Document.GetElementsByTagName("body").outerHtml. (Other things changes *are* returned, like the new contents of an editable div). /// Anyhow this method, triggered by javascript that knows it did something that will be lost, is here in order to work around this. The Javascript does something like: var origin = window.location.protocol + '//' + window.location.host; event.initMessageEvent ('PreserveClassAttributeOfElement', true, true, theHTML, origin, 1234, window, null); document.dispatchEvent (event); /// The hard part here is knowing which element gets this html

listen for these events raised by javascript.

View calls this once the main document has completed loading. But this is not really reliable. Also see comments in EditingView.UpdateSingleDisplayedPage. TODO really need a more reliable way of determining when the document really is complete

Called from a JavaScript event after it has done everything appropriate in JS land towards saving a page, in the process of wrapping up this page before moving to another. The main point is that any changes on this page get saved back to the main document. In case it is an origami page, there is some special stuff to do as commented below. (Argument is required for JS callback, not used).

we need to guarantee that we save *before* any other tabs try to update, hence this "about to change" event

Flag that the current (former) page selection has finished, so it's safe to select another page.

Flag that a page selection is currently under way.

stop listening for these events raised by javascript.

Set a style on the body of the main content page that will zoom it to the extent the user currently prefers.

When the user types ctrl+n, we do this: 1) If the user is on a page that is xmatter, or a singleton, then we just add the first page in the template 2) Else, make a new page of the same type as the current one