Shannon is a general purpose stream-oriented programming language; it is concise and yet feature rich. Streams, FIFOs, and Unix shell-style pipes are first-class concepts in the language. You can connect functions and FIFOs within your program similar to the way you connect processes with pipes in the Unix shell. These constructs in Shannon, however, are highly efficient as no true multitasking is involved, and at the same time they allow you to write more concise and readable code for chained data processing. State is a special type of function that returns a reference to its own local data and any nested functions it may have. In effect, states implement classes in terms of OOP, and yet classes per se aren't part of the language. A special type of modules marked as "persistent" is an effective replacement for databases and SQL. This allows you to access persistent shared data using native Shannon constructs, eliminating the need for an extra query language. Intuitive and minimalist syntax and semantics are used. Particularly, "minimalist semantics" means less things to remember and more possibilities. Shannon is statically-typed, although it provides dynamic typing facilities as well.
Qt for Urbi is a binding of the Qt library in Urbi, enabling you to create native graphical interfaces dynamically directly from Urbi. It exposes urbiscript events to ease the use of Qt signals and slots. Major and minor version numbers of the Qt for Urbi packages reflects the Urbi SDK version number for which they were built. Loading it in another version of the Urbi kernel probably won't work. For instance, Qt for Urbi 2.4.x will only work with Urbi SDK 2.4.y. It is still a bit experimental. Only the 32-bit Linux version is available, and not all classes and members are bound yet.
HGL is a compiler/interpreter suite for developing images. It features its own simple but powerful language, an output format configurable by plugins, runtime input handled by plugins, and easy integration into various environments like Web servers or graphical applications. The input is taken from a source file, which has to be compiled for quick and frequent access by the interpreter. An interpreter then runs the compiled files, takes input from custom plugins (if neccessary), and outputs its result via custom plugins.