Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep

org.devtools.util.* (17)org.devtools.webtrans.* (16)org.devtools.wiki.* (44)

Package Samples:

org.devtools.util.adt
org.devtools.util.sort
org.devtools.util
org.devtools.util.debug
org.devtools.util.typeconversion
org.devtools.webtrans.util
org.devtools.webtrans
org.devtools.wiki.test
org.devtools.wiki.util
org.devtools.wiki
org.devtools.wiki.translators

Classes:

EnclosingStringChangeSet: A list of edits to an integer-indexed String, along with some facilities to merge changes together, or apply them to the document. This is a newer version of StringChangeSet, which attempts to have a simpler implementation during insertion and deletion ops. I'm attempting to push all of the computational and representational complexity into the apply() method. It was a goal of the old version of this interface to furnish a way to resolve conflicts between groups of changes. In practice, I think it will make more sense (and be easier) to reduce the probability of conflicts in the first place by ...
SimpleTranslatorManager: Translates a WebContent into HTML by applying a number of Translators. Each Translator can insert, delete, and replace text in the original content. The changes are gathered together, merged, and applied to the document at the end of the process. (This is done so that each Translator module works with the real, original document and does not accidentally interpret partial changes to the document to be original content.) In addition, TranslatorManager hides any literal areas from the Translators, so that it cannot be considered or changed. (A literal area is any text enclosed in the LITERAL symbols). ...
CachingTranslatorManager: Translates a WebContent into HTML by applying a number of Translators. Each Translator can insert, delete, and replace text in the original content. The changes are gathered together, merged, and applied to the document at the end of the process. (This is done so that each Translator module works with the real, original document and does not accidentally interpret partial changes to the document to be original content.) In addition, TranslatorManager hides any literal areas from the Translators, so that it cannot be considered or changed. (A literal area is any text enclosed in the LITERAL symbols). ...
WikiTranslatorManager: Translates a WebContent into HTML by applying a number of Translators. Each Translator can insert, delete, and replace text in the original content. The changes are gathered together, merged, and applied to the document at the end of the process. (This is done so that each Translator module works with the real, original document and does not accidentally interpret partial changes to the document to be original content.) In addition, TranslatorManager hides any literal areas from the Translators, so that it cannot be considered or changed. (A literal area is any text enclosed in the LITERAL symbols). ...
Watch: A stopwatch that can be used to measure code performance. Construct one directly by calling the constructor. Or, construct one using the newWatch() method of the Timer factory, and then measure time using the Watch's methods. This watch is designed to work much like a real stopwatch; the start() method causes the watch to begin or continue measuring time, stop() causes the watch to stop measuring time, time() returns the amount of time that has elapsed so far (but without stopping the measurement), and reset() causes the amount of time measured to become zero, and also stops the watch. A formal ...
Translator: This interface should be implemented by classes that translate text in some useful way. The primary method required is translate(), which will be called once for each document that should be translated. Each TranslatorInterface implementor should represent a way to translate documents, rather than the translation of a certain document. Translator implementors should not keep state around about a particular document that they convert; the translate() method should be self-contained and have no side effects. Translator methods should be callable concurrently, so ideally implementors should have no ...
Changes: A list of edits to an integer-indexed document (whose elements are Objects, I guess), along with some facilities to merge changes together, or apply them to a document. Changes are specified as replacements or enclosures of regions , which are consecutive lists of objects in the document of a certain length which begin at a certain point. Each time a set of changes is merged into this change, an integer should be assigned to the changes that were merged in so that conflicts can be marked. A conflict occurs whenever two replacements have the same starting point, when replacements overlap, or when ...
CVSFilePersister: A file-based persistence mechanism that implements the Persister interface. Each file action (save, delete) is committed to a source control system. This implementation assumes that a page's URL can be constructed by appending the page title (and therefore disk file name) to the base URL. This object expects to see the option CVSFilePersister.RootDir in the config file, and takes it to mean the directory which it should scan to acquire the files to be served as WebContent. Properties for objects are written to a file called XXX.properties for each resource XXX. Accordingly, CVSFilePersister expects ...
StringChanges: A list of edits to an integer-indexed String, along with some facilities to merge changes together, or apply them to the document. In this implementation, "regions" are substrings of a master document String. This implementation trades RAM for computational speed on the replace, enclose, and merge operations. Conflicts are not actually computed until getConflicts is called, and it's likely to be expensive, so you should probably not call that a large number of times. And of course, apply is the most expensive of all. Any changes which are added directly to this ChangeSet (not merged in) are considered ...
FilePersister: A file-based persistence mechanism that implements the Persister interface. This implementation assumes that a page's URL can be constructed by appending the page title (and therefore disk file name) to the base URL. This object expects to see the option FilePersister.RootDir in the config file, and takes it to mean the directory which it should scan to acquire the files to be served as WebContent. Properties for objects are written to a file called XXX.properties for each resource XXX. Accordingly, FilePersister expects that all files with a .properties extension are properties files that it created, ...
WebContent: A handle to some content on the site. These should only be created by Persister implementors, and should maintain a reference to their Persister. This interface only describes the methods exposed to callers on the Persister that this WebContent implementation is bundled with. Since these objects serve as both handle and content, it is pretty important that they can be light-weight when necessary. For example, it would be a particularly bad idea to load the content of this page right when this object is created. Instead, the actual page should be loaded on command when the content's accessor is ...
WikiServices: Provides services and config options to the translators and factory-izes the various Wiki components. Note that some objects may choose to be singletons, so multiple calls to getWhatever() may return the same object. Of course, if the returned object is a singleton, one might expect it to do a good job of handling potentially synchronous conditions. WikiServices expects a sole initial argument from the ServletConfig, which should be of the form "ConfigFile = /location/of/properties/file.properties". This file should contain one or more of the following properties:
MultiProperties: Behaves like an ordinary java.util.Properties, except that when it encounters multiple properties of the same name, it concatenates them with the separator string. Properties are written out again similarly. For example, when MultiProperties loads a properties file containing: myProp = foo myProp = bar The MultiProperties will subsequently contain one property whose name is myProp and whose value is foo:bar . (Assuming that the separator string is ":", which is the default.)
DevtoolsLNFTranslator: Inserts the wondrous devtools.org look and feel header and footer. Expects the following parameters to be available from the TranslatorServices: Wiki.FrontPage: The name of the page that is the entry point to the site. Wiki.EditPage: The name of the page that allows the user to edit pages. Wiki.DeletorPage: The name of the page that will delete pages.
TranslatorManager: Translates a WebContent into HTML by applying a number of Translators. Each Translator can insert, delete, and replace text in the original content. The changes are gathered together, merged, and applied to the document at the end of the process. (This is done so that each Translator module works with the real, original document and does not accidentally interpret partial changes to the document to be original content.)
WidgetTranslator: An abstract base class for widget translators. Searches for text of the form [widget param=value:value param=value...] and replaces it with whatever text is returned from its handleWidget method. Subclasses should override the handleWidget method to do something useful with the widget. This widget also obtains a reference to the services object so that your subclass doesn't have to.
StockLNFTranslator: Inserts a stock look and feel header and footer. Expects the following parameters to be available from the TranslatorServices: Wiki.FrontPage: The name of the page that is the entry point to the site. Wiki.EditPage: The name of the page that allows the user to edit pages. Wiki.DeletorPage: The name of the page that will delete pages.
PropertyListTranslator: Bolds all of the '''-enclosed strings in the document, Emphasizes all of the ''-enclosed strings in the document, and both bolds and emphasizes all of the '''''-enclosed strings in the document. This translator will not work with any other translators that process single quotes. To get the correct behavior, implement a translator which combines all single-quote processing into one.
QuoteTranslator: Bolds all of the '''-enclosed strings in the document, Emphasizes all of the ''-enclosed strings in the document, and both bolds and emphasizes all of the '''''-enclosed strings in the document. This translator will not work with any other translators that process single quotes. To get the correct behavior, implement a translator which combines all single-quote processing into one.
EditTranslator: Inserts a page editor widget, which edits the contents of the page named by the page query item. FIXME: Should be able to take a page to edit in the tag itself, like "[editor page=BlahPage]". Expects the following parameters to be available from the TranslatorServices: Wiki.PutterPage: The name of the page that can write content to disk.
ChangelogEntryTranslator: Appends fields from an HTML form to the content of a page. The fields to append should be specified in a :-delimited list in the fieldkeys parameter. The page and type parameters specify which page will be appended. Each form parameter will be written as |name|=|value|\n to the content of the page.
FormEntryTranslator: Appends fields from an HTML form to the content of a page. The fields to append should be specified in a :-delimited list in the fieldkeys parameter. The page and type parameters specify which page will be appended. Each form parameter will be written as |name|=|value|\n to the content of the page.
OnsiteLinkTranslator: Picks up all of the mixed-case words in the page as on-site links. If the mixed-case word is not a page of the current type, searches other types. If it is not a page of any type, inserts an editme (?) after the name. Only considers pages that have a type in the list OnsiteLinkTypes.
TempWebContent: A temporary WebContent object. There is no hookup to a persistence layer, so any changes made will not be saved. This is useful for performing transient changes that result in a WebContent object, without the overhead of hitting a disk or other Persister type.
Debugger: This class is used to perform debugging operations on a run of code. Helps control the mess of prints that debugging deals with. This class and its methods are final so that a savvy compiler could optimize away code that is guarded with the avoidCompile flag.

Home | Contact Us | Privacy Policy | Terms of Service