Free xboard us showthread software for linux

XBoard project is a X and Windows graphical chessboard.
XBoard is a graphical chessboard for X that can serve as a user interface for GNU Chess, Crafty, other chess engines, and the Internet Chess Servers.
XBoard can also be used by itself to read and write game files in PGN (portable game notation). WinBoard is a port of XBoard to Microsoft Win32.
You can build xboard on most systems with the following commands.
./configure
make
Enhancements:
- Version 4.2.7 corrects about two dozen bugs in the 4.2.6 release.
- In addition, WinBoard 4.2.7 comes bundled with GNU Chess 5.07 instead of the old 5.02+ version.
- The XBoard and WinBoard source code trees have been merged, so the xboard download now contains the complete source for both.

JNutrix project is a small application written with the Java language. You can search and find more then 130 nutrient values, if they are recorded, of over 5300 foods usually found on the Canadian market ( or 7200+ foods for the U.S.A. version ).
The utilization is quite trivial and make use of the mouse except for entering the name of the food. The name of the food can be search for by entering the first characters or a few sets of characters separated by spaces. Once the food is found and its quantity fixed the food can be cumulate to form a meal, which you can print.
The nutrients can be sorted by clicking on the column header. You can research foods on their contents for three differents nutrients.
The canadian version of the program has a French or English interface as well as a bilingual database, to the user to choose.
The USA version use the latest database: .USDA National Nutrient Database for Standard Reference, Release 19 (2006).
Please note: the database is included only in the binary distributions.
Enhancements:
- First release of the USA version. Use the USDA National Nutrient Database for Standard Reference, Release 19 (2006).

AUSTRUMI is a bootable Live CD Linux distribution with a business card size (50MB). Imagine the ability to boot your favorite Linux distribution whether you are at home, at school or at work.
Main features:
Graphic
- gqview - image browser
- gimp - Image Manipulation Program
- inkscape - SVG editor
Office
- gcalctool - graphical calculator
- abiword - word processor
- gnumeric - spreadsheet editor
- stardict - dictionary
- bluefish - html editor
- gv - a PostScript and PDF previewer
Network
- nmap - network scaner
- ettercap - sniffer/interceptor/logger for LAN
- airsnort - wireless LAN (WLAN) tool
- gspoof - sending tool of TCP/IP packets
- hydra - login cracker
- LinNeighborhood - samba client
- tsclient - frontend for rdesktop and vncviewer
- telnet - telnet client
- gputty - ssh client
- mtr - traceroute
Internet
- firefox - WWW browser
- gftp - ftp client
- skype - free internet telephony
- gitmail - mail client
- apache - Web server
- vsftpd - ftp server
- xmail - mail server
Multimedia
- mplayer - movie player
- simplecdrx - CD creation and audio manipulation program
Games
- ltris - classic Tetris clone
- atomix - logical game
- xboard:phalanx - chess
- gnomine - variation of minesweeper
- gtkballs - clone of well-known DOS game "Lines"
- gsoko - logical game
- icebreaker - clasic Xonix clone
Other
- emelfm - file manager
- rxvt - color VT102 terminal emulator
- htop - task manager
- xproc - system information
- partimage - partition imaging utility
- voarti - firewall/router
- gtkfind - graphical file finding program
- turma - search (and replace) text
- xfdiff4 - graphical diff frontend
- hexedit - shows/modify a file both in ASCII and in hexadecimal
- gcrontab - a crontab editor

Geo:Coder:US 1.00 offers a full-feature facility for geocoding US addresses, that is, estimating the latitude and longitude of any street address or intersection in the United States, using the TIGER/Line data set from the US Census Bureau. Geo:Coder:US uses Geo:TigerLine to parse this data, and DB_File to store a highly compressed distillation of it, and Geo:StreetAddress:US to parse addresses into normalized components suitable for looking up in its database.

You can find a live demo of this code at http://geocoder.us/. The demo.cgi script is included in eg/ directory distributed with this module, along with a whole bunch of other goodies. See Geo:Coder:US:Import for how to build your own Geo:Coder:US database.

Consider using a web service to access this geocoder over the Internet, rather than going to all the trouble of building a database yourself. See eg/soap-client.pl, eg/xmlrpc-client.pl, and eg/rest-client.pl for different examples of working clients for the rpc.geocoder.us geocoder web service.

Major Features:

1. Geo:Coder:US->geocode( $string )
   • Given a string containing a street address or intersection, return a list of specifiers including latitude and longitude for all matching entities in the database. To keep from churning over the entire database, the given address string must contain either a city and state, or a ZIP code (or both), or geocode() will return undef.
   • geocode() will attempt to normalize directional prefixes and suffixes, street types, and state abbreviations, as well as substitute TIGER/Line's idea of the "primary street name", if an alternate street name was provided instead.
   • If geocode() can parse the address, but not find a match in the database, it will return a hashref containing the parsed and normalized address or intersection, but without the "lat" and "long" keys specifying the location. If geocode() cannot even parse the address, it will return undef. Be sure to check for the existence of "lat" and "long" keys in the hashes returned from geocode() before attempting to use the values! This serves to distinguish between addresses that cannot be found versus addresses that are completely unparseable.
   • geocode() attempts to be as forgiving as possible when geocoding an address. If you say "Mission Ave" and all it knows about is "Mission St", then "Mission St" is what you'll get back. If you leave off directional identifiers, geocode() will return address geocoded in all the variants it can find, i.e. both "N Main St" and "S Main St".
   • Don't be surprised if geocoding an intersection returns more than one lat/long pair for a single intersection. If one of the streets curves greatly or doglegs even slightly, this will be the likely outcome.
   • geocode() is probably the method you want to use. See more in the following section on the structure of the returned address and intersection specifiers.
2. Geo:Coder:US->geocode_address( $string )
   • Works exactly like geocode(), but only parses addresses.
3. Geo:Coder:US->geocode_intersection( $string )
   • Works exactly like geocode(), but only parses intersections.
4. Geo:Coder:US->filter_ranges( $spec, @candidates )
   • Filters a list of address specifiers (presumably from the database) against a query specifier, filtering by prefix, type, suffix, or primary name if possible. Returns a list of matching specifiers. filter_ranges() will ignore a filtering step if it would result in no specifiers being returned. You probably won't need to use this.
5. Geo:Coder:US->find_ranges( $address_spec )
   • Given a normalized address specifier, return all the address ranges in the database that appear to cover that address. find_ranges() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_ranges() to find the closest match possible in preference to returning nothing. You probably want to use lookup_ranges() instead, which will call find_ranges() for you.
6. Geo:Coder:US->lookup_ranges( $address_spec, @ranges )
   • Given an address specifier and (optionally) some address ranges from the database, interpolate the street address into the street segment referred to by the address range, and return a latitude and longitude for the given address within each of the given ranges. If @ranges is not given, lookup_ranges() calls find_ranges() with the given address specifier, and uses those returned. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.
7. Geo:Coder:US->find_segments( $intersection_spec )
   • Given a normalized intersection specifier, find all of the street segments in the database matching the two given streets in the given locale or ZIP code. find_segments() ignores prefix, suffix, and type fields in the specifier for search purposes, and then filters against them ex post facto. The intention for find_segments() to find the closest match possible in preference to returning nothing. You probably want to use lookup_intersection() instead, which will call find_segments() for you.
8. Geo:Coder:US->lookup_intersection( $intersection_spec )
   • Given an intersection specifier, return all of the intersections in the database between the two streets specified, plus a latitude and longitude for each intersection. You probably want to just use geocode() instead, which also parses an address string and determines whether it's a proper address or an intersection automatically.

Requirements: Perl

BabyChess is a chess program. You can edit chess games, play chess on the internet, and play locally against engines.
BabyChess is distributed as free software under the terms of the GNU GPL.
Main features:
- Games between humans and/or engines can be played in the match window. XBoard engines are supported.
- The chess position editor lets you edit a chess position, and save it in FEN notation, as used by other chess programs.
- The chess game editor understands PGN notation.
- The game archive editor reads PGN files that contain any number of chess games. It displays a list of all games and lets you edit those games using the game editor.
- The ICS client connects you to an Internet Chess Server and lets you play games against human opponents.
- The "evaluator" of BabyChess is a chess engine that uses its own communication protocol. It is not an XBoard engine. This program is given a FEN position as an argument and analyzes the position. During the thinking process, information about the current best move and more is written.
- The game editor uses the chess evaluator to analyze chess positions.
- Internally, the evaluator uses 64 bit numbers even on 32 bit systems, meaning it is possible to analyze more than 2 billion positions on PCs.
- This program implements an XBoard chess engine. It uses the evaluator as a backend.
- In addition to the standard algebraic notation (SAN). French, German and Dutch notations are supported. Figurine notation is also supported, also the current fonts dont make it look good. New notations can be created.

Pos is an experimental chess program based not on the Shannon algorithm, but on several others. Pos is not a brute force system.

The algorithm used is determined by a genetic (evolutionary) algorithm.

How to run it?

In a terminal

When using the SUN Java 5.0 runtime environment, start it with "java -Xmx384M -jar pos.jar".

Xboard/WinBoard

The program should now fully support xboard/winboard. Start it with commandline "java -Xmx384M -jar pos.jar --io-mode xboard".

For example: xboard -firstChessProgram "java -Xmx384M -jar pos.jar --io-mode xboard"

jose project is a graphical Chess game tool for Linux.
- You can store chess games in a database (backed by MySQL).
- You can view games and edit variations and comments.
- You can play against a "plugged-in" chess engine and use it for analysis.
Main features:
- graphical frontend to MySQL database
- read and write PGN (Portable Game Notations) files
- 2D and 3D view
- edit games, insert comments, variations
- plug-in chess engine for play and analysis; supports both XBoard and UCI protocol.
- Play Fischer Random Chess / Chess 960, or Shuffle Chess
- ECO opening classification
- Position Search
- Create HTML and PDF files.
- Web Servlet interface
3D package installation:
Unzip the package into your existing jose directory.