Free to guess software for linux

rope is a Python IDE. Python ropes main goal is to provide features like auto-completion, refactorings, content assistance, and outlines.

Refactoring: In recent years refactoring has become a basic task of everyday programing, specially in java community. In the agile programing methodologies, like Extreme Programing, Refactoring is one of the core practices.
Some IDEs support some basic refactorings like PyDev (which uses bicycle repair man). These IDEs have a limited set of refactorings and fail when doing refactorings that need to know the type of objects in the source code (specially for relatively large projects). rope tries to provide a rich set of refactorings. Some of the refactorings require type inferencing which is described later.
Auto Completion: One of the basic features of modern IDEs is the availability of auto-completion. Some Python IDEs have auto-completion support but in a limited form. Since the type of many variables cannot be deduced from simple analysis of the source code. Auto-completing modules names, class names, static methods, class methods, function names and variable names are easy. But auto-completing the methods and attributes of an object is hard. Because the IDE needs to know the type of the object that cannot be achieved easily most of the time in dynamic languages. rope uses Type Inferencing algorithms to solve this problem.
Type Inferencing: One disadvantage of dynamic languages like python is that you cannot know the type of variables by a simple analysis of program source code most of the time. Knowing the type of variables is very essential for providing many of the refactorings and auto-completions. rope will use type inferencing to overcome this problem.

Static type inferencing uses program source code to guess the type of objects. But type inferencing python programs is very hard. There have been some attempts though not very successful (examples: psycho: only str and int types, StarKiller: wasnt released and ShedSkin: good but limited). They where mostly directed at speeding up python programs by transforming its code to other typed languages rather than building IDEs. Such algorithms might be helpful.

There is another approach toward type inferencing. That is the analysis of running programs. This dynamic approach records the types variables are assigned to during the program execution. Although this approach is a lot easier to implement than the alternative, it is limited. Only the parts of the program that are executed are analyzed. If developers write unit tests and use test driven development this approach works very well.

csvdiff is a simple perl script to compare two (comma) seperated files with each other.
Mindless is an SDL-based puzzle game similar to the classic boardgame Mastermind.
The goal of the game is to crack a secret code consisting of four balls which can each be one of eight colors. The players takes turn guess (or do it simultaneously) and the first one to guess his/her code has won.
If both players takes the same number of turns to get the code correct then both has won.
For your help when guess you will for each (incorrect) answer see a combination of one or more black tokens and one or more white tokens on the right side of your last answer.
Each black token means that one of your balls is both of the correct color and location, but you dont know which one, and each white token means that one of your balls is of the correct color but wrong location.
You can play human vs. human, human vs. computer, or computer vs. computer.
Currently each player can either be controlled by a human player, a human with some computer assistance or by the computer. For computer controlled players there exists three different difficulty settings: "Automata", which is the simplest, "Computer" which is the default and "AI" which is the hardest.
Note that the AI setting uses quite a lot CPU cycles and it runs very slowly with more than 8 colors.
Enhancements:
- New gui elements, alternative AIs and "cyborg" mode.

Test::Lazy is a quick and easy way to compose and run tests with useful output.

SYNOPSIS

use Test::Lazy qw/check try/;

check(1 => is => 1);
check(0 => isnt => 1);
check(a => like => qr/[a-zA-Z]/);
check(0 => unlike => qr/a-zA-Z]/);
check(1 => > => 0);
check(0 => < => 1);

try(qw/a/ => eq => a);
try(qw/a/ => ne => b);
try(qw/a/ => is => [a]);
try( < stmt >, < cmpr >, < expected >, [ < msg > ] )

Evaluate < stmt> and compare the result to using < cmpr>. Optionally provide a < msg> to display on failure. If < msg> is not given, then one will be automatically made from < stmt>, < cmpr>, and < expected>.
try will also try to guess what representation is best for the result of the statement, whether that be single value, ARRAY, or HASH. Itll do this based on what is returned by the statement, and the type of < expected>. See `perldoc -m Test::Lazy` for more detail.

Note, if < expected> is an ARRAY or HASH, this function will convert it to its JSON representation before comparison.

try("2 + 2" => == => 5);

# This will produce the following output:

# Failed test 2 + 2 == 5
# at __FILE__ line __LINE__.
# got: 4
# expected: 5
check( < got>, < cmpr>, < expected>, [ < msg> ] )

Compare < got> to < expected> using < cmpr>. Optionally provide a < msg> to display on failure. If < msg> is not given, then one will be automatically made from < got>, < cmpr>, and < expected>.

Note, if < got> or < expected> is an ARRAY or HASH, this function will convert them to their JSON representation before comparison.

check([qw/a b/] => is => [qw/a b c/]);

# This will produce the following output:

# Failed test ["a","b"] is ["a","b","c"]
# at __FILE__ line __LINE__.
# got: ["a","b"]
# expected: ["a","b","c"]
template( ... )

Convenience function for creating a Test::Lazy::Template. All arguments are directly passed to Test::Lazy::Template-new>.

See Test::Lazy::Template for more details.

Returns a new Test::Lazy::Template object.

cmpr

< cmpr> can be one of the following:

ok, not_ok, is, isnt, like, unlike,
, =, lt, gt, le, ge, ==, !=, eq, ne,

BrainCurses project is a clone of the Mastermind game.
Braincurses is a game of cunning. The point of the game is to uncover the secret 4 color code. The secrect code is chosen randomly by the computer then the player has 10 (10 is the default, you can change this now at the command line) tries to guess the correct code.
For each correct color youll get a white peg on the left panel. If you get a correct color in the correct place youll get a red peg on the left panel. The order of the white and red pegs has no correlation to the user guessed pegs. (In fact,
the red pegs will always be put first if there are any.)
The player has 6 different colored pegs to chose from: red, white, blue green, yellow and purple. The game will take those colors in the bottom panel. Important note, to move into the next field press the *enter* key not the spacebar! If you happen to misspell a word it will go back and wait for you to retry and spell it correctly.
Once you have input your four color choices and hit enter it will display colored pegs in the center panel matching your color choices. If any of your guesses are correct there will be on the left panel a corresponding white or red peg.
Enhancements:
- Working on setting up information exchange between Answer and Guess class without a client program, need to figure out how to do that! Once that is done then I can set up comparing the user guesses to the random numbers.
- Getting a lot closer to finishing the "backend" of the project up!
- Got it working for the most part, expect a few bugs that I am trying to iron out.

PekSystray is a system tray dockapp similar to the GNOME notification area applet. But its designed for any window manager supporting.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).
It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- Complete reorganisation of the interface and code.
- Support for an unlimited number of icons.
- This release will only allocate necessary memory.
- It automatically creates another dock when the first one is full.
- --width and --height are available, superceding --vertical and --square.
- --multiple is the default now; it has been removed and --no-multiple added.
- A bug where some applications (grip, castpodder, etc.) had their icons at 0,0 has been fixed.

Log Watcher is a tool for log watching and colorize.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- manual typos
- change defaults in config file
- minor changes needed to build on OpenBSD
- fixed lwatch crashes for some spurious configuration

GameStat project is an easy to use library for querying status from game servers.

GameStat is an easy to use library for querying status from game servers. This is a beta release for v1.1, so there might be bugs.

You can find a list of all the games/masters in games.txt. If no port is given, GameStat will try to guess it for you. If you use a generic protocol you will need to specify a port. The -help parameter will give you a more detailed list of all the parameters available.