No summary generated for these documents.
File Summary
|
about.xul |
A simple dialog which gives some information about Mozile.
|
debug.xul |
Formats and displays all of the debugging messages stored in the mozileDebugList of the document which opens this file.
|
local.conf |
No overview generated |
mozile.js |
This file is used to configure and load Mozile. Mozile is a collection of JavaScripts which allow inline editing of XHTML/XML documents in Mozilla browsers. See the "INSTRUCTIONS" section below for more details on configuring this file.
Project Homepage: http://mozile.mozdev.org
For details on configuration, see:
http://mozile.mozdev.org/docs/mozileDocs.html
|
MozileCore.js |
This file defines the Mozile object, which contains most of Mozile's methods and properties. Also defines the MozileCommand and MozileCommandList objects, from which all other commands are derived, and extends the Node and Selection objects in simple ways.
|
source.xul |
Asks the opening document's Mozile object for the string version of the document or the current editor, then displays that string in a text box.
|
TestModule1.js |
A simple module which is used only for testing.
|
TestModule2.js |
A simple module used only for testing purposes.
|
UndoRedo.js |
Allows Mozile to store a stack of past document states, and restore them on command.
|
widgets.css |
This file defines the basic CSS style rules for the MozileEditor. These rules are meant only to make the Mozile widgets and dialogs functional, and other rules will be needed to make it look pretty.
|
widgets.xbl |
This file describes the Mozile editor widget and toolbar widget in Mozilla's XBL and XUL languages.
|
XHTMLBasic.js |
The XHTMLBasic modules includes commands derived from the MozileCommand object which allow for editing of HTML and XHTML documents. ALso included is a revision of the Mozile.initializeToolbar() function, which creates a number of commands commonly used in XHTML editing.
This module does not include support for validation of XHTML documents. Instead it makes some assumptions about XHTML, which lead to a more light-weight implementation. Elements are distinguished into block and non-block (inline) elements, based on their CSS "display" property. Most commands function differently on blocks than they do on inline elements. While the distinction could allow the creation of invalid XHTML documents, in most cases the commands will preserve the validity of the XHTML.
|