Free modifier software for linux

Eyefi ImageModifier library is a high-level programming interface for describing and caching a series of image transformations which are applied to source images, typically for display on web pages.
The work process is as follows: you define a chain of transformations, optionally giving it a name, and then apply an image to this chain, which results in a new image. If the image is applied to the chain a second time, a cached image will be used.
Currently, the following filters are defined:
- resize
- border
- apply color mask
- round corners
- cropping (to ratio, to dimension, square)
- color blending
- text (ttf / t1)
- margin
- overlay (for watermarking)
- grayscale
The sub-pages of this project document these different filters, the general ImageModifier API, and integration with the Smarty template engine.
Enhancements:
- A new source mask modifier which can draw masked text over images, and several other minor features and bugfixes.

File::Sort is a Perl module to sort a file or merge sort multiple files.

SYNOPSIS

use File::Sort qw(sort_file);
sort_file({
I => [qw(file_1 file_2)],
o => file_new, k => 5.3,5.5rn, -t => |
});

sort_file(file1, file1.sorted);

This module sorts text files by lines (or records). Comparisons are based on one or more sort keys extracted from each line of input, and are performed lexicographically. By default, if keys are not given, sort regards each input line as a single field. The sort is a merge sort. If you dont like that, feel free to change it.

Options

The following options are available, and are passed in the hash reference passed to the function in the format:

OPTION => VALUE

Where an option can take multiple values (like I, k, and pos), values may be passed via an anonymous array:

OPTION => [VALUE1, VALUE2]

Where the OPTION is a switch, it should be passed a boolean VALUE of 1 or 0.
This interface will always be supported, though a more perlish interface may be offered in the future, as well. This interface is basically a mapping of the command-line options to the Unix sort utility.

I INPUT

Pass in the input file(s). This can be either a single string with the filename, or an array reference containing multiple filename strings.

c

Check that single input fle is ordered as specified by the arguments and the collating sequence of the current locale. No output is produced; only the exit code is affected.

m

Merge only; the input files are assumed to already be sorted.

o OUTPUT

Specify the name of an OUTPUT file to be used instead of the standard output.

u

Unique: Suppresses all but one in each set of lines having equal keys. If used with the c option check that there are no lines with consecutive lines with duplicate keys, in addition to checking that the input file is sorted.

y MAX_SORT_RECORDS

Maximum number of lines (records) read before writing to temp file. Default is 200,000. This may eventually change to be kbytes instead of lines. Lines was easier to implement. Can also specify with MAX_SORT_RECORDS environment variable.

F MAX_SORT_FILES

Maximum number of temp files to be held open at once. Default to 40, as older Windows ports had quite a small limit. Can also specify with MAX_SORT_FILES environment variable. No temp files will be used at all if MAX_SORT_RECORDS is never reached.

D

Send debugging information to STDERR. Behavior subject to change.
The following options override the default ordering rules. When ordering options appear independent of any key field specifications, the requested field ordering rules are applied globally to all sort keys. When attached to a specific key (see k), the specified ordering options override all global ordering options for that key.

d

Specify that only blank characters and alphanumeric characters, according to the current locale setting, are significant in comparisons. d overrides i.

f

Consider all lower-case characters that have upper-case equivalents, according to the current locale setting, to be the upper-case equivalent for the purposes of comparison.

i

Ignores all characters that are non-printable, according to the current locale setting.

n

Does numeric instead of string compare, using whatever perl considers to be a number in numeric comparisons.

r

Reverse the sense of the comparisons.

b

Ignore leading blank characters when determining the starting and ending positions of a restricted sort key. If the b option is specified before the first k option, it is applied to all k options. Otherwise, the b option can be attached indepently to each field_start or field_end option argument (see below).

t STRING

Use STRING as the field separator character; char is not considered to be part of a field (although it can be included in a sort key). Each occurrence of char is significant (for example, delimits an empty field). If t is not specified, blank characters are used as default field separators; each maximal non-empty sequence of blank characters that follows a non-blank character is a field separator.

X STRING

Same as t, but STRING is interpreted as a Perl regular expression instead. Do not escape any characters (/ characters need to be escaped internally, and will be escaped for you).

The string matched by STRING is not included in the fields themselves, unless demanded by perls regex and split semantics (e.g., regexes in parentheses will add that matched expression as an extra field). See perlre and "split" in perlfunc.

R STRING

Record separator, defaults to newline.

k pos1[,pos2]

The keydef argument is a restricted sort key field definition. The format of this definition is:

field_start[.first_char][type][,field_end[.last_char][type]]

where field_start and field_end define a key field restricted to a portion of the line, and type is a modifier from the list of characters b, d, f, i, n, r. The b modifier behaves like the b option, but applies only to the field_start or field_end to which it is attached. The other modifiers behave like the corresponding options, but apply only to the key field to which they are attached; they have this effect if specified with field_start, field_end, or both. If any modifier is attached to a field_start or a field_end, no option applies to either.

Occurrences of the k option are significant in command line order. If no k option is specified, a default sort key of the entire line is used. When there are multiple keys fields, later keys are compared only after all earlier keys compare equal.
Except when the u option is specified, lines that otherwise compare equal are ordered as if none of the options d, f, i, n or k were present (but with r still in effect, if it was specified) and with all bytes in the lines significant to the comparison. The order in which lines that still compare equal are written is unspecified.

pos +pos1 [-pos2]

Similar to k, these are mostly obsolete switches, but some people like them and want to use them. Usage is:

+field_start[.first_char][type] [-field_end[.last_char][type]]

Where field_end in k specified the last position to be included, it specifes the last position to NOT be included. Also, numbers are counted from 0 instead of 1. pos2 must immediately follow corresponding +pos1. The rest should be the same as the k option.

Mixing +pos1 pos2 with k is allowed, but will result in all of the +pos1 pos2 options being ordered AFTER the k options. It is best if you Dont Do That. Pick one and stick with it.

Here are some equivalencies:

pos => +1 -2 -> k => 2,2
pos => +1.1 -1.2 -> k => 2.2,2.2
pos => [+1 -2, +3 -5] -> k => [2,2, 4,5]
pos => [+2, +0b -1] -> k => [3, 1b,1]
pos => +2.1 -2.4 -> k => 3.2,3.4
pos => +2.0 -3.0 -> k => 3.1,4.0

AMX Mod X project is a Half-Life Metamod plugin.
AMX Mod X is a Metamod plugin which allows you to write modifications for Half-Life with the Pawn scripting language.
It provides in-game administration tools, game statistics, server management, and gameplay modifiers. It is based on the original AMX Mod.
AMX Mod X is a versatile Half-Life metamod plugin which is targetted toward server administration.
It has a wide array of scripting capabilities so people can write "plugins", or files which add on to a mods functionality.
Plugins can take form in administrative services (adding new admin commands), statistics generation (StatsX), fun additions (godmode, etc), gameplay changes (WC3, CSDM), and much, much more!
You can also write modules to expand the functionality of AMX Mod X and add to the scripting language.
Enhancements:
- Fixed am46213: New-style menus that had numbered blanks would cause Core to guess the item numbers wrong.
- Fixed am46266: Team name detection did not work for TFC.
- Fixed a bug where get_func_id() would crash on an invalid plugin.
- Added an optional timeout parameter to SQL_MkDbTuple().
- Added a "queuetime" parameter to threaded query handlers, to get the amount of time passed.
- Extended CreateMultiForward() with CreateMultiForwardEx() for filtering old/new plugins from forwards.
- Fixed am45337: SQLX_GetQueryString() did not work with threaded queries.
- Fixed am46350: geoip.inc having faulty a double-inclusion barrier.
- Fixed am46378: unregister_forward() attempted to remove from the wrong hook table.
- Fixed am46336: Vexd_Utilities.inc did not include VexdUM for AMX Mod Compat compiling.
- Fixed am46630: rename_file() could not use relative paths.
- Fixed am45990: amxmod_compat.amxx could conflict and crash hand-ported AMX Mod plugins.
- Fixed am46340: miscstats.amxx could throw an RTE finding the enemy team.
- Fixed am46335: adminchat.amxx color tsay messages were not space aligned. Additionally, the leading space can now be omitted.
- Fixed am46699: stats.amxx for DoD did not display working multi-lingual menus.
- Fixed am46559: miscstats.amxx could throw an RTE if a player got more than 6 kills in a row.
- Fixed am45492: DoDX would overwrite the stats database on load.
- Fixed am46112: WinCSX.exe would not load properly on some versions of Windows.
- Fixed am45362: AMXX Studio did not indent correctly.

Debug::Trace is a Perl extension to trace subroutine calls.

SYNOPSIS

perl -MDebug::Trace=foo,bar yourprogram.pl

Debug::Trace instruments subroutines to provide tracing information upon every call and return.

Using Debug::Trace does not require any changes to your sources. Most often, it will be used from the command line:

perl -MDebug::Trace=foo,bar yourprogram.pl

This will have your subroutines foo() and bar() printing call and return information.

Subroutine names may be fully qualified to denote subroutines in other packages than the default main::.

By default, the trace information is output using the standard warn() function.

MODIFIERS

Modifiers can be inserted in the list of subroutines to change the default behavior of this module. All modifiers can be used in three ways:

:name to enable a specific feature.
:noname to disable a specific feature.
:name(value) to set a feature to a specific value. In general, :name is equivalent to :name(1), while :noname corresponds to :name(0).

The following modifiers are recognized:

:warn

Uses warn() to produce the trace output (default). :nowarn Sends trace output directly to STDERR.

:caller

Add basic call information to the trace message, including from where the routine was called, and by whom. This is enabled by default.

:stacktrace

Add a stack trace (call history).

:maxlen(length)

Truncate the length of the lines of trace information to length characters.

The following modifiers can be used to control the way Data::Dumper prints the values of parameters and return values. See also Data::Dumper.

:indent

Controls the style of indentation. It can be set to 0, 1, 2 or 3. Style 0 spews output without any newlines, indentation, or spaces between list items. :indent(0) is the default.

:useqq

When enabled, uses double quotes for representing string values. Whitespace other than space will be represented as [ntr], "unsafe" characters will be backslashed, and unprintable characters will be output as quoted octal integers. This is the default, use :nouseqq to disable.

:maxdepth(depth)

Can be set to a positive integer that specifies the depth beyond which which we dont print structure contents. The default is 2, which means one level of array/hashes in argument lists and return values is expanded. If you use :nomaxdepth or :maxdepth(0), nested structures are fully expanded.

:quotekeys

Controls wether hash keys are always printed quoted. The default is :noquotekeys.

sortkeys

Controls whether hash keys are dumped in sorted order. The default is :nosortkeys.

Modifiers apply only to the subroutines that follow in the list of arguments.

mcelog decodes machine check events (hardware errors) on x86-64 machines running a 64-bit Linux kernel.
It should be run regularly as a cron job on any x86-64 Linux system (if it is not in the default packages on your x86-64 distribution, please complain to your distributor).
mcelog project can also decode machine check panic messages from console logs.
The latest x86-64 2.6 kernel wont log machine check errors to the kernel log anymore. You need this tool to decode them.
Create the device first.
mknod /dev/mcelog c 10 227
Enhancements:
- Modifier command line options are now allowed after --ascii.
- A decoded address is no longer printed twice for --ascii.
- The SMBIOS anchor scan was fixed to work on more machines and no longer crashes when no anchor is found. --ascii reparsing of mcelog output was fixed.
- NONE entries are not printed in SMBIOS.

PDL::NiceSlice Perl module contains a nicer slicing syntax for PDL.

SYNOPSYS

use PDL::NiceSlice;

$a(1:4) .= 2; # concise syntax for ranges
print $b((0),1:$end); # use variables in the slice expression
$a->xchg(0,1)->(($pos-1)) .= 0; # default method syntax

$idx = long 1, 7, 3, 0; # a piddle of indices
$a(-3:2:2,$idx) += 3; # mix explicit indexing and ranges
$a->clump(1,2)->(0:30); # default method syntax
$a(myfunc(0,$var),1:4)++; # when using functions in slice expressions
# use parentheses around args!

$b = $a(*3); # Add dummy dimension of order 3

# modifiers are specified in a ;-separated trailing block
$a($a!=3;?)++; # short for $a->where($a!=3)++
$a(0:1114;_) .= 0; # short for $a->flat->(0:1114)
$b = $a(0:-1:3;|); # short for $a(0:-1:3)->sever
$n = sequence 3,1,4,1;
$b = $n(;-); # drop all dimensions of size 1 (AKA squeeze)
$b = $n(0,0;-|); # squeeze *and* sever
$c = $a(0,3,0;-); # more compact way of saying $a((0),(3),(0))

# Use with perldl versions < v1.31 (or include these lines in .perldlrc)
perldl> use PDL::NiceSlice;
# next one is required, see below
perldl> $PERLDL::PREPROCESS = &PDL::NiceSlice::perldlpp;
perldl> $a(4:5) .= xvals(2);

Slicing is a basic, extremely common operation, and PDLs slice method would be cumbersome to use in many cases. PDL::NiceSlice rectifies that by incorporating new slicing syntax directly into the language via a perl source filter (see the perlfilter man page). NiceSlice adds no new functionality, only convenient syntax.

NiceSlice is loaded automatically in the perldl shell, but (to avoid conflicts with other modules) must be loaded automatically in standalone perl/PDL scripts (see below). If you prefer not to use a prefilter on your standalone scripts, you can use the slice method in those scripts, rather than the more compact NiceSlice constructs.

Dynpet is a free open source software programmed in Ruby similar to the Tamigotchi key chain. The objective of the game is to not let the pet die and take care of it. See the Roadmap for information on what Dynpet will be in the future.

For more information on playing and downloading, please visit Manual and Download page. Dynpets goal is to make this game entertaining and fun while providing a good experience in general (not prone to crash, extremely buggy, extremely slow, etc)

Installation:

Since this program is programmed in Ruby, you will need a ruby interpreter to get the game working.

You are not required to download any dependencies for this program other than the ruby interpreter.

Playing the Game:

For more in-depth information, please visit http://dynpet.sourceforge.net/user.html
To play this game, all you need is to run this program in the command line or terminal. (If youre on window, you can just click on it)

If you dont have any pet file to load, you will need to create a new pet. You can do that when the menu start up or the game start up by
typing "creation" without quote. Once youre there, you will choose a name, name your file, and choose a gender. When youre done with that,
you are taken directly to the game.

The game itself is very simple. They show you the statistics of your pet when it is beginning than it goes asking you questions on what you would like to do.
You will have stats like hunger, health, and love with their maximum points they can have like health_limit, hunger_limit, love_limit.

We also have stat like needs and wants which act as a bonus modifier. We have experience and exp_limit to show how many experience points needed to level the pet.

You either type "feed", "play", "groom" , or "end". Anything else you typed does nothing.

The feed increase the hunger stat, play increase the love stat, and groom increase the health stat.

End just mean that, end the game. It doesnt exit the program entirely though.

Once you enter feed, play, groom, if you enter that again, it will do nothing because they arent finished. Once they are finished, they will tell you in a message.
That message will mean that your pets stats went up(THEY NEVER GO DOWN). You can enter it again once the event is over.

There is a system that deduct points from your pets stat. Randomly they choose which stats to deduct, which number, and which time.
They are tied in the bonus and experience system which only happen once every 20 time that the system deducts points.

You can see they are counting down to 0 turns which alway start with 19 and end with 0.

Once the experience system is triggered, they spring into action. If any stats happens to be over the limits, they deduct points until it equal the limit.

They add it to the experience points. The bonus system also tiggered. If they are over the needs stat, than you gain points depending on the needs number.

If you are over the want stat, you gain more points. In contrast, when you are under, you only lose points on needs, not wants stat.

In the event that one of your love, health, and hunger stat managed to be 0 or lower( The pet died), the game will revert to the state of when you first created the pet.

Simple UDP proxy/pipe is an advanced UDP proxy/datapipe/packets forwarder and modifier with multiple functions.

Multiple clients allowed (you can connect many clients you want to this proxy), creation of ACP files (tcpdump capture files, just like a sniffer), packets forwarding (chat style, each packet is forwarded to all the other clients and server connected), packets injection (the tool opens a specific UDP port where you can send your customized packets which will be sent to the server), hexadecimal visualization and plugins support for the modification and visualization of the packets with some example plugins already included (Zdaemon huffman, Doom huffman, Half-life decoding and one for the replacement of the text strings).

Plugins (which work on both Windows and Linux) are very basic to create and use, just take a look at example_sudp.c for more informations.