Free directmedia layer software for linux

OSDL project has for goal to provide a free portable high-level open-source library for multimedia and game programming. It is based upon low level graphical backends, notably Sam Lantingas SDL, which means Simple DirectMedia Library.
OSDL is a C++ framework built currently on top of SDL, thus OSDL stands for Objet oriented Simple DirectMedia Library.
OSDL makes use of the Ceylan library, the place where we gathered all generic developments needed by OSDL.
OSDL is also strongly linked with our project dedicated to the creation of an open-source gaming console, Once Sol. More generally speaking, one may take a look at our project portal, Esperide, which gathers all we are doing in the video game field.
At first, most people are primarily interested in screenshots, then in the OSDL API, finally in the recommended way of getting OSDL, which is named LOANI.
This is still an early stage of OSDLs development, so little information is to be found on this website. We nevertheless hope it will get bigger and bigger, as the source code grows. We advise you to look at the column we named Documentation, since many interesting articles about game creation lie there.
Enhancements:
- SVN used instead of CVS
- The Autotools are used, instead of custom-made GNUMakefiles
- integration to the Ceylan 0.5 version
- OSDL scheduler robustified and enhanced a lot
- numerous tests improved (full test suite added), and many bugs fixed

The CAN Abstraction Layer (CANAL) provides a single interface for programs to use different CAN drivers.
It consists of a CANAL daemon that handles client and driver communication, a canalLogger that logs messages in a window, and a simple diagnostic application. C++ clases and DLL/DL interfaces are provided.
Enhancements:
- The configuration readings for CanalWorks were upgraded.
- A GUID ordering problem in canald was fixed.
- A problem with clear message list switch in CanalWorks was fixed.
- A problem in which Linux version Level I received a thread with an invalid count returned for DataAvailable was fixed.

SYNOPSIS

#####
# Subroutines
#
use Tie::Layers qw(is_handle config);

$yes = is_handle( $file_handle );

($key, $old_value) = config(%options, $key);
($key, $old_value) = config(%options, $key => $new_value );

####
# Config default startup options
#
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, @option_list);
@old_options_list = config(%options, %option_list);

#####
# Class interface
#
require Tie::Layers;

#####
# Using support methods and file handle with
# the file subroutines such as open(), readline()
# print(), close()
#
tie *LAYERS_FILEHANDLE, Tie::Layers, @options
$layers = tied *LAYERS_FILEHANDLE;


#####
# Using support methods only, no file subroutines
#
$layers = Tie::Layers->TIEHANDLE(@options);

($key, $old_value) = $layers->config($key);
($key, $old_value) = $layers->config($key => $new_value );

@old_options_list = $layers->config(@option_list);
@old_options_list = $layers->config(@option_list);
@old_options_list = $layers->config(%option_list);

$data = $layers->fin($filename, @options);

$data = $layers->fout($filename, $data, @options);

$yes = $layers->is_handle( $file_handle );

If a subroutine or method will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}.

The Tie::Layers program module contains the tie file handle Tie::Layers package. The Tie::Layers package provides the ability to insert a stack of subroutines between file subroutines print and realine and the underlying $file. The syntax of the subroutines of each layer of the readline stack and the print stack must comply to the the requirements described herein below.

This is necessary so that the Tie::Layers READLINE and PRINT subroutines know how to transfer the output from one layer to the input of another layer. The stacks are setup by supplying options with a reference to the subroutine for each layer in the print stack and the readline stack. The Tie::Layers are line orientated and do not support any character file subrouintes.

The getc, read, and write file subroutines are supported by the Tie::Layers package. The seek routines are line oriented in that the seek and tell subroutine positions are the line in the underlying file and not the character position in the file.

RULI stands for Resolver User Layer Interface. Its a library built on top of an asynchronous DNS stub resolver. RULI provides an easy-to-use interface for querying DNS SRV resource records. The goal is to promote wide deployment of SRV-cognizant software. RULI aims to fully support SRV-related standards. There are bindings for PHP, Perl, Guile/Scheme, Java, and Lua. IPv6 is supported.

Now you can understand the benefits of SRV records and please see how RULI can help you.

SRV records are more complex than A records

Handling DNS SRV is not as simple as to deal with ordinary address records. When one performs a query for A records by calling gethostbyname(), he gets a list of addresses which should be contacted in the same order as they were received. For SRV records, there is an additional logic that must be applied to the records, based on their weight and priority, to discover the correct sequence for contacting them.
RULI can handle SRV records for you

The SRV logic is described in RFC 2782. Those who intend to use SRV benefits in their application are expected to implement that exact behavior. RULI can help here: it automatically performs all the SRV logic for you.
Keep focus on your application logic

Application developers probably want to spend time on their business logic; not dealing with the details of the DNS protocol or implementing the SRV specification.

RULI is a tested framework designed to properly fetch SRV records. It saves you time and head aches.
RULI is free as in free beer and in free speech

PHP MySQL Database Layer Class is a php class providing some very useful methods to work with a mySQL database.
Main features:
- connects you to a mySQL host and select a database in a single call (opposed to PHPs native functions which requires two steps)
- has a "query" method that has the same role as PHPs mysql_query but this one will tell you about the affected rows (through the "affectedRows" property) when executing an INSERT, UPDATE, DELETE query and about the found rows (through the "foundRows" property) when executing a SELECT query - the "foundRows" property tells you how many records would the query return if there was no LIMIT applied to it - very useful when creating listing so you dont have to do a query to determine how many records you have in a database and the again a query to show only the records from a page
- has an "escape_string" method that will "mysql_real_escape_string" your string weather the magic_quotes are on or not
- has a "dlookup" method that i am sure you will find VERY useful once you get to know it: it return data from a single table cell based on standard mySQL WHERE criteria - see the manual for detailed info! (yes, it acts exactly like the function with the same name from microsft access)
- provides you with a very useful debug interface which shows you each query your script is running, for how long, the total number of queries made, the total execution time of your queries, errors of your queries and what are the values of $_GET, $_POST, $_COOKIES and $_SERVER superglobal variables. The debug interface is template driven and supports localisation.
- it will notify you if a specific query is executed more than once and will advise you to optimize the script
- you can instruct it to send you an email if a query runs longer then a specified time
- the code is heavily documented so you can easily understand every aspect of it and even maybe use it as a php tutorial
Enhancements:
- the state of $_FILES and $_SESSION superglobals are now also shown in the debug window
- better integration with XTemplate (previously, there was a variable assigned to each entry in the language file now the XTemplates feature to handle arrays is used)
- properties will now have default values in PHP 4

Object Relational Membrane is a Python package that provides the functionality of an object relational layer like EJB or other persistence storage systems.
Object Relational Membrane is a thin compatibility layer between SQL table layouts and Object Oriented Python. While providing a good deal of functionality, it tries to be as small and simple as possible. It currently works with PostgreSQL and Gadfly.
Adapters for Firebird and MySQL are planed.
Enhancements:
- A number of small changes and enhancements.
- The last release previous to a "beta" release.

Database Independent Abstraction Layer for C (libdbi) implements a database-independent abstraction layer in C, similar to the DBI/DBD layer in Perl.
Writing one generic set of code, programmers can leverage the power of multiple databases and multiple simultaneous database connections by using this framework.
Main features:
Database-level abstraction:
Your programs dont need to deal with the arbitrary interfaces and oddities of each database library. libdbi handles all the details for you, you just tell it what you want the database to do.
Modularity:
Since database code written with libdbi is not tied to one specific database server, you can effortlessly switch databases or give your users the option to specify their own database settings.
Clean interface:
With ample documentation describing libdbi and its well thought out object-oriented design, programming with libdbi should be less painful than programming with native database libraries. And you only need to learn it once instead of learning each database librarys syntax.
Accommodates coder apathy:
libdbi is written to do The Right Thing(tm), not just some quick hack that does the job in a half-assed fashion. This saves tons of your $100/hour time from debugging, so that you can mess around having fun during the hours that clients are paying you to debug. It also strives to reduce the worldwide crisis of carpal tunnel syndrome, so it uses constructs such as this one to pack multiple function calls into one line, saving you the bother of typing more than you have to:
dbi_result_get_fields(result, "id.%i firstname.%s lastname.%s fractional_value.%f", &id, &firstname, &lastname, &floatval);
Driver interface:
The dynamic linking used by libdbi allows for driver authors to license their drivers however they please - they are not restricted to the GPL or LGPL. Drivers are easy to write, and require no special installation.
Error handling:
Instead of checking every single database call for errors, libdbi gives programmers the option of registering an error handler callback, similar to a signal handler. Because we know youll "forget" to check for errors otherwise :)
Convenience:
Spend your time writing clever code, not reinventing the wheel with your own single-use, #define-abusing, less featureful database interface.
libdbi implements a database-independent abstraction layer in C, similar to the DBI/DBD layer in Perl. Writing one generic set of code, programmers can leverage the power of multiple databases and multiple simultaneous database connections by using this framework.
The libdbi-drivers project maintains drivers for libdbi. Drivers are distributed seperately from the library itself.
There are currently drivers for MySQL, PostgreSQL, SQLite, and mSQL. More are on the way.
Enhancements:
- Support for a timezone suffix in time and date types was added.
- Error handling and error reporting were vastly improved.
- Some memory leaks were fixed.