Free vs software for linux

Snoopy vs. the Red Baron is an open-source one/two player combat game, available for Mac OS X, Linux, BeOS, QNX and Windows.
The original Snoopy was a tiny game for the Apple Macintosh, with black and white graphics, but already almost all the levels of the new Snoopy/SDL were implemented.
Snoopy could be played by two opponents, sharing a single screen and keyboard, and although it had poor graphics and tough controls, we very much liked to play it.
While we learned programming, we constantly sought for simple, yet interesting projects. If you have ever tried to learn a new language or API, you will have recognized that the simplest way in mastering the stuff is simply reprogramming an existing application, without losing much thought on design and originality.
So my friend reprogrammed Snoopy, in Object Pascal, using SAT, the Sprite Animation Toolkit, on his Classic II. That version of Snoopy features a fully functional AI, network play, but only the first level ( weapons drop).
While he was at it, he also implemented a "missing feature", the bombs, for which there where graphics and sounds in the game, but which could not be thrown.
When I discovered SDL, I recognized that it would be ideal for the job. Running on Windows, Linux, MacOS, BeOS and many other platforms, it is my new toolkit of choice for multimedia programming. It took us several weeks to port Snoopy (besides going to school, but now the work is almost done, with only the finishing touches to be made.
I can only encourage everyone to try SDL; it is really easy and portable (if worked right).

MassSpec::ViewSpectrum::RealVsHypPeptide is a Perl module to view a real mass spectrum on the same graph as a hypothetical spectrum generated by fragmenting a peptide in silico.

SYNOPSIS

use MassSpec::ViewSpectrum::RealVsHypPeptide;
open GRAPHIC, ">mygraphic.png" or die "Unable to open output filen";
binmode GRAPHIC;

my @masses = (78.1,81.1,81.7,85.4,86.8,88.8,89.4,97.6,99.0,99.4,108.7,112.1,129.1,
130.1,132.1,147.7,157.1,158.1,159.1,169.1,171.1,175.1,187.1,229.1,246.2,258.1,
266.0,327.2,328.2,345.2,415.2,426.2,432.2,531.2,559.3,623.4,639.3,643.3,644.4,
645.0,647.5,686.4,687.4,689.4);
my @intensities = (8.7,7.7,7.3,10.5,7.7,7.3,8.4,8.0,9.1,9.1,7.3,29.0,12.6,7.3,8.0,
7.7,11.9,9.8,10.1,7.3,10.5,131.0,9.4,50.3,22.7,44.7,16.8,30.4,18.2,53.1,25.5,
15.7,7.7,14.0,46.8,38.4,7.3,11.5,8.7,7.3,8.7,7.3,24.8,194.2);
my $peptide = "RTSVAR";

my $vs = MassSpec::ViewSpectrum::RealVsHypPeptide->new($peptide, @masses,@intensities);
$vs->set(yaxismultiplier => 1.8); # a sample tweak to adjust the output
$vs->set(title => "BSA-689 -- " . $peptide);

my $output = $vs->plot();
print GRAPHIC $output;
close GRAPHIC;

MassSpec::ViewSpectrum::RealVsHypPeptide - View a real mass spectrum on the same graph as a hypothetical spectrum generated by fragmenting a peptide in silico. The in silico fragmention is performed by generating all of the possible peptides which contain either the amino-terminal or carboxyl-terminal amino acids.

Negative peak intensity values are permitted; this permits the drawing of "pseudospectra" which, for example, illustrate peaks present in one spectrum but missing in another. Note that these negative peaks have no true intensities, but in some cases we assign different heights to illustrate the differences among different hypothetical peaks. In addition, pseudocoloring of both positive and negative peaks is performed to illustrate what type of ion that peak represents. In some cases these ions are labelled explicitly, although in practice it is best to minimize this labelling to avoid excessive clutter.

Video server is a streaming video server which feeds a Java applet/application for display. The updates are rather slow, somewhere in the 10 frames/second range on a PIII. The server is written in Bigloo scheme and C. The client is written in Java.

To bring up the video server you have to do the following.

./vs --channel 25 --sd 12 --input 0

./vs --help
for more options. (This seems broken with the newest version of bigloo .... )

How to bring up a java client to connect to a server:
Insure that video/java is in your classpath, and invoke

java vpanel servername

Konversation project is a user friendly Internet Relay Chat client.
Enhancements:
- A bug that caused left-to-right text contained in lines determined to be right-to-left text to appear reversed has been fixed.
- Whether a line is treated as right-to-left vs. left-to-right text is now determined by the amount of each type of character in the line, improving the user experience in chats involving bi-directional text considerably.
- The "Edit Network" dialog has been refined for clarity and ease of use.
- A warning dialog to prevent accidentally quitting Konversation has been added.
- The Auto Replace list can now be sorted.
- The /media script command now sports improved player recognition, enhanced and easier configurability, the ability to distinguish between audio and video media as well as newly added support for kdetv. New /audio and /video command aliases have been added to expose these new abilities.
- The lower boundary of the default DCC port range has been raised from 1025 to 1026 to avoid conflicts with the commonly blocked Windows RPC port 1025.
- Dismissing an OSD notification by clicking on it will now also cancel the systray notification flash.
- A new configuration file option [OSD]OSDCheckDesktopLock has been added, allowing to manually disable the screensaver check in non-KDE environments that do not support it, causing the OSD not to be displayed.
- A bug that could lead to the "Switch to" sub-menu in the context menus of tabs not to be updated properly upon switching tabs has been fixed.
- A bug that caused the irc setBack DCOP call not to function has been fixed.
- A bug that caused ampersands in the names of tabs not to be displayed and an immediately following character to be used as keyboard accelerator has been fixed.
- A bug that caused ignoring nicknames with [ or ] characters in them to fail has been fixed.
- Command aliases containing regular expression syntax can no longer cause built-in commands not to function.
- A bug that caused the Konversation irc:// protocol handler not to function has been fixed. Its compatibility with systems that do not use the GNU bash shell as default shell has been improved.
- A notable number of code quality improvements suggested by KDEs automated quality control service EBN have been implemented.

GDS2 is a module for quickly creating programs to read and/or write GDS2 files.

Create Method

new - open gds2 file

usage:
my $gds2File = new GDS2(-fileName => "filename.gds2"); ## to read
my $gds2File2 = new GDS2(-fileName => ">filename.gds2"); ## to write

fileNum - file number...

usage:

close - close gds2 file

usage:

$gds2File -> close;
-or-
$gds2File -> close(-markEnd=>1); ## experimental -- some systems have trouble closing files
$gds2File -> close(-pad=>2048); ## experimental -- pad end with s till file size is a
## multiple of number. Note: old reel to reel tapes on Calma
## systems used 2048 byte blocks

High Level Write Methods

printInitLib() - Does all the things needed to start a library, writes HEADER,BGNLIB,LIBNAME,and UNITS records

The default is to create a library with a default unit of 1 micron that has a resolution of 1000. To get this set uUnit to 0.001 (1/1000) and the dbUnit to 1/1000th of a micron (1e-9). usage: $gds2File -> printInitLib(-name => "testlib", ## required -isoDate => 0|1 ## (optional) use ISO 4 digit date 2001 vs 101 -uUnit => real number ## (optional) default is 0.001 -dbUnit => real number ## (optional) default is 1e-9 );

## defaults to current date for library date

note:

remember to close library with printEndlib()
printBgnstr - Does all the things needed to start a structure definition

usage:

$gds2File -> printBgnstr(-name => "nand3" ## writes BGNSTR and STRNAME records
-isoDate => 1|0 ## (optional) use ISO 4 digit date 2001 vs 101
);

note:

remember to close with printEndstr()

printPath - prints a gds2 path
usage:
$gds2File -> printPath(
-layer=>#,
-dataType=>#, ##optional
-pathType=>#,
-width=>#.#,
-unitWidth=>#, ## (optional) directly specify width in data base units (vs -width which is multipled by resolution)
-xy=>@array, ## array of reals
-xyInt=>@array, ## array of internal ints (optional -wks better if you are modifying an existing GDS2 file)
);

note:
layer defaults to 0 if -layer not used
pathType defaults to 0 if -pathType not used
pathType 0 = square end
1 = round end
2 = square - extended 1/2 width
4 = custom plus variable path extension...
width defaults to 0.0 if -width not used
printBoundary - prints a gds2 boundary
usage:
$gds2File -> printBoundary(
-layer=>#,
-dataType=>#,
-xy=>@array, ## array of reals
-xyInt=>@array, ## array of internal ints (optional -wks better if you are modifying an existing GDS2 file)
);

note:
layer defaults to 0 if -layer not used
dataType defaults to 0 if -dataType not used
printSref - prints a gds2 Structure REFerence
usage:
$gds2File -> printSref(
-name=>string, ## Name of structure
-xy=>@array, ## array of reals
-xyInt=>@array, ## array of internal ints (optional -wks better than -xy if you are modifying an existing GDS2 file)
-angle=>#.#, ## (optional) Default is 0.0
-mag=>#.#, ## (optional) Default is 1.0
-reflect=>0|1 ## (optional)
);

note:
best not to specify angle or mag if not needed
printAref - prints a gds2 Array REFerence
usage:
$gds2File -> printAref(
-name=>string, ## Name of structure
-columns=>#, ## Default is 1
-rows=>#, ## Default is 1
-xy=>@array, ## array of reals
-xyInt=>@array, ## array of internal ints (optional -wks better if you are modifying an existing GDS2 file)
-angle=>#.#, ## (optional) Default is 0.0
-mag=>#.#, ## (optional) Default is 1.0
-reflect=>0|1 ## (optional)
);

note:
best not to specify angle or mag if not needed
printText - prints a gds2 Text
usage:
$gds2File -> printText(
-string=>string,
-layer=>#, ## Default is 0
-textType=>#, ## Default is 0
-font=>#, ## 0-3
-top, or -middle, -bottom, ##optional vertical presentation
-left, or -center, or -right, ##optional horizontal presentation
-xy=>@array, ## array of reals
-xyInt=>@array, ## array of internal ints (optional -wks better if you are modifying an existing GDS2 file)
-x=>#.#, ## optional way of passing in x value
-y=>#.#, ## optional way of passing in y value
-angle=>#.#, ## (optional) Default is 0.0
-mag=>#.#, ## (optional) Default is 1.0
-reflect=>#, ## (optional) Default is 0
);

note:

best not to specify reflect, angle or mag if not needed

PvPGN (Player vs Player Gaming Network) is free software that emulates a Blizzard Battle.net server. PvPGN project currently supports all Battle.net games, such as StarCraft, Diablo II, and Warcraft III, and gives you the power to run your own server, manage your own users, run your own tournaments, etc.
Some common uses of a PvPGN server:
- When wanting to have a small community with local users and small ladders (lots of internet cafes do that)
- For people who want to play on a LAN but with Battle.net-like statistics
- For people who find Battle.net too slow or laggy and want to play on a local server with no lag
It puts you as a "System Administrator" in control. Use a PvPGN server to host your own LAN parties or put the server online and on the internet for everyone. You can run tournaments, have your own local competition ladders. The power is in your hands.
Enhancements:
[D2CS/D2DBS]
- added pid files to the confs
- fixed a bug where server could not be (un)installed as a win32 service
- added check and modified the default motd to not have a too big motd that was crashing the clients just after character selection
[VERSIONCHECK]
- added SC/BW 1.13c entries
- added SC/BW 1.13d entries
- added SC/BW 1.13e entries
- added W3 1.20a entries
[SQL]
- reorganized optimized and made more safe the existent codes
- added a new sql layout called "sql2" in config
[MISC]
- fixed security issue where an op of a channel was able to set the topic of any other channel
- added more information to "/finger" display (if issued by an admin)
- added a new command, "/tos" to display the Terms Of Service on request

EncFS provides an encrypted filesystem in user-space. EncFS runs without any special permissions and uses the FUSE library and Linux kernel module to provide the filesystem interface. You can find links to source and binary releases below.

As with most encrypted filesystems, Encfs is meant to provide security against off-line attacks; ie your notebook is stolen, your backups are stolen, etc. The way Encfs works is different from the �loopback� encrypted filesystem support built into the Linux kernel because it works on files at a time, not an entire block device.

You do not need to allocate storage ahead of time for EncFS.

Advantages of a pass-thru system vs an encrypted block device:

An empty EncFS filesystem consists of a couple dozen bytes. With a loopback encrypted filesystem, you allocate a filesystem ahead of time with the size you want.

An EncFS filesystem can be backed-up on a file-by-file basis. A backup program can detect which files have changed, even though it wont be able to decipher the files. This way backups can be made without needing to mount the encrypted filesystem.

An EncFS acts as a translator for filenames and file data and should theoretically be able to pass through to any underlying filesystem. You could have an EncFS filesystem on a DVD, or a DVD mounted remotely and served through a Samba server and mount it locally with EncFS in order to view the encrypted data (your mileage may vary).