RoboBrain SDK is a simple, lightweight 2D game engine for Android phones and tablets. It supports OpenGL ES 1.0 Rendering, a custom GameActivity class, a World/Entity system, basic physics and collision detection, animated and static sprites, and support for Multitouch and accelerometer input.
Asynchronous DNS Resolver for Haskell is a library that provides an asynchronous DNS resolver on top of GNU ADNS. Not all options are supported, but A, MX, and PTR lookups work nicely. There is also support for retrieving generic RR types, CNAMEs, and for NSEC zone walking. The library can be expected to work with fine ADNS 1.4 or later. It might also work with version ADNS 1.3, but that hasn’t been tested.
Aspose.Report is a .NET query building and charting control. It allows developers to quickly add ad hoc capabilities to their .NET applications as well as create 21 popular chart types with some stylish effects like 3D rendering, transparency, gradients, and anti-aliasing. Simply drag and drop the Aspose.Report component on Web or Win form, assign a DataTable object as data source, and abstract a variety of outputs including SQL, Select, Where, and Order By statements and many more.
The Scalable Assembler at Notre Dame (SAND) replaces the early stages of the Celera Assembler with scalable versions that can run on collections of commodity computers. By harnessing clusters, clouds, grids, or just random machines in your office, many bioinformatics tasks can be reduced from weeks or months down to minutes or hours.
JS Measurer measures a webpage's width and height interactively. It lets the user define an area in the page by dragging the mouse pointer. The object renders the area outline as the mouse moves, showing the width and height of the area in pixels, as well the coordinates of the top-left corner of the area. A bookmarklet is also available, so this object can be used as a link placed, for instance, in the browser toolbar.
Huxley is a set of classes that makes it trivial to produce legitimate output for queries made by the prevailing standard of REST queries. Instead of writing a network API with many methods, being run over RPC, you instead write only a couple of methods that are accessed by HTTP GET requests. You then return the results (in either XML, JSON, or text) for processing. XML and JSON are chosen because of the ease by which they can be parsed by most languages. In this way, you open up the scope of your network services to many more people than would otherwise have access to it.