Free indian xboard us desi software for linux

Dilbert [US] is a Firefox extension that adds a little button to status bar and when you click it, it will show todays official US Dilbert from www.dilbert.com.

Doesnt work if you have installed Dilbert [CZ]! If you have, uninstall it first!

If you like my extension, please come back and leave me your comments or rating. Thank you.

Get up to date news about India Business from Rediff Business Edition RSS Feed.
Rediff Business widget brings, right on your desktop, the latest news from the bussiness world taken from this Indian news source.
Stay up-to-date with the latest bussiness news.

del.icio.us post is a Firefox extension that allows you to posts current page or link to del.icio.us. Adds an entry to the context menu and a button to the toolbar.

Due to some changes in version 0.4, it is advised to first uninstall any previous versions of this extension before proceeding with the installation.

After installing use View -> Toolbars -> Customize... to add the button to the toolbar.

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).

miniCHESS is a chess game WindowMaker dockapp.

miniCHESS was born out of boredom. I warn you... if your a chess enthusiast and play a lot then please use xboard or some other chess gui.

Even though miniCHESS has that kinda cool factor, it does get hard on the eyes. I like using miniCHESS for games in which Im in no hurry to finish and go on for a couple days.

Sorry but miniCHESS has no save/restore features yet.

Usage:

miniCHESS has a variety of options:

-h help
-t play text game (def = mouse game)
-r more random moves by the engine
-a hard, engine will also think on your time (def = no)
-d n max search depth used by the engine (def = 29)
-c n max time the engine gets to make a move (def = inf)
-T n size of the transposition table (def = 150001)
-C n size of the cache table (def = 18001)
-k #color background color for a checkmated king (def = #ff0000)
-b #color background color for the black pieces (def = #000000)
-f #color foreground color for the black pieces (def = #ffffff)
-1 #color color for the dark squares (def = #c8c365)
-2 #color color for the light squares (def = #77a26d)

If you specify a search depth (-d) to (say) 4 ply, the program will search until all moves have been examined to a depth of 4. If you set a maximum time (-t) per move and also use the depth option, the search will stop at the specified time or the specified depth, whichever comes first.

Gnuchess is a cpu hog while its thinking. Be aware. When the hard option (-a) is specified then the engine thinks all the time and pins your cpu.

Also gnuchess can be a memory hog. Specifying the size of the transposition and cache tables will modify the memory used. See the memory usage excerpt from the gnuchess FAQ below.

White piece colors are the reverse of what is specified for the black pieces.

QiPan project consists of the reference implementation of the CXBoard communication protocol.
QiPan is the reference implementation of a cxboard compliant interface program.
CXBoard is a communication protocol, modeled after XBoard and UCI, used for communication between Chinese Chess engines and interfaces.
Enhancements:
- This release contains new pieces and additional features that make it nicer to use and able to connect to 3rd party engines.

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