The pTest framework is an Object Oriented PHP 5 testing framework. It differs from other testing frameworks in that it doesn't suffer from a dogmatic following of JUnit. A good feature of this framework is that it can be as easily used from the command line as embedded and extended by your application. Tests are easy to write, and don't require naming conventions or other code changes.
LAPLib (Linear Algebra Performance Library) is an object-oriented software library which provides an elegant interface to access the optimized performance of these old-style libraries. LAPLib transparently handles all low-level details concerned with invocation of BLAS and LAPACK functions. Using LAPLib, developers can write expressions in a C++ object-oriented fashion and greatly reduce the complexity associated with using BLAS and LAPACK routines while maintaining excellent performance.
STL-MPI is an extension to MPI to support easy transfer of STL objects. It allows tight integration of MPI with objects from the C++ Standard Template Library, assisting the development of efficient parallel programs using message-passing in C++. STL-MPI provides a transparent and unified mechanism in C++ to transmit STL containers in an object-oriented and type-safe manner. It supports nested containers for data transport.
The Widget Jones Library is a lightweight, flexible, template-driven widget build system. It is intended to simplify creating portable widgets. Write your code once, build it with WJL, then run it on several widget platforms like Apple Dashboard, Windows Vista Sidebar, iGoogle, and more.
The GlynnTucker.Cache assembly provides a data structure for caching slow data retrievals. For example, it can cache data retrieved from a database server over the network. Think of it as a Hashtable that can automatically expire its data after a set amount of time or a specified period of inactivity, on a per-object basis. It is written in C# and it should work with any .NET language.
The Generic Grid Broker component acts as a meta-scheduler sitting on top of existing Grid middleware (such as Globus Toolkit, gLite, or UNICORE). Its role is to intelligently schedule the execution of jobs on the Grid with efficient and optimized management of resources. For example, as the Globus Toolkit cannot select by itself a remote resource on which to submit the job, it has to implement a meta-scheduler for handling some high-level decisions.