# 4DOM version 0.10.2

###

4Suite http://FourThought.com/4Suite

Copyright (c) 2000 Fourthought, Inc., USA

http://lists.fourthought.com/mailman/listinfo/4suite or send mail too support@4suite.com

Current version: 0.10.2

### License/Copyright

4Suite is copyright Fourthought, Inc. (http://FourThought.com). Please read the file COPYRIGHT for the complete copyright andterms of license.

### Description

4Suite is a collection of Python tools for XML processing and object-databases.

The current version is 0.10.2. See the ChangeLog for notes on the current version.

4Suite is an integrated packaging of several formerly separately-distributed components. These are as follows.

`2001-01-16:` 4Suite 0.10.1 released.
`2000-11-30:` 4Suite 0.10.0 released.
`2000-11-14:` 4Suite 0.9.2 released, including first public release of DbDom and 4XLink.
`2000-10-11:` 4Suite 0.9.1 released, including first public release of 4XPointer.
`2000-09-20:` 4Suite 0.9.0 released. 4DOM, 4XPath, 4XSLT, and 4RDF are now bundled therein. Including first public release of 4ODS.

### Installation

Download 4Suite install one of the binary packages. Alternatively, you can download the source instead and install using Python distutils as follows:

    python setup.py install

See PACKAGES for more information about the available 4Suite packages.

If you have difficulty installing this software, send a problem report to 4Suite@lists.fourthought.com describing the problem.

For a complete installation instructions see the HOWTOs.

### 4DOM

4DOM is an implementation of the World-Wide Web Consortium recommended standard document object model for Python. 4DOM implements DOM Core level 2, HTML level 2 and Level 2 Document Traversal.

4DOM is designed to allow developers rapidly design applications that read, write or manipulate HTML and XML.

4DOM follows the Python DOM binding, for which there is some documentation in the development version of the Python 2.0 docs.

#### Directory Structure

`xml/dom` - Core DOM components (including XML classes)
`xml/dom/html` - HTML components
`xml/dom/ext` - Extensions and proprietary components
`xml/dom/docs` - (currently minimal) documentation
`DOCUMENTATION_PATH/4Suite-0.10.2/demo/4DOM` - Small scripts demonstrating some uses of 4DOM. See the README in this directory.
`DOCUMENTATION_PATH/4Suite-0.10.2/test_suite/4DOM` - Test scripts.

#### Accessors/Mutators for Attributes

Following discussion on the Python XML SIG mailing list, 4DOM provides two ways to access DOM interface attributes. As an example, the DOM IDL definition for the Node interface contains `readonly attribute DOMString childNodes`. This can be accessed as a simple Python attribute: `node.childNodes`, or as a method call using the Python/CORBA mapping for attributes: `node._get_childNodes()` [if childNodes were a read/write attribute, there would also be a `node._set_childNodes()`]. There is a slight speed advantage to using the latter convention.

#### Document._get_ownerDocument()

Document._get_ownerDocument() returns a pointer to itself.

#### Creating HTML Element Nodes

HTMLDocument.createElement() overrides the Document.CreateElement() method, looking up the specified tag and returning an instance of the propriate HTML node. For instance:

              # html_doc is an instance of HTMLDocument
              table_elem = html_doc.createElement("TABLE")
              # table_elem is an instance of HTMLTableElement

#### Deviations

4DOM does not implement DOMString. Instead, the interfaces use a plain Python string or unicode object instead. Note that Python strings do not have particular length limitations, and Python 2.0 is required for unicode support.

The DOM Spec sections on the `removeAttribute`, `removeAttributeNS` and `removeAttributeNode` method of the Element interface has some rules for Attribute removal with respect to default values. 4DOM only follows these rules if you remove attributes using the removeAttribute method, and the default attribute will not be properly set if you use removeNamedItem to remove an attribute from the NamedNodeMap returned by Element.getAttributes.

4DOM does not implement HTMLElement features strictly for browser environment, for example, blur and focus properties of HTMLSelectElement.

Some methods of the DOM spec for HTML do not allow for errors associated with missing nodes. So, for example, HTMLDocument::setTitle() does not allow for the return of an error if the HTMLDocument does not have an HTMLHeadElement child. 4DOM, in these cases, will automatically add in needed elements in order to strictly follow the DOM interface spec. The methods for which 4DOM provides automatic document completion are:

  `HTMLDocument::getDocumentElement()`
  `HTMLDocument::setTitle()`
  `HTMLDocument::getBody()`
  `HTMLDocument::setBody()`
  `HTMLTableElement::insertRow()`
  `HTMLTableRowElement::insertCell()`

See 4DOM Extensions for documentation of proprietary extensions and helper functions provided by 4DOM.

### Quick Start

There are demo files and test suites for each component in the documentation directories set up by Distutils. These should provide useful examples.

### Known Bugs

See the TODO file

### Contact and Support

For release notes and news, see http://4Suite.org

Please consider joining the 4Suite users and support mailing list

http://lists.fourthought.com/mailman/listinfo/4suite

4Suite developers monitor the above list, and prefer for support requests to come thereby so that others can benefit from the discussion. If this is unsuitable, you can address the 4Suite developers directly:

support@4suite.org