Free controlled by software for linux

XMMS-Control provides a Web-based control for XMMS.
XMMS-Control is a web-based interface for the XMMS (X MultiMedia System). XMMS is an MP3 player for Linux based systems (it also plays other media formats).
XMMS-Control is a graphical interface for the command-line utility XMMS-Shell.
Using XMMS-Control, you can control the music playng from an XMMS equipped machine from any PC on the network, including wireless laptops/PDAs!!!
Imagine being out in the pool and being able to control the music with an 802.11b based PocketPC using a browser! You can do it with XMMS-Control!
XMMS-Control has an interface for standard PCs (desktops/laptops), as well as a mobile/PDA formatted interface, for smaller screens!!!
In addition, XMMS-Control can itself be controlled via other programs (i.e., custom interfaces) using the XMMS-Control API/Hooks program! You can tie XMMS-Control into a larger system via this method.
Lets say youre creating a system for whole-house automation, and you wish to use ONE consistent interface. Well, with the XMMS-Control API/Hooks, you can!!!
Enhancements:
- Some major bugfixes... should work MUCH BETTER on most platforms that had problems before. If you had problems getting XMMS-Control installed and running, please try this new version! Please read the new installation entries in the manual!!!
- More detailed installation instructions for getting XMMS-Shell up and running (including V0.99) in the README & manual.
- Directories are now SORTED alphabetically on the file chooser screen (previously was unsorted).
- Should handle MP3 lists with file names and ID3 tags containing commas much better now (previously when a comma was encountered, the list was off by one, the name would get split, and the second half would go to the next line).

XMMSd web control plug-in allows XMMS to be controlled with a Web browser. It makes it easier for languages like PHP to remotely control XMMS.

Frottle (Freenet throttle) is a project to control traffic on wireless networks. Such control eliminates the common hidden-node effect even on large scale wireless networks. Frottle is currently only available for Linux wireless gateways using iptables firewalls, with plans to develop a windows client in the future.
Frottle is made to schedule the traffic of each client, using a master node to co-ordinate actions. This eliminates collisions, and prevents clients with stronger signals from receiving bandwidth bias.
Frottle has been developed and tested on the large community wireless network of WaFreeNet. We have found running frottle has given us a significant improvment in the network usability. Testing results will be documented here as time permits.
Frottle currently operates as a userspace application, receiveing outbound packets via the iptables QUEUE functionality. Access to the network is controlled by the frottle master, sending each client a control packet (token) which contains information about how much data can be sent at this time.
Each client receives its token and sends any required data, one at a time. This eliminates collisions, and with a reasonable signal packetloss is virtually zero. Also, since each client gets a limited slice of the bandwidth, everyone can get fair access regardless of their signal strength. Whilst this mechanism does result in increased latency, overall network performance and utilisation can significantly increase.
Main features:
- Traffic queues built in to frottle assign different, dynamic priorities to different traffic. Most traffic has a default priority. Traffic to/from specified ports (and ICMP packets) are made high priority. Traffic for connections that have done more than 2 MB of data and have a rate of more than 5 KB/s are made low priority. When a client is polled, high priority traffic is sent first, then default, then low until the poll quota is used.
-
- Realtime info on each clients performance is available from the master in a html file and optionally at each client in a similar html file. (The names and locations of these files is set in /etc/frottle.conf.)

Channel is a generic/simple facility with the purpose of making event dispatching and message passing as straightforward to use as data structures:
Channel is a template library, with its major components configurable as template parameters:
template
<
class Id_Type,
class Id_Trait = IdTrait ,
class SynchPolicy = ACE_MT_SYNCH,
class AllocPolicy,
class Router = MapRouter
>
class Channel
By replacing Id_Type, Id_Trait and Router with various concrete classes, Channel can support table/linear message routing, hierarchical routing and associative routing (Linda style) at the demand of user. The same way, we can use integer, string, POD structs or any class as message ids (provided that proper operations are defined with Id_Trait)
Channel provides complete publish/subscribe interface for channel members (peer threads in message passing and objects in event dispatching) to pub/sub message/event ids/types and send/receive messages/events
Channels are process local entities which can be "connected" to allow transparent distributed communication between members in different channels (Connectors based on tcp socket and unix domain socket are provided as samples)
Namespace control:
The ids published/subscribed by channel members constitute channels namespace.
Channel provides publish/subscribe scope control; When ids are published/subscribed, peers can specify desired scope (LOCAL, REMOTE, GLOBAL)
When 2 channels are connected, their namespaces are automatically "merged", which is transparent to both channel members and programmers. Members can communicate with members in remote channels the same way as with local members (by pub/sub ids).
Namespace merge/integration is controlled by:
Id scope specification
filters and translators defined at channel connections
Channel communication are peer-2-peer; there are no central daemons required for message passing.
Channel support both asynchronous message passing and synchronous event dispatching models.
Channel is built on top of
ACE (Adaptive Communication Environment) to gain platform independence.
Enhancements:
- The framework was ported to Windows XP with VC8.
- Dispatching policy was added as a Channel template parameter to support various dispatching algorithms.
- Broadcast and simple RoundRobin dispatching policies were implemented for testing.
- Callback was changed to functor style so that normal functions and functors can be directly used as callbacks.

WorkBone is a simple, curses-based CD player that is controlled by the num-lock keys. It uses the cdtool package can be used to determine the contents of a CD before playing it.

WorkBone uses the numeric keypad as a control panel to allow you to move track to track, play, stop, pause, and resume playing of audio CDs. Additionally, the running times are continuously updated and displayed. Make sure you have your NUM LOCK engaged when using WorkBone. A template is displayed to guide you, and pushing the DEL key on the numeric pad will bring up a help screen.

RealTimeBattle project is a a robot programming game for Unix.
RealTimeBattle is a programming game, in which robots controlled by programs are fighting each other.
The goal is to destroy the enemies, using the radar to examine the environment and the cannon to shoot.
Main features:
- Game progresses in real time, with the robot programs running as child processes to RealTimeBattle.
- The robots communicate with the main program using the standard input and output.
- Robots can be constructed in almost any programming language.
- Any number of robots can compete simultaneously if allowed by your operating system.
- A simple messaging language is used for communication, which makes it easy to start constructing robots.
- Robots behave like real physical object.
- You can create your own arenas.
- Highly configurable.
Enhancements:
- Added BroadCast class for new logging system
- Added ClientInterface class for experimental network support
- Changed ArenaRealTime to use BroadCast singleton for logfiles
- Created working autoconf / automake / autoheader structure
- Imported some configuration data out of older versions and modified them so thatyou can install RealTime Battle on a modern system

HuaRongDao project is an ancient Chinese puzzle game.

The puzzle "HuaRongDao" has been the most popular puzzle in China for hundreds years. It came from part of the well-know story "The legend of three kingdoms".

At the end of Han Dynasty (about 200 AC.), China was divided into three kingdoms, Wei, Shu and Wu. "Caocao", the leader of Wei, wanted to unit China, however, was totally defeated at "ChiBi" by the allies of Shu and Wu. Only he and other 30 people escaped from HuaRongDao and came back to Wei.

After about 30 years, China was still united by Wei (named Jin at that time) into one country.

Its aim is to move pieces on the board in order to move the largest one to the center of the bottom. It is a very small game, and it is very challenging. This implementation is based on the curses library.

The game is controlled by keyboard only. Its features include undo, redo, and bookmarks. Custom starting patterns are also supported.

GNUstep is a cross-platform, object-oriented framework for desktop application development.

Based on the OpenStep specification originally created by NeXT (now Apple), GNUstep enables developers to rapidly build sophisticated software by employing a large library of reusable software components.

GNUstep is used in production environments at several organizations...

...an object-oriented tool development kit

The first two packages (GNUstep-make and GNUstep-base) that make up the core libraries contain a complete system for writing non-graphic tools in Objective-C. The make package allows you to setup a simple and powerful system for building, installing and packaging your tools. The base package includes all the classes necessary for writing an incredible array of tools, from wrappers for system tools to tools for communicating with web and other types of servers.

...a graphical development kit

The core libraries contain classes for developing a complete graphical application for almost any purpose. Along with our object-oriented, graphical development applications, ProjectCenter and Gorm its simple to write very complex commercial applications in weeks or months, rather than years (or often, never) in the case of other development environments.

...a desktop

Many GNUstep applications have been written to provide a powerful user experience for working on your computer. These include our workspace manager, GWorkspace, and mail client, GNUMail. GNUstep does NOT have a window manager. You can use any window manager you want, although we recommend that you use WindowMaker for a better experience (The WindowMaker project is not associated with GNUstep). Many other applications that are useful for a desktop are not contained on this web site, nor are the controlled by the GNUstep project - there are too many ideas about what a descktop should look like that we have not made up our minds about which one to endose yet. Here are some current ones:

- Project Backbone
- Etoile