From 4764a5b58e0ad166b28a360adc00aa2effbc1905 Mon Sep 17 00:00:00 2001 From: Google Code Exporter Date: Sat, 14 Mar 2015 17:27:42 -0400 Subject: [PATCH] Migrating wiki contents from Google Code --- MudClient.md | 23 +++++++++++++++++++++++ ProjectHome.md | 30 ++++++++++++++++++++++++++++++ SimpleJNDI.md | 11 +++++++++++ XmlWriter.md | 3 +++ 4 files changed, 67 insertions(+) create mode 100644 MudClient.md create mode 100644 ProjectHome.md create mode 100644 SimpleJNDI.md create mode 100644 XmlWriter.md diff --git a/MudClient.md b/MudClient.md new file mode 100644 index 00000000..60397f40 --- /dev/null +++ b/MudClient.md @@ -0,0 +1,23 @@ +## Description ## +A mudclient written entirely in java, using the swing UI components, and some of it's own custom components. + +## Aims ## +Initially the mud client will only work with Elephant Mud , however later on in the project it is planned to make specific support and features plugins. + +The mudclient requires java 1.4 or higher which can be downloaded from www.java.com . + +## Current Status ## + +### Implemented ### + * Telnet Negotiation + * Ansi control code support + * Elephant Mud external client mode support + * Multiple output windows for one mud + * Configurable Keybindings +### To Do ### + * Make the configuration alterable at runtime + * Make the configuration persistent + * Aliases, Macros & Triggers + * Support for using 'ed' whilst in external client mode + * A pluggin framework + * Remove specific Elephant Mud stuff and make it into a plugin \ No newline at end of file diff --git a/ProjectHome.md b/ProjectHome.md new file mode 100644 index 00000000..32068455 --- /dev/null +++ b/ProjectHome.md @@ -0,0 +1,30 @@ +A small (inactive) community of open-source Java(tm) components. + +Projects: + + * charlotte - A bit format utility. + * jardiff - Visualizes API differences between two different versions of a Java project. + * [MudClient](MudClient.md) - Swing mudclient for the Elephant MUD + * norbert - robots.txt parser + * oscube - Simple-JNDI based framework. + * payload - Self-extracting jar creator. + * [SimpleJNDI](SimpleJNDI.md) - In-memory JNDI implementation. + * scraping–engine - oscube based website scraping framework. + * trail-taglib - Breadcrumbs JSP tag library. + * Tig-Threads - Thread management utility. + * [XmlWriter](XmlWriter.md) - Simple API to output XML. + + * genjava: + * gj-core - General utility library. + * gj-config - Simple configuration API, for use with JNDI. + * gj-scrape - HTML/XML semi-parser. + * gj-csv - CSV reader/writer. + * gj-find - UNIX find command-like library. + * gj-mail - JavaMail helper utility. + * gj-xml - Simple XML parser. + +The latest version of each component is available in the [Downloads](http://code.google.com/p/osjava/downloads/list). + +For older versions, see the [SVN dist directory](http://osjava.googlecode.com/svn/dist/releases/official/). + +JAR files are available via a [Maven repository](http://osjava.googlecode.com/svn/dist/maven/). \ No newline at end of file diff --git a/SimpleJNDI.md b/SimpleJNDI.md new file mode 100644 index 00000000..32a4d82a --- /dev/null +++ b/SimpleJNDI.md @@ -0,0 +1,11 @@ +## The Problem ## +Simple-JNDI is intended to solve two problems. The first is that of finding a container independent way of opening a database connection, the second is to find a good way of specifying application configurations. + +Unit tests or prototype code often need to emulate the environment within which the code is expected to run. A very common one is to get an object of type javax.sql.DataSource from JNDI so a java.sql.Connection to your database of choice may be opened. +Applications need configuration; a JNDI implementation makes a handy location for configuration values. Either as a globally available system, or via IoC through the use of some kind of JNDI configuration facade (see gj-config). + +## A Solution ## + +A simple implementation of JNDI. It is entirely library based, so no server instances are started, and it sits upon Java .properties files, XML files or Windows-style .ini files, so it is easy to use and simple to understand. The files may be either on the file system or in the classpath. + +Simple-JNDI depends on no external jars for its basic functionality, however to get certain optional features you will still need to download external jars. When describing these features, the manual will point out which jars are needed and where to get them. \ No newline at end of file diff --git a/XmlWriter.md b/XmlWriter.md new file mode 100644 index 00000000..67e76103 --- /dev/null +++ b/XmlWriter.md @@ -0,0 +1,3 @@ +A great way to output Xml. Far easier to code with than painful DOM or SAX like solutions and much nicer in terms of speed and memory usage. + +While XmlWriter contains its own xml outputter, it has the ability to sit on top of other core Xml writing products, such as XmlEnc. In addition, the user may layer other functionalities on top of the core writing, such as on the fly schema checking, date/number formatting, specific empty-element handling and pretty-printing. \ No newline at end of file