|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
|---|---|
| ArticleBuilder<T> | |
| ArticleDocument | |
| DocumentBuilder | The interface implemented by objects capable of building a certain type of document. |
| EntryBuilder<T> | |
| FootnoteBuilder<T> | |
| Initializer<T> | |
| ItemizedListBuilder<T> | |
| LastEntryBuilder<T> | |
| ListItemBuilder<T> | |
| ParaBuilder<T> | |
| RowBuilder<T> | |
| SectionBuilder<T> | |
| Table2ColsBuilder<T> | |
| Table3ColsBuilder<T> | |
| Table4ColsBuilder<T> | |
| Table5ColsBuilder<T> | |
| Table6ColsBuilder<T> | |
| TableBuilder | |
| Terminator | |
| VerbatimBuilder<T> | |
The package providing the interfaces to be implemented by
classes responsible for generating content. The
nl.flotsam.pecia package provides the interfaces seen
by clients from the outside. This package provides the interfaces
that need to be understood by anone interested in generating a
particular type of output format. (That is, this is just the basis
of an implementation. You are of course free to implement the API
provided by nl.flotsam.pecia in any way you like.)
The basic idea behind the default implementation is to construct
instances of DocumentElements on the fly, by having them constructed by the
DocumentBuilder.
For every DocumentElement,
this factory needs to be able to construct a dedicated builder
instance. The builder implementation is expected to build the
actual output document.
Whenever you feel the need to build another kind of output
format, I suggest you start with the basic implementation of the
DefaultDocumentBuilder, and override the operations that are
actually expected to generate relevant output. You might also
consider subclassing the existing DefaultDocumentBuilder sublclasses found in the docbook and html
packages. Again, you probably would only be required to override
some operations, and not all of them.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||