9 projects tagged "Web"
Ansilove/PHP is a set of tools that convert ANSi and artscene-related file formats into PNG images, supporting ANSi (.ANS), PCBOARD (.PCB), BiNARY (.BIN), ADF (.ADF), iDF (.IDF), TUNDRA (.TND), and XBiN (.XB) formats. It includes a command line converter and a library for doing "on the fly" conversions. It creates optimized 4-bit PNG files and supports SAUCE, 80x25, 80x50, Amiga fonts, and iCE colors. It supports 14 MS-DOS charsets (IBM PC, Baltic, Cyrillic, French Canadian, Greek (CP737 and 869), Hebrew, Icelandic, Latin-1, Latin-2, Nordic, Portuguese, Russian, Turkish) as well as unofficial charsets (Armenian, Persian).
JSONBOT is a remote event-driven framework for building bots that talk JSON to each other over XMPP. This distribution provides bots built on the JSONBOT framework for console, IRC, XMPP for the shell and WWW, and XMPP for the Google App Engine. A plugin infrastructure can be used to write your own functionality.
ChiMeRA is a configuration management tool designed around three basic concepts. The first is a framework for managing servers, allowing for command execution and file transfer over SSH. The second is a repository for managing files that enables change tracking, archiving, and management of various user definable configuration files across multiple servers through a standard revision control tool. The third concept is an aesthetic principle of simplicity, giving administrators straightforward interfaces to manage complicated environments.
Rangy is a cross-browser JavaScript range and selection library. It provides a simple standards-based API for performing common DOM Range and Selection tasks in all major browsers, abstracting away the wildly different implementations of this functionality between Internet Explorer and DOM-compliant browsers.
Node is similar in design to and influenced by systems like Ruby's Event Machine or Python's Twisted. Node takes the event model a bit further: it presents the event loop as a language construct instead of as a library. In other systems, there is always a blocking call to start the event loop. Typically, one defines behavior through callbacks at the beginning of a script, and at the end starts a server through a blocking call like EventMachine::run(). In Node, there is no such start-the-event-loop call. Node simply enters the event loop after executing the input script. Node exits the event loop when there are no more callbacks to perform. This behavior is like browser Javascript: the event loop is hidden from the user.