Free oasis ebxml registry reference implementation project software for linux

Objective Modula-2 programming language is a hybrid between Smalltalk and Modula-2 based on the object model and runtime of Objective-C.
The design is an example how native Cocoa/GNUstep support can be added to static imperative programming languages without implementing a bridge.
Objective Modula-2s scope encompasses the design of the Objective Modula-2 programming language and the implementation of a compiler to implement it. The initial compiler will generate Objective-C source code.
Enhancements:
- This code is used to verify ideas and concepts which come up in the course of defining the language.
- It is in an early stage, incomplete and subject to frequent changes.

Open Project Services (OPS) is a project collaboration platform, integrating server components such as e-mail, calendaring, timesheets, documents, knowledge, etc. with standards complient clients. Open Project Services consists of a project server and a set of client extensions.
We are building a project collaboration platform. It consists of a project server that integrates with services needed within a project, e.g. e-mail, calendaring, timesheets, documents, knowledge, etc.
The project server is a Webservices hub based on Java (J2EE). The persistence layer for project information is LDAP. We use OpenLDAP now, but others should also be possible. The e-mail backend makes use of a standard IMAP server. Our reference implementation uses Courier.
We are building extensions/plugins for clients, making them OPS-enabled. We support e.g. Mozilla Thunderbird (XUL) and Squirrelmail (PHP) for e-mail clients. For the calendaring and timesheet components we have a Mozilla Sunbird extension (XUL).
In short: we are building a project collaboration environment on an OSS stack, enriching services with project information, using COTS clients/servers and open standards.
Enhancements:
- This release includes some changes to the underlying LDAP schema to make it possible to disable tasks when they are completed.
- To make use of this new feature, the Web services and the sunbird timesheet client have to be updated.

The OpenSCADA project aims to create a full-featured and state-of-the-art SCADA (Supervisory Control and Data Acquisition) system to be used in industrial and civil engineering applications to control distributed systems from a master location.
The OpenSCADA project was started in order to create a common standard for SCADA applications. This includes specifications, interfaces and reference implementations.
Enhancements:
- This release has many new features and enhancements to existing functionality.
- The interfaces and the reference implementation were cleaned up a little bit.
- The new upstream version of Utgard was added.

OLSR daemon project is an implementation of the Optimized Link State Routing protocol for mobile ad-hoc networks (MANETs).
OLSR is a routing protocol for mobile ad-hoc networks. The protocol is pro-active, table driven and utilizes a technique called multipoint relaying for message flooding. olsrd also implements a popular optional link quality extension. Currently the implementation compiles on GNU/Linux, Windows, OS X, FreeBSD and NetBSD systems.
Olsrd is ment to be a well structured and well coded implementation that should be easy to maintain, expand and port to other platforms. The implementation is RFC3626 compliant with respect to both core and auxiliary functioning.
Olsrd supports use of loadable plugins. These can be used to to handle and generate custom packettypes to be carried by OLSRs MPR flooding scheme or for any other desired functioning.
Enhancements:
- Network simulator (olsr_switch) added. Read more in the README file included in the release.
- New experimental fish eye link distribution algorithm. Read more in the README file included in the release.
- Tiny Application Server(TAS) plugin added
- Plugin interface changes. Olsrd now exports all symbols mening that plugins can access all olsrd functions easily.
- Olsrd now builds and runs on OpenBSD
- Build system rewrites(OS detection is now done automagically)
- Lots of bugfixes and minor changes

Optimization Algorithm Toolkit is a workbench and toolkit for developing, evaluating, and playing with classical and state-of-the-art optimization algorithms on standard benchmark problem domains; including reference algorithm implementations, graphing, visualizations and much more. The project was developed initially by Jason Brownlee as a part of his Ph.D. program.
The goal of this project is to deliver obscure-and-prevalent, old-and-new optimization algorithms from research literature to both research scientists and algorithm practitioners alike. Algorithms include biologically inspired approaches such as evolutionary algorithms (genetic algorithms), swarm algorithms (ants and particle swarm), and immune system algorithms.
Also included are more conventional approaches such as approaches inspired by physics including simulated annealing and extremal optimization. Problem domains include numerical function optimization, traveling salesman problems, and protein folding all with many standard benchmark instances taken from research literature.
A user-friendly graphical interface is provided to rapidly evaluate and compare algorithm and problem configurations, visualize algorithm behavior, and graph algorithm performance over time. A robust, modular, and extensible framework underlies the platform to facilitate the easy addition and modification of algorithms, addition of new problem domains and problem instances as well as facilitate more advanced algorithm experimentation.
The algorithm implementations are extensible and easily support modification and applicaition to varied problem domains. Please report any bugs, feature requests or include your own algorithms by accessing the services on the project home website. This is an open source project (released under the GPL) so the source code is available. The project was compiled with Java 1.5 (update 9).
Enhancements:
- This release includes many framework and graphical interface fixes, as well as a few new algorithms to play with.

Lost Cities project is an implementation of Reiner Knizias card game of risk management.

It supports Internet play and includes a complete set of rules.

Each player is dealt eight cards. Each turn, a player must play a card or discard a card, and then draw. Each card has a color and either a value which is either from 2 to 10, or is a handshake. There are three handshakes per suit, and one of each number card.

Each player has one play pile per suit. Your play piles are shown at the top of the window, and your opponents are at the bottom. You may only play higher-numbered cards on top of lower-numbered cards; handshake cards must go before all numbered cards.

Discard piles are also sorted by suit, but discards may be in any order. Discards are shown in the center of the window. After you have played or discarded, you may draw either from the deck, or from any discard pile.

When the last card is drawn from the deck, the game ends immediately.

Network Transparent Widgets short from NTW, is a protocol and application framework that allows a single server to serve thousands of remote GUI applications.
The client applications are nearly indistinguishable from local, native applications. The protocol is language and architecture neutral. Server language bindings for C and Java are in heavy development.
Main features:
Speed: Remote apps can run at a speed which is nearly indistinguishable from a locally running application. Since the client draws the widgets natively, its not necessary to transfer graphical data, only widget state data. This can be done asynchronously, so the responsiveness of the UI never suffers.
Persistence: Its just as easy to write the ntw protocol data to disk as it is to the network, so the state of the entire gui application can be easily saved. This also happens transparently, so the developer doesnt have to spend any time loading and saving data. Also, if a network connection dies or the client computer loses power, the application can be restarted from the point of failure at the next connection.
Portability: using the protocol, an ntw server application running on a Unix machine could talk to an ntw client for Windows, and vice versa. So a developer could write a program on Linux that could be run from any OS without any porting necessary. Any language or platform that can read and write data to a network can use the protocol to create gui apps.
Scalability: Since the ntw server does not store or draw widget graphics, the memory and computational overhead of running an ntw application is much less than a comparable X Window application. A low end machine could easily serve hundreds of remote clients.
Productivity: Users can run ntw apps without installing anything but the client. Developers can release new versions of their apps without the users having to do anything, much like a web page.
Reference Implementation:
The current reference implementation of the client implements most of the widgets in the Gtk toolkit, and is written in C using the GTK+ 2.0 toolkit for drawing the widgets and handling events. It compiles and runs on FreeBSD, Linux, and Windows, and likely other Unix variants also. Youll need the GTK+ toolkit installed to run the client, and the GTK+ development headers to compile it.
The source code also include a server reference implementation and a sample server application. The "server" is really a set of C language bindings to functions that create and send ntw widget data. The bindings can be used in much the same way as any other GUI toolkit. See the file "ntwtest.c" for the example application. Its been tested on FreeBSD, Linux, and Windows XP. The server library should compile and run on most systems with a C compiler and support for sockets, without the need for any additional libraries.
The protocol is defined by the two header files, ntw.h and ntw_signals.h. These are C header files that describe exactly the byte layout for each of the widgets and all of the opcodes and events that can be sent.
There are still some widgets missing, and some of the signals raised by GTK are not yet handled in the protocol. This will be fixed in the near future.
Note: Although the reference implementation is coded in GTK, the NTW protocol is designed to be independent of any particular widget toolkit. GTK was picked due to favorable design features and a favorable license.
Enhancements:
- 02JUL06 - Fixed bug in update.c where spin_button was switched with slider
- 02JUL06 - Removed status field from image_buffer widget protocol