prtpacker (Portable Resource Tree Packer, pronounced PIRT-Packer) is a tool for creating C or C++ source code from external program resources such as images, text, or data. These resources can be arranged in a tree structure much like a typical file system. After compiling and linking the resulting source code you can access the resource tree from within your software through a simple API. Be aware that all resources stay in memory and cannot be easily deallocated.
The Interactive Television Publishing System (ITPS) offers a simple way to produce ATVEF-A compliant ETV features. At the heart of the system is a database that separates form (in this case, device-specific markup code) from content (text and images appropriate to show segments). Database content is published to HTML via Perl using device-specific modules. A handful of additional static HTML pages, such as the search form, make up the remainder of the code required to support a particular client device. Devices are routed to appropriate pages via a "sniffer" page, implemented using the XSSI syntax available in Apache 1.3 or higher.
MySQL DBDesigner is a visual database design system that integrates database design, modeling, creation, and maintenance into a single, seamless environment. It combines professional features and a clear and simple user interface to offer the most efficient way to handle your databases.
AePro is a compilation manager for programs written in progres4gl. It compares modification times and will only (re)compile the programs whose source code has changed. It is intended to be used in combination with Aegis, a transaction-based software configuration management system that provides a framework within which a team of developers may work on many changes to a program independently.
Macker is an architectural rule-checking utility for Java. It's meant to model the architectural ideals programmers always dream up for their projects, and then break. It is not a lint checker--it operates on a more global, more logical level, focusing on class dependencies rather than source code formatting. Macker has no default set of rules; it's flexible, and writing a rules file is part of the development process for each unique project. You can tailor a rules file to suit a specific project's structure, or write some general "good practice" rules for your code. Macker typically runs as an Ant task, but can also be invoked with a shell script.