Free mature singles software for linux

TurboGears project is based on the agile, mature, cross-platform, well-documented, easy and fun Python programming language.
Python makes it super simple to get started with TurboGears, whether youre running Windows, Linux, Mac OS X or even a cell phone. OK, so youre probably not going to want to run a web server on your cell phone.
Any way you slice it, youll be amazed how quickly you get started!
Installation:
Even though you dont have Easy Install yet, you can still take advantage of it. Instead of one-command installation, it will be two-step installation. And, youll have Easy Install for the next update!
The instructions below will install into the primary system locations for Python modules. On many systems, this requires superuser access. So, performing the installation below will require you to enter your password. If your system does not have sudo installed or configured properly, you can su to the superuser account and then run the command.
Note that on some Linux systems (Ubuntu, for example), you may need to install a "python-dev" packages in order for everything to compile correctly.
- Download the ez_setup.py script.
- Run sudo python ez_setup.py -f http://www.turbogears.org/download/index.html --script-dir /usr/local/bin TurboGears
Enhancements:
- Much better on-line documentation was provided.
- Internationalization is now also available for the JavaScript files.
- When using SAprovider for identity management, passwords are now encrypted on the fly if a identity.saprovider.encryption_algorithm is set to md5 or sha1 in app.conf.
- An alternative quick-start model that uses Elixir (using -e switch) is proposed.
- A similar one will become the default in 1.1.

Apache Xindice is a database designed from the ground up to store XML data or what is more commonly referred to as a native XML database. The name is pronounced zeen-dee-chay in your best faux Italian accent. Dont worry if you get it wrong though, we wont mind. We just care that you spell it correctly.
You might be wondering what a native XML database is good for? Well it pretty much has one purpose, storing XML data. If you dont have any XML data, dont want any XML data or think XML is the most over-hyped technology of the new millennium, then Xindice is not for you. Were not out to change the way data in general is stored, only to provide a good solution for storing XML data. If you survey your projects and see XML popping out of every corner, then Xindice might be a real help for storing that XML.
The benefit of a native solution is that you dont have to worry about mapping your XML to some other data structure. You just insert the data as XML and retrieve it as XML. You also gain a lot of flexibility through the semi-structured nature of XML and the schema independent model used by Xindice. This is especially valuable when you have very complex XML structures that would be difficult or impossible to map to a more structured database.
At the present time Xindice uses XPath for its query language and XML:DB XUpdate for its update language. We provide an implementation of the XML:DB API for Java development and it is possible to access Xindice from other languages using built in XML-RPC API. As standards in the XML database area mature Xindice will include support for those that are most important.
Xindice is the continuation of the project that used to be called the dbXML Core. The dbXML source code was donated to the Apache Software Foundation in December of 2001.
Native XML database technology is a very new area and Xindice is very much a project still in development. The server currently supports storing well formed XML documents. This means it does not have any schema that constrains what can be placed into a document collection. This makes Xindice a semi-structured database and provides tremendous flexiblity in how you store your data, but, also means you give up some common database functionality such as data types. In its current state Xindice is already a powerful tool for managing XML data. However, there is still much that needs to be done. Feedback and contributions are actively encouraged.
This document attempts to describe those features that are working and can be used today. You should review the README file that is part of the Xindice distribution for the most current status on the project.
Main features:
- Document Collections: Documents are stored in collections that can be queried as a whole. You can create collections that contain just documents of the same type or you can create a collection to store all your documents together. The database doesnt care.
- XPath Query Engine: To query the Document Collections you use XPath as defined by the W3C. This provides a reasonably flexible mechanism for querying documents by navigating and restricting the result tree that is returned.
- XML Indexing: In order to improve the performance of queries over large numbers of documents you can define indexes on element and attribute values. This can dramatically speed up query response time.
- XML:DB XUpdate Implementation: When you store XML in the database you may want to be able to change that data without retrieving the entire document. XUpdate is the mechanism to use when you want to do server side updates of the data. It is an XML based language for specifying XML modifications and allows those modifications to be applied to entire document collections as well as single documents.
- Java XML:DB API Implementation: For Java programmers Xindice provides an implementation of the XML:DB API. This API is intended to bring portability to XML database applications just as JDBC has done for relational databases. Most applications developed for Xindice will use the XML:DB API.
- Command Line Management Tools: To aid the administrator Xindice provides a full suite of command line driven management tools. Just about everything you can do through the XML:DB API can also be done from the command line.
- Modular Architecture: The Xindice server is constructed in a very modular manner. This makes it easy to add and remove components to tailor the server to a particular environment or to embed it into another application.
- Database Structure
- The Xindice server is designed to store collections of XML documents. Collections can be arranged in a hierarchy similar to that of a typical UNIX or Windows file system.
- In Xindice the data store is rooted in a database instance that can also be used as a document collection. This database instance can then contain any number of child collections. In a default install of Xindice the database instance is called db and all collection paths will begin with /db. It is possible to rename the database instance if desired though it is not necessary to do so.

RocketSled is a object-oriented, full featured, Web-based application development framework for PHP 5.
Its packages include Active Record and Object Relational Mapping, an advanced XML-based templating language, and a multi-user management suite.
Main features:
- Completely Object Orientated
- Flexible program structure
- Package-centric applications for easy re-deployment
- Integrated XML based templating language (RSML)
- XML based form validation engine (FormML)
- Does not require database for basic install
- Extra packages (currently 2 available) for ActiveRecord and user management
- ActiveRecord package with automated data tainting and universal pagination
- MIT License
Enhancements:
- All packages are now included in the same CVS repository for more basic version numbering, and the system has increased in stability and is more mature.
- It has also had numerous bugfixes and feature enhancements.
- Although the documentation is still very lacking, there is a Getting Started tutorial that will hopefully allow people to start looking at the framework more seriously.

The UserLinux Project is developing an effective, streamlined, freely available Linux distribution for businesses of all sizes. The project is not-for-profit with associated services available from a network of commercial service providers.

UserLinux organization will be a not-for-profit organization. The UserLinux product is a GNU/Linux distribution based from Debian GNU/Linux, but streamlined to a smaller set of default applications.

UserLinux will be freely available in both source and ISO formats. UserLinux will be complemented by a worldwide network of (generally for-profit) service providers offering certification, support, and professional services.

UserLinux will offer businesses unrivaled value by providing a strong base of intelligently selected software accompanied by vendor neutral support and certification options.

Security, training, and worker portability issues are greatly reduced through the selection of the prime application for a specific need. There are no licensing fees for software or development tools. Support services are available from a variety of professional service providers, but are never mandatory.

The UserLinux product is a Linux Operating System distribution streamlined to a smaller set of default applications for business use. The UserLinux variants, currently in beta testing, are freely available in both source and CD installation image formats.

UserLinux has four primary configurations:

Enterprise Server:A solid production server featuring Apache, Samba, and Postfix. Great as a web or file server.
Enterprise Desktop:GNOME desktop featuring OpenOffice.
GUI Server:Features a thin Graphical User Interface environment for more convenient local administration. Same core functionality as Enterprise Server.
SOHO Desktop (Small Office/Home Office):A desktop and server in one. A wider range of capabilities to meet the needs of small businesses.

UserLinux will be driven by the not-for-profit UserLinux Organization and backed by a network of for-profit professional service providers. The distribution will be accompanined by available certifications for people, software, and hardware.

Key UserLinux Advantages:

Streamlined:UserLinux is a streamlined distribution with one key application in mind for a given piece of functionality. One web browser, one word processor, one mail client, one web server. This reduces support overhead both for users and for maintaining security.
Standards compliant:UserLinux encourages cooperation with other open source organizations, and values compliance with open standards.
Designed for business:The UserLinux distribution is specially tailored towards the needs of business.
Professional Services:The third party network of UserLinux affiliated commercial Independent Software Vendors (ISVs) allow for choice in professional services and custom application design options. The separation between the UserLinux organization and the ISVs is a win-win proposition allowing both the support advantages of a service provider network and the neutrality advantages of an operating system not tied to a single company.
Flexible:While each UserLinux configuration is designed to support common functionality as shipped, the systems are also open for expansion beyond the standard UserLinux set.
Disclosure:As a not-for-profit organization working with software developed in the open, the UserLinux organization as well as the development process for the UserLinux distribution are in the open. Critical system updates are clearly and promptly announced so systems remain properly secured.
Lack of lock-in:There are no licensing fees for the UserLinux distribution or related development tools. Service is available from your choice of service providers, but is never mandatory.
Free to obtain:ISO images and the source code are freely available.
Inexpensive to maintain:The streamlined nature of the UserLinux distribution assures less software to update. There are no per seat charges or OS licenses to be tracked and audited.
Secure:Leveraging from the power of open source, the code used in the UserLinux distribution not only has thousands of hours of development but thousands of hours of peer review.
Certifications:Hardware, software, support and professional certifications will be available. The standards and corresponding tests will be created by UserLinux with third parties performing the testing activities.
Mature Software:UserLinux is directly based from Debian GNU/Linux, a general focus, free Linux distribution in existence for over a decade. Key components of UserLinux, including the highly popular Linux Kernel and Apache web server, are very mature with millions of critical-use installations.

TunesBrowser project is a simple music player, capable of playing music found on iTunes shares.
TunesBrowser can connect to the latest iTunes applications (as of April 29 2004) and is implemented on top of libopendaap.
TunesBrowsers interface is quite similar to that of iTunes. TunesBrowser was written with the purpose of being a prototype front-end for libopendaap. I intend to integrate libopendaap with other, more mature, players.
Main features:
- Play mp3s off other computers running iTunes
- Discovery of hosts over Rendezvous.

SwingWT is a 100% pure Java library which aims to be a free implementation of Swing and AWT. Unlike Swing, SwingWT drives native peer widgets for your platform from SWT. You can see a screenshot of the basic SwingWT demo here (Linux/GTK2) and here (MacOSX).
Main features:
- More responsive GUIs and faster startup times
- Less RAM usage for applications
- Many developers prefer the Swing API
- Existing Swing applications dont need to be recoded
- Mature Swing UI designers can be used
- Developers deploying to *nix/Win32 can compile natively with GCJ and the applications can be distributed without a VM. Linux distribution makers could package many existing Java/Swing applications that previously could not be distributed in workable state.
- SWT components can be directly accessed through the API, allowing mix and match (make Eclipse plugins with Swing!)
- All platform benefits such as font sub-pixel decimation for LCD monitors (unavailable in Swing)
- Use Swing on mobile devices!
- The best of both worlds! New Swing components for JClosableTabbedPane, JCoolBar, JTaskTrayItem..
- A FREE implementation of Swing you can redistribute and modify to suit your own requirements
- Insulation from changes to the SWT APIs
- Insulation from differences between SWT platforms
Enhancements:
- This release contains many fixes and compatibility improvements, including support for AudioClip and SWT 3.2.

Excalibur is an open source software project of The Apache Software Foundation. Our primary product is a lightweight, embeddable Inversion of Control container named Fortress that is written in java.

Inversion of control, also known as the hollywood principle ("dont call us, well call you"), is a simple but powerful concept. The idea is that we dont "wire up" all the pieces that make up an application (the "components") by writing lots of this-component-uses-that-one-like-so code, nor do we use some kind of lookup directory (like JNDI, for example) where each component decides what components to interact with itself. Instead, we instruct a smart piece of software, the container, to tell the components how to interact.

Fortress (and also its predecessor, "ECM") is such a container. It is lightweight, by which we mean that it doesnt need a lot of resources, take a lot of disk or memory, or impose all sorts of demands on its environment. Fortress is also embeddable, by which we mean that you can use fortress inside just about every java environment. More concretely, you can use it as the basis of a large standalone development platform (like the Keel project), at the core of a servlet-based web application (like Cocoon) or even as the basis of a GUI application (like GuiApp).

Fortress knows how to manage components that have been developed using a rigid lifecycle contract called Avalon-Framework. In the next upcoming release, fortress will also be able to manage ordinary javabeans, and support for other kinds of Inversion of Control are planned.

Besides providing fortress, excalibur also provides a small library of very useful components. We also distribute some of the libraries used to build fortress (and some other containers) seperately. This selection of libraries is called containerkit.

So why is excalibur an interesting project?

Heres a few partial answers.

good code. Code that comes from the mature avalon project (everything that used to be branded as "Avalon Excalibur" and "Avalon Fortress"). This includes two lightweight Inversion of Control containers. One of these powers, among other things, Cocoon. The other ("fortress") is the basis of projects like Keel. Excalibur also includes powerful and mature reusable "components" and "libraries", handling tasks ranging from thread management to component pooling to (URI-and-similar-) source resolving.

smart developers. Most of these people are or have been active in the avalon project in various roles. Several of them are apache members. Together they have loads and loads experience under their belts related to inversion of control development. In fact, Im confident to say this list includes some of the biggest experts on inversion-of-control-style container development.

exciting community. Several open source and commercial projects (both at apache and elsewhere) depend on and contribute to the excalibur project. A strong team of enthousiastic developers (with strong ties to several other projects in the same problem domain) has various big and small plans with excalibur. One of the leading open source organisations in the world, The Apache Software Foundation, is hosting the project, providing insight, advice, infrastructure, legal backing, a time- and battle-proven development process, and much more.