Free activecollab 0.7.1 software for linux

GameScroll is a system for playing and writing interactive fiction like Choose Your Own Adventure or Fighting Fantasy gamebooks... But instead of flipping pages, GameScroll runs them as an impartial gamemaster!

Adventures can remember where youve been and what youve done, unlike web-based "choose your own adventure" games!

acoc is an arbitrary command output colourer.

Ever wondered why the output of your favourite UNIX/Linux commands is still displayed in black-and-white after all these years?

Ever had to search back through your scroll-buffer in search of gcc errors and salient information to tell you what went wrong with your programs execution?

acoc is a regular expression based colour formatter for programs that display output on the command-line. It works as a wrapper around the target program, executing it and capturing the stdout stream. Optionally, stderr can be redirected to stdout, so that it, too, can be manipulated.

acoc then applies matching rules to patterns in the output and applies colour sets to those matches. A picture is worth a thousand words, so look at the sample screenshots in the next section.

Authentic project is a Liberty-enabled identity provider aiming to address a broad range of needs, from simple to complex setups.
Its Liberty compliance relies on Lasso, a free softaware implementation of the Liberty Alliance specifications. It is a quixote application and is commonly run inside the Apache Web server.
Main features:
Liberty conformance
While not certified itself Authentic implements Liberty protocols through the use of Lasso that has been certified as conformat to Liberty specifications in May 2005. Authentic implements every feature required by the Identity Provider Conformance Matrix.
Additionally it has several extra features; for example it can act as a proxy identity provider, redirecting requests from service providers to other identity providers; or sharing identity attributes through ID-WSF Personal Profile (with an appropriate version of Lasso).
Performance
The underlying components are quite fast and Authentic doesnt slow things down. There are no hard measure yet but a quick benchmark using ab (from Apache) yielded more than 200 requests per second on my development laptop (Centrino 1.5GHz, 1GB RAM).
Ease of Administration
Authentic has a nice and useful web administrative interface; it provides convenient identity management and log analysis. It also has its share of parameters so it adapts to different needs without any code change.
Enhancements:
- This release fixes minor but annoying issues with 0.7.0 (error display and translations).

Guichan project is a portable C++ GUI library designed for games using Allegro, SDL and/or OpenGL.
Guichan has a very abstract design which allows users of Guichan to use different objects for displaying of graphics and grabbing of user input. Guichan comes with (for now) 3 implemented graphics objects (SDLGraphics, OpenGLGraphics and AllegroGraphics) and 2 implemented input objects (SDLInput and AllegroInput).
Guichan is designed for games. This means that Guichan lacks many features of more advanced GUI libraries (such as GTK, QT). However, this should not be considered a weakness of Guichan but on the contrary a strength of Guichan. When making games you normally dont need all features in advanced GUI libraries. They often complicate things and adding a dependency such as QT for a small platform game doesnt really feel good. Guichan is small but contains all basic GUI features making it ideal for games.
Guichan is designed for games. This means that Guichan will not take over your game/application when it comes to initialization of external libraries. When making games you normally want to initiallize all extern libraries yourself. This gives all users of Guichan a freedom thats almost required in game development. Guichan should not be considered a full GUI library but rather a tool or helper library for game development.
Guichan is designed for games. This means that Guichan comes with a small number of really ugly default widgets. Also, there exists no themes or theme handling for Guichan. Every user of Guichan is suppose to make new widgets by ineherit from the standard widgets or by overloading standard widgets functions. This is very powerful and beats all theme based GUIs. If we would implement theme handling, for widgets to be able to look exaclty as you want, it would have to be very complex and it would increase the size of Guichan. We believe that theme handling for a specific GUI is nothing a game developer wants to learn when developing a simple game. The knowledge of standard C++ ought every game developer possess that uses Guichan, so no new learning is required (except the API) for using Guichan.
Guichan is designed in a very abstract way making it very easy to extend Guichan for your own needs. It is even very easy to implement new graphics objects making Guichan as portable as ANSI C++ is.
Guichan comes under the BSD license and there exist a very good reason for the choice of BSD over LGPL (which i believe are the standard licenses for open(free) source library projects). BSD lets you link with Guichan statically or even include all of the source for Guichan into your own project not using any linkage at all (which would violate the LGPL license). We believe this is something users of Guichan might want to do because of our philosophy of using inheritance and function overloading over theme handling.
Main features:
- Doesnt take over your application when it comes to initialization of external libraries.
- Clean modular objectoriented design.
- Graphics support for SDL, Allegro and OpenGL.
- Input support for SDL and Allegro.
- No themes! As with Javas swing, member functions overloading and inheritance is the way to go.
- Comes with a set of standard widgets.
- No threading! The user of Guichan always has the power to tell Guichan when it can perfom logic and when it can draw itself.
- Licensed under the BSD license and therefore static linkage with Guichan is allowed.
- Very small compared to other GUI libraries like Qt or GTK.

Jolt is a Java Virtual Machine Daemon. This program provides a means to invoke the JDK tools javac, javadoc, and jar from the command line while reusing the same JVM instance across invocations.

Jolt daemon is intended primarily for use as a helper tool to make compilation of Java code with make as fast as (and potentially faster than) with Jakarta Ant.

It can also be used to run arbitrary Java programs (as with java); this is particularly useful for command-line utilities that are run over and over, where the cost of launching the JVM each time would be prohibitive (or at the very least, annoying).

Usage:

The `runjolt shell script can be used as a wrapper for the `jolt binary. It checks for the presence of the JAVA_HOME environment variable (which should be set to the top-level installation directory of JDK 1.4.0 or later) and augments LD_LIBRARY_PATH accordingly before invoking `jolt proper.

Gecode/R is a Ruby interface to Gecode, allowing constraint programming in Ruby. The interface is intended for people with no previous experience of constraint programming, aiming to be easy to pick up and use in practice.
Constraint programming
Constraint programming is a declarative programming paradigm, you describe what kind of solution you want rather than how you want it computed. When using constraint programming you try to model the problem and then feed that model to the solver. The solver then searches for a solution by exploring the space of all possible assignments while using the constraints in the model to prune parts without having to visit them.
A popular example would be Soduko, to solve a Soduko with constraint programming you feed the rules (all numbers in each row must be distinct etc) to the solver, which then searches for a solution satisfying all the constraints.
Enhancements:
- A new Website has been launched, and a lot of documentation has been added (both code and user documentation).

libGlass is a library for distributed computing that makes its programming easy.
The Glass framework is a scalable set of components that can be used by applications to perform distributed computing. Applications are built reusing the available components as needed.
One of the major goals of libGlass is to be a user-friendly framework, not only suitable for new applications, but also for legacy code.
This is an important feature, as most available solutions for distributed computing require a substantial amount of rewrite of legacy code; some of them require a complete change of the application design.
libGlass was designed to achieve the following goals:
- User transparency: the library must be as transparent as possible. Any tasks that are repetitive or that can be done automatically should be done by the library, without user intervention.
The API (Application Programmers Interface) should be simple and intuitive, with a smooth learning curve and provide high level primitives that can be easily used to solve any problems. Legacy code should be easy to port.
- Extensibility: the library must be easily extensible, requiring no recompilation or any other modification to support new features; they must work as plug-ins.
- Performance and efficiency: since the library is for distributed computing, it has to be efficient, consuming as little processing time as possible.
- Network protocol independence: an abstraction layer makes it possible to change the underlying network protocols easily. The application can use the network protocol most efficient for its needs.
- Portability and interoperability: heterogeneous clusters and grid computing being every day more common, the library must be not only portable, but allow different architectures to interoperate seamlessly, something that is not true for most implementations of distributed computing solutions.
- Scalability: there is no use for a distributed solution that does not scale well. Glass has to work well in all sorts of environments, from small clusters to huge grids, and be able to adapt itself to achieve best results.
- Reconfigurable network architecture: most existing solutions are based on a fixed network architecture, usually Master/Slave or Client/Server.
Given the requirements of scalability and performance, and the fact that peer-to-peer applications are everyday more common, its unreasonable to fix the network architecture: the developer should be free to define how nodes will connect with each other.
- Reliability and fault tolerance: distributed computing often requires reliability. Its not acceptable that the misbehavior or crash of a single node crashes the entire computation.
As clusters grow in size and grid computing becomes more common, the MTBF (Mean Time Between Failures) shrinks to a point that it cannot be ignored.
libGlass must be able to handle node crashes gracefully, keeping the application running and avoiding deadlocks and other problems that could arise from the node crash. Nodes should be allowed to join or leave at anytime.
- Thread support: the library must be completely thread-safe.
With clusters of symmetric multiprocessors (SMP) computers becoming more common and new technologies such as HyperThreadingTM, its unacceptable for a distributed computing framework to have thread issues.
Main features:
Plugins:
- Synchronous shared memory
- Distributed asynchronous events
- Synchronization barriers
- Remote aliases
Protocols:
- TCP/IP
- UDP/IP (unfinished)
Architectures:
- Client/Server
- Pure peer to peer (planned)
- Hierarchical (planned)
- Anonymous peer to peer (planned)
Bindings for:
- Java (mostly finished)
Enhancements:
- Fixed packaging problems that could abort compilation