The GUIShell project is a collection of utilities facilitating the use of the GTK+ toolkit in shell scripts through the gtkshell utility. The ACE configuration environment provides sample scripts utilizing gtkshell for desktop utilities. rootcat provides the ability to display messages to the root window using Xft, allowing one to write status display scripts.
gitg targets cases where it is useful to provide a graphical representation of Git data or actions. The history view is a good example, where graphical representation helps to get an overview of the repository. gitg does not aim to be an advanced tool that allows access to every feature of Git through a graphical interface. However, it will try to incorporate common actions that might require multiple actions on the command line (like staging, unstaging, reverting, and committing).
The primary aim of the Gtk+2 panel project is to provide a panel that reuses whatever is available (if it is not overkill) in the obvious way, such as subclassing GtkWidget instead of implementing applets, or by using a GtkBuilder file instead of defining a new format to customize the panel. This approach gives some additional advantages for free: you can use common tools in uncommon ways. Above all, you can use Glade to design your own panel. All the dependencies apart from GTK+ are (and hopefully will be) optional.
JCGO (pronounced as "j-c-go") translates (converts) programs written in Java into platform-independent C code that can be compiled (by third-party tools) into highly-optimized native code for the target platform. JCGO is a powerful solution that enables your desktop, server-side, embedded, mobile, and wireless Java applications to take full advantage of the underlying hardware. In addition, JCGO makes your programs, when compiled to native code, as hard to reverse engineer as if they were written in C/C++. The JCGO translator uses some optimization algorithms that allow, together with optimizations performed by a C compiler, the resulting executable code to reach better performance compared with the traditional Java implementations (based on the Just-In-Time technology). The produced executable does not contain nor require a Java Virtual Machine to execute, so its resource requirements are smaller than that required by a typical Java VM. This also simplifies the process of deployment and distribution of an application.