Schroedinger is the combination of Apache Tomcat with a nice, clean Swing GUI. It provides an easy way to create and test JSP and Servlet Web applications. It records every JSP/HTTP activity so that every possible bug can be corrected immediately. Schroedinger can be used in personal mode, which prevents others from using its JSP Server while you develop the application. Alternatively, Schroedinger's working directory can be opened via file-sharing, so that a JSP can be copied to any computer of the JSP development team.
WSO2 Web Services Framework for C is a standards compliant, enterprise grade, C library for providing and consuming Web services. WSO2 WSF/C is a complete solution for building and deploying Web services, and implements a very wide range of WS-* specifications, including MTOM, WS-Addressing, WS-Policy, WS-Security, WS-SecurityPolicy, WS-Reliable Messaging, and WS-eventing. All the Web services specification implementations are tested for interoperability with Microsoft .NET, WSO2 WSAS, and other J2EE implementations.
The XEVM is an XML processing engine. It's a multi-threaded, Pub/Sub environment for dynamic programming on an event-driven state machine with TCP communications, tight fault free memory management, powerful set algebra, and a magical database. It is 100% C++ (25,000 LOC), with a thin porting layer; there are implementations for POSIX (Mac/Linux) and Win32. The XEVM is for processing XEPL (the Xepl Engine Programming Language).
LaTeX is a document preparation system for high-quality typesetting based on TeX. It is most often used for medium-to-large technical or scientific documents, but it can be used for almost any form of publishing. It is not a word processor; instead, it encourages authors not to worry too much about the appearance of their documents, but to concentrate on getting the right content.
Bibgrep indexes and efficiently searches BibTex files. Its usage is similar to the command grep and the queries use a Google-like syntax. Bibgrep will create an index for each BibTex file it touches, and keep the result within "~/.bibgrep.idx" (by defaults). It watches the modification date and the size of the original BibTex file, and will update (and delete) its index as needed.