Current version contains packages with the following functionality groups:
- cache: an invalidating bean enabling to use a cached value for a specified time frame
- calendar: routines for manipulating datetime-based objects of different types (deprecated Date, Calendar, etc.)
- cfg: automatic XML-based configuration for Java applications
- collections: proper implementations of pairs and triples, with specific comparators
- crypto: an efficient AES implementation and some common crypto routines
- engine: synchronous and asynchronous RESTful beans, performance stopwatches and a generic application state machine
- file: digest operations, filters, and other common file operations
- http: a RESTful request-response handler for servlets, configurable one-liner GET / POST / DELETE queries (with asynchronous versions)
- logging: formatters for JULI and a configuration manager for logging
- math: an in-place statistical analyzer for the specified data stream
- swing: various data models, filters and simple components of frequent use
- text: charset support without exception handling
- threading: an extended SwingWorker with support for background action arguments and non-void results
- xml: a performant XML parser
The main goal of LCK is to have one single .jar file with core functionality enabling to build sophisticated threaded applications with network and data source access. All this without the versioning and dependency hassle. In fact, we are not there, yet. The current version of the software depends on a group of libraries listed on the sidebar but the project is in active development, and the state of full independence from any external libraries is planned to be achieved in 2009.
