Free store images software for linux

This little Java program helps to sort your images from digital cameras. It reads the EXIF-Header of the JPEG-Files an copies the images from the source dir to a centralized target dir sorted by year, month and day.

The files are renamed to represent their capture date and time. So you will have a Image repository sorted by capture date of the images.

Additionally some of the image meta informations will be stored in a database along with the MD5 hash of the image as primary key. SortImages check each image beforce copying if its already in the database. If not, the image will sorted into the appropriate folder.

Process Raw Images is a service menu for processing many raw images at once. Supports output to Jpeg, Png and Tiff.

SIR - Simple Image Resizer is a simple application for resizeing images. SIR - Simple Image Resizer is inspired by GTPY - ImageResizer.
But I used C++/QT anda QImage class to convert the images.
SIR - Simple Image Resizer can convert into and from the following formats:
- JPEG
- PNG
- BMP
- GIF
- XPM
- PGM
- PBM
- PPM
To compile:
#qmake sir.pro
#make
Enhancements:
- Polish translation added (Thanks zoteek)
- Minor bug fixes

ImageServer is a software for maintaining archives of images. Theres much software available to manually view, categorize and search images. ImageServer was designed to solve a different problem:
Imagine being a photographer or photo agency: You have a lot of images in many formats, all stored in a directory structure - your archive.
This creates at least two problems:
- The archive may contain different images with the same name. What do you do when a customer orders "flowers.tif" and this name exists in twenty different subfolders in your archive?
- The customer doesnt need your original 22megapixel 16-bit tiff file for his powerpoint presentation or layouting, he wants a small jpeg instead.
The first problem can be managed by assigning unique names to images every time an image is put into the archive.
The second problem is a little more difficult. Youll have to convert the requested images to smaller JPEGs. After doing that for too many times, you start caching the small JPEGs so you wont have to convert again for the next customer asking for that image. But then, you edit the original image and forget to update the JPEGs. Furthermore, its not enough to keep these resized jpegs for presentations, your customers graphics department also wants correctly downsampled eps images for layouting advertisements in QuarkXPress. So you start having two slaveArchives - one with JPEG and one with EPS images - and spend half of your day trying to synchronize the three.
ImageServer solves both problems automatically. It is a program with a nice GUI, configured to watch your masterArchive. As soon as images are put into any subfolder, theyll be assigned unique names if necessary. Afterwards, each image is read, and for each defined slaveArchive, a preview is created and saved. The same happens when an image in the masterArchive is altered. All this works completely automatically, theres nothing youll have to do; the GUI is just for being able to watch whats happening.
Main features:
- Input file checking: as soon as an image is put into the archive, ImageServer checks the extension to see whether it really is an image. If not, it is put into a specified folder outside of the archive.
- If configured to do so, an image without a suiting name is assigned a new name which is constructed of both the subfolders it resides in and a unique-per-subfolder serial number of arbitrary length.
- When detecting a change in the masterArchive, ImageServer can play a sound.
- When starting to convert an image, ImageServer can play a sound.
- ImageServer can remember the names it has already assigned to images in the past. This way, names assigned to an image A will never be assigned to another image B after A has been deleted.
- Any number of slaveArchives can be defined, and they can be in any location.
- Each defined slaveArchive can have completely different settings for the images that will populate it. Resizing or resampling? RGB or CMYK? Jpeg, EPS, PNG or TIFF?
- You can choose whether each slaveArchive should inherit the exact same directory structure from the masterArchive or whether the slaveArchives images should all be put into the same folder.
- In case dazuko missed something, you can tell imageserver to manually look into a folder. It can then either process all images in that folder or only those where slaveArchive-images are missing.

WWW::Google::Images is a Google Images Agent.

SYNOPSIS

use WWW::Google::Images;

$agent = WWW::Google::Images->new(
server => images.google.com,
proxy => my.proxy.server:port,
);

$result = $agent->search(flowers, limit => 10);

while ($image = $result->next()) {
$count++;
print $image->content_url();
print $image->context_url();
print $image->save_content(base => image . $count);
print $image->save_context(base => page . $count);
}

KIWI Image System provides a complete operating system image solution for Linux supported hardware platforms as well as for virtualisation systems like Xen Qemu or VMware. The KIWI architecture was designed as a two level system. The first stage, based on a valid software package source, creates a so called physical extend according to the provided image description. The second stage creates from a required physical extend an operating system image. The result of the second stage is called a logical extend or short an image.
A normal installation process is starting from a given installation source and installs single pieces of software until the system is complete. During this process there may be manual user intervention required. However an operating system image represents an already completed installation encapsulated as a file and optionally includes the configuration for a specific task. Such an operating system starts working as soon as the image has been brought to a system storage device no matter if this is a volatile or non volatile storage. The process of creating an image takes place without user interaction.
This means all requirements of the encapsulated system has to be fulfilled before the image is created. According to this the so called image description tree stores all the information needed to create an image.
Main features:
- Distribution independent
- Support for virtualisation systems like Xen
- Support for deploying images over the network
- Support for VMware / Qemu images
- Support for USB-Stick systems
- Support for LiveCD/DVD systems
- Centralized image description based on XML
- Prebuild boot images for SUSE systems
- Prebuild PXE configuration usable with kiwi netboot images
- SUSE Linux on a 128MB flash card.. yes thats possible