Free much like software for linux

TinyMUSH 3 project is a descendant of the TinyMUD server, and thus supports multi-user communication in a text-based "virtual world" format, via TCP/IP connections (presumably, but not necessarily, Internet connections).
The end result looks much like text adventures games of the mid-1980s. Though its simplest application is as a chat server, TinyMUSH 3 is intended to have the flexibility and power to support highly complex roleplaying environments.
TinyMUSH 3 is a derivative of TinyMUSH 2.0, originally created through the fusion of the TinyMUSH 2.2 and TinyMUX 1.6 code branches. The server is under active development and support.
Enhancements:
- Fixed Always clear @prog data on logout
- Fixed tools (src/tools). Add an install tag to the tools makefile.
- Update LibTools to version 1.5.22.
- Update AutoConf to version 2.59.
- Fixed function logf() in udb_* conflict with build-in function logf(), rename the function to warning().
- Remove unused port-concentrator code.
- Automated build of TinyGDBM within ./configure.
- Updated the build process a bit to keep in line with autoconf standards.

Lich is a scripting engine for text-based MUDs. It is not a complete front-end in and of itself: it operates much like a proxy server and communicates with the user through their chosen front-end (effectively giving the appearence of expanding the front-ends features with its own). Lich includes a slightly altered, extended, embedded-version of the Ruby interpreter.

This means it allows you to write and run scripts for a text-based MUD in the Ruby language. Why Ruby? Several reasons, really; first, moreso than any other language Ive personally played with, Ruby accomodates you rather than trying to make you accomodate it. As a language Ive found Ruby to possess an elegant self-sufficiency that abstracts away the need for a competent grasp of its low-level functioning, allowing one to simply make use of its features with very little need to be concerned with programmings more mundane details.

I could probably spend hours talking about the things Ive come to love in Ruby, but in the interest of saving time, I can sum it up by saying two things: I used Ruby because its a personal preference of mine, and because the interpreter is able to fit together so beautifully with an independently developed piece of software that it almost seems a shame not to take advantage of its extensible design.

mudFTP is a protocol used for transfer of text files between a MUD server and a mudFTP client program. The text files can be notes, programs, room descriptions, etc. Once the file is transferred to the client, it is edited locally using the users favorite text editor.

In order to install mudFTP on your server, your server must have a centralized mechanism for editing text entries. In case of most MERC derivatives, this happens via the function string_append which takes a char** and takes over the control over input from the user, reallocating the text string as necessary. In any case, a fair knowledge of the C programming language and your MUD server is required in order to install mudFTP.

Once installed on the server side, mudFTP will listen on another port - typically youd wand this to be 6 higher than the normal port (e.g. if your mud is on port 4444, your mudFTP port would be on port 4450).

You users then use the mudFTP client program to connect. The client program identifies itself to the server with the MUD username/password and then waits for a request.

When a user with mudFTP enabled then edits a text using the text editing mechanism, it notices that there is a mudFTP connection and sends the text there instead of to the normal user screen. The users mudFTP client reads the text, saves it to a temporary file and spawns an editor. The user edits the file, and when satisfied, exits the editor. This causes the mudFTP client to send the text back to the server - which in turn replaces the text the user was editing with the new text from the client.

The server source code is ported to following platforms:

* Diku-like servers:
o Envy 2.2 with ILAB OLC
o Mythran 3.1.6b
o ROM 2.4b6 with Ivans OLC 1.72 (by Jessica Boyd)
o ROT 1.4 (by Dominic J. Eidson)
o Circle 3.0 (by George Greer)
* Non-Diku
o LDMUD (by Markus Peter) - should be portable to any LP [New!]

Ports under development:

If you are interested in porting to a new server platform, please email me. mudFTP should be portable to your server as long as your server has some central mechanism for editing text strings.

The C version of the client code works under the following platforms:

* Linux (libc5 as well as glibc)
* Any UNIX (untested, but the code is fairly compatible)
* Windows 95 and NT (port by Cath Allen)
* Windows 98 (untested)

The Java version of the client will work on any Java-capable platform.
Id very much like someone to port the client to the Macintosh platform

glChess is a chess game with 3D OpenGL graphics.

An open-source 3D chess program. It uses openGL and gtkglarea (from GTK+) for the rendering and is designed for use in unix.

It will soon be able to be played over network much like xboard can currently. It has tentative support for computer play. Playable against a human or against "crafty" AI.

Send To Thunderbird like sendToTb you can quickly send images to Thunderbird or just resize it through Service Menu.


Just select images (.jpg only), right click -> Actions -> Send to Thunderbird.

CodeWorker is a versatile Open Source, licensed under GNU Lesser General Public License, parsing tool and a source code generator devoted to generative programming.
Generative programming is a software engineering approach interested in automating the production of reusable, tailor-made, adaptable and reliable IT systems.
In laymans terms, CodeWorker lets you generate code by parsing existing languages, or by creating and parsing your own language. Once a language file has been parsed, CodeWorker provides several techniques for generating code.
The tools scripting language drives the parsing and source code generation process. The scripting language syntax is derived from the C family of languages, making it familiar to most programmers.
The template syntax is like like JSP, ASP, or Velocity. It has variations for parsing, code generation, or functional programming, giving the developer a number of options for organizing CodeWorker projects.
Parsing
CodeWorker can be trained to parse almost any language and provides two distinct methods for creating parsers:
- the extended-BNF notation is declarative, and is a derivative of BNF (the Backus-Naur Form defines the grammar of a language) extended with regular expressions, predefined non-terminals and useful directives. Something close to javacc or to ANTLR in the JAVA world except a separate parser class is not necessary with CodeWorker. This means that parsing scripts can be tested without having to compile a separate parser class.
- Reading tokens is procedural and a somewhat obsolete now that CodeWorker handles BNF parsing scripts smoothly.
While parsing files, CodeWorker feeds nodes into a parse tree. A tree is a convenient structure to represent a hierarchical set of nodes, as in XML for instance.
The parse tree is populated by the parsing task, and used by the source code generation script to generate code, text or binary data.
Source Code Generation
CodeWorker can parse a language and use the resulting parse tree to generate source code via template-based scripts. One example is database DDL (Database Definition Language). CodeWorker has been used to parse DDL and generate large portions of a Java application.
CodeWorkers source code generation can occur in three ways: generation, expansion or translation.
- generation uses a script, much like JSP or PHP, to produce an output file. Only certain areas, called protected areas in the vocabulary of CodeWorker, are preserved in the file.
- expansion is used when small portions of an existing file need to be generated. The points where code is to be inserted are called markers in the vocabulary of CodeWorker, and code is inserted at the markers. The Class Wizard of Visual C++ generates code using this principle.
- translation mode is used when both parsing and source code generation are required to produce a file. Here are the description of two main families of use:
- source-to-source translation: a file must be rewritten in a different syntax. For example, a LaTeX file might have to be translated in HTML.
- program transformation: a source file has to change for optimizing, refactoring, instrumenting or rewriting selected portions. For example, a script could add a trace at the beginning of each function body of a JAVA or C++ source code. To do that, parsing discovers function bodies, and source code generation will insert the code that implements the trace.
Enhancements:
- Concepts of Aspect-Oriented Programming were added to code generation with joint points, advices, and point cuts.
- It allows a better separation of concerns inside a code generation process, leading to improved reading and maintenance of large and complex template-based scripts.
- A new BNF directive was added: #readPythonString.
- Some bugfixes and updates were made in the Eclipse plugin.

Claros Chat is finally ready. It is a web based (fully Ajax) instant messaging client which is capable of talking with the Jabber protocol. Claros Chat is well tested with Google Talk and it supports all major browsers such as Internet Explorer, Firefox, Safari, Mozilla.
The project has a minimalistic and an elegant user interface which looks much like a desktop application. Anyone interested in the application can test drive it at http://www.claros.org/chat.
Main features:
- Works with any Jabber server, including Google Talk.
- No setup needed on the client machine, works 100% within the browser, no plugins required.
- It is a 100% Ajax application, with a clean and nice user interface.
- Supports all major browsers.
- It can display user avatars including your own.
- Supports many of the emotions with MSN like smileys.
- All features such as changing status, changing status text, loading buddy list, adding/removing new buddy are all implemented.
- Can chat with as many users as you like.
- Users can set auto away at the preferences screen.
- Much words are useless, youve got to see it yourself, "it is one of the best looking and usefull open source instant messaging applications(or simply the best) in the world". See and believe for yourself. Just try the demo to see.(Login with your own Google username/password)
- You can start your own corporate chat network. Download a Jabber server from http://www.jabber.org and use Claros Chat to chat with your collegues.
- You can connect and chat with MSN, AOL, ICQ, Yahoo chat networks providing that you have your own Jabber server with a suitable gateway installed.
- It is open source and completely free software.