[all pages:] introduction message/location/muli format dtd xantlr tdom ops paisley metajava umod option auxiliaries d2d downloads & licenses people bibliography APPENDICES:: white papers white papers 2 white papers 3 project struct proposal SOURCE:option.dtd SOURCE:dtd.umod DOC:deliverables.ddf DOC-DE:deliverables.ddf DOC:mtdocpage.ddf DOC-DE:mtdocpage.ddf [site map]



All pages: introduction message/location/muli format dtd xantlr tdom ops paisley metajava umod option auxiliaries d2d downloads & licenses people bibliography APPENDICES:: white papers white papers 2 white papers 3 project struct proposal SOURCE:option.dtd SOURCE:dtd.umod DOC:deliverables.ddf DOC-DE:deliverables.ddf DOC:mtdocpage.ddf DOC-DE:mtdocpage.ddf [site map]



go one page back go to start go to start go one page ahead
option bandm meta_tools d2d

Smaller Auxiliary Classes



(related API documentation: package util,    package graficUtils,    package format.java   )


1          Auxiliary Classes For Processing XML
2          Auxiliary Classes Extending Java Specific Utilities
3          Auxiliary Classes For Graphics and User Interfaces
4          Auxiliary Classes Special to meta_tools based Projects

Naturally, there are a lot of smaller classes and code collections serving as auxiliary, low-level tools. These appear only at certain places, or ubiquituously, but in any case may be very valuable for the user beyond their originally intended role. Since they are small, the API documentation is mostly sufficient, once you know what they do in principle (and that they do exist !-)

We simply collect some of these classes here as a central reference point. Since this collection is growing constantly, please refer to the API docs of the containing packages for the latest developments. Currently, these packages are

  1. util .
  2. graficUtils .
  3. format/java .

^ToC 1 Auxiliary Classes For Processing XML

SAXEventStream and SAXEventQueue for storing "re-ified" SAX events (cf. [Sax04]).

ContentPrinter for printing XML documents (arriving as SAX calls) in different formats.

As base classes for user-defined filters: DefaultContentHandler, which throws away all incoming SAX calls, and ContentProxy which propagates them one-to-one.

Contrarily, TeeContentHandler delivers SAX events and SAX error messages to more than one target.

DOM2SAXConverter and SAX2DOMConverter serialize a w3c dom document into sax events, and vice versa.

NamespaceName is an ubiquituous auxiliary class modeling name spaces and backward-compatible behaviour w.r.t. comparison.

SaxAuthor for easily generating well-formed sequences of SAX api calls.

^ToC 2 Auxiliary Classes Extending Java Specific Utilities

ComparatorChain for cascading Comparators

ClassProbe defines static methods for finding recursive static references to classes via breadth-first search.

ConfigurableClassLoader mimics the -classpath behaviour of java.

DynamicMatcher, DynamicVisitor and DynamicRewriter do what their name promises, and are based on reflection.

FileTree creates a javax swing JTree object which represents the structure of a certain tree in a file system.

FileVistor for processing a sub-tree of the file system in a "visitor" style.

LookAheadIterator , an iterator which additionally allows arbitrary deep look-ahead.

Rational, realizes rational numbers (important for MUSIC, etc.)

Resource, aux functions for dealing with "resources" in the java sense, i.e. non-class files in a class-file tree.

^ToC 3 Auxiliary Classes For Graphics and User Interfaces

<>/util/SwingExecSync.html, is a worker for transparently executing code which accesses swing resources from within the swing execution thread and from outside.

Vt100, defines escape sequences for this widely-used standard terminal.

Geom, provides auxiliary geometric calculations.

Draw, provides complex draw operations.

LayoutGrid and LayoutLeftmost try automated placement of graphical representations of the nodes of a certain relation.

^ToC 4 Auxiliary Classes Special to meta_tools based Projects

MakeMakefile creates Makefiles according to the needs of a possible meta_tools based project file structure.

JarLinker builds an utmost compact jar file for deployment, in which only those run-time classes are contained which are reachable from one (or more) explicitly given main classes. (Further resource files can be added by explicit naming)
Its command line parameters are

( definitions from file ../../src/eu/bandm/tools/util3/JarLinkerOptions.xml )

--debug int
  the verbosity
--exclude ( string) +
  names of packages to exclude.
--inputs ( uri) +
  the binary input sources in which to search (directories or jar files)
--main ( string) +
  the name(s) of the main class(es) which define reachability. The very first will be the *main* class in the jars Manifest.
--manifest uri
  base manifest file
--output uri
  the path to the jar file to generate
--ressourceDirs ( uristring) *
  pair of source/target, where to move directories of ressources
--seal bool
  whether to seal all packages




go one page back go to start go to start go one page ahead
option bandm meta_tools d2d

made    2023-01-09_11h39   by    lepper   on    washington-ubuntu        Valid XHTML 1.0 Transitional Valid CSS 2.1

produced with eu.bandm.metatools.d2d    and    XSLT    FYI view page d2d source text