Free conversion units software for linux

MOV, MP4 conversion service is final and working version of my script, which I use to convert files supported by ffmpeg to MOV / MP4 format, supported by my iPod Video G5.

Everything was tested to be easy to use (finally, after installation). If You have any problems with it, just let me know - Ill try to help as far as I can.

INSTALLATION:

Just download "avi2mov" script, and save it in /usr/sbin/ directory (You can save it in any directory, but take care later, because i assume, youve saved it in /usr/sbin/ :) ).

After this, You need to set proper permissions, so use chmod:

chmod +x /usr/sbin/avi2mov

Finally, You need to add this converter to Service Menu. Create file

/usr/kde/3.5/share/apps/konqueror/servicemenus/convert-avi-to-mov.desktop

with Kate for example, and copy and paste this code:

[Desktop Action MediaConvertFile]
Exec=/usr/sbin/avi2mov %U
Icon=reload
Name=Convert selected file to mov / mp4 ...
[Desktop Entry]
Actions=MediaConvertFile
Encoding=UTF-8
Icon=reload
ServiceTypes=video/*
ExcludeServiceTypes=kdedevice

Qalculate! is a multi-purpose desktop calculator for GNU/Linux. Qalculate! project is small and simple to use but with much power and versatility underneath.
Features include customizable functions, units, arbitrary precision, plotting, and a user-friendly interface (KDE or GTK+).
Main features:
- Redesigned GUI with history view in the main window
- Display of as-you-type expression parsing and function hints
- Enhanced completion
- Scaling of result display to vertically fit the window
- Nicer history listing
- Enhanced result display with much nicer parentheses
- Meta modes
- 67 new units: bel (B) and neper (Np), information units such as bit and byte, many convenience units (km/h, deciliter, etc), and more.
- Binary prefixes
- Some new variables and functions
- Fixed help display in new yelp
- Fixed compile with cln-1.1.10
- Fixed regressions in simplification
- Fixed f(x) return type analysis (ex. log(x) represents a real number if x represents a positive). This was by accident unused.
- ...and many more bug fixes and enhancements...

UFO: Alien Invasion is a 3D UFO-inspired tactical game.
UFO: ALIEN INVASION is a strategy game featuring tactical combat against hostile alien forces which are about to infiltrate earth at this very moment. You are in command of a small special unit which has been founded to face the alien strike force.
To be successful on the long run, you will also have to have a research team study the aliens and their technologies in order to learn as much as possible about their technology, their goals and the aliens themselves.
UFO: Alien Invasion is heavily inspired by the X-COM series by Mythos and Microprose. The first game of the series, UFO DEFENSE, became a classic and, in our honest opinion, is one of the best games ever made.
UFO: Alien Invasion is neither a sequel nor a remake of UFO DEFENSE - we simply had the urge to create a similar strategy game, which will hopefully be as entertaining as the original was for the players (and for the developers, of course). Join the IRC-Channel at irc.freenode.org named #ufo:ai and contribute to the developing process.
Gameplay:
The game is turn-based. Well, this might sound somewhat old school now, but trust us: turn-based games are fun!
Each member of your squad has a limited number so called "time units" each round, which are consumed when you order the unit to walk, to fire a weapon or to perform any of the other miscellaneous actions. When all your forces are out of time units, the aliens turn starts. In addition to eliminating as many enemies as possible, your mission is to minimize civilian casualties as well as to acquire parts of the advanced alien technology.
Once youve acquired sufficient samples of the unknown technology, your research labs will be able to reproduce the alien weapons and devices in order to use them against their original creators.
Game Engine:
The game engine is based on a heavily modified version of IDs Quake2 Engine. This doesnt imply that UFO: Alien Invasion is a mod or a total conversion at all! No, UFO: AI is a stand-alone game which doesnt require Quake2 or any similar program to run. Our self-developed game engine is featuring up-to-date OpenGL graphics and special effects, increased texture resolution, hardware accelerated clipping of map layers to toggle between floors, a new animation system for player models, a stunning AI and a few other gimmicks.
Multiplayer support:
You can play UFO: ALIEN INVASION with your friends via LAN or Internet. One player takes the role of the human special squad while the other is in control of the alien invaders. Co-op team play with multiple players on both sides is also supported for up to three teams on each side (6 players total).
Enhancements:
- Implemented sv_roundtimelimit cvar to set the maximum time a team has to finish their round in multiplayer.
- Completely rewritten saving and loading system.
- Finished implementation of Flashbang - now Flashbang will disable enemys reactionfire as well.
- Reintroduced employees renaming again.
- Hire menu and Team Select menu now shows Health bar as well.
- Heavily improved chat subsystem for multiplayer as well as Multiplayer Team Selection menu.
- Improved describing weapons and ammo in UFOpedia and other menus, including displaying firemodes.
- Added multiplayer server password protection.

KRioUtil is a KDE program for interfacing with third, fourth, and fifth generation Rio mp3 players. It is meant to be a graphical, more user-friendly version of rioutil.
Main features:
- Upload files to the player
- Delete files from the player
- Download files from the player
- Format one or both memory units on the player
- Create and edit playlists of songs on the player [planned]
- Automatic conversion of recognized formats (ogg, wav,...) [planned]
- Downsample audio files [planned]

OpenInteract2::Conversion::ActionConfig is a Perl module that can convert old action.perl files into INI configurations.

SYNOPSIS

use OpenInteract2::Conversion::ActionConfig;

my $old_config_text = join( , );
print OpenInteract2::Conversion::ActionConfig
->new( $old_config_text )
->convert();

Utility for translating an action table configuration, either in a serialized Perl format or in an actual Perl hashref, into an INI format. It also does a few transformations along the way to make fieldnames/values consistent and ensure there are no deeply nested datastructures.

Test::Unit::TestCase is a unit testing framework base class.

SYNOPSIS

package FooBar;
use base qw(Test::Unit::TestCase);

sub new {
my $self = shift()->SUPER::new(@_);
# your state for fixture here
return $self;
}

sub set_up {
# provide fixture
}
sub tear_down {
# clean up after test
}
sub test_foo {
# test the foo feature
}
sub test_bar {
# test the bar feature
}

(Taken from the JUnit TestCase class documentation)

A test case defines the "fixture" (resources need for testing) to run multiple tests. To define a test case:

implement a subclass of TestCase
define instance variables that store the state of the fixture
initialize the fixture state by overriding set_up()
clean-up after a test by overriding tear_down().

Each test runs in its own fixture so there can be no side effects among test runs. Here is an example:

package MathTest;
use base qw(Test::Unit::TestCase);

sub new {
my $self = shift()->SUPER::new(@_);
$self->{value_1} = 0;
$self->{value_2} = 0;
return $self;
}

sub set_up {
my $self = shift;
$self->{value_1} = 2;
$self->{value_2} = 3;
}

For each test implement a method which interacts with the fixture. Verify the expected results with assertions specified by calling $self->assert() with a boolean value.

sub test_add {
my $self = shift;
my $result = $self->{value_1} + $self->{value_2};
$self->assert($result == 5);
}

Once the methods are defined you can run them. The normal way to do this uses reflection to implement run_test. It dynamically finds and invokes a method. For this the name of the test case has to correspond to the test method to be run. The tests to be run can be collected into a TestSuite. The framework provides different test runners, which can run a test suite and collect the results. A test runner either expects a method suite() as the entry point to get a test to run or it will extract the suite automatically.

If you do not like the rather verbose backtrace that appears when a test fails, you can use the quell_backtrace() method. You will get any message provided, but not the backtrace.