Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add navigation "scrollbar" macro

...

The MarkupWriter interface allows the majority of component code to treat the generation of output as a stream. In reality, MarkupWriter is more like a cursor into the DOM tree, and the DOM may ultimately be operated upon in a random access manner (rather than the serial (or buffered) approach used in Tapestry 4).

{|=
Div
Wiki Markup
style
float:right
; width
:30%


} {
Info
:
title
=
A
Note
For
Tapestry
4
Users
}

In

Tapestry

4,

markup

generation

was

based

on

generating

a

character

stream.

At

the

lowest

level,

the

fact

that

the

output

was

in

a

markup

format

such

as

HTML,

XHTML

or

WML

was

not

known.

Higher

levels,

such

as

the

IMarkupWriter

interface

(and

its

implementations)

provide

the

concept

of

markup

generation:

elements,

attributes,

start

tags

and

end

tags.

This

technique

breaks

down

when

two

elements

are

peers,

and

not

in

a

parent/child

relationship.

For

example,

the

rendering

of

a

FieldLabel

component

is

affected

by

its

companion

TextField

component.

Handling

these

cases

in

Tapestry

4

required

a

number

of

kludges

and

special

cases.

{info} {float}


DOM Classes

The implementation of this DOM is part of Tapestry, despite the fact that several third-party alternatives exist. This represents a desire to limit dependencies for the framework, but also the Tapestry DOM is streamlined for initial creation, and a limited amount of subsequent modification. Most DOM implementations are more sophisticated than needed for Tapestry, with greater support for querying (often using XPath) and manipulation.

Once the Document object is created, you don't directly create new DOM objects; instead, each DOM object includes methods that create new sub-objects. This primarily applies to the Element class, which can be a container of text, comments and other elements.

Document

The Document Object object represents the an entire document, which is to say, an entire response to be sent to the client.

...

The Document class also has methods for setting and getting the DTD, adding comments and text, and finding an element based on a path of element names.

Element

An Element Object object represents an element of the document. Elements may have attributes, and they may themselves contain other elements, as well as text and comments.

...

The write() method writes text inside the current element. It scans the provided text for XML control characters ('<', '>', and '&') and converts them to their XML entity equivalents ('<&lt;', '>&gt;', and '&amp;'). The result is correct, safe, HTML/XML output even when the content (which may come from a template, or from an external source such as a database) contains such problematic characters.

...

The writeRaw() method writes unfiltered text into the DOM. When the DOM is rendered to markup, the provided string is written to the output stream exactly as-is. Care should be taken, as this can easily result invalid markup, or even markup that is not well formed. It can also introduce XSS vulnerabilities if the text comes from end users without proper filtering.

comment()

Adds an XML comment. The comment delimiters will be supplied by Tapestry:

Code Block
java
java
  writer.comment("Start of JS Menu code");
  

Scrollbar