Free 0.2 in to mm software for linux

run in xterm is an servcie menu which adds "run in xterm" & "run in xterm as root" to action menu on binary files, scripts etc.

It has 2 languages: english and polish.

Installation:

copy/save this file in
~/.kde/share/apps/konqueror/servicemenus

Downloads in Tab is an extension which opens "Downloads" manager in tab from Tools menu.

Opens "Downloads" manager in tab from Tools menu or automaticlly when a download starts, when in options you uncheck "Show the Downloads window when downloading a file"

To use tab, in Firefox Options dialog uncheck "Show the Downloads window when downloading a file"

To use window, in Firefox Options dialog check "Show the Downloads window when downloading a file"

To use neither, disable or remove this extension and in Firefox Options dialog uncheck "Show the Downloads window when downloading a file" which will restore original functioning.

Set photo in Kopete is a really simple service menu that just sets the current photo as your photo in Kopete, nothing more, nothing less.

It doesnt handle directories containing space yet, if someone have a workaround so that KURL dont escapes all characters that would be nice=)

Just put this file in ~/.kde/share/apps/konqueror/servicemenus or use http://www.kde-look.org/content/show.php?content=11435 to install it.

bkp is a command line backup tool intended for local storing written in bash under GPL license. It allows you to make a solid backup of your data, keeping original files permissions.
bkp has a date (dd-mm-YY) support, so you will be able to know when you have made your backups. In this way you can upgrade them. It also support : gzip compression, background mode, md5 checking, events logging (and managing) and default directory.
This program can convert relative pathname of file or directory to its absolute pathname; in this way bkp can also rebuild original directory tree.
Usage : bkp.sh < files > | < directories > [[ option ]]
Enhancements:
- added --encrypt option : is now possible to encrypt backup using gpg.
- some functions have been reimplemented due to support --encrypt option.
- fixed --import option, now this option adds correctly backup to database and uses scp transfer method.
- added --export option : in now possible to export bakcup on a remote
- host using scp transfer method.
- added --verbose option.
- function help_option () now gives more details (users errors info).
- made some generic changes to program output.
- made some generic optimization.
- fixed some generic errors.

MP3::Info is a Perl module that can manipulate / fetch info from MP3 audio files.

SYNOPSIS

#!perl -w
use MP3::Info;
my $file = Pearls_Before_Swine.mp3;
set_mp3tag($file, Pearls Before Swine, q"77s",
Sticks and Stones, 1990,
q"(c) 1990 77s LTD.", rock & roll);

my $tag = get_mp3tag($file) or die "No TAG info";
$tag->{GENRE} = rock;
set_mp3tag($file, $tag);

my $info = get_mp3info($file);
printf "$file length is %d:%dn", $info->{MM}, $info->{SS};
my $mp3 = new MP3::Info $file;
$mp3->title(Perls Before Swine);
printf "$file length is %s, title is %sn",
$mp3->time, $mp3->title;

$mp3 = MP3::Info->new(FILE)

OOP interface to the rest of the module. The same keys available via get_mp3info and get_mp3tag are available via the returned object (using upper case or lower case; but note that all-caps "VERSION" will return the module version, not the MP3 version).

Passing a value to one of the methods will set the value for that tag in the MP3 file, if applicable.

use_mp3_utf8([STATUS])

Tells MP3::Info to (or not) return TAG info in UTF-8. TRUE is 1, FALSE is 0. Default is TRUE, if available.

Will only be able to turn it on if Encode is available. ID3v2 tags will be converted to UTF-8 according to the encoding specified in each tag; ID3v1 tags will be assumed Latin-1 and converted to UTF-8.

Function returns status (TRUE/FALSE). If no argument is supplied, or an unaccepted argument is supplied, function merely returns status.

This function is not exported by default, but may be exported with the :utf8 or :all export tag.

use_winamp_genres()

Puts WinAmp genres into @mp3_genres and %mp3_genres (adds 68 additional genres to the default list of 80). This is a separate function because these are non-standard genres, but they are included because they are widely used.

You can import the data structures with one of:
use MP3::Info qw(:genres);
use MP3::Info qw(:DEFAULT :genres);
use MP3::Info qw(:all);

remove_mp3tag (FILE [, VERSION, BUFFER])

Can remove ID3v1 or ID3v2 tags. VERSION should be 1 for ID3v1 (the default), 2 for ID3v2, and ALL for both.

For ID3v1, removes last 128 bytes from file if those last 128 bytes begin with the text TAG. File will be 128 bytes shorter.

For ID3v2, removes ID3v2 tag. Because an ID3v2 tag is at the beginning of the file, we rewrite the file after removing the tag data. The buffer for rewriting the file is 4MB. BUFFER (in bytes) ca change the buffer size.

Returns the number of bytes removed, or -1 if no tag removed, or undef if there is an error.

set_mp3tag (FILE, TITLE, ARTIST, ALBUM, YEAR, COMMENT, GENRE [, TRACKNUM])

set_mp3tag (FILE, $HASHREF)

Adds/changes tag information in an MP3 audio file. Will clobber any existing information in file.

Fields are TITLE, ARTIST, ALBUM, YEAR, COMMENT, GENRE. All fields have a 30-byte limit, except for YEAR, which has a four-byte limit, and GENRE, which is one byte in the file. The GENRE passed in the function is a case-insensitive text string representing a genre found in @mp3_genres.

Will accept either a list of values, or a hashref of the type returned by get_mp3tag.
If TRACKNUM is present (for ID3v1.1), then the COMMENT field can only be 28 bytes.

ID3v2 support may come eventually. Note that if you set a tag on a file with ID3v2, the set tag will be for ID3v1[.1] only, and if you call get_mp3tag on the file, it will show you the (unchanged) ID3v2 tags, unless you specify ID3v1.

get_mp3tag (FILE [, VERSION, RAW_V2])

Returns hash reference containing tag information in MP3 file. The keys returned are the same as those supplied for set_mp3tag, except in the case of RAW_V2 being set.
If VERSION is 1, the information is taken from the ID3v1 tag (if present). If VERSION is 2, the information is taken from the ID3v2 tag (if present). If VERSION is not supplied, or is false, the ID3v1 tag is read if present, and then, if present, the ID3v2 tag information will override any existing ID3v1 tag info.

If RAW_V2 is 1, the raw ID3v2 tag data is returned, without any manipulation of text encoding. The key name is the same as the frame ID (ID to name mappings are in the global %v2_tag_names).

If RAW_V2 is 2, the ID3v2 tag data is returned, manipulating for Unicode if necessary, etc. It also takes multiple values for a given key (such as comments) and puts them in an arrayref.

If the ID3v2 version is older than ID3v2.2.0 or newer than ID3v2.4.0, it will not be read.

Strings returned will be in Latin-1, unless UTF-8 is specified (use_mp3_utf8), (unless RAW_V2 is 1).

Also returns a TAGVERSION key, containing the ID3 version used for the returned data (if TAGVERSION argument is 0, may contain two versions).
get_mp3info (FILE)

Returns hash reference containing file information for MP3 file. This data cannot be changed. Returned data:

VERSION MPEG audio version (1, 2, 2.5)
LAYER MPEG layer description (1, 2, 3)
STEREO boolean for audio is in stereo

VBR boolean for variable bitrate
BITRATE bitrate in kbps (average for VBR files)
FREQUENCY frequency in kHz
SIZE bytes in audio stream
OFFSET bytes offset that stream begins

SECS total seconds
MM minutes
SS leftover seconds
MS leftover milliseconds
TIME time in MM:SS

COPYRIGHT boolean for audio is copyrighted
PADDING boolean for MP3 frames are padded
MODE channel mode (0 = stereo, 1 = joint stereo,
2 = dual channel, 3 = single channel)
FRAMES approximate number of frames
FRAME_LENGTH approximate length of a frame
VBR_SCALE VBR scale from VBR header
On error, returns nothing and sets $@.

Hugin is a panorama tools GUI.

Goal: an easy to use cross-platform GUI for Panorama Tools.

With hugin you can assemble a mosiac of photographs into a complete immersive panorama, stitch any series of overlapping pictures and much more.

Main Window

This window consists of a toolbar that provides quick access to important functions. It also contains the Images, Lens, Control Point, Optimizer and Panorama Tab, which will be explained below.

Images Tab

Images can either be added with the Add button, or via drag and drop. To change the orientation of one or more images, select them in the list on the left. The image will be show in the preview area, and its orientation (yaw, pitch and roll values) can be edited on the left.

It is possible to select multiple images at the same time. Changes in orientation will be applied to all selected images

Lens Tab

The lens tab looks a lot like the Images tab, except that the lens settings can be edited here. As in the Images Tab, multiselection can be used to change the parameters for multiple images.

Currently only one lens is supported. The idea is that the Lens describes the process that was used to create the image. The most important parameters are the Lens type and the HFOV (Horizontal Field of View). Hugin will read the EXIF information in jpg files created by digital cameras, so usually it is filled out correctly.

Photographers do not use a HFOV in degrees, but the focal length. The focal length can be entered and it will be converted to HFOV in degrees, like the panorama tool require it. The focal length entered is taken to be for 35 mm film cameras.

Usually images are more or less distorted. This can be seen especially if there are long straight lines close to the image border, which are usually not completely straight but bent a little. The a b and c parameters are used to remove that distortion. They are applied radially from the image center, which can be moved by changing the d and e parameters.

During image capture, it is possible that the parameters vary, that is are not the same for each image. This can have many reasons, one of the could be a scanner that cuts a way a few pixel more at one side than the other. Other parameters stay the same, like usually the a,b and c parameters (if the zoom and focus for the images is the same).

The inherit checkmark means that this parameter doesnt vary between the images that were captures with that lens setting. If a parameter is inheritied it is forced to be the same for all images. When inherited parameters are optimized they are kept the same for all images, whereas parameters that are not inherited can get values specific for a single picture.

Control Point Tab

Control Points are probably the most important thing when using panorama tools. The Tab consists of two image displays and tab bars to switch images to be editied. The bottom contains a list view where Points can be selected and some fields to edit a selected point. Points can also be selected by clicking or dragging on them in the images. It is possible to zoom out to show the full image.

Adding a control point works by clicking into one image to select a point and then into the other image. If auto add is not set, the points can be moved by clicking at some other place in the images. They are added to the list of control points by pressing the right mouse button. If you press the right mouse button when only one point is slected, the point selection will be aborted. auto add adds the control point as soon as both points have been specified.

Control point creation is influenced by the following checkboxes:

auto fine tune hugin helps you to find the second point by looking for it in a search region (shown by a rectange around the cursor). This might not always work, but usually is reliable, if the image distortions are not too big. Try and play with it.
auto add A control point is automatically added when both points are know. You wont have time to refine the selection before adding the point.
auto estimate Tries to estimate the position of the second point by estimating the translation between the two images. This is very crude and probably only works for single row panoramas created from rectilinear images.

All these flags can be combined. I typically use auto fine tune and auto estimate at the same time. Then hugin usually automatically selects the second point correctly. Well for single row panos that is...

The images are zoomed out, the first click zooms to a temporary 100% view to give you the chance to refine your selection. Note that only the second click will trigger the auto estimate.

The Fine Tune button can be used to find a better position for the point in the right image for already selected point. Contrary to auto fine tune it only looks in a very small area around the point. This function is especially useful if you moved both points by hand, but want to have fine tuned control points.

Press the middle mouse button to pan the image. If you press shift key while paning, both images will move.

This window supports some keyboard shortcuts:

a add a new point that has been selected in both images, and the auto add is switched off.
cursor keys scroll image under the mouse cursor
shift + cursor keys scroll both images at the same time
f fine tune currently selected control point pair. Same as the Fine Tune button
Del Remove currently selected control point.
0 Zoom out to full view.
1 100% view.
Mouse function
Function
control key + mouse movement Scroll image under cursor
shift key + mouse movement Scroll both images
left button Use left mouse button to select new points or drag existing points.
right mouse button Add control point, if auto add is switched off
middle mouse button Scroll image under cursor
shift + middle mouse button Scroll both images

Optimizer Tab

The optimizer moves the images into the right position, so that they can be assembled into a hopefully seamless panorama.

To select what the optimiser should try to estimate, use the Optimize combo box, then click the Optimize Button. If you select the "custom" setting, you can change

Pano Panel

Options concerning the output panorama can be set here.

minb is a content management system that makes it possible to share Moments with others or just log them for your own use.
The data is stored in XML-format and does not require a database. Its design is extremely modular and it supports read-only accounts for sensitive data.
The engine is equally fit to be used as a blog, a personal homepage framework, or a publicly accessible information site concentrating on news or project coordination.
Multiuser support:
As long as no user is registered, you will not be able to add entries and (if you do this manualy) to view them.
Follow the instructions after loading "index.php" and register. The first registered user is a superuser (if you wanna change it, edit ./db/users.db manualy).
Only the superuser should be able to add new users, grant them superuser status and change preferences.
As long as only one user is registered, no author name will be displayed assuming that the site belongs to only one person.
After > 1 users register, the author name will be displayed.
Themes support:
There is a file named "default.css" in "./include/themes". Please feel free to change this theme according to your feeling for design.
After adding a new theme, it will be displayed as an option to choose in the preferences menu.
Do not forget to mail me your theme! I intend to add them to the website of the project.
Modules support:
I added some sample modules in "./include/modules". The modules support is not user friendly yet.
There are some directories in "./include/modules".
Every *.php file in these directories will be used as a module in a separate