Class: Node (in XML)

• Inheritance
• Description
• Instance protocol
  • Twoflower
  • accessing
  • copy
  • enumerating
  • inspecting
  • namespaces
  • printing & storing
  • queries
  • testing
  • visiting

Inheritance:

   Object
   |
   +--XML::Node
      |
      +--XML::Attribute
      |
      +--XML::Comment
      |
      +--XML::Document
      |
      +--XML::Element
      |
      +--XML::Entity
      |
      +--XML::Notation
      |
      +--XML::PI
      |
      +--XML::Text

Package:

stx:goodies/xml/vw

Category:

XML-VW-Nodes

Version:

rev: 1.49 date: 2019/08/06 17:10:09

user: stefan

file: Node.st directory: goodies/xml/vw

module: stx stc-classLibrary: vw

Description:

An XML.Node represents a logical component of an XML Document. Logically, the
document is composed of declarations, elements, comments, character references, and 
processing instructions, all of which are indicated in the document by explicit markup. 
The various subclasses of XML.Node represent these various components.

Subclasses must implement the following messages:
        printing
                printCanonicalOn:
                printHTMLOn:
                printNoIndentOn:endSpacing:spacing:

Instance Variables:
        parent  <XML.Node | nil> 
        flags   <SmallInteger> 

Instance protocol:

 isHTMLBodyElement

 attributes

 children

Visualworks uses the method #children to do essentially the same as elements.
I suppose children may be the better name.

 discard

speed up common cases

 document

 elements

Visualworks uses the method #children to do essentially the same as this. Does not do much though

 expandedName

 flags

 flags: flagBits

 parent

 parent: aNode

 pathName

answer the path name of this node

 selectNodes: aBlock

 tag

 unDiscard

clear the discard flag

 cloneTree

answer a copy of the tree, so that removal of child elements
from the copy does not affect the original node.

Make a shallowCopy to protect the parent

 elementsDo: aBlock

intentionally left blank

 nodesDo: aBlock

 nodesReverseDo: aBlock

 treePosition

answer a SequencableCollection which holds the position of the node
in the document tree

 inspector2TabTree

extra tab to be shown in an inspector2.

 inspectorExtraAttributes

extra (pseudo instvar) entries to be shown in an inspector.

 findNamespaceAt: qualifier

 findQualifierAtNamespace: ns

 namespaceAt: qualifier

 qualifierAtNamespace: ns

 canonCharacterTable

http:www.w3.org/TR/2001/REC-xml-c14n-20010315#Page.10 (Attribute nodes)

 canonicalPrintString

 displayOn: aGCOrStream

what a kludge - Dolphin and Squeak mean: printOn: a stream;

 noIndentPrintString

 prettyPrintColorizedOn: aStream

 prettyPrintColorizedOn: aStream depth: indent

 prettyPrintOn: aStream

 prettyPrintOn: aStream depth: indent

self subclassResponsibility

 printCanonical: text on: aStream

Print myself on the stream in the form described by
James Clark's canonical XML.

 printCanonical: text withEscapedLineFeeds: withEscapedLineFeeds on: aStream

Print myself on the stream in the form described by
James Clark's canonical XML.

 printCanonicalOn: aStream

Print myself on the stream in the form described by James
Clark's canonical XML.

** This method raises an error - it must be redefined in concrete classes **

 printHTMLOn: aStream

Print myself on the stream in a form usual for HTML.

** This method raises an error - it must be redefined in concrete classes **

 printNoIndentOn: aStream

Print myself on the stream with line breaks between adjacent
elements, but no indentation.

 printNoIndentOn: aStream endSpacing: endSpacingBlock spacing: spacingBlock

Print myself on the stream with line breaks between adjacent
elements, but no indentation.

** This method raises an error - it must be redefined in concrete classes **

 printOn: aStream

self printAsOneLineOn: aStream

 simpleDescription

 storeOn: aStream

blocked: ascii storeString not possible (recursive - element - children - parent)

 hasAncestor: aNode

 hasSubNodes

 precedes: aNode

 xPath

I am not sure if this position counter *should*
really start at 1 or at 0.
cg: yes, they do start at 0!

 isAttribute

 isBlankText

 isComment

 isContent

 isDiscarded

 isDocument

 isElement

 isEntity

 isLike: aNode

 isProcessingInstruction

 isText

 isYAXODomNode

 verifyContents

 acceptVisitor: aVisitor

Double dispatch back to the visitor, passing my type encoded in
the selector (visitor pattern)