Free thin layer chromatography basic software for linux

The layer extract plug-in is a Gimp plug-in that creates a new image/film by periodically extracting layers from another image.

It takes one interval (number of sequent layers) every period. The number of periods can be limited.

"< Image >/Filters/Animation/Layer Extract"

MWChat Basic (My Web based Chat) is the free version of our online chat system.

Licenses are IP based, one license per IP.

It has support for multiple rooms and languages, a large number of IRC-like commands, private messages and rooms, message encryption, buddy lists, logging, registered users, chat profiles, file sharing, and more. It is a very lightweight, full-featured, and secure chat room.

Vista Basic provides a theme similar to Microsoft Vista.

window borders similar to those of Microsoft Vista when using non Aero compatible software (such as JRE 6 or Photoshop CS 2)

GNU Transport Layer Security Library is a library which implements a secure layer over a reliable transport layer such as TCP/IP. GNU Transport Layer Security Library implements the TLS 1.0 and SSL 3.0 protocols, accompanied with authentication methods such as X.509, OpenPGP, and SRP.
Main features:
- Support for TLS 1.1 and SSL 3.0 protocols
- Support for TLS extensions
- Support for authentication using the SRP protocol
- Support for authentication using both X.509 certificates
- and OpenPGP keys Support for X.509 and OpenPGP certificate handling.
- Supports all the strong encryption algorithms
- Supports compression
- Runs on most Unix platforms
Enhancements:
- Support for Proxy Certificates as per RFC 3820 were added.
- The --generate-proxy option was added to certtool.
- certtool --certificate-info now prints information for Proxy Certificates.
- New APIs were added to set proxy subject names and get or set a proxy cert extension.
- Parsing of pathLenConstraints in BasicConstraints with missing CA was fixed.
- A self-test was added to test for regressions of pathLenConstraint.
- Certtool now prints times in UTC when printing certificate/CRL info.
- Importing of ASCII armored OpenPGP keys was fixed.

Thin FTP Upload project is an FTP upload applet designed for integration with Web applications.
Do you want to quickly add FTP file upload functionality to your website? Then Thin FTP Applet, a product that can be installed in less than 2 minutes is the product to choose.
To send files using the File Transfer Protocol, all your users have to do is to drag and drop them onto the designated area of the browser. Entire directory tree and a virtually unlimited number of files totalling several giga bytes can be transfered in this manner.
If your server is configued to allow annoymous transfers your users dont even have to login. Else they can login interactively by entering their username and password. Or else you can make it easier for them by using a single predefined username and password for each user so that multiple accounts do not have to be created.
Whats New in 1.02 Stable Release:
- The new version of the applet aims for improved compatibility with a wider range of FTP servers, epecially those servers deployed on Windows.
- The new version includes a subtle change in the way that the applet handles the trailing slash in the URL.
Whats New in 2.0 Development Release:
- Interrupted FTP uploads can now be resumed.
- A new progress monitor has been added.
- The applet loading mechanism has been changed, and the applet can now be configured using HTML parameters.

Contrast Mask adds a Contrast Mask layer to the current image - useful for heightening the contrast in photographs that are over- or under-exposed, or those with extreme dynamic ranges.

Takes two arguments, blur radius and layer opacity.

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.

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.