Free provider magazine software for linux

Image Magazine provides a content type which acts both as a folder and as an image.
You populate it with 2 to 4 images, and optionnaly select a layout.
Options include width, background color, padding and margin, and layout mode.
ImageMag then merges the images into a layout while keeping the aspect ratios.
You can then use and call your ImageMag as a standard ploneImage, this mean you can :
.use instance/image_thumbnail, instance/image_large, and so on suffixes to call its different sizes
.call it directly from kupu to illustrate your articles (see readme.txt)
Works with:
- Plone 2.5.2
- Plone 2.5.1
- Plone 2.5

Direct Access Provider Library in short DAPL is a transport-independent, platform-independent, high-performance API for using the remote direct memory access (RDMA) capabilities of modern interconnect technologies such as InfiniBand, the Virtual Interface Architecture, and iWARP.
This is the reference implementation of that specification by the DAT Collaborative who maintain the DAPL API.
Enhancements:
- Support was added for new IB verbs client register event.
- Some problems supporting create qp without recv cq handle or recv qp resources were fixed.
- Some timeout and long disconnect delay issues exposed during scalability tests were fixed.
- Minor build problems were fixed.
- Support for multiple IB devices was added to dat.conf to support IPoIB HA failover.
- Support for returning local and remote port information was added.
- The RPM spec file was cleaned up.
- Enviroment variables to configure connection management timers were added.

Firebird .NET Data Provider is an ADO.NET data provider for Firebird. Firebird .NET Data Provider is written in C# and provides a high-performance native implementation of the Firebird API. It also includes an implementation of the Firebird Services API and Firebird array datatype support.

Firebird is a relational database offering many ANSI SQL standard features that runs on Linux, Windows, and a variety of Unix platforms. Firebird offers excellent concurrency, high performance, and powerful language support for stored procedures and triggers. It has been used in production systems, under a variety of names since 1981.

Firebird is a commercially independent project of C and C++ programmers, technical advisors and supporters developing and enhancing a multi-platform relational database management system based on the source code released by Inprise Corp (now known as Borland Software Corp) on 25 July, 2000 under the InterBase Public License v.1.0

Template::Provider::OpenOffice is a OpenOffice (ODT) Provider for Template Toolkit.

This module extends Template::Provider to automatically extract the content.xml file from an OpenOffice zip file and run it through Template::Toolkit for processing.

We use OpenOffice::OODoc to actually open the document and extract the content.xml file. This gives us the benefit of having the methods available to add/subtract files in addition to parsing and processing the content file if we want to do some custom work in addition to templating.

mod_perl project brings together the full power of the Perl programming language and the Apache HTTP server. You can use Perl to manage Apache, respond to requests for web pages and much more.

mod_perl gives you a persistent Perl interpreter embedded in your web server. This lets you avoid the overhead of starting an external interpreter and avoids the penalty of Perl start-up time, giving you super-fast dynamic content.

As youd expect from the Perl community, there are hundreds of modules written for mod_perl, everything from persistent database connections, to templating sytems, to complete XML content delivery systems. Web sites like Slashdot and Wired Magazine use mod_perl.

mod_perl is an Apache Software Foundation project. It is licensed under the Apache Software License.

Template::Plugins is a Perl module with plugin provider.

SYNOPSIS

use Template::Plugins;

$plugin_provider = Template::Plugins->new(%options);

($plugin, $error) = $plugin_provider->fetch($name, @args);

The Template::Plugins module defines a provider class which can be used to load and instantiate Template Toolkit plugin modules.

Sudoku Savant is a simple GUI-driven application to solve and generate Sudoku puzzles through logical means.

Sudoku Savant generates and solves standard Sudoku puzzles with anything from 3x3 to 5x6 or 6x5 grids, using the following strategies:

- Singletons
- Locked candidates
- Number subsets
- X-Wings, Swordfish and Jellyfish
- Both Simple and Multi-Colouring.

These strategies should be enough to provide a step by step solution for any Sudoku puzzle that you are likely to find in a newspaper or magazine, although Savant can also resort to "trial and error" if presented with something really pathologically nasty. (This will at least confirm that the puzzles solution is unique.)

You may also parameterise or turn off the more advanced strategies, to see whether they were really needed.

Finally, Sudoku Savant lets you solve the puzzle by hand, providing hints, cell colouring, up to 4 pencil marks per cell, and the ability to high-light any incorrect moves. A partially completed puzzle can be saved in a simple text format so that you can continue solving it later.

phpMyID is a small, fairly lightweight, standalone, single-user Identity Provider for OpenID authentication.
OpenID is an open, decentralized, free framework for user-centric digital identity (I stole that from their website). But what does it mean? Well, basically OpenID is a way to authenticate yourself to various places (websites) by verifying your identity as the owner of a particular URL (say, a website of your own).
Instead of giving a username and password to a login form, you just give it your URL. Youre then directed to your "identity provider" to log in, and when it authenticates you, you go back to the site you were orignally trying to get into. Why this is good or bad, and what the actual implications of it are... well, thats all mostly outta scope as far as phpMyID is concerned. Suffice it to say, phpMyID acts as an "identity provider" so you can log in to OpenID enabled sites.
From a user point of view, OpenID is a neat concept, but it has a few flaws. For example, when I wanted to actually, yknow, get an OpenID thingie of my own so I could log into OpenID sites, I found there was no satisfactory way to get one. My options were:
Download a ready made application to handle serving up identities and create myself an account in it. - There arent many of these, and what few there are seem to be geared towards multi-user setups. Since theres only one of me, this option seemed like overkill.
Download a complex set of libraries and build an application to handle serving up my identity. - Again there are not many of these, and what few there are seem a bit overcomplicated for my needs.
Set up an account with a third party provider. - A bad option for me because I really dont like the idea of coupling a theoretically decentralized framework to one of a handfull of third party providers (and giving them my account credentials). Sure, someone who doesnt have their own site and server technology will probably go this way, but not me.
Since I couldnt find the simple solution that I wanted, I did what any [idiot|geek] would do, and created the missing option for myself: a single user OpenID server. phpMyID.
Usage
phpMyID is a single user (though, if you were so inclined, you could easily turn it into a multi-user setup) IdP, or "Identity Provider" for the OpenID framework. Its a single PHP script with minimal dependancies.
You dont need a database, you dont need to make your filesystem writable, you dont need to download any libraries, and you dont need to recompile PHP. Okay, well, you shouldnt need to do any of that.
Installing phpMyID requires an MD5 hashing utility. Why? Because you have to authenticate to it using a password. phpMyID uses HTTP Digest authentication for security and your password must be encrypted when you enter it during installation. Say it with me: "passwords should never be stored or transmitted in plain text" (one of the advantages of phpMyID and OpenID is that they never are).
For Linux or OSX (or any other Unix-like OS), I suggest using OpenSSL to encrypt your password. For Windows, there are a number of utilities available, but I recommend this one by Colin Plumb. Its public domain code, and it will do exactly what you need (yes, the hash it create is all upper-case - dont worry, phpMyID will convert it for you). You can use PHPs md5 function to generate your hash for you on the fly, but I must discourage doing so. Not only does it take all the fun out, but you have to store your password in plain text to make it go.
Complete installation instructions, including examples of how to encrypt your password, are available in the provided README file (heres the svn version).
Enhancements:
- This release should fix the outstanding (known) "bad signature" errors, adds a number of refinements, includes a testing mode, and provides support for a more versatile set of "big math" functions.