Projects

Apache Zeta Components (eZ Components)

claimed by Apache Software Foundation

Apache Zeta Components are a high quality, general purpose library of loosely coupled components for the development of applications based on PHP5. Beside typical modules for web application development like a template engine, database tools and an MVC component, Apache Zeta Components contain ... [More] command line tools, a chart rendering library, a WebDAV server, a universal document conversion component and more tools to ease developers' lives. Apache Zeta Components was originally developed by eZ Systems under the name "eZ Components" and was sponsored to the Apache Software Foundation for further development. Since 7/2010 the components have been known as "Apache Zeta Components." eZ Systems still builds their core products on top of Apache Zeta Components and contributes to the project. [Less]

libanculus-sharp

libanculus-sharp is a reusable utility library written in C#. "Anculus" means servant in Latin, and that is exactly what the library does. It serves and helps you to easily and quickly write new applications. libanculus-sharp contains all the building blocks that you need to develop a good C# application.

minlog

OverviewMinLog is a Java logging library. Key features: Low overhead Logging statements below a given level can be automatically removed by javac at compile time. Simple and efficient The API is concise and very efficient at runtime. Extremely lightweight The entire project consists of one Java ... [More] file with just over 100 non-comment lines of code. The JAR is 2.6kb (2kb with pack200). UsageMessages are logged using static methods: Log.info("Some message."); Log.debug("Error reading file: " + file, ex);A static import can be used to make the logging more concise: import static com.esotericsoftware.minlog.Log.*; // ... info("Some message."); debug("Error reading file: " + file, ex);While optional, for brevity the rest of this documentation assumes this static import is in place. If log statements from different libraries or areas of an application need to be differentiated, a category can be specified: info("some lib", "Some message."); debug("some lib", "Error reading file: " + file, ex);Log levelSetting the level will log that level, as well as all higher levels: Log.set(LEVEL_INFO);The levels are: LEVEL_NONE disables all logging. LEVEL_ERROR is for critical errors. The application may no longer work correctly. LEVEL_WARN is for important warnings. The application will continue to work correctly. LEVEL_INFO is for informative messages. Typically used for deployment. LEVEL_DEBUG is for debug messages. This level is useful during development. LEVEL_TRACE is for trace messages. A lot of information is logged, so this level is usually only needed when debugging a problem. Conditional loggingThe current log level can be checked before the message is logged: if (ERROR) error("Error reading file: " + file, ex); if (TRACE) { StringBuilder builder = new StringBuilder(); // Do work, append to the builder. trace(builder); }Checking the log level before calling the logging method is optional, but prevents unnecessary method calls and string concatenation for log levels that are disabled. Fixed logging levelsMinLog users can choose from the regular "minlog.jar" or from from a JAR file like "minlog-info.jar" which has a fixed logging level that cannot be changed at runtime (calls to Log.set() have no affect). During compilation, any conditional logging statements below the fixed level will be automatically optimized away by the Java compiler. Please see OverheadAndComparisons for more about the overhead when using MinLog with/without conditional logging and with/without a fixed logging level. The document also compares the MinLog overhead with log4j and java.util.logging. Output customizationThe default logger outputs messages in this format: time level: [category] messageWhere "time" is the time elapsed since the application started. For example: 00:00 TRACE: [kryo] Wrote string: moo 00:00 TRACE: [kryo] Wrote object: NonNullTestClass 00:01 TRACE: [kryo] Wrote string: this is some data 00:01 TRACE: [kryo] Compressed to 7.97% using: DeflateCompressor 00:12 TRACE: [kryo] Decompressed using: DeflateCompressor 00:12 TRACE: [kryo] Read string: this is some dataThe output can be customized: static public class MyLogger extends Logger { public void log (int level, String category, String message, Throwable ex) { StringBuilder builder = new StringBuilder(256); builder.append(new Date()); builder.append(' '); builder.append(level); builder.append('['); builder.append(category); builder.append("] "); builder.append(message); if (ex != null) { StringWriter writer = new StringWriter(256); ex.printStackTrace(new PrintWriter(writer)); builder.append('\n'); builder.append(writer.toString().trim()); } System.out.println(builder); } } // ... Log.set(new MyLogger());Using this mechanism, log messages can be filtered (eg, by category), written to a file, etc. [Less]

log5f

It's a logging utility for ActionScript 3.0 language, it supports FlashPlayer 9.0 and AIR 1.0 Log5F uses only FlashPlayer's capabilities, so it can be used for Flash/Flex/AIR applications. Log5F is a port of Log4J.

Genalyze

The Genalyze log analyzer, a simple yet highly extensible framework for parsing log files, was designed for parsing T-Server log files generated by Genesys contact center software platform, yet is generic and easy enough to adapt for other log formats.

log4sh

log4sh is an advanced logging framework for shell scripts (eg. sh, bash) that works similar to the logging products available from the Apache Software Foundation (eg. log4j, log4perl).

A logging anti-framework.

Simple Log is logging anti-framework. It is written in protest against the many "logging frameworks" that are available and recommended by many developers. Simple Log is a small library that does logging very simply and requires you to do almost nothing (other than actually logging) to get ... [More] log output happening. It doesn't attempt to solve every logging problem in one package, but I believe it will be suitable for at least 80% of applications that need logging. It is much simpler to use than a logging framework, especially in terms of configuration. And, being simple, it also has the advantage of having a tiny deployment JAR size of just 17.5 KB. [Less]

pyshuriken

Log parser framework written in python to analyze and process almost any log File.

wisephp

WisePHP is a Framework for PHP programers and come with - data base abstration; - XSLT files compilation; - Log sistem; - very good debug; and works very good with extjs javascript framework.

Live Labs Simple Logging Library

A simple Logging Library for .NET 3.5.